INCIDENT RESPONSE · SOC 2 · ISO 27001 · PCI DSS
Incident response management software with a plan, a register and notice deadlines
Record each incident the day you become aware of it, see the notification deadline, and keep the written decision to notify or not. The plan, the test and the register sit with your other controls.
From $47/mo · Prices published · No sales call · Monthly billing
Audit readiness
0 %
Built for teams of 5 to 200
What incident response management software does for an audit
Incident response management software keeps the incident response plan, the record of every incident and the evidence that the plan was tested in one place. The register shows when you became aware of each incident, who owns it, what was reached and how the notification question was answered, including a written decision not to notify with its author and date. Auditors for SOC 2 (CC7.3 to CC7.5), ISO 27001 (Annex A 5.24 to 5.28) and PCI DSS (requirement 12.10) sample exactly these records.
The buyer is usually a security or compliance lead at a company of 5 to 200 people. The plan exists as a document, incidents live in chat threads and a ticket queue, and nobody can show the auditor one list with dates and outcomes. Enterprise incident platforms answer a different question: paging, war rooms and forensics. A small team needs the plan, the register and the proof.
Complies tracks incidents as records tied to controls. The incident register is on every paid plan: Starter is $47 a month billed yearly, Growth is $119 and Scale is $299. The honest limit is below, Complies does not page on-call staff or run forensics.
Complies assists with compliance workflows. It is not legal advice, and it does not certify you or guarantee audit outcomes. Your auditor decides; Complies gets you ready.
The three things an auditor asks about incident response
A plan with an owner and a test date
The auditor asks who owns the incident response plan, when it was last reviewed and when you last exercised it. PCI DSS 12.10.2 expects a review and test at least every 12 months. The plan sits on the calendar with an owner, and the exercise is a dated task.
obligation trackingA register of every incident
Each incident is logged with the day you became aware, scope, owner and status. Nothing is deleted. A closed incident keeps its history, which is what a SOC 2 sample of CC7.4 will read.
evidence collectionA notification decision in writing
Whether to notify a regulator, customers or a card brand is a decision with a clock on it. The register shows the deadline and stores the outcome, including a decision not to notify, with reasoning, author and date.
control mappingIncident response tools compared by who they are built for
Incident tools split into on-call and response platforms for engineering teams and compliance platforms that keep the record auditors test. Where a vendor publishes no price, the table says so.
| Tool | Built for | Pricing | Best fit |
|---|---|---|---|
| Complies | Security and compliance leads at 5 to 200 person companies | Published. $47, $119 and $299 a month billed yearly | Incident register, notice deadlines and the plan test as audit evidence |
| On-call and incident platforms (PagerDuty, incident.io and similar) | Engineering and SRE teams | Per-seat plans, check each vendor page | Paging, war rooms and timelines during the incident |
| Enterprise GRC suites (Archer, MetricStream, ServiceNow) | Large regulated enterprises | Quote only, no public benchmark | Incident management across many business units |
| A spreadsheet and a chat channel | Anyone starting out | No licence cost | Few incidents and one person who keeps it current |
If an incident means paging people at 3 a.m., you need an on-call tool and a compliance record. They are different jobs, and many teams run both. For a comparison against the quote-only suites, see MetricStream alternatives, Archer alternatives and AuditBoard alternatives.
What a small team gets from a compliance-grade incident register
The clock is visible
Each incident shows its notification deadline from the day of awareness, so an overdue decision is flagged instead of discovered in the audit.
Decisions not to notify are defensible
A written, dated and attributed no-notify decision is what a regulator or auditor asks for after the fact.
Nothing disappears
Incidents are closed, never deleted, and a wrongly recorded decision is reopened with both steps kept in its history.
One test counts twice
A documented tabletop counts toward SOC 2, ISO 27001 and PCI DSS at once because controls are cross-mapped.
Lessons become tasks
Post-incident findings turn into owned tasks and feed the risk register with a score and a treatment.
Published price, no demo
See the cost before a sales call and pay monthly if you need the program for one audit cycle.
How an incident runs through the register in four steps
Record it the day you know
Log the title, what was reached and an owner even before severity is clear. The notice clock starts on that day.
Work it and keep notes
Add updates to the record. Every step lands in the incident history with who did it and when.
Decide on notification
A manager or admin records whether notice was sent or why it is not required, with the reasoning.
Close and learn
Close the incident, turn findings into tasks and schedule the yearly plan test.
Who this is for, and who it is not
A GOOD FIT WHEN
- Your SOC 2, ISO 27001 or PCI DSS audit asks for the incident plan, a test and a list of incidents.
- Incidents currently live in chat and nobody can produce one dated list.
- A regulation gives you a fixed window to notify and you need to track it.
- You want to see the price before a sales call.
LOOK ELSEWHERE WHEN
- You need paging, on-call schedules or a war room during live incidents.
- You need forensics, SIEM or automated detection.
- You want the incident plan written or the tabletop run for you. Your team or a consultant still does both.
- You need a FedRAMP environment or CMMC support.
Questions about incident response management software
It is software that records security incidents and manages their handling from detection to closure, with owners, status, deadlines and history. Compliance-focused versions also keep the incident response plan and the evidence it was tested, which is what SOC 2, ISO 27001 and PCI DSS auditors sample.
For a team of 5 to 200 people that must pass an audit, a compliance platform such as Complies fits because the register, notice deadlines and plan test live beside your other controls. Engineering teams that need paging should add a dedicated on-call tool.
The Security criterion expects incident response procedures, tested through CC7.3 (evaluating events), CC7.4 (responding) and CC7.5 (recovering). Auditors typically ask for the plan, evidence it was reviewed, and a sample of real incidents with their handling.
PCI DSS 12.10.2 requires the plan to be reviewed and tested at least once every 12 months. SOC 2 and ISO 27001 set no fixed number, but annual testing is the common expectation, plus a review after any significant incident.
Yes. ISO 27001:2022 Annex A 5.24 covers planning and preparation, 5.25 assessing events, 5.26 responding, 5.27 learning from incidents and 5.28 collecting evidence. You document the process and keep records that it is followed.
It depends on the rule. HIPAA breach notification must go out without unreasonable delay and no later than 60 days after discovery. SEC Regulation S-P amendments set 30 days for customer notice. The register shows the deadline for the rule that applies to your company.
No. Software records, times and evidences the response, but people investigate, contain and decide. Complies does not page staff or perform forensics, and it does not replace legal advice on whether notice is required.
Complies publishes $47, $119 and $299 a month billed yearly, with the incident register on every paid plan. Enterprise suites quote by scope, and on-call tools price per seat on their own pages.
Yes. Complies bills monthly at $95, $239 and $599 or yearly at roughly half that rate, so a team that needs one audit cycle can stay flexible.
Frameworks and guides
SOC 2 compliance software
ISO 27001ISO 27001 compliance software
PCI DSSPCI DSS compliance software
SOC 2SOC 2 Controls List With All 33 CC1 to CC9 Common Criteria
PCI COSTPCI DSS Compliance Cost for SaaS and Small Business
GRCArcher and MetricStream Alternatives for a Scaling Company
Put your incident record in order before the audit
Prices published, $47 to $299 a month. Monthly billing. Start today, no sales call.