accountability
Being able to tie every action on a system to the one person who did it, so they can be held responsible.
In more detail
Accountability depends on unique identities plus reliable records such as logs and audit trails. It is the last step of IAAA and supports investigations, audits and discipline. It breaks as soon as several people share one account, because the log then names an account rather than a person.
Example
09:17:20 deploy? authz allowed as root: /usr/bin/rm -rf /srv/app/releasesRelated terms
- IAAA — The four steps of every access decision: identification, authentication, authorisation and accountability.
- accounting — Recording what users and systems do, such as logins, commands and resources used, so the activity can be reviewed later.
- shared account — One login used by several people, such as a team deploy account whose password everybody knows.
- auth.log — The Linux log file that records logins, SSH sessions, sudo use and other authentication events.
Taught in
- CIA Triad, Non-Repudiation & Parkerian Hexad — Cybersecurity Fundamentals, GRC & Cryptography
- Security Governance vs Security Management — Cybersecurity Fundamentals, GRC & Cryptography
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Privacy Principles, GDPR Subject Rights & Minimization — Cybersecurity Fundamentals, GRC & Cryptography
- Enterprise Risk Registers & Treatment Plans — Cybersecurity Fundamentals, GRC & Cryptography