Report: Incident Response and Management for ABC Software Inc.

This report details incident response and management strategies for ABC Software, Inc. It begins by outlining procedures for identifying and documenting security incidents, emphasizing the importance of monitoring, detection, alerting, and reporting. The report then explores the process of informing operational managers and stakeholders about threats, followed by an examination of breach investigation, including password security, human error, and system vulnerabilities. Enforcement mechanisms for breaches, covering capital requirements, liquidity, and governance, are also discussed. Furthermore, the report addresses damage assessment, including system evacuation and recovery plans, and concludes with procedures for reviewing responses and updating policies to ensure ongoing effectiveness and adaptation to changing circumstances. The report is a comprehensive guide to managing security incidents within the organization.

Running head: Management of Incident Response
Incident Response and its Management
Name of Student:
Name of University:
Author note:

1Incident Response and its Management
Introduction:
It can be defined as an approach for addressing and also managing an attack or breach
whenever there is a failure in the security measure (Carver et al., 2016). In this report it is
discussed about a plan which can be implemented to address and to manage an attack when
the security measures will fail in ABC software, Inc.
1st: Procedures to initially identify and document an incident
In case to initially identify any threat a plan must be generated, in case of a failure of
the security technology. A security team should be trained who will monitor for any unusual
events and detect if any. After the detection they must report the incident that have been
detected. For such plan the following processes must be followed:
i. Monitor
ii. Detect
iii. Alert
iv. Report
2nd: Procedures that will inform tactical operational managers, internal and
external stakeholders, and/or individuals affected
As the team will detect a threat they will immediately transfer the threats to the
operational departments so that they can take steps against the attack as soon as possible
(Tanguy et al., 2016).
3rd: Procedures to investigate the breach, to mitigate harm to individuals, and to
protect against further breaches
After the arrival of a breach, it is necessary to investigate about the breach. While
investigating there are certain aspects which should be kept in mind. Such as to check the

2Incident Response and its Management
weakness of a password, to check whether there is any human error or any failure of process
(Bromiley et al., 2016). It is also necessary to investigate the vulnerabilities for any old
system. After this investigation it will be easier to mitigate any harm on any individual and
also it will be easier to protect from any further attack.
4th: Enforcement mechanisms for breaches and non-adherences
Enforcement mechanisms in case of breaches and also for non-adherences depends on
the particular areas:
i. Capital requirements
ii. Large espousers
iii. Liquidity
iv. Reporting obligations
v. Governance
5th: Procedures to assess the damage to the organization and estimate both the
damage cost and the cost of the containment efforts
In case of any damage in the ABC software, Inc. the following steps are to be followed:
a. Evacuation of the system
b. Shut down power
c. Recovery plan.
6th: Procedures to review response and update policies
In case of reviewing the response and to update the policies the following steps are to be
followed:
a. The implementation is as it is intended.
b. Access should be done as they are used.

3Incident Response and its Management
c. Whether the circumstances are changed or not is to be determined.

4Incident Response and its Management
References:
Bromiley, M. (2016). Incident Response Capabilities in 2016: The 2016 SANS Incident
Response Survey. SANS Institute, June.
Carver, M., DiValentin, L. W., Lefebvre, M. L., Hovor, E., & Rozmiarek, D. W. (2016). U.S.
Patent No. 9,386,041. Washington, DC: U.S. Patent and Trademark Office.
Tanguy, L., Tulechki, N., Urieli, A., Hermann, E., & Raynal, C. (2016). Natural language
processing for aviation safety reports: from classification to interactive
analysis. Computers in Industry, 78, 80-95.