Zertio
Section 10/72

Section 1 of 9 · Reference: ISO/IEC 27001:2022 (incl. Amd 1:2024), Introduction and Clauses 1 to 3, supplemented by terms from ISO/IEC 27000

Information security fundamentals

The first section lays the foundation: why information security is a leadership issue for an organization in the first place, which assets are protected, which protection goals apply and how information security differs from data protection and pure IT security.

At a glance

The core relationships of this section as a diagram

Note on this sectionLessons 2 and 3 (Carbanak, history of the standard) are not part of the standard. They are based on publicly reported facts and on the history of the standard; they serve to provide context, not exam preparation in the narrower sense.

The three protection goals of information security

Confidentiality, integrity and availability — what the ISMS preserves through the risk management process (Introduction 0.1, Clause 6.1.2 c) 1))

Intersection diagram of the three protection goals Three overlapping circles for confidentiality, integrity and availability. The protected information is in the common intersection. Confidentiality authorized users only Integrity unaltered Availability accessible when needed Informa- tion

Confidentiality violated

Data exfiltration from the customer database. The system keeps running, the data are correct — they are just no longer secret.

A.5.15 A.8.24

Integrity violated

A faulty import mixes up application data. Everything is available and confidential — but wrong.

A.8.32 A.8.15

Availability violated

The citizen portal is down for four hours. Nothing has leaked, nothing has been falsified — it is just not reachable.

A.8.13 A.8.14

Remember: a ransomware incident usually affects all three goals at the same time — encryption affects availability, the prior data exfiltration affects confidentiality, manipulated backups affect integrity.

From BS 7799 to ISO/IEC 27001:2022 (incl. Amd 1:2024)

The sequence of editions of the standard and its adoption in Europe and Germany

Timeline of the history of the standard Seven milestones from BS 7799 in 1995 via the ISO editions of 2005, 2013 and 2022 to the German edition of 2024. 1995 BS 7799-1 Controls 1999 BS 7799-2 certifiable 2005 ISO/IEC 27001 1st edition 2013 2nd edition 114 controls 2022 3rd edition 93 controls 2023 EN ISO/IEC 27001 CEN adoption 2024 DIN EN German edition Break point 2022: alignment with the Harmonized Structure (Annex SL) and to ISO/IEC 27002:2022 — Annex A is restructured from 14 clauses into 4 themes
Crucial in practice: anyone holding a certificate based on the 2013 edition must completely rebuild the Statement of Applicability during the transition — controls were merged, eleven are new and the numbering is different throughout.

The 9 lessons

Click to expand · a tick on the left marks a lesson as completed

Further reading

Overviews, tables and tools for reference

The attack chain and the controls that break it

The course of the Carbanak campaign — and where Annex A comes in

Five-stage attack chain with assigned controls Phishing, entry, reconnaissance, privilege escalation and cash-out. Below each stage are the Annex A controls that apply there. 1. Phishing email with attachment 2. Entry malware active 3. Recon months undetected 4. Privileges legitimate accounts 5. Cash-out damage occurs A.6.3 awareness and training A.8.7 / A.6.8 malware, reporting channel A.8.15 / A.8.16 logs, monitoring A.8.2 / A.5.18 privileged rights, recertification A.5.3 Segregation of duties The chain can be broken at any point. The earlier, the cheaper — but you must not rely on any single stage. That is why the standard requires prevention, detection and response side by side, not one after the other.
From stage 4 onwards, the attack used only legitimate privileges. That is exactly why prevention is not enough: without logging (A.8.15) and monitoring for anomalous behaviour (A.8.16), such an attack looks like normal operation.

From event to incident — and what happens next

The assessment according to A.5.25 is the switch point: only the assessment turns an event into an incident

Flow chart of incident management Observation, reporting according to A.6.8, assessment according to A.5.25 as the decision point, then either documentation and closure or response according to A.5.26, collection of evidence according to A.5.28 and learning according to A.5.27. Observation something is noticed Report A.6.8 Incident? A.5.25 No incident document, close Response A.5.26 Evidence A.5.28 Learning A.5.27 Preparation: process, roles, communication A.5.24 — must be in place beforehand, not in an emergency no yes Lessons learned strengthen the controls — the circle is closed
An event is an observed occurrence that may be relevant to information security. An incident is an event or series of events that is likely to adversely affect business operations or information security. Without the assessment according to A.5.25, this distinction does not exist — and neither does a reliable reporting channel.

Information security and data protection — related, not identical

Two protected assets, two interests, one shared toolbox

Two overlapping areas for information security and data protection On the left, information security with all information of the organization; on the right, data protection with personal data; in the intersection, the technical and organizational measures. Information security all information of the organization in the organization’s interest trade secrets, quotations, source code, contracts Data protection personal data in the data subject’s interest purpose limitation, erasure, access requests, legal basis Intersection A.5.34 A.8.10 A.8.11 Remember: a perfectly secured system can be operated in breach of data protection law — and a procedure that complies with data protection law can be insecure. Confidentiality, integrity and availability do not imply any obligation to delete. Data protection law does; the standard addresses this via A.8.10 and A.5.34.
Typical exam example: job application documents are stored encrypted, with strict access control and complete logging — but kept indefinitely. That is a data protection violation, not a security deficiency. The control that applies is A.8.10 Information deletion.

