Identity and access
Who should have access, how to prove it, and how to handle the identity weaknesses attackers use most.
The packs behind these answers
How do we…
Methods: how a thing is done well.
- How do we run an access review that isn't rubber-stamped?
- How often do we review access, and who does the reviewing?
- How do we decide which systems belong in the review?
- How do we review access to a system a supplier runs for us?
- How do we review privileged and administrator access?
- How do we prove to an auditor that the review really happened?
- How do we roll out phishing-resistant MFA, and in what order?
- How do we set up a new starter's access before their first day?
- How do we build role-based access profiles without a role-mining project?
- How do we control administrator access without a PAM platform?
- How do we find and control service accounts nobody owns?
When do we…
Triggers and timing: when something has to happen.
Who decides…
Authority: who may approve, accept or act.
If…, then how…
Situations: something has happened, what now.
- If a reviewer misses the deadline, then what?
- If the review finds leavers who still have access, then what?
- If someone calls the help desk asking for an MFA reset, then how do we verify who they are?
- If a session token was exposed, is a password reset enough?
- If some SaaS accounts sit outside SSO, then how do we find and close the gaps?
- If a contractor's engagement ends without HR knowing, then how do we catch it?
- If an administrator uses their admin account for email or browsing, then what?
Other categories
- Vulnerabilities and exposure19 questions
- Risk, exceptions and acceptance19 questions
- Policy and governance10 questions
- Board and executive reporting16 questions
- Third parties and suppliers20 questions
- Incidents and regulatory notification25 questions
- Resilience and recovery18 questions
- Regulation, audit and certification26 questions
- Data and AI20 questions
- Leading the security function35 questions