/
/
Incident Response – Anatomy of an Incident Response Test Plan PT 2

Incident Response – Anatomy of an Incident Response Test Plan PT 2

Share

Incident Response

Testing your Incident Response Plan as discussed last week is critical and an external requirement for some organizations (e.g., PCI DSS compliance). For PCI, testing must occur at least annually and include lessons learned postmortem to update or evolve the plan. The two common IR test methods are a Tabletop Exercise and Functional Exercise (Simulated Attack). Your test approach should align with the steps documented in your IR Plan, regardless of the testing method you have selected.

As outlined in NIST SP 800-84, the following steps help an organization to prepare for and conduct a test of its Incident Response Plan and procedures.

 

IR-Blog-Graphic-Final-Corrected

As with many cyclical, iterative processes, the Incident Response Lifecycle does not officially end. After the completion of a test, after action items may be assigned to personnel for continued improvement and in preparation for the next periodic IR test. One of the interesting results of an IR test is the identification of gaps in procedure or tools. Where are the blind spots within our organization’s logging and monitoring solutions? Are our procedures sufficiently detailed and clear, so that responders understand what needs to be done, in a given situation? Organizations increasingly rely on playbooks to define (and automate) responses to predictable events. These playbooks may originate externally and be modified to conform to an organization’s unique characteristics. For example, the Cybersecurity and Infrastructure Security Agency (CISA) has aRansomware Guide resource that is publicly available and useful guidance for security controls preparation, IR planning, and IR response procedures.

Looking for a knowledgeable partner for your cybersecurity and compliance efforts? We’re Here To Help!

Here at MegaplanIT, we have decades of experience handling incident response plans, testing, and analysis of threats to production environments. Our SOCaaS can aid you in identifying and responding to security events and malicious activities within your environment. Our dedicated consultants advise on incident response plan scenarios, custom-tailored to your organization, minimizing impact to your team while maintaining the maximum return on investment. Reach out today, for assistance with creating a test or reviewing processes for compliance.

Subscribe to Our Newsletter

ON WATCH, ALL THE TIME

Featured Articles

Point-to-Point Encryption (P2PE) in the payment card industry involves deploying a recognized solution by the PCI council, where hardware, processes, and technology undergo rigorous testing against the current P2PE Standard v3.1 or earlier versions. The P2PE standard combines a recognized and certified PTS device with software and encryption methods to allow cardholder data to be encrypted upon swipe and transmitted encrypted throughout the merchant environment until decrypted within a decryption environment, inaccessible to the merchant.
In today’s rapidly evolving cybersecurity landscape, achieving and maintaining PCI compliance is more critical than ever. With the latest update to PCI DSS 4.0.1, businesses must adapt to meet new standards designed to enhance security and flexibility. This updated PCI Compliance Checklist outlines the essential steps for staying compliant while optimizing your organization’s security posture.
As with many things in popular culture, the PCI Data Security Standard (PCI DSS) has many myths associated with it. The PCI DSS has existed for many years and despite the efforts of the PCI Security Standards Council (PCI SSC) and industry experts, many misconceptions and myths persist. Below we will cover some common PCI DSS myths vs. the reality.
The PCI DSS standard is largely responsible for dictating the way organizations all over the world approach cybersecurity and the protection of credit card data. As v4.0 of the standard approaches, organizations should aim to identify and plan updates for the aspects of their security and compliance programs that are most likely to be affected.
Employees of companies of all sizes are now either required to shelter in place or State and Government lock-downs are forcing companies to require their employees to work remotely. How will this impact your PCI-DSS Compliance?