Final test

12 questions across the section · pass mark 60 percent

Final test section 1

12 questions

Question Which statements about the term “effectiveness” are correct?

Multiple choice: one to three answers are correct.

ExplanationEffectiveness is about achieving objectives, not about effort – the ratio of results to resources is efficiency, a concept not required in 27001 and explicitly different. Clause 10.1 requires continual improvement of suitability, adequacy and effectiveness. — Reference: ISO/IEC 27000, Terms – “effectiveness” · ISO/IEC 27001:2022, 10.1 Continual improvement

Question Which other properties can be included in addition to confidentiality, integrity and availability according to ISO/IEC 27000?

Multiple choice: one to three answers are correct.

ExplanationThe definition of information security names confidentiality, integrity and availability as the core and adds in a note that other properties such as authenticity, accountability, non-repudiation and reliability can also be involved. Cost-effectiveness is not one of them. — Reference: ISO/IEC 27000, Terms – “information security” (preservation of confidentiality, integrity and availability)

Question What is availability according to ISO/IEC 27000?

Multiple choice: one to three answers are correct.

ExplanationThe standard defines availability as accessibility and usability on demand by an authorized entity – without any numerical target. Specific availability targets are set by the organization itself, for example in service level agreements; the standard does not require this. — Reference: ISO/IEC 27000, Terms – “availability” (accessibility and usability on demand)

Question How do an information security event and an information security incident differ?

Multiple choice: one to three answers are correct.

ExplanationAn event is initially just an observation. Only when it jeopardizes business operations or threatens information security does it become an incident. The assessment and decision on this is the subject of A.5.25. — Reference: ISO/IEC 27000, Terms – “information security event” and “information security incident” · Annex A, A.5.25 Assessment and decision on information security events

Question An administrator is asked to explain what ISO/IEC 27000 means by a vulnerability. Which statement is correct?

Multiple choice: one to three answers are correct.

ExplanationA) Correct. ISO/IEC 27000 defines a vulnerability as a weakness of an asset or control that can be exploited by one or more threats. B) Incorrect. This describes the threat, i.e. the potential cause of an incident. The vulnerability is the weakness it exploits. C) Incorrect. An incident that has occurred is a possible consequence. The vulnerability exists beforehand, whether or not it is exploited.

Question What is a nonconformity according to ISO/IEC 27000?

Multiple choice: one to three answers are correct.

ExplanationA nonconformity is simply the non-fulfilment of a requirement – whether the organization’s own, the standard’s or a legal one. A security incident can reveal a nonconformity but is not the same thing, and it can be identified by anyone, for example in an internal audit. — Reference: ISO/IEC 27000, Terms – “nonconformity” (non-fulfilment of a requirement)

Question What does the term “availability” describe according to ISO/IEC 27000?

Multiple choice: one to three answers are correct.

ExplanationISO/IEC 27000 defines availability as “accessible and usable on demand by an authorized entity”. Accuracy and completeness, on the other hand, describe integrity.

Question A service provider asks what the term performance denotes in the ISO/IEC 27000 family. Which statement is correct?

Multiple choice: one to three answers are correct.

ExplanationA) Incorrect. This is the definition of effectiveness. It is a neighbouring term but does not answer the question about performance. B) Correct. ISO/IEC 27000 defines performance as a measurable result; it can relate to activities, processes, products or the entire organization. C) Incorrect. Service metrics are an application from contractual practice, not the term itself.

Question Does risk identification under the current ISO/IEC 27001 have to be carried out on the basis of assets, threats and vulnerabilities?

Multiple choice: one to three answers are correct.

ExplanationA) Incorrect. This describes the 2005 edition, which prescribed this triad. Clause 6.1.2 “Information security risk assessment” has no longer mentioned it since 2013. B) Correct. The standard requires risks to be identified in terms of the loss of confidentiality, integrity and availability. The asset-based approach remains one possible implementation. C) Incorrect. An asset register can help with the assignment, but the standard does not require it for risk identification.

Question Which statements about the term “risk” according to ISO/IEC 27000 are correct?

Multiple choice: one to three answers are correct.

ExplanationThe standard adopts the definition from ISO 31000: effect of uncertainty on objectives, where the deviation can be positive or negative. Multiplying likelihood by the extent of damage is one possible method of risk analysis, not a definition in the standard. — Reference: ISO/IEC 27000, Terms – “risk” (effect of uncertainty on objectives)

Question What distinguishes a correction from a corrective action?

Multiple choice: one to three answers are correct.

ExplanationThe correction treats the symptom (locking the lost notebook), the corrective action the cause (enforcing mandatory encryption). Clause 10.2 requires both: reacting and evaluating the need for action to eliminate the causes. — Reference: ISO/IEC 27000, Terms – “correction” and “corrective action” · ISO/IEC 27001:2022, 10.2 Nonconformity and corrective action

Question Which statements about the term “interested party” are correct?

Multiple choice: one to three answers are correct.

ExplanationThe term is deliberately broad and explicitly includes someone who merely *perceives* themselves to be affected. A contractual relationship is not a prerequisite – authorities, customers, employees and neighbours can all be relevant. — Reference: ISO/IEC 27000, Terms – “interested party” · ISO/IEC 27001:2022, 4.2 Understanding the needs and expectations of interested parties