Define the work.
Identify the systems, risks, and responsibilities your team owns. Match those responsibilities to a published certification syllabus rather than choosing by title alone.
For employers & security teamsPlan development
Plan development
around the work.
Use a clear certification scope and a verifiable credential record to inform professional development, capability conversations, and assessment planning.
Discuss your team’s direction
The workforce perspectiveStart with responsibilities.
Start with responsibilities.
Then choose the credential.
Certification is one part of evaluating capability.
Use it alongside experience and work evidence.
Plan the preparation.
Discuss existing experience, identify gaps, and allow time for focused study. Each professional still submits an individual application and receives an admissions decision.
Verify the outcome.
Use the public credential record to check the holder, certification, validity dates, and current status. Keep the verification link with your professional development records.
A working template for managersTurn responsibilities
Turn responsibilities
into a development brief.
Refine this template against the selected syllabus
and your team’s actual responsibilities.
| Area of responsibility | A task worth discussing | Evidence to look for | Related discipline |
|---|---|---|---|
| AI engineering & security | Explain how retrieved content and tool permissions affect an assistant’s risk. | A threat model, an evaluation plan, and a reasoned control choice. | AI Security ↗ |
| Application security | Scope an authorization assessment and communicate a reproducible finding. | Authorized test evidence, impact analysis, and a remediation check. | Offensive Security ↗ |
| Audit & assurance | Evaluate how a control operates and trace the evidence supporting a conclusion. | Evidence requests, sampling context, and a scoped observation. | Governance ↗ |
Before you nominate a colleague
Agree on the relevant scope, the preparation time available, and the evidence the professional can present. A team plan coordinates development; each applicant still receives an individual admissions decision.
Three areas of practiceDifferent functions.
Find role-aligned credentials Different functions.
A shared language of evidence.
Professional discipline
AI Security
Model risk, AI attack surfaces, agent behavior, and generative AI controls.
Professional disciplineOffensive Security
Penetration testing, application assessment, red team operations, and exploitation.
Professional disciplineGovernance & Assurance
Information security controls, AI management systems, risk, and audit evidence.
What to confirm.
- The credential holder’s name matches the professional.
- The certification scope is relevant to the work.
- The public ID resolves to the expected issuer record.
- The status is valid, and the expiry date has not passed.
- The credential is considered alongside practical evidence and experience.
A focused conversationYour team.
Your team.
Your objectives.
Tell us which roles and disciplines matter to your organization. We can discuss the certification scope and the application process before you make a plan.
Every applicant is reviewed individually. An organizational enquiry does not reserve admission or guarantee certification.