EFQM and Strategy Assessors

Case: Annex A controls that actually fit

A small software company adopted ISO 27001 and, terrified of missing something, implemented nearly every Annex A control at full strength. Two things happened: developers drowned in process, and shipping slowed to a crawl. Security had become the enemy of the business it was meant to protect.

Annex A is a menu, not a mandate. The Statement of Applicability exists precisely so you can justify what you apply and what you don't, proportionate to your actual risks. Applying everything maximally isn't rigour — it's a failure to do the risk analysis that decides what matters.

We went back to the risks. For a cloud software firm, source-code integrity, access management and secure development mattered enormously; certain physical and legacy controls barely applied. We right-sized accordingly, documented the reasoning, and handed developers controls that fit how they actually worked.

Certification held. Velocity recovered. Security improved, because controls people can live with get used. Proportion, not maximalism, is what the standard actually asks for.