
Security Incident Response Management (ICT and Aviation Maintenance)
4
Background
The Port of Seattle (Port) is a municipal corporation of the State of Washington, organized on September
5, 1911, under the State statute RCW 53.04.010. The Port is composed of three operating divisions,
namely, Aviation, Maritime, and Economic Development, and employs approximately 2,000 employees.
The Port owns and operates assets, including Seattle-Tacoma International Airport (SEA), conference
facilities, fishing and recreational boating marinas, industrial properties, and cruise ship terminals. This
Information Technology audit included the following departments in its scope:
Information and Communication Technology (ICT) delivers and supports a wide variety of
technology solutions to enable Port objectives.
The Information Security Department is integrated with ICT, Maritime, and Aviation Maintenance.
The department provides strategies, operations, and controls for protecting the Port’s information
systems and sensitive data, while increasing business resiliency.
Aviation Maintenance (AV/M) provides services to support the operations of SEA, its tenants, and
guests. Within AV/M, in the Aviation Electrical & Electronic Systems team, the 44 Electronic
Technicians (ETs) provide support and maintenance of custom and off-the-shelf operational
applications to the airport’s business units.
According to the Center for Internet Security (CIS) controls, a comprehensive cybersecurity program
includes protections, detections, response, and recovery capabilities. The primary goal of incident
response is to identify threats on the enterprise, respond to them before they can spread, and remediate
them before they can cause harm. When an incident occurs, if an enterprise does not have a
documented plan; it is almost impossible to know the right investigative procedures, reporting, data
collection, management responsibility, legal protocols, and communications strategy that will allow the
enterprise to successfully understand, manage, and recover.
As per the National Institute of Standards and Technology (NIST) Computer Security Incident Handling
Guide
3
, an event is “any observable occurrence in a system or network”, while a computer security
incident is “a violation or imminent threat of violation of computer security policies, acceptable use
policies, or standard security practices”.
The incident response lifecycle (Figure 1), consists of four phases:
Preparation: Establishing an incident response capability so the organization is ready to
respond to incidents, but also preventing incidents by ensuring that systems, networks, and
applications, are sufficiently secure.
Detection and Analysis: Determining whether an incident has occurred and, if so, the type,
extent, and magnitude of the problem.
Containment, Eradication, and Recovery:
a. Containment - provides time for developing a tailored remediation strategy. An essential
part of containment is decision-making (e.g., shut down a system, disconnect it from a
network, or disable certain functions).
b. Eradication - may be necessary to eliminate components of the incident, such as deleting
malware and disabling breached user accounts.
c. Recovery - restore systems to normal operation, confirm that the systems are functioning
normally, and (if applicable) remediate vulnerabilities to prevent similar incidents.
Recovery may involve such actions as restoring systems from clean backups, and
rebuilding systems from scratch.
3
https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800‐61r2.pdf