The Security Incident Response Plan provides a systematic incident response process for all Information Security Incidents that affect any of Haystack's information technology systems, network, or data, including data held or services provided by third-party vendors or other service providers. This plan applies to all Haystack assets utilized by personnel acting on behalf of Haystack or accessing its applications, infrastructure, systems, or data. All personnel are required to read, accept, and follow all Haystack policies and plans.
Haystack intends for this plan to:
An “Information Security Incident” means an actual or reasonably suspected unauthorized use, disclosure, acquisition of, access to, corruption of, deletion, or other unauthorized processing of sensitive information that may compromise the privacy, confidentiality, integrity, or availability of that information.
Haystack has a Security Response Team (SRT) consisting of predetermined employees from key departments to manage security incidents. The SRT provides timely, organized, informed, and effective responses to information security incidents to:
The SRT also oversees and coordinates the development, maintenance, and testing of the plan, its distribution, and ongoing updates. The Security Incident Response Plan is activated when a security incident occurs, and the SRT is responsible for evaluating the situation and responding accordingly. Depending on the severity of an incident, the SRT may request engagement from various support teams to assist with the mitigation of the incident. The SRT meets periodically for training, education, and review of the documented plan.
The SRT consists of a core team with representatives from key Haystack groups and stakeholders. The current SRT roster may be contacted at security@haystackteam.com.
The process outlined below should be followed by the appropriate staff at Haystack in the event of an Information Security Incident. Haystack assigns resources and adopts procedures to timely assess automated detection results, screen internal and external reports, and identify actual information security events. Each identified Information Security Incident must be documented.
Responding to a data breach involves the following stages:
All steps must be documented in an incident log or corrective action plan. The data breach response is not purely linear, as these stages often overlap.
After the incident is resolved, senior management should meet with the SRT and relevant team members for a post-mortem to understand the incident and determine preventive measures for the future. The retrospective should be documented and key learnings presented to appropriate team members in a timely manner.
Testing the plan annually ensures its effectiveness and practicality. Any gaps discovered during testing will be addressed by management. Tests must be thoroughly documented and can include:
Haystack business needs, local situations, laws, and regulations may occasionally call for an exception to this policy or any other Haystack policy. Management will determine an acceptable alternative approach if an exception is needed.
Any violation of this policy or other Haystack policies may result in disciplinary action, up to and including termination of employment. Haystack reserves the right to notify law enforcement of any unlawful activity and cooperate in any investigation. Conduct in violation of this policy is not considered within the scope of an employee’s or contractor’s work duties.
This plan will be reviewed and tested annually. Updating the plan and revising this document to reflect changes, testing updates, and training personnel are crucial. Test results will be documented and signed off by management, shared internally, and tracked to resolution. Changes will be communicated across the organization.