Telecoms insight
What Ofcom's Telecoms Access Review 2026-31 means for ISP compliance evidence
The Telecoms Access Review is not an ISO 27001 rule, but it changes the operating environment for ISPs, altnets, wholesale buyers, and infrastructure users. That makes clean evidence ownership more important.
7 min readISP, altnet, wholesale telecoms, and TSA compliance teams
- TAR 2026-31 is about fixed telecoms access, pricing, competition, and migration; it does not directly mandate ISO 27001.
- More wholesale access, supplier dependency, and migration work can create new evidence pressure for ISPs and altnets.
Read What Ofcom's Telecoms Access Review 2026-31 means for ISP compliance evidenceIncident evidence insight
Palo Alto zero-days are an ISO 27001 evidence problem, not just a patching problem
When a perimeter firewall zero-day is exploited before every team has patched, the compliance question becomes practical: can you prove exposure, ownership, mitigation, customer impact, and management review quickly enough?
7 min readMSPs, ISPs, SaaS security teams, and ISO 27001 owners
- A firewall zero-day response is not only a technical patching exercise; it is also an evidence, ownership, and assurance exercise.
- The useful ISO 27001 record is a short, time-bound evidence pack: assets, exposure decision, mitigation, change record, investigation notes, customer impact, and review trail.
Read Palo Alto zero-days are an ISO 27001 evidence problem, not just a patching problemMSP guide
ISO 27001 for MSPs
ISO 27001 for MSPs is most valuable when it reduces the overhead of recurring client security reviews, supplier evidence requests, and internal approval work across service delivery and operations.
7 min readManaged service providers, service delivery leads, CTOs, and assurance owners
- ISO 27001 for MSPs should make recurring client assurance work easier to answer, not just easier to describe.
- MSPs usually feel the pain where service delivery, supplier evidence, and internal controls overlap.
Read ISO 27001 for MSPsSaaS guide
ISO 27001 for SaaS companies
ISO 27001 for SaaS companies is usually less about writing more policies and more about making security reviews, supplier assurance, approvals, and evidence easier to run as a live workflow.
7 min readSaaS founders, IT managers, security leads, and compliance owners
- ISO 27001 for SaaS companies usually becomes painful where buyer diligence and internal coordination meet.
- The work is easier when SoA decisions, risks, approvals, evidence, and supplier follow-up stay connected.
Read ISO 27001 for SaaS companiesSoA guide
How to write a Statement of Applicability
To write a Statement of Applicability properly, start with scope, risk treatment, and real control ownership. A good SoA explains why a control applies, how it is handled, and where the evidence sits.
8 min readISO 27001 owners, consultants, IT leads, and teams drafting or cleaning up an SoA
- A good Statement of Applicability is a management document, not a control-number spreadsheet.
- The SoA should explain applicability, implementation status, and supporting evidence clearly.
Read How to write a Statement of ApplicabilityStandards update
ISO/IEC 27001:2022 vs 2013: what actually changed
The 2022 edition did more than tidy up wording. It updated the main body of the standard, aligned Annex A to ISO/IEC 27002:2022, and changed how many teams need to review their ISMS.
6 min readSecurity leads, IT managers, compliance owners, and teams updating older ISO/IEC 27001 material
- The 2022 edition is the current core version of the standard, published on 25 October 2022.
- The biggest practical changes are in Annex A, but the main body of the standard changed too.
Read ISO/IEC 27001:2022 vs 2013: what actually changedQuestionnaires
How SaaS teams handle security questionnaires
SaaS teams handle security questionnaires best when they stop treating each one as a fresh project. The repeatable answer is a live workflow for controls, evidence, suppliers, approvals, and review notes.
7 min readSaaS IT managers, security leads, founders, and commercial teams under buyer-diligence pressure
- Security questionnaires usually expose workflow gaps more than technical gaps.
- The best answer is to reuse a live control and evidence system instead of rebuilding from memory.
Read How SaaS teams handle security questionnairesAnnex A
Annex A in ISO/IEC 27001:2022: from 114 controls to 93
The Annex A refresh is the most visible change in ISO/IEC 27001:2022. The control set was reduced from 114 to 93 and regrouped into four themes that are easier to read but not necessarily lighter to implement.
6 min readISO/IEC 27001 practitioners, internal owners, consultants, and teams reviewing a Statement of Applicability
- Annex A moved from 14 groups to four themes: organizational, people, physical, and technological.
- The new structure is easier to navigate, but it still expects a serious review of applicability and evidence.
Read Annex A in ISO/IEC 27001:2022: from 114 controls to 93Telecoms guide
Telecoms Security Act checklist for UK operators
A Telecoms Security Act checklist for UK operators should cover duties, evidence ownership, supplier oversight, access control, reviews, and the operating trail behind the next request for proof.
7 min readUK telecoms, broadband, ISP, altnet, and connectivity teams
- A useful Telecoms Security Act checklist is operational, not just documentary.
- Most friction comes from evidence ownership, supplier follow-up, and review cadence.
Read Telecoms Security Act checklist for UK operatorsNew controls
The 11 new Annex A controls in ISO/IEC 27001:2022
The 2022 revision introduced 11 new controls. They are a useful signal of where ISO/IEC 27001 now expects more explicit thinking about cloud, data handling, monitoring, resilience, and secure engineering.
7 min readSecurity managers, IT leads, developers, and anyone updating a 2013-era control set
- The 11 new controls are not random additions. They point to areas where modern operating practice has moved.
- Several of the new controls formalize things many teams already do informally.
Read The 11 new Annex A controls in ISO/IEC 27001:2022Practical review
How to review a 2013-era ISMS against ISO/IEC 27001:2022
If your documents, SoA, or audit material still feel rooted in the 2013 structure, the review needs to go deeper than swapping control numbers. A cleaner review starts with the management system and then works back through Annex A and evidence.
6 min readOrganizations updating an older ISMS, consultants, and internal owners cleaning up inherited ISO/IEC 27001 material
- Start with the live ISMS and not just the control register.
- Review clauses, SoA logic, and evidence together rather than in isolation.
Read How to review a 2013-era ISMS against ISO/IEC 27001:2022