EU AI Act requirements in the library
Seeded and linked to controls, with overlap to ISO 42001 counted once.
The EU AI Act sets duties by the risk an AI system carries, and the work to prove it is extensive. Purplecop has the Act's requirements in the library beside ISO 42001, so the governance you build for one counts toward the other.
What changes for an AI provider or deployer on Purplecop.
The Act and the standard on one library.
Seeded and linked to controls, with overlap to ISO 42001 counted once.
A control shared across frameworks is created once in the library, not rebuilt for each one. The work you do for the EU AI Act counts toward everything else you hold.
Acceptable use, model lifecycle and oversight policies to start from, tagged to the AI frameworks they serve.
Purplecop AIMS records each model with its owner, its purpose and its risk classification.
Model risk is scored on impact and autonomy, not likelihood alone, so an agent that acts by itself is weighed differently.
Model inventory, AI risk, AI controls and the evidence that an AI system is governed, mapped to ISO 42001, the NIST AI RMF and the EU AI Act.
The team that runs your engagement works inside the same system, so the work they do stays with you.
Also on the platform
Onboard, assess, score and continuously monitor every vendor in one workflow.
Asset discovery, network monitoring and the audit log in one module, so every asset’s data lives in one place.
Live phishing campaigns with per-user risk scores, run entirely in-house.
Role-based security awareness training for every employee, tracked to completion.
A directory of the people in scope for training, policy sign-off and access reviews.
Role-based access control with granular permissions, on a least-privilege model.
It can, where an AI system is placed on the EU market or its output is used in the EU. Your scope is something we work through with you.
Purplecop records each system's risk classification; deciding the classification remains a human judgement, supported by our practitioners.
They overlap. Shared controls are created once and count for both.
It scales with how much you integrate: the more connectors you turn on, the more evidence is collected automatically, saving up to 70% of the time you used to spend preparing for each conformity check.
We will walk the product against your scope and show you what runs on day one and what needs configuring.