SOC 2 continuous monitoring: control checks and security monitoring

For startups heading into a SOC 2 Type 2 audit. What compliance tools usually call continuous monitoring is an automated check of your settings. CC7.2 to CC7.4 also ask whether anyone watched what happened, and what they did about it. Jutsu does both: daily checks on connected systems, and 24/7 detection, triage, and recorded response.

Start free
Jutsu dashboard
Jutsu · SOC overview
  • Control checks every dayAWS, Google Cloud, GitHub, Google Workspace, Cloudflare, Vercel, Railway, and your hosts, each resource pass or fail.
  • Security monitoring around the clockEvery alert from a connected source gets a category, severity, risk score, and verdict.
  • Response on the recordOn the Startup plan a person approves each action. Every action is logged and can be reverted.
  • Records for the whole windowThe Startup and Growth plans keep data for 365 days, with 90 days searchable.

What is SOC 2 continuous monitoring?

SOC 2 continuous monitoring means two different things

Search for SOC 2 continuous monitoring and you'll find two jobs under one name. The first is control monitoring: a tool checks your settings on a schedule and flags drift, such as MFA turned off or a storage bucket made public. Compliance platforms sell this, and it matters.

The second is security monitoring: collecting the logs your systems produce, raising alerts, deciding which alerts are real, and responding. That is what the system operations criteria, CC7.2 to CC7.4, describe. A settings check can show that logging is turned on. It can't show that anyone read the logs.

A Type 2 report covers a period, commonly 3 to 12 months, so your auditor looks for both kinds of record across the whole window, not just on the day of the audit.

What CC7.2, CC7.3, and CC7.4 ask for

The AICPA's Trust Services Criteria group these under system operations, the CC7 series. In plain words:

  • CC7.1: find configuration changes that open new weaknesses, and newly disclosed vulnerabilities that affect you.
  • CC7.2: watch your systems for unusual activity that could mean an attack, a natural disaster, or an error, and analyze it to decide whether it is a security event.
  • CC7.3: decide whether a security event is an incident that could stop you meeting your objectives, and act to prevent or fix the damage.
  • CC7.4: respond to incidents through a defined incident response program: understand, contain, fix, and tell the people who need to know.
  • CC7.5: recover from incidents, find the root cause, and stop them happening again.

Where the wording comes from

The list above is our paraphrase. The criteria themselves are in the AICPA's 2017 Trust Services Criteria, with revised points of focus (2022), which SOC 2 reports use today. The evidence auditors ask for, below, follows soc2auditors.org's guide to logging and monitoring controls. Both checked Nov 2026.

In October 2026 the AICPA published an exposure draft of revised criteria that renumbers this series. If it is issued as drafted, it applies to engagements beginning on or after December 31, 2027 (summary on soc2auditors.org, checked Nov 2026). Until then, the CC7 numbers above are the ones your auditor uses.

Do you need a SIEM for SOC 2?

No. The criteria don't name a product. CC7.2 asks for monitoring and analysis, and a central log store with alerting is one design an auditor can accept, judged against your risks.

What you do need is evidence that the monitoring ran. Auditors commonly ask for audit logging turned on in every cloud account and region you use, a list of log sources checked against your systems, retention that reaches back to the start of the period, alert rules and who gets paged, and alert records with triage notes.

A SIEM is one way to get there, if someone reads its alerts. For a startup without a security team, the hard part is rarely collecting logs. It's the review, every day, for the whole audit window. SIEM for startups compares the ways to cover it.

SOC 2 logging requirements, in practice

The criteria don't list log types or a retention period. These habits leave an auditor something to test, and security monitoring for startups lists what to watch in each system:

  • Turn on audit logging everywhere you run: AWS CloudTrail, Google Cloud audit logs, the Azure Activity Log, Google Workspace, and GitHub.
  • Keep logs for at least the whole audit period. For a 12-month Type 2 window, that means 12 months or more.
  • Alert on the events that matter: sign-ins from unusual places, new admins, MFA turned off, public storage, and leaked secrets.
  • Record what was decided about each alert, and by whom.
  • Check that each log source is still sending. A source that went quiet in month four is a gap in your evidence.

How Jutsu covers both halves

Jutsu runs the control checks and the security monitoring in one product, from the same connections.

  • Control checks: Jutsu checks connected AWS, Google Cloud, GitHub, Google Workspace, Cloudflare, Vercel, and Railway accounts, and the hardening of your Windows, Linux, and macOS hosts, every day. Microsoft Azure adds 35 CIS-based checks, and Supabase checks settings such as member MFA, SSL enforcement, and row-level security. Each resource gets a pass, fail, or not-applicable result, and the results feed your recurring evidence tasks.
  • Detection: connected sources are watched around the clock by built-in rules, among them AWS rules such as Security group opened to the world and S3 bucket made public, and 19 Azure rules.
  • Triage: each alert gets a category, severity, risk score, and verdict. Related alerts become one incident, and alerts the AI isn't sure about go to a person.
  • Response: on the Startup plan a person approves each action before it runs, and Growth adds policy-guided automation. Every action is recorded with its status (pending, running, succeeded, failed, or reverted).
  • Records: incident reports and SOC activity reports, daily and weekly on the Startup plan. The Startup and Growth plans keep data for 365 days, with 90 days searchable.
  • Source health: Pipeline Health shows when each source's events last arrived, and a rule whose source sent nothing in 24 hours is marked Silent.
  • Audit access: read-only access for your auditor, limited to the frameworks and dates you choose.

What stays with you

Jutsu is software with AI agents, not a team of people watching your alerts. Someone on your team approves responses, owns the written incident response plan, and runs the review after an incident. Your auditor decides whether the controls operated. Jutsu supports readiness and evidence collection. Your team and your auditor remain responsible for the audit, and Jutsu does not guarantee an audit outcome.

SOC 2 CC7 criteria: config checks vs security monitoring

What each criterion asks, the kind of monitoring that answers it, and what Jutsu keeps as a record.

CriterionWhat an auditor asksConfig check or security monitoring?What Jutsu records
CC7.1: find weaknesses and risky configurationHow do you find misconfigurations and newly disclosed vulnerabilities, and what did you do about them?Mostly a config check. This is the part compliance tools call continuous monitoring.A daily pass, fail, or not-applicable result per resource on connected systems, with fix steps for failures. GitHub's Dependabot and code scanning alerts arrive as events.
CC7.2: monitor for anomaliesWhich systems send logs, who reviews the alerts, and can you show alert records across the whole period?Security monitoring. A config check can show logging is on, not that anyone read the logs.Every connected source's events, the alerts raised from them, and each alert's category, severity, risk score, and verdict. Source health shows when each source last sent events.
CC7.3: decide which events are incidentsWhat makes an event an incident, who decided, and when?Security monitoring, plus your written severity criteria.Triage verdicts, incidents built from related alerts with their own severity and confidence, alerts sent to a person, and case history with comments and evidence.
CC7.4: respond to incidentsShow your response plan, and incident records from detection to closure.Security monitoring, plus your written plan.Each response action and its status, approved by a person on the Startup plan, and incident reports.
CC7.5: recover and learnShow the recovery steps and the review after an incident.Your process. Tools hold the records.Incident reports, reverted actions in the execution history, and SOC activity reports. The review itself is your team's work.

Criteria paraphrased from the AICPA's 2017 Trust Services Criteria (revised points of focus, 2022); auditor questions follow soc2auditors.org. Both checked Nov 2026. Your auditor decides what evidence is enough for your system.

Three steps, end to end

  1. Connect the systems in scope

    Connect AWS, Google Workspace, GitHub, or your hosts. Each documented connection takes about 10 minutes or less.

  2. Checks and monitoring start

    Jutsu checks settings every day and watches events around the clock, from the same connections.

  3. Show your auditor the records

    Invite your auditor with read-only access, limited to the frameworks and dates you choose.

What Jutsu records for SOC 2 monitoring

  • Daily control checks

    A pass, fail, or not-applicable result for each resource, feeding your evidence tasks.

  • 24/7 detection

    Built-in rules watch connected cloud accounts, sign-ins, code, and hosts around the clock.

  • Triage records

    A category, severity, risk score, and verdict on every alert.

  • Incidents and escalations

    Related alerts grouped into one incident, and unsure ones sent to a person.

  • Response history

    Each action with its status, approved by a person on Startup, and revertible.

  • Source health

    When each source last sent events, so a quiet source doesn't become a gap in your evidence.

Common questions

What is SOC 2 continuous monitoring?

Two things share the name. Control monitoring checks your settings on a schedule and flags drift, such as MFA turned off. Security monitoring collects logs, raises alerts, decides which are real, and responds, which is what CC7.2 to CC7.4 describe. A Type 2 audit looks for records of both across the audit period.

Do I need a SIEM for SOC 2?

No. The Trust Services Criteria don't name a product. You need monitoring that runs and evidence that it ran: logging turned on in the systems in scope, retention that covers the audit period, alert rules, and records of what was decided about each alert. A SIEM can produce that if someone reviews its alerts. Jutsu produces it with AI triage and a person approving responses.

What are the SOC 2 CC7.2 requirements?

CC7.2 asks you to monitor your systems for unusual activity that could mean an attack, a natural disaster, or an error, and to analyze it to decide whether it is a security event. Auditors commonly ask for audit logging in every cloud account you use, a list of log sources, retention back to the start of the period, alert rules, and alert records with triage notes.

What are the SOC 2 logging requirements?

The criteria don't list log types or a retention period. In practice, turn on audit logging everywhere you run (for example AWS CloudTrail, Google Cloud audit logs, the Azure Activity Log, Google Workspace, and GitHub), keep logs for at least the whole audit period, alert on the events that matter, and record what was decided about each alert.

Is a compliance tool's continuous monitoring enough for CC7.2?

A settings check covers much of CC7.1 and shows that logging is turned on. It doesn't review the logs, so on its own it doesn't show that anyone detected, evaluated, or responded to security events. Your auditor decides what is enough for your system, so ask them early.

How long should we keep logs for SOC 2?

At least as long as your audit period, so the auditor can test any date in it. A 12-month Type 2 window needs 12 months or more. In Jutsu, the Startup and Growth plans keep data for 365 days, with 90 days searchable.

Does Jutsu make us SOC 2 compliant?

No tool can. An independent auditor issues the report. Jutsu runs the control checks and the security monitoring, keeps the records, and gives your auditor read-only access. It does not guarantee an audit outcome.

Which Jutsu plans include this?

Compliance, including the daily checks, comes with every paid plan, and approval-based response starts on the Startup plan: Startup ($149/month), Growth ($499/month), or Enterprise (custom quote). The Free plan shows the monitoring workflow but doesn't include compliance.

Show your auditor monitoring that ran

Start on the Free plan to see the workflow. Compliance and approval-based response come with the Startup plan.

Start free

Subscribe to our newsletter

Get the latest security tips, product updates, and news delivered to your inbox.