Plain language
If we can’t explain a risk in a sentence, we don’t understand it well enough yet. You won’t need a glossary to read our work.
Approach
Four steps, with a principal from the first conversation to the last report.
The four steps
We start with the business: what you do, what you hold, who relies on you and what your obligations are. The standard comes second.
We measure where you stand against the standard or framework that applies, and rank the gaps by risk. You get it in writing.
We write the policies, set up the controls and stand up the governance with the people who will run them. When we leave, it is yours.
Someone who did not build it audits the result against the standard. We report to the board, and prepare you for certification if you want it.
One management system
ISO/IEC 27001 and ISO/IEC 42001 are organised into the same seven clauses. An organisation that runs one already has the frame for the other.
So we build one management system that carries both: one risk register, one audit program, one report to the board. There is one system to run, and nothing falls between two teams.
ISO/IEC 27001Information security
ISO/IEC 42001Artificial intelligence
Annex A: security controls
Annex A: AI controls
What to expect
If we can’t explain a risk in a sentence, we don’t understand it well enough yet. You won’t need a glossary to read our work.
A firm of twenty and a national operator need different answers to the same standard. We build what fits, and nothing you won’t use.
Every finding points to what we saw. Every recommendation says which risk it treats.
We build with your people, so the system keeps working after we have gone.
Tell us what you’re working on. We’ll tell you whether we can help, and how.