What auditors really expect
An ISO 27001 or CyFun audit is often seen as an exciting moment of inspection. Yet an audit is not about flawless paperwork, but about one central question: does your organisation have its information security under control, and can it demonstrate that?
Good preparation is therefore not only about “passing the audit”, but about building structure, insight, and clear responsibilities. This not only helps during the audit but also strengthens your organisation in the long term.
In this post, we take a closer look at what auditors actually expect and how to prepare your organisation realistically, without letting theory outweigh practice.
ISO 27001 and CyFun: different approach, same principle
ISO 27001 and the CyberFundamentals Framework start from the same principle: understanding and managing business risks. The difference lies mainly in the form.
ISO 27001 requires a formally established management system (an ISMS), with clear roles, policies, monitoring, and improvement. CyFun places more emphasis on concrete security measures and the maturity level of your organisation.
In both cases: those who have their basics in order are already far ahead. Preparation largely follows the same lines.
Unsure whether to choose ISO 27001 or CyFun? You can read more about that in this post.
If you already know which audit you want to undergo, the following five focus points are crucial to start well-prepared:
- Scoping & objective
- Current risk analysis
- Understandable and workable documentation
- Actively involve employees & management
- Conduct an internal audit
1. Scope & objective of the audit: Determine in advance what will be assessed
An audit only goes smoothly if it is clear in advance what exactly will be assessed. Therefore, defining the scope is one of the most important steps in your preparation.
The scope describes which processes, systems, activities, employees, and locations are included in the audit. This seems simple but can quickly become complex in organisations with multiple sites, cloud environments, or many external suppliers.
A well-defined scope is:
- aligned with your core activities
- clear to all involved
- logical and defensible to the auditor
A vague or poorly substantiated scope almost always leads to extra questions and unnecessary discussions during the audit.
For ISO 27001, the entire Information Security Management System (ISMS) is within scope. This includes, among other things, policies, risk management, security measures, and continuous improvement. For CyFun, the focus is more on concrete measures and the maturity level of your organisation.
Whatever framework you choose: clearly document what is in and out of scope. This prevents surprises and provides peace of mind during the audit.
2. Risk analysis: Demonstrate that you understand and monitor risks
ISO 27001 and CyFun audits rely heavily on risk thinking. The auditor does not expect a theoretical model but a realistic picture of what can go wrong in your organisation and how you deal with it.
Concretely, this means your organisation must be able to explain which risks are relevant to its operations, why some risks are prioritised, and how the chosen measures contribute to risk mitigation.
A risk analysis that is alive in the organisation, evolves with changes, and is used as a management tool weighs far more than a one-time exercise. A purely theoretical exercise created only for the audit is quickly exposed.
3. Make documentation workable and understandable
Policies and procedures are necessary but are not an end in themselves. During an audit, the focus is mainly on whether agreements are understandable and effectively applied. In other words: do they fit the daily reality of employees, and do they understand them?
Employees do not need to know every detail but should be able to explain in broad terms what is expected of them regarding information security.
Policies that no one reads or recognises increase risk rather than reduce it. Both for ISO 27001 and CyFun, a few documents are mandatory, but that number is smaller than many organisations think.
Fewer documents, clearly written and embraced by the organisation, build more confidence with the auditor than an overflowing folder rarely opened.
How do you ensure employees actually understand your policy?
The key lies in clear communication:
- Write policies in plain language, understandable for everyone in the organisation.
- Avoid unnecessary jargon and technical reasoning. Employees primarily focus on performing their own role.
- Emphasise concrete expectations: what must someone do, refrain from, or report? Also explain why, without going too deeply into technical aspects.
The simpler and more concrete your policy, the more likely it will actually be applied. And that is exactly what auditors are looking for.
4. Actively involve employees and management
As also mentioned in the video, an audit is not an IT party. Employees play an important role in information security. They need to know which information is sensitive, how to handle it, and what is expected of them in case of incidents or deviations.
Management also plays a key role. Auditors explicitly check whether leaders take responsibility, provide direction, and make decisions based on risks. This does not mean management must know every detail inside out, but there must be demonstrable involvement, monitoring, and guidance.
When information security visibly forms part of meetings, decision-making, and priorities, it shows maturity. It gives auditors confidence that security is not a one-time exercise but an integral part of operations.
5. Conduct an internal audit and practice before it really counts
An internal audit or preparatory evaluation is one of the most underestimated yet valuable steps leading up to an external audit. It is a moment to critically examine your own operations without external pressure.
During an internal audit, you test whether agreements are followed, documentation matches practice, and responsibilities are clear. This reveals potential risks or errors while you still have time to address them.
It is important that the results of such an exercise do not end up in a drawer. Auditors look not only at the findings but especially at what is done with them. Are improvement actions documented? Is there follow-up? Are adjustments made where necessary?
Organisations that can demonstrate they evaluate and improve themselves show maturity. This often weighs more than a situation where “everything seems in order” but has never been tested.
An audit as a checkpoint, not a finish line
An ISO 27001 or CyFun audit is not the finish line but rather a snapshot within a continuous path toward better digital resilience.
Those who approach audits as a management tool gain more than just a positive report. It leads to better decisions, more trust from clients, and a stronger foundation for future obligations, such as NIS2. That positive report is an added bonus.
Need support in your preparation?
Every organisation is different. What works for one may be too heavy or too light for another.
Are you facing an audit or want to know how audit-ready your organisation is today?
Cingulum supports organisations, large and small, in building audit-ready information security, tailored to their reality.
Curious how we can support you? Feel free to contact us.

