Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Advisory firms document what should happen. Compliance monitoring checks what actually happened: whether your operations follow the laws and policies that apply to you. It needs dated evidence and one person accountable for correcting failures, on a schedule you keep. An annual audit cannot replace that work.
For a finance or security lead facing an insurance renewal and an audit in the same quarter, start with a monthly evidence set. Sample controls quarterly. Give every exception one owner and a deadline. That creates a record you can test rather than an evidence folder assembled from memory.
Why does the evidence folder go stale?
Evidence goes stale when collection starts only after an auditor requests it. A new system or a vendor change can make an earlier record insufficient. Monitoring checks adherence between audits. An audit independently examines the controls and evidence within its scope; audits can be internal or external.
A-LIGN's 2026 Compliance Benchmark Report, as cited by Bright Defense, found that 97% of surveyed organizations run at least two compliance audits a year. That finding describes the survey respondents, not every business. It does explain why treating each evidence request as a separate project creates repeated work.
A policy shows intent. A dated record of the control running, such as a change ticket, shows that it operated. If a control did not run in March, no document created in October can prove that it did. Ask for the artifact, not another copy of the policy.
What do you pull before you set the cadence?
Last year's audit request list and your latest cyber-insurance questionnaire show which records you have been asked to produce. Mark the requests you cannot answer with dated evidence. Use those gaps to select your first controls.
- Collect both documents and mark missing or outdated evidence.
- Choose five or six frequently requested controls as your starting set.
- Name one owner and a collection date for each control.
- Run that set for two quarters before expanding it.
Choose controls based on your obligations and exposures, not just the easiest records to collect. An access-removal control matters because a departed employee's account can remain usable. A completed spreadsheet matters only if someone checked the accounts behind it.
Which evidence should be collected every month?
Prioritize records that change frequently. For a mid-market healthcare or financial firm, the following is a practical starting set, subject to the contracts and requirements that apply to it:
- Access grants and removals, including departures and role changes
- Administrator privilege changes, with the approver identified
- The vendor list, showing new and ended relationships
- Open exceptions, with owners and closure dates
- Training completion, including overdue assignments
- The incident and near-miss log, including decisions to close items without further action
Name the person who pulls each record and the day it is due. Monthly collection takes staff time. Protect that time and keep the initial scope small enough to sustain. Some controls need more frequent operation; a monthly evidence review does not mean you wait a month to remove a departed employee's access.
If your insurer asks how staff handle suspicious email, a policy saying employees receive training is insufficient. Keep completion records and evidence of reporting activity. Separate what staff were told to do from what the records show they did.
How should a quarterly review be documented?
Sample controls rather than rereading the entire policy library. Choose records that let the reviewer test whether the control operated as written. Record the date, reviewer, sample and findings.
- Select controls based on risk, recent changes and previous findings.
- Identify the underlying records sampled and the period they cover.
- Compare those records with the control's stated requirements.
- Document failures, corrective actions, owners and due dates.
For access removals, compare departure records with account-disable timestamps. A completed checklist without that comparison does not establish whether access ended on time. Record enough detail that another reviewer can repeat the test.
What resets the evidence between reviews?
A material change calls for an extra check. Do not wait for the quarterly meeting when one of these events changes the control or the exposure:
- A new system, application or cloud service goes live
- A vendor is added or changes how it handles your data
- A key employee leaves or an administrator changes roles
- A vendor issues a new assurance report or the available report no longer covers the period you need
Recheck the vendor list and available assurance reports quarterly. Confirm which service each report covers and whether relevant findings remain unresolved. Having a report in the folder does not establish that it covers the service your business uses.
Do not leave the logs entirely with your IT provider. The provider can supply records, but someone accountable inside your business must confirm that they demonstrate what your policy requires. Ask for the raw records, the export date and the period they cover, so you can test them yourself.
The vendor exposure is local, too. The Fort Worth Star-Telegram reported in 2026 that an incident at a third-party software company exposed employee data at Fort Worth and Crowley ISDs. For your own vendors, establish who sends incident notices and who inside your business receives and escalates them.
Who owns an exception when it stays open?
An exception records a departure from a requirement or a risk accepted for a defined period. It needs enough detail for leadership to understand what remains exposed:
- One named owner
- A stated reason it remains open
- A compensating control that reduces the risk
- A closure date
Escalate an exception that remains open through two review cycles, or any control whose evidence cannot be produced. Take it to the executive responsible for the program. If someone repairs the failure, retain the finding and the corrective-action record rather than quietly replacing the missing evidence.
The program also needs an accountable executive. That is the role a virtual CSO fills. We operate security programs across all 13 risk domains and report directly to the board. Whoever holds that responsibility, distinguish the executive accountable for the program from the person assigned to close each finding.
What should the board see each quarter?
Report unresolved exposure and decisions needed. A tool inventory does not tell the board whether access reviews ran or whether a vendor finding remains open.
| Item | What the board needs to see |
|---|---|
| Open exceptions | The count and any past their closure date |
| Ownership | The named owner of each open exception |
| Closure date | When each exception is due to close |
| Trend | Whether open items are falling quarter over quarter |
| Evidence gaps | Controls whose evidence could not be produced |
| Escalations | Items open through two review cycles and the action proposed |
Explain changes in the count. More findings can reflect better testing rather than worse controls. Fewer findings can reflect completed remediation or a narrower review. The board needs that distinction before deciding where to assign resources.
How do you set the cadence before the next audit cycle?
Assign the program owner before buying another platform. Software can collect records and flag missing evidence. It cannot accept risk on your behalf or decide whether a corrective action is adequate.
We are based in Fort Worth and serve organizations in Texas, California, Nevada and New Mexico. We are Texas DPS-licensed and CPP, CISSP, CISM credentialed. Our work is operating the program, not stopping at an assessment.
Bring your latest audit request list and insurance questionnaire to a 30-minute risk discussion. Book a 30-minute risk discussion, use the contact inquiry form, or call 817-677-0515. For sector-specific context, see our security services for healthcare organizations and financial services firms.
Frequently asked questions
What is compliance monitoring, in plain terms?
Compliance monitoring is the ongoing internal review of whether operations follow applicable laws, regulations and company policies. It uses records and tests to identify failures between audits. Each finding needs an accountable owner and a documented response.
How is compliance monitoring different from an audit?
Monitoring is part of running the business: collecting evidence, checking controls and correcting failures on a defined schedule. An audit independently examines a defined scope at a particular time or over a stated period. Audits can be internal or external, and monitoring does not replace them.
Which evidence should a healthcare or financial firm collect each month?
Start with access changes, administrator privileges, vendor changes, open exceptions, training completion and incident records. Confirm the set against applicable obligations, contracts and prior audit requests. Monthly collection is a starting cadence, not permission to delay urgent control actions.
Do we need software to run compliance monitoring?
No dedicated platform is required to start. A small control set can run with assigned owners, a calendar and dated records stored with appropriate access controls. Software can automate collection and reminders, but someone must review the evidence and resolve findings.
What should a compliance plan include?
A compliance plan should define its scope, applicable obligations, risk priorities, control owners and review schedule. It should also specify how findings are corrected and reported to leadership. For each control, identify the evidence that will demonstrate it operated.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article6 min read
IoT Security Solutions: How to Inventory and Segment Devices
Connected cameras and building controllers need an inventory, network separation, unique credentials and a named responder. This is the order to work in and who owns each step.
Read article