SOC 2 monitoring of controls (CC4.1): how a small team shows it checks itself
Updated
CC4.1 asks whether you check your own controls, not whether you have an internal audit department. The criterion reads: the entity "selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning" (KirkpatrickPrice). For a team of five that means someone who did not run a control looks at it on a schedule, writes down what they found, and the findings go to the person who can fix them (CC4.2). None of the four sources below, two audit firms and two vendors, names an interval or a required function; the auditor tests the cadence your own policy states. Confirm with your CPA firm.
What the criterion says, and what the points of focus add
Linford & Co, an audit firm, says the two monitoring criteria are COSO principles 16 and 17 and admits they read "a little vague," which is why the AICPA attaches points of focus; it also says an entity need not have a control for each point of focus (Linford). AuditBadger, a vendor, puts it the same way: the points of focus "help interpret the criteria; they are not separate requirements" (AuditBadger). The points themselves, as Linford and hicomply list them (hicomply):
- a balance of ongoing and separate evaluations;
- the rate at which the business and its processes change;
- the current control set as the baseline;
- evaluators who understand what they are evaluating;
- ongoing evaluations built into business processes;
- scope and frequency of separate evaluations varied by risk;
- separate evaluations performed periodically for objectivity;
- a range of evaluation types, such as penetration tests, third-party assessments and internal audits.
CC4.2 then asks that deficiencies are evaluated and communicated "in a timely manner" to the people responsible for fixing them, "including senior management and the board of directors, as appropriate," and that management tracks whether they are fixed (Linford) (hicomply).
Who may do the checking
Linford gives two rules: a person cannot monitor their own work, and the monitor must understand the process well enough to "recognize and distinguish between what is expected and variances" (Linford). Its worked example fits a small company: an employee outside engineering picks a dozen production changes a year and checks each for authorization, peer review and QA approval, then reports the result to management. KirkpatrickPrice's example is a reporting cadence: department heads receive reports every two weeks and leadership meets monthly to review them and decide on changes (KirkpatrickPrice). Neither says the checker must be a dedicated role. At a company with no second team, the co-founder who does not deploy can sample engineering's records, and the Security Owner can sample everyone else's; an outside advisor once a year covers the Security Owner's own work.
Where the four sources differ
| Topic | Linford (audit firm, 2023) | KirkpatrickPrice (audit firm, 2019) | hicomply (vendor) | AuditBadger (vendor, 2026) |
|---|---|---|---|---|
| Minimum frequency | Key controls at least annually, in one review or spread over the year | Gives an example (biweekly reports, monthly meeting), no minimum | None | None; by risk and change |
| Who checks | Not the person who runs the control; must know the process | Knowledgeable personnel | Evaluators with sufficient knowledge | Suitable competence and objectivity |
| Internal audit | One evaluation type among eight | One of three examples | One of three examples | Not mentioned |
| Evidence named | Documented proof a manual control was performed | The meetings and reports you can describe | Tracking that deficiencies are fixed on time | Schedule and rationale, monitoring history, review results, findings with follow-up |
| Sells | SOC audits | SOC audits | A GRC platform | Evidence and control tracking software |
Dates: Linford's post is by a partner and CPA, published 25 January 2023; KirkpatrickPrice's is from 11 January 2019, so both postdate the 2017 criteria but are not recent. hicomply's page shows no visible date (its page markup says July 2026), and AuditBadger's says reviewed 23 September 2026. None quotes the AICPA text beyond the criterion wording, so read all four as practitioner views.
The one point the sources leave open
Whether a company with no internal audit function needs to create one. Every source lists internal audit as a type of evaluation; none says it is required, and none says in so many words that it is optional for a small company. What they do say is enough to plan around: Linford's two rules on who may check, and AuditBadger's point that access reviews, restore tests and penetration tests "do not cover the whole control system by themselves," so a periodic look at the wider control set, including governance and communication, is also expected (AuditBadger). If your auditor expects more, ask them which point of focus they are reading from.
A monitoring calendar a small team can run
An example, built from free templates on this site, not a requirement. Each row names the record it leaves, because the record is what the auditor samples.
| Cadence | Check | Kind | Record |
|---|---|---|---|
| Weekly | Alert and log review by the on-call engineer | Ongoing | Dated review note; see logging requirements |
| Monthly | Spot check of one control by someone who does not run it (Linford's change sample, or a hire's acknowledgment) | Separate | A row in the exception register or a ticket |
| Quarterly | Access review, restore test, metrics report to management | Separate | access review, restore test log, security metrics report with signed minutes |
| Annually | Policy review, penetration test, independent evaluation of the risk register | Separate | annual policy review, pen test scope and report, risk register with the evaluator's note |
For CC4.2, keep one findings list. AuditBadger's example control is a single register covering pen test issues, failed monitoring tests, audit observations and incident follow-ups, each with severity, owner, due date and status, with open items reported to leadership quarterly; the places it says companies slip are pen test findings left in a PDF, alerts sent to channels nobody watches, and leadership that "first hears about a control gap from the auditor" (AuditBadger). Linford makes the same point from the other side: the external examination should validate what management already learned from its own monitoring, not be "the first exposure" (Linford).
What the generated policies say
Policyseed sells a kit, so read these as one example, not a requirement. In the generated set the monitoring commitments sit in the Risk Assessment and Management Policy and the Information Security Policy; both list CC4.1 and CC4.2 in their criteria mapping.
Control operation is monitored through defined evidence: access reviews, vulnerability scans, backup and restore tests, incident metrics, vendor reviews and training completion. When monitoring shows a control has failed, the related risk is re-scored and, if it reaches High or Critical, a triggered assessment is opened.
Risk Assessment and Management Policy, item 4.9
Control monitoring. Engineering, People Operations and the Security Owner collect the evidence in 4.9 on the cadence set in the relevant policy, record results against mapped risks and raise a ticket for any control not operating; the Security Owner reviews results monthly and re-scores affected risks.
Risk Assessment and Management Policy, item 5.9
Findings from internal reviews, external audits, penetration tests and post-incident reviews are entered in the register or linked to an existing risk within ten business days, so one prioritized action list exists.
Risk Assessment and Management Policy, item 4.12
At least annually, someone who does not own the register (a member of Executive Management, an internal reviewer or an external advisor) evaluates whether the assessment was complete, scores consistent and treatments carried out, and records the outcome.
Risk Assessment and Management Policy, item 4.13
Management reporting. The Security Owner delivers a written status report to Executive Management at least quarterly covering open risks, incidents, vulnerability and patch status, access review results, vendor reviews and progress against objectives. Decisions are minuted.
Information Security Policy, item 5.4
Item 4.13 is the policy's answer to Linford's first rule: the person who owns the register does not evaluate it. The quarterly report in item 5.4 is the CC4.2 channel, and the security metrics report gives it a format with a Not met column. How the auditor samples these records is covered in SOC 2 sampling; what a recorded failure looks like in the report is in exceptions and qualified opinions.
Frequently asked questions
- Does SOC 2 require an internal audit function?
- None of the four sources on this page says so. Linford & Co, KirkpatrickPrice and hicomply each list internal audit as one type of evaluation among several (penetration tests, third-party assessments, vulnerability scans), and AuditBadger does not use the term at all. Linford's two rules are the ones to meet: the person checking a control cannot be the one who runs it, and they must understand the process well enough to tell expected from wrong. At a small company that can be a co-founder checking engineering's work, or an outside advisor once a year.
- What is the difference between ongoing and separate evaluations?
- The criterion says ongoing and/or separate, and none of the sources defines the terms outright. Reading the points of focus as Linford and hicomply list them, ongoing evaluations are built into the business process (an alert reviewed each week, a dashboard someone owns) and separate evaluations are periodic reviews done for objectivity, with scope and frequency varied by risk (a quarterly sample of changes, an annual review of the whole control set). A mix of both is a point of focus, not a rule that each must exist.
- How often must controls be monitored under CC4.1?
- The criterion sets no interval. Linford's view is that key controls should be assessed at least annually, as one annual review or as smaller monthly or quarterly reviews that cover every control over the year. KirkpatrickPrice's example is biweekly reports and a monthly leadership meeting. These are an audit firm's recommendation and an example, not an AICPA number; the auditor tests the cadence your own policy states.
- Do points of focus have to be implemented one by one?
- No. Linford says an entity need not have a control for each point of focus, and AuditBadger says the points of focus help interpret the criteria and are not separate requirements. They are the auditor's reading guide. Use them to check your own monitoring for gaps, not as a checklist to tick.
- What evidence does an auditor ask for under CC4.1 and CC4.2?
- Linford: documented evidence that a manual control was performed, for example a peer's approval recorded on a change. AuditBadger: the evaluation schedule and its rationale, monitoring history, management review and assessment results, and findings with their follow-up actions; for CC4.2, a findings register export, a management deck showing open deficiencies, a ticket trail from finding to verified fix, and a remediation deadline rule. hicomply adds that management should track whether deficiencies are fixed on time.
- Is a penetration test enough to satisfy CC4.1?
- The sources list penetration testing as one evaluation type, not as the whole answer. AuditBadger says access reviews, restore tests and penetration tests support particular safeguards but do not cover the whole control system by themselves, and that a periodic assessment of the wider control system, including governance and communication, is also expected. See the penetration testing guide for what the test itself proves.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.