Compliance evidence collected year-round, not assembled in a panic

ManySignal generates evidence packages for: SOC 2 Type II (CC6, CC7, CC8 controls for security monitoring, incident response, and change management), ISO 27001 (A.12 Operations Security, A.16 Incident Management), PCI DSS 4.0 (Requirements 10, 11, 12 for log management, testing, and incident response), HIPAA (45 CFR 164.308 security incident procedures), and GDPR Article 33/34 incident notification. Evidence is continuously collected throughout the year, not assembled at audit time.

ManySignal maintains a continuous evidence library: alert logs with triage outcomes (proving monitoring is active and alerts are investigated), detection rule test results (proving controls are tested), configuration snapshots (proving security settings are maintained), and incident response records (proving procedures are followed). Auditors receive read-only access to a structured evidence repository rather than requiring the security team to compile it.

When an incident is classified with a data breach indicator, ManySignal starts a countdown timer based on the incident discovery timestamp and the organization's GDPR obligations. Notifications are sent to the assigned DPO as the 72-hour deadline approaches. ManySignal also generates a draft Article 33 notification pre-populated with the available breach information (date of breach, categories of data, estimated number of individuals, likely consequences).

Yes. Compliance officers can be granted read-only access to the ManySignal evidence repository with permissions scoped to their framework requirements. They can pull annual evidence packages, search for specific control evidence, and generate audit-ready exports independently. This reduces the burden on the security team during audit periods significantly.

ManySignal maps evidence to multiple frameworks simultaneously. An alert investigation record can serve as evidence for SOC 2 CC7.2, ISO 27001 A.16.1.5, and PCI DSS Requirement 12.10 at the same time. The evidence export wizard lets compliance officers select the target framework and generates a structured package with only the relevant control mappings — preventing duplicative evidence collection across frameworks.

Initial connector configuration and evidence collection begins within 24–48 hours of deployment. Historical evidence imports from existing tools (SIEM exports, ticketing system records) take 1–2 weeks depending on data volume. A complete evidence library for a 12-month audit period typically requires the platform to be running for that full period — for existing customers, the library is already built. For new deployments before an imminent audit, ManySignal provides a gap analysis showing which control evidence is already available versus what needs to be supplemented manually.

Yes. ManySignal maintains SOC 2 Type II certification (audited annually), ISO 27001 certification, and GDPR DPA (Data Processing Agreement) compliance for EU customers. The ManySignal SOC 2 report is available to customers under NDA for inclusion in their vendor risk assessment. Customers operating in regulated industries can reference ManySignal's certifications when documenting their third-party security controls.

When a case is closed with a data breach classification, ManySignal generates a structured incident report pre-formatted for regulatory submissions: discovery date and time, categories of personal data affected, estimated number of data subjects, likely consequences, and measures taken or proposed. The draft Article 33 (GDPR) or HHS breach notification (HIPAA) is pre-populated from the investigation evidence — compliance officers review, supplement with additional detail, and submit. All drafts are retained with the case evidence package.

Yes. For organisations operating across jurisdictions, ManySignal tracks concurrent notification deadlines: GDPR's 72-hour SA notification, HIPAA's 60-day HHS notification, SEC's 4-business-day material incident disclosure, and state-level breach notification laws. Each deadline is tracked from the discovery timestamp and escalates independently to the assigned DPO, CCO, or legal contact. ManySignal's jurisdiction configuration maps affected data subjects to the applicable notification requirements.

On contract termination, customers receive a full evidence export in structured JSON and PDF formats — all investigation records, alert logs, configuration snapshots, and compliance packages generated during the contract period. Exports are provided within 30 days of contract end and are formatted for long-term retention without requiring ManySignal software to read. The export includes metadata sufficient for retrospective audit response.