CAIRNCYBER ADVISORY, homeContact

Services

Security standards & governance

Your security standards have fallen behind the technology, adoption is inconsistent, and an upcoming audit or regulatory requirement is bringing the gaps into focus.

For banks, asset managers, custodians, the fintechs that sell to them and the law firms that advise them.

Security standards fail for one of two reasons. Either they are written for the auditor and ignored by delivery, or they are written by engineers and cannot be evidenced when the regulator asks. The work is producing a set that does both.

The engagement pattern

Start from what is actually being built. Standards written in isolation from current delivery describe a firm that does not exist.

Engage stakeholders deliberately and widely. I have run a full standards overhaul involving more than fifty stakeholders across risk, audit, legal and technology. The point of that effort is adoption after I have gone.

Map once, report many times. NIST CSF v2, DORA and ISO 27001 overlap heavily. Structuring the control set so a single piece of evidence satisfies several obligations is what separates a sustainable programme from a permanent reporting burden.

Regulatory context

Most of my work has been in financial services, where DORA, the PRA’s outsourcing and third-party expectations (SS2/21) and the FCA and PRA operational resilience rules set the pace. For AI, add model risk management (PRA SS1/23), ISO 42001 for a management system that can be certified, and the EU AI Act where a system’s output is used in the EU. The same patterns apply in any sector where an external body can compel you to demonstrate your controls rather than describe them.

Start a conversation

Send me an outline of the problem and your timescale. I normally reply within one working day and will tell you directly whether I think I can help.