The decision
What should this practitioner learn and demonstrate next?
The planner creates a six-week sequence by role. It combines physical security fundamentals, AI governance, evaluation, communication, and a portfolio artifact so learning can be reviewed through actual work.
Current or target role family.
A six-week development sequence and official-resource route.
The practitioner and manager agreeing on evidence of progress.
Competency model
Build across four connected capabilities.
Threat, risk, systems, incidents, evidence, response, and continuity.
Use cases, data, model limits, evaluation, automation bias, and uncertainty.
Policy, privacy, accountability, testing, monitoring, change control, and stop conditions.
Requirements, business cases, executive communication, training, and cross-functional decisions.
Working tool
Generate the six-week plan
Select the role that best matches the work to be performed, not simply the current job title.
Official certification and professional-development resources are opened separately. Verify current eligibility, fees, requirements, and renewal rules with the issuing organization.
Evidence of capability
End the cycle with something reviewable.
A sanitized alarm-triage test with human decisions, errors, and stop conditions.
An AI use-case register with owners, data boundaries, controls, and pilot gates.
An architecture and acceptance plan covering standards, failure, recovery, and evidence.
A vendor-neutral requirements brief with assumptions, alternatives, and evaluation method.
A synthetic incident workflow, terminology map, and reflective after-action review.
A one-page explanation of where AI helps, where it stops, and who remains accountable.
Method and limits
A development scaffold, not a credential assessment.
The role plans are deterministic examples. They do not evaluate experience, certify competence, guarantee employment, or replace current requirements from ASIS, SIA, employers, regulators, or credential issuers.