CyberKit

TCC Database

Also called TCC.db, Transparency, Consent, and Control, privacy permissions.

macOS privacy database recording which apps were granted sensitive access.

What it is

Transparency, Consent, and Control (TCC) governs app access to protected resources (camera, microphone, full disk, location, contacts, automation), and records each decision in SQLite TCC.db files (a system store plus a per-user one under ~/Library/Application Support/com.apple.TCC). Each row notes the client, the resource, and whether access was allowed.

Where it lives

Per-user: ~/Library/Application Support/com.apple.TCC/TCC.db; system-wide: /Library/Application Support/com.apple.TCC/TCC.db (macOS)

Why it matters

The database shows exactly which applications obtained sensitive permissions and when, helping an examiner spot malware that talked the user into granting full-disk or accessibility access. Unexpected grants (or evidence of TCC manipulation) are strong indicators of compromise on macOS.

In practice

A TCC.db entry granting an unknown app Accessibility access explained how the malware was able to log keystrokes and control the UI.

What to look for

  • Apps granted Full Disk Access, screen recording or accessibility.
  • Grants for apps the user does not recognize.
  • Changes to TCC.db outside normal prompts.

Common mistake

Missing it during triage. Granted permissions tell you what a malicious app could reach.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Mobile Verification Toolkit Open source

    Checks iOS and Android backups and file systems for signs of known spyware.

  • iLEAPP Open source

    Parses iOS extractions into readable reports of apps, messages and system logs.

Read next

Sources