SwarmPT · engineer standard
Who is allowed to point this at your network.
Two things, not one
A credential is not a permission.
This distinction matters enough that we built the platform so the two can never be confused. SA-APEX is a public professional credential, earned by anyone qualified, including people who work for firms that compete with us. SwarmPT Lead Authorization is an internal Security Arsenal permission, granted to an employee, scoped to specific client work, monitored and revocable.
| Artifact | What it means | Authorizes production SwarmPT? |
|---|---|---|
| Security AI Engineering course completion | The person completed the AI safety and engineering curriculum. | No |
| Exam eligibility | Prerequisites and readiness conditions were verified. | No |
| SA-APEX certification | The person passed the independent performance assessment. | No, not by itself |
| SwarmPT Lead Authorization | Security Arsenal approved an employee for controlled client use. | Yes — within assigned scopes, while active |
Critical control
Course completion is never marketed as certification, and no platform status is allowed to look like permission to operate on a client. Authorization is explicit, revocable, time-bound and auditable — and it lives in a separate service from the public credential registry so a change to one cannot silently alter the other.
The internal bar
What an engineer clears before they direct a live engagement.
- Included:An active SA-APEX credential — the public, independently assessed standard.
- Included:Company-specific qualification on our own controls, client-scope rules and incident readiness.
- Included:Supervised operation on real engagements before independent operation is granted.
- Included:A scoped authorization naming which clients and which engagement types it covers, with a start and an end.
- Included:Continuous monitoring, with the authorization revocable independently of the public credential.
Revoking an internal authorization does not touch someone’s public credential, and losing a public credential ends the internal authorization immediately. They move independently in one direction and dependently in the other, on purpose.
The boundary
Public standard, private product.
| The public SA-APEX program | Security Arsenal SwarmPT |
|---|---|
| Vendor-neutral competencies and performance criteria. | Security Arsenal proprietary software, workflows, agents, prompts, orchestration and operations. |
| The candidate builds an original AI security application, or uses a generic controlled assessment framework. | Authorized employees use the actual product, and only after internal qualification. |
| Open to qualified practitioners, including people who work for other security firms. | Never licensed or disclosed through the public certification. |
| The credential proves professional readiness. It conveys no product entitlement. | Access is an employment-based, scoped, monitored, revocable company authorization. |
Nothing in the certification teaches, distributes, simulates in detail or exposes SwarmPT implementation. Candidates build their own tooling from a bare Kali server and an API token — which is a harder assessment than handing them ours would be, and happens to make the boundary trivial to hold.
Why this exists at all
The engineer is the operator, not a signature at the bottom.
The swarm was built by the person who runs the engagements, against one criterion: can it do this better than me? If not, make it better. It is a force multiplier for an engineer who already knows what they are looking for — driven live, not launched and collected.
That only works if the person driving it can do the work themselves. An operator who cannot read the code, cannot write the exploit and cannot tell a real boundary crossing from a confident paragraph will produce something that looks like a test and is not one.
Master the attack before commanding the swarm. That is the whole standard, and SA-APEX is how it gets measured.
Buying a test rather than sitting an exam? Get a real price.