Chapter 1 Computer Security Incident Response
Chapter 1 Computer Security Incident Response
CHAPTER 1
PURPOSE:
AUTHORITY:
Sections 20.23(4)(a) and 334.048(3), Florida Statutes (F.S.)
SCOPE:
This procedure is applicable to all information and technology resources, at all levels of
sensitivity, whether owned and operated by or operated on behalf of the Department.
Additionally, consultants, outside agency workers, and volunteers assume the
Department Employee Reporting Responsibilities established within this procedure,
and are included in any reference to employee throughout this procedure.
This procedure establishes the minimum standards for Department CSIRT functions.
Districts may implement processes that meet or exceed the Department requirements in
this procedure.
REFERENCES:
Section 282.318, F.S.
Section 20.055 F.S.
Rule Chapter 60GG-2, Florida Administrative Code (F.A.C.)
Security and Use of Technology Resources, Topic No. 325-060-020
Computer Security Incident Response Team 1-1
Topic No. 325-000-002 Effective: 07-01-2020
Transportation Technology Manual
Computer Security Incident Response Team (CSIRT)
(1) Immediately report any breach of security, including but not limited to,
unlawful accesses, suspected intrusions, theft, or other actions that
compromise the security of technology resources to the FDOT Service
Desk.
(4) Establish any additional security controls that are deemed necessary by
the CSIRT as a result of a computer security incident investigation.
The role of the CSIRT is to serve as the first responder to computer security incidents
within the Department and to perform vital functions in identifying, mitigating, reviewing,
documenting, and reporting findings to management. The CSIRT coordinates with the
Chief Technology Officer (CTO), but is accountable directly to the Secretary.
(8) Reporting incidents to the Florida Digital Services and the Cybercrime
Office
(10) Staying current on functional and security operations for the technologies
within their individual area of responsibility
Incident Managers are assigned based on the process outlined in CSIRT. In cases of a
conflict of interest, an alternative incident manager is assigned. Incident managers will
not be assigned to an incident if there is a potential for conflict of interest. In the event of
a similar conflict of interest involving a core CSIRT member, the conflict must be
reported to the designated CSIRT Leader and to the CIO immediately. The CIO will
determine the appropriate course of action based upon the circumstances surrounding
the incident, and the nature of the conflict of interest.
The ISM will serve as the CSIRT leader. In the event that the ISM is not available during
a security event, the CIO will act as the CSIRT leader or designate a CSIRT leader to
serve in the interim. The CSIRT leader is responsible for managing the activities of the
CSIRT.
(8) Ensuring Class 2 and Class 3 incidents are reported to the Florida Digital
The Chief Information Officer is responsible for ensuring operational support is available
for the resolution and remediation of incidents. This includes providing coordinated
oversight between the various OIT sections, establishing priorities, and assisting in the
prioritization of future work required based on lessons learned. The CIO will work
closely with the CTO to detail the impact of incidents on OIT.
Chapter 20.055, F.S. tasks each agency’s Inspector General with initiating, conducting,
and coordinating investigations related to the programs and operations of each state
agency. The Department’s OIG will assign a representative to serve on the CSIRT to
ensure that CSIRT reviews are properly handled and that reviews that uncover policy
violations, fraud, or other abuses are transferred to the OIG for further investigation
when appropriate.
The OIG representative will determine if and when law enforcement agencies should be
called during the course of an incident review whenever the OIG has reasonable
grounds to believe there has been a violation of criminal law. If a CSIRT incident
requires the intervention of law enforcement, the OIG will contact law enforcement and
develop any required protocols before exchanging investigative information. The CSIRT
leader will keep the FDS-CISO informed of any referrals to law enforcement and ensure
CSIRT members are fully briefed on any interagency incidents. The CSIRT leader
and/or designated member of OIG staff may serve as a liaison among law enforcement,
FDS-CISO, and the CSIRT.
CSIRT members must be familiar with published security guidelines available through
the Department’s published security policies and procedures. Each CSIRT member will
serve as a subject matter expert for the area of the Department they represent. As
representatives of their respective areas, each member will ensure that all policies and
procedures as well as state and federal laws that apply to their specific area of
responsibility are being adhered to during the implementation of this CSIRT procedure.
Each CSIRT member should have an awareness of the duties of the other CSIRT
members.
Each CSIRT member must also be available (or have a designee available) to respond
to security incidents during business and non-business hours in order to mitigate
possible incidents and react swiftly to minimize damage to critical infrastructure,
computer system(s), networks, and data.
The CSIRT will classify each incident as a Class 0, Class 1, Class 2, or Class 3 incident
based upon risk-based severity. These classifications allow for consistency for reporting
and tracking purposes. If an incident meets several criteria in different rating categories,
the incident will be defined based on the highest rating. Class 0 are deemed to be
observable events that are worth being documented with the understanding they may
possibly become incidents. Examples including but not limited to are anti-malware
protection that prevents infection, an Intrusion Prevention System (IPS) that drops
inbound traffic. The following criteria will be used to determine incident classification:
The reason for the escalation or downgrade must be documented as part of the
process.
(5) Conclusions
(6) Recommendations
After the conclusion of the computer security incident review, any and all new
information relevant to the computer security incident must be documented in an
amended final report.
1.5.1 Methodologies
The CSIRT will use current best practices in reviews. These practices are intended to
ensure the following:
(1) CSIRT reviews are preserved to the extent dictated by the current
Department policies and pertinent laws, rules and regulations.
(2) Evidence and its integrity is properly preserved, collected, secured, and
documented consistent with the chain of custody requirements as directed
by the OIG.
1.5.2.1 Interviews
The CSIRT must conduct all interviews in a professional manner and document them
during or immediately after the interview.
1.5.2.2 Evidence
Authorized personnel will collect and preserve evidence and its integrity according to
Department procedures and will ensure the appropriate chain of custody. All physical
evidence must be secured in a lockable location and all electronic evidence must be
secured by appropriate network security. Only the Department-appointed custodian(s)
of the evidence will have access to the evidence location, and they will account for the
custody of all keys, lock combinations or electronic key cards. All transfers of evidence
must be authorized, thoroughly documented and signed for. The evidence custodian(s)
must be aware of location and physical security of evidence at all times.
TRAINING:
None.
FORMS:
None.