Why would a shop need “Audit log”?
Planned C0358
For Audit log (SEC-0001) the catalog says: Append-only log of sensitive actions with user, device, time. It is core priority within “” and sits in both Lite and Pro. It is not a feature yet.
Hardware, platform and safety
Questions about the Security, Audit & Privacy module of the catalog.
Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made
Planned C0358
For Audit log (SEC-0001) the catalog says: Append-only log of sensitive actions with user, device, time. It is core priority within “” and sits in both Lite and Pro. It is not a feature yet.
Planned C0359
Audit on permission changes (SEC-0008) is assigned to both Lite and Pro. Section “”: Audit-log entry (user, device, time, before/after values) written for permission changes. Tier names are catalog labels, and no prices are published.
Planned C0360
Secrets in OS keystore depends on Audit log. By itself it covers: Windows DPAPI/Credential Locker, Android Keystore, iOS Keychain. These are catalog links between planned items in “”.
Planned C0361
Offline license verification depends on Audit log. By itself it covers: Signature verification without phone-home. These are catalog links between planned items in “”.