+DER.3.1 Audits and Revisions
---+DER.3.1.G1. Insufficient or Unplanned Implementation of Security Safeguards
---+DER.3.1.G2. Ineffective or Inefficient Implementation of Security Safeguards
---+DER.3.1.G3. Insufficient Implementation of the ISMS
---+DER.3.1.G4. Insufficient Auditor Qualifications
---+DER.3.1.G5. Lack of Long-Term Planning
---+DER.3.1.G6. Lack of Planning and Coordination when Performing an Audit
---+DER.3.1.G7. Lack of Coordination with Employee Representatives
---+DER.3.1.G8. Deliberate Concealment of Deviations
---+DER.3.1.A1 Definition of Responsibilities [Top Management] (B)
---+DER.3.1.A2 Preparing an Audit or Revision (B)
---+DER.3.1.A3 Conducting an Audit [Audit Team] (B)
---+DER.3.1.A4 Performing a Revision (B)
---+DER.3.1.A5 Integration into the Information Security Process (S)
---+DER.3.1.A6 Definition of an Audit and Revision Basis and a Uniform Evaluation Scheme (S)
---+DER.3.1.A7 Drawing Up an Audit Program (S)
---+DER.3.1.A8 Creation of a Revision List (S)
---+DER.3.1.A9 Selection of an Appropriate Audit Team or Revision Team (S)
---+DER.3.1.A10 Creation of a Audit Plan or Revision Plan [Audit Team] (S)
---+DER.3.1.A11 Communication and Behaviour During Audits [Audit Team] (S)
---+DER.3.1.A12 Holding an Initial Meeting [Audit Team] (S)
---+DER.3.1.A13 Inspection and Review of Documents [Audit Team] (S)
---+DER.3.1.A14 Selection of Samples [Audit Team] (S)
---+DER.3.1.A15 Selection of Appropriate Audit Techniques [Audit Team] (S)
---+DER.3.1.A16 Schedule of the On-Site Audit [Audit Team] (S)
---+DER.3.1.A17 Performance of the On-Site Audit [Audit Team] (S)
---+DER.3.1.A18 Conducting Interviews [Audit Team] (S)
---+DER.3.1.A19 Revision of the Risk Treatment Plan [Audit Team] (S)
---+DER.3.1.A20 Holding a Closing Meeting [Audit Team] (S)
---+DER.3.1.A21 Analysis of Audits [Audit Team] (S)
---+DER.3.1.A22 Creation of an Audit Report [Audit Team] (S)
---+DER.3.1.A23 Documentation of Revision Results (S)
---+DER.3.1.A24 Conclusion of the Audit or Revision [Audit Team] (S)
---+DER.3.1.A25 Evaluation of an Audit (S)
---+DER.3.1.A26 Monitoring and Adapting the Audit Program (S)
---+DER.3.1.A27 Storage and Archiving of Documents on Audits and Revisions (S)

DER.3.1 Audits and Revisions

Introduction

Audits and revisions are fundamental to every successful information security management system (ISMS). An organisation's overall level of information security can only be assessed when established security safeguards and processes are regularly audited to determine whether they are still effective, complete, appropriate, and up to date. Hence, audits and revisions are a suitable tool for determining, achieving, and maintaining an appropriate level of security. Audits and revisions make it possible to identify security deficiencies and undesirable developments and create appropriate safeguards in response.

An audit (lat. audire = to hear, to listen) is a systematic, independent examination of activities and their results. This involves checking compliance with defined requirements such as norms, standards, or guidelines. A revision (revise = control, check) investigates whether documents, conditions, objects, or methodologies are correct, effective, and appropriate. Unlike an audit, a revision does not necessarily have to be performed independently. A revision may also include maintenance that incorporates subsequent improvements.

Objective

Module DER.3.1 Audits and Revisions defines requirements for audits and revisions in order to improve information security in an organisation, avoid improper developments in this area, and optimise security safeguards and processes.

Scoping and Modelling

The module must be applied once to the entire information domain under consideration. It covers internal audits (first-party audits) and revisions, as well as audits of service providers and partners (second-party audits). Certification audits (third-party audits) are not considered in this module.

The IS audits that are obligatory for federal government agencies in Germany are also not addressed. These are covered in module DER 3.2 Audits Based on the BSI "Guideline for IS Audits”.

Useful Resources

The International Organization for Standardization (ISO) describes guidelines for auditing management systems in the standard ISO 19011:2011.

The International Organization for Standardization (ISO) describes guidelines for auditing an ISMS in the standard ISO/IEC 27007:2011.

The Information Security Forum describes guidelines for auditing an ISMS in “The Standard of Good Practice for Information Security”.

1. Přehled

Název Standard
DER.3.1.A1 Definition of Responsibilities [Top Management] (B)

An organisation’s Top Management MUST appoint an employee who will be responsible for planning and initiating audits and revisions. The Top Management MUST ensure that there is no conflict of interests in this appointment.

The organisation MUST use audits and revisions to improve its security safeguards.

DER.3.1.A2 Preparing an Audit or Revision (B)

Prior to an audit or revision, an organisation MUST define the audit object and its corresponding goals. The affected contact partners MUST be informed. Depending on the object of the audit or revision, the employee responsible MUST inform the Employee Representatives of the planned audit or revision.

DER.3.1.A3 Conducting an Audit [Audit Team] (B)

During an audit, the Audit Team MUST check whether the requirements of guidelines, norms, standards, and other relevant specifications are being fulfilled. The organisation being audited MUST be aware of these requirements.

The Audit Team MUST carry out a document check and an on-site audit during each audit process. During the on-site audit, the Audit Team MUST ensure that it never actively interferes with systems itself and does not issue instructions regarding changes to the audit object.

The Audit Team MUST document all the results of the audit in writing and summarise them in an audit report. The audit report MUST be submitted to the contact person of the organisation in a timely manner.

DER.3.1.A4 Performing a Revision (B)

Within the framework of a revision, the Audit Team MUST check that the current requirements are being met in a complete, correct, and appropriate manner. The organisation in question MUST correct any deviations found as quickly as possible. The respective revisions MUST be documented in a revision history.

DER.3.1.A5 Integration into the Information Security Process (S)

An organisation SHOULD provide a policy for internal ISMS auditing. It SHOULD also establish a policy on the management of corrective action. These policies SHOULD specify that regular audits and revisions are part of the security process and initiated by said process.

Furthermore, the CISO SHOULD ensure that the results of audits and revisions are returned to the ISMS and incorporated into its improvement. The CISO SHOULD include the audits and revisions carried out and their results in their regular report to the organisation's Top Management. This SHOULD also detail the deficiencies eliminated and the quality improvements made.

DER.3.1.A6 Definition of an Audit and Revision Basis and a Uniform Evaluation Scheme (S)

An organisation SHOULD establish a uniform basis for audits. A uniform evaluation scheme SHOULD be defined and documented for evaluating the implementation of requirements.

DER.3.1.A7 Drawing Up an Audit Program (S)

The CISO SHOULD draw up an audit program that contains all the audits and revisions to be performed in the next several years. Objectives SHOULD be defined for the audit program that are derived in particular from the information security goals at hand and the aims of the corresponding organisation.

The CISO SHOULD provide for contingency reserves in the organisation's annual resource planning. The audit program SHOULD be subject to its own continuous improvement process.

DER.3.1.A8 Creation of a Revision List (S)

The CISO SHOULD maintain one or more revision lists that document the current status of the revision objects and the scheduled revisions.

DER.3.1.A9 Selection of an Appropriate Audit Team or Revision Team (S)

An organisation SHOULD assemble a suitable team for every audit and revision. It SHOULD appoint a leading auditor (Audit Team Leader) or a leading revisor. This person SHOULD take complete responsibility for carrying out the audits or revisions.

The size of the Audit Team or revision team SHOULD correspond to the area to be audited. In particular, the organisation SHOULD consider the competencies required for the subjects of an audit and the size and local distribution of the area to be audited. The members of the audit or revision team SHOULD be appropriately qualified.

The neutrality of the Audit Team SHOULD be guaranteed. The revisors SHOULD also be independent. If external service providers are deployed as auditors or revisors, their independence SHOULD be checked and they SHOULD be obliged to maintain confidentiality.

DER.3.1.A10 Creation of a Audit Plan or Revision Plan [Audit Team] (S)

Prior to an audit or a major revision, the Audit Team Leader or the lead revisor SHOULD create an audit or revision plan. For audits, the audit plan SHOULD be part of the final audit report. The audit plan SHOULD be updated throughout the audit and adjusted as required. Minor revisions SHOULD be scheduled according to the revision list.

The respective organisation SHOULD provide sufficient resources to the Audit Team or revision team.

DER.3.1.A11 Communication and Behaviour During Audits [Audit Team] (S)

The Audit Team SHOULD set clear rules for the exchange of information between the Audit Team or revision team and the employees of the organisation or department to be audited. The Audit Team SHOULD use suitable safeguards to ensure that the information shared in an audit remains confidential and its integrity remains intact.

Persons supporting the audit SHOULD NOT influence its activities. Furthermore, they SHOULD be obliged to maintain confidentiality.

DER.3.1.A12 Holding an Initial Meeting [Audit Team] (S)

The Audit Team or revision team SHOULD hold an initial meeting with the relevant contact persons. The audit or revision procedure SHOULD be explained and the framework conditions of the on-site audit agreed. The respective persons in charge SHOULD confirm this.

DER.3.1.A13 Inspection and Review of Documents [Audit Team] (S)

The documents SHOULD be checked by the Audit Team based on the requirements defined in the Gap Analysis Plan. All the relevant documents SHOULD be reviewed as to whether they are up to date, complete, and comprehensible. The results of the document check SHOULD be documented. To the extent that doing so makes sense, the results SHOULD also be incorporated into the on-site audit.

DER.3.1.A14 Selection of Samples [Audit Team] (S)

The Audit Team SHOULD select the samples for the on-site audit in a risk-oriented manner and justify them in a comprehensible way. The selected samples SHOULD be documented. If the audit is being performed based on the target objects and requirements of an IT-Grundschutz module, these SHOULD be selected on the basis of a previously defined method. When selecting samples, the results of previous audits SHOULD be taken into consideration, as well.

DER.3.1.A15 Selection of Appropriate Audit Techniques [Audit Team] (S)

The Audit Team SHOULD implement suitable methods for each of the areas to be audited. Furthermore, it SHOULD be ensured that all audits are proportionate to the situation at hand.

DER.3.1.A16 Schedule of the On-Site Audit [Audit Team] (S)

The Audit Team SHOULD set the schedule of the on-site audit together with the contact person in question. The results SHOULD be documented in the audit plan.

DER.3.1.A17 Performance of the On-Site Audit [Audit Team] (S)

At the beginning of an on-site audit, the Audit Team SHOULD hold an initial meeting with the persons in charge at the organisation concerned. Afterwards, all the requirements specified in the Gap Analysis Plan SHOULD be checked using the audit methods defined. If a selected sample deviates from the documented status, the sample SHOULD be extended as needed until the issue is clarified. The Audit Team SHOULD conduct a closing meeting after the audit. It SHOULD briefly present the results (without assessments) and explain the steps ahead. The meeting SHOULD be documented in writing.

DER.3.1.A18 Conducting Interviews [Audit Team] (S)

The Audit Team SHOULD conduct structured interviews. Questions SHOULD be concise, precise, and easy to understand. In addition, appropriate interviewing techniques SHOULD be used.

DER.3.1.A19 Revision of the Risk Treatment Plan [Audit Team] (S)

The Audit Team SHOULD check that the remaining residual risks are appropriate and acceptable for the information domain concerned. It SHOULD also check whether the organisation's Top Management has acknowledged its acceptance of these risks in a binding manner. Safeguards that fundamentally support the information security of the entire organisation MUST NOT be included in this assumption of risk.

The auditor SHOULD verify at random whether and to what extent the safeguards defined in the risk treatment plan have been implemented.

DER.3.1.A20 Holding a Closing Meeting [Audit Team] (S)

The Audit Team SHOULD conduct a closing meeting with the respective persons in charge at the audited organisation. This SHOULD present the preliminary audit findings and lay out the next steps.

DER.3.1.A21 Analysis of Audits [Audit Team] (S)

After an on-site audit, the Audit Team should further consolidate and evaluate the information gained. After any additional information and documentation requested after the fact are analysed, the audited safeguards SHOULD be subjected to a final evaluation. The Audit Team SHOULD allow the organisation in question a sufficient time frame for providing the requested documentation. Documents not received by the agreed date SHOULD be considered non-existent.

DER.3.1.A22 Creation of an Audit Report [Audit Team] (S)

The Audit Team SHOULD transfer the results obtained into an audit report and document them transparently.

The organisation audited SHOULD ensure that all the entities affected are provided with the sections of the audit report that are important and necessary for them within an appropriate time frame.

DER.3.1.A23 Documentation of Revision Results (S)

The results of a revision SHOULD be documented uniformly by the revision team.

DER.3.1.A24 Conclusion of the Audit or Revision [Audit Team] (S)

After the audit or revision, all the relevant documents, data storage media, and IT systems SHOULD be returned or destroyed. This SHOULD be coordinated with the audited organisation. In doing so, storage obligations resulting from legal or other binding requirements SHOULD be taken into account accordingly. Furthermore, the CISO SHOULD have all the forms of access granted to the Audit Team or revision team disabled or deleted.

There SHOULD be an agreement with the auditors or revisors as to how the results are to be handled. This SHOULD also establish that the audit results must not be forwarded to other organisations without the consent of the audited organisation.

DER.3.1.A25 Evaluation of an Audit (S)

The audited organisation SHOULD eliminate the deviations or shortcomings identified in the audit report or within the framework of a revision within a reasonable period of time. The corrective measures to be taken SHOULD be documented, along with the corresponding deadlines and the persons responsible. Corrective measures that have been completed already SHOULD also be documented. The organisation SHOULD establish and use a defined procedure for this purpose.

In the event of serious deviations or shortcomings, the Audit Team or revision team SHOULD check whether the corrective measures have been carried out.

DER.3.1.A26 Monitoring and Adapting the Audit Program (S)

The audit program followed SHOULD be monitored and adapted continuously to ensure compliance with regard to dates, audit objectives, audit contents, and audit quality.

The appropriateness of the audit program SHOULD be checked based on the requirements it is meant to fulfil and the results of the audits performed. It SHOULD be adapted as necessary.

DER.3.1.A27 Storage and Archiving of Documents on Audits and Revisions (S)

The organisation in question SHOULD file and store audit programs and documents on audits and revisions in a traceable and audit-proof manner in accordance with regulatory requirements. This SHOULD ensure that only authorised persons can access audit programs and documents. The organisation SHOULD securely destroy the audit programs and documents after the retention period has expired.

1.1 Odkazy

1.2 Identifikované požadavky

1.3 Související regulace

2. Identifikované požadavky

Požadavky
Zdroj Požadavek

3. Související regulace

Regulace
Zdroj Regulace

Propojené úkoly