Detectionmediumexperimental

File Access Of Signal Desktop Sensitive Data

Detects access to Signal Desktop's sensitive data files: db.sqlite and config.json. The db.sqlite file in Signal Desktop stores all locally saved messages in an encrypted SQLite database, while the config.json contains the decryption key needed to access that data. Since the key is stored in plain text, a threat actor who gains access to both files can decrypt and read sensitive messages without needing the users credentials. Currently the rule only covers the default Signal installation path in AppData\Roaming. Signal Portable installations may use different paths based on user configuration. Additional paths can be added to the selection as needed.

Convert In Phoenix Studio

Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.

Launch
Andreas Braathen (mnemonic.io)Created Sun Oct 195d6c375a-18ae-4952-b4f6-8b803f6c8555windows
Log Source
Windowssecurity
ProductWindows← raw: windows
Servicesecurity← raw: security

Definition

Requirements: System Access Control List (SACL) policy with attributes List folder/read data on Objects

Detection Logic
Detection Logic2 selectors
detection:
    selection:
        EventID: 4663
        ObjectType: 'File'
        ObjectName|contains: '\AppData\Roaming\Signal\'
        ObjectName|endswith:
            - '\config.json'
            - '\db.sqlite'
    filter_main_signal:
        ProcessName|endswith:
            - '\signal-portable.exe'
            - '\signal.exe'
    condition: selection and not 1 of filter_main_*
False Positives

Unlikely, but possible from AV or backup software accessing the files.

Rule Metadata
Rule ID
5d6c375a-18ae-4952-b4f6-8b803f6c8555
Status
experimental
Level
medium
Type
Detection
Created
Sun Oct 19
Path
rules/windows/builtin/security/win_security_signal_sensitive_config_access.yml
Raw Tags
attack.credential-accessattack.t1003
View on GitHub