| Topic | Integration between technical testing and the management system |
| Reference standard | ISO/IEC 27001 — information security management system |
| Symptom | The same vulnerabilities reappear in every annual test |
| Cause | The technical report does not go into the risk analysis or the treatment plan |
| Correction | Each finding becomes a risk with an owner, a deadline and verification |
In almost every company we support, the security management system and the technical tests are contracted separately: different supplier, different budget, different meeting.
And so, the technical finding dies in a PDF.
The pattern is always the same
A penetration test is contracted, a report arrives with vulnerabilities ranked by criticality, the three noisiest are fixed and the file is stored away. The management system —which is what should record the risk, assign an owner and verify closure— never learns that the report existed.
A year later the test is repeated and the same vulnerabilities appear. Not because no one fixed them, but because no one fixed the cause: the process that produces them remains the same.
What changes when they are connected
- Each technical finding enters the risk analysis with an owner and a date, not as an annex.
- The treatment plan stops being a list of good intentions and comes to have evidence of closure.
- The next test measures real progress, because it compares against something.
- Management stops seeing security as a recurring expense and starts seeing it as an indicator that moves.
It is not more budget
It is the same money, connected: the technical test feeds the system, and the system tells the test where to look the following year.
If your last pentesting report is stored in a folder and not in your risk matrix, there is work for AXONA’s CYBER line.
Frequently asked questions
Why do the same vulnerabilities reappear every year?
Because the test report is filed away instead of becoming inputs to the risk analysis. Without an owner, a deadline and subsequent verification, correction depends on someone’s memory.
Is a pentest valid as evidence for ISO 27001?
It is valid as an input, not as a substitute. The standard requires risk management: the report feeds that management, but the evidence is the treatment of the finding and its verification.
Who should receive the technical report?
In addition to the technical area, whoever manages the management system. That dual recipient is the cheapest correction and the one that delivers the most results.
How often should technical tests be carried out?
It depends on exposure and on changes to the infrastructure. More important than frequency is that each test is compared with the previous one to measure whether findings were closed.
Primary sources
Need support on this topic? We offer an initial scope assessment at no cost.
Let’s talk about your case →About the author
ONAC Lead Evaluator since 2012 and ISO Management Systems Lead Auditor since 2005 at accredited certification bodies. Industrial Engineer, Master in Organizational Management and Specialist in Occupational Health and Safety. Graduate professor in specialization and master’s programs at Colombian universities. More than 25 years of experience in manufacturing and services, in the public and private sectors.
View professional profile on LinkedIn →