ITSMs, system administrators and system users SHOULD sign a statement that they have read and agree to abide by their respective SOPs.
5.6. Incident Response Plans
Objective
5.6.1.
Incident Response Plans (IRP) outline actions to take in response to an information security incident.
Context
Scope
5.6.2.
This section relates to the development of IRPs to address information security, and not physical incidents within agencies. Information relating to other
mandatory documentation can be found in Section 5.1 - Documentation Fundamentals.
Rationale & Controls
5.6.3.
Contents of IRPs
5.6.3.R.01.
Rationale
The guidance provided on the content of IRPs will ensure that agencies have a baseline to develop an IRP with sufficient flexibility, scope and
level of detail to address the majority of information security incidents that could arise.
5.6.3.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:902]
Agencies MUST include, as a minimum, the following content within their IRP:
broad guidelines on what constitutes an information security incident;
the minimum level of information security incident response and investigation training for system users and system administrators;
the authority responsible for initiating investigations of an information security incident;
the steps necessary to ensure the integrity of evidence supporting an information security incident;
the steps necessary to ensure that critical systems remain operational;
when and how to formally report information security incidents; and
national policy requirements for incident reporting (see Chapter 7 – Information Security Incidents).
5.6.3.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:904]
Agencies SHOULD include the following content within their IRP:
clear definitions of the types of information security incidents that are likely to be encountered;
the expected response to each information security incident type;
the authority within the agency that is responsible for responding to information security incidents;
the criteria by which the responsible authority would initiate or request formal, police investigations of an information security incident;
which other agencies or authorities need to be informed in the event of an investigation being undertaken; and
the details of the system contingency measures or a reference to these details if they are located in a separate document.
5.7. Emergency Procedures
Objective
5.7.1.
Classified information and systems are secured before personnel evacuate a facility in the event of an emergency.
Context
Scope
5.7.2.
This section covers information relating to the securing of classified information and systems as part of the procedures for evacuating a facility in the
event of an emergency.
5.7.3.
The safety of personnel is of paramount importance.
Rationale & Controls
5.7.4.
Evacuating facilities
5.7.4.R.01.
Rationale
When evacuating a facility, it is important that personnel secure classified information and systems as they would at the end of operational
hours. This includes, but is not limited to, securing media, logging off of workstations and securing safes and cabinets. This is important as an
attacker could use such an opportunity to gain access to documents, applications or databases that a system user had already authenticated to
or use another system user’s credentials for a malicious purpose.
5.7.4.R.02.
Rationale
During an evacuation, the safety of staff is of primary importance. Where it is immediately obvious to wardens and/or staff that the securing of
classified information and systems prior to the evacuation of a facility would lead to, or exacerbate, serious injury or loss of life to personnel,
the facility may be evacuated without personnel following the necessary procedures to secure classified information and systems.
5.7.4.R.03.
Rationale
Where facilities are evacuated and classified information and systems haveNOT been secured, the Chief Warden or Floor Warden MUST be
notified as soon as possible. Steps should be taken to secure the site as soon as it is safe to do so.
5.7.4.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:922]
Agencies MUST include in procedures for personnel evacuating a facility the requirement to secure classified information and systems prior to
50
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents