A.5.24 - Information Security Incident Management Planning and Preparation
Description
To ensure the organization is prepared to respond to information security incidents in a swift, structured, and effective manner by establishing clear reporting channels, processing pipelines, and rapid escalation workflows.
SIEM Compliance
Sentio SIEM acts as the central technical foundation for your Incident Management Plan, ensuring that when an incident occurs, the team has the ingestion pipelines and notification architecture ready to execute immediately:
Robust Data Pipeline Preparation (Apache NiFi Backbone): CyberSift utilizes Apache NiFi as its core ingestion layer to predictably manipulate, enrich, and route logs. This ensures that critical security telemetry is structured and available before an incident happens, eliminating parsing delays when every second counts.
Structured Escalation Integration: Sentio’s alerting engine can be pre-configured to map directly to your organization’s formal incident response playbooks, routing specific anomalies to the correct stakeholder tiers automatically. An example of this would be “When a high severity alert comes in, push it to Pager Duty”
Reporting: Sentio features a dedicated Reporting Functionality that allows teams to instantly compile comprehensive, structured security reports. These reports act as the official audit trail for the incident, providing the precise data points required for post-incident reviews and driving continuous improvement across your security posture
Evidence
Notification Configuration Profiles
The organization can configure a simple NiFi flow to deliver high-severity to communication channels such as (Slack, Microsoft Teams, Email, PagerDuty and so on) to ensure security teams are instantly alerted.
This can realistically be anything and not necessarily only high severity alerting.
Sample showing high severity alerting to Freshdesk ticket