Point-in-time assessment vs continuous monitoring
Author
Audrey
NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.
Date Published
There's a marketing argument you'll run into the moment you start shopping for AI or vendor-risk tooling: point-in-time assessments are stale the day you get them; you need continuous monitoring. Vanta, among others, markets on exactly this line. It's a fair argument — and like most fair arguments, it's true in some cases and oversold in others.
If you own compliance at a credit union or an RIA, you don't need a philosophy of monitoring. You need to know which one your examiner is actually asking for, where the cheaper option is genuinely sufficient, and where paying for the recurring one is money well spent instead of money spent to look diligent. Let's take those in order.
First, what the words mean
A point-in-time assessment is a snapshot. As of a date, here's your AI vendor footprint, here's what each vendor does with data, here's how it maps to your oversight obligations. It's a dated artifact — a report — that says "this was true on July 11." Its strength is that it's finished: a thing you can hand to an examiner, file, and point to. Its weakness is exactly what the critics say — the world moves after the date on the page.
Continuous monitoring is a standing process that watches for change and tells you when something moves — a new OAuth app connected, a vendor's data-handling terms changed, a sub-processor added. Its strength is freshness. Its weakness is that "monitoring" without a decision attached is just a feed of alerts, and a feed nobody has time to action is not oversight. For a one- or two-person program — roughly 63% of TPRM programs, per the Ncontracts 2026 State of TPRM survey (n=173) — an unmanaged alert stream can be worse than a clean snapshot, because it creates a record of things you were told about and didn't get to.
What the examiner is actually asking for
This is the part that cuts through the marketing, and the answer differs by regulator.
If you're an RIA or broker-dealer, the Reg S-P amendments are unusually specific, and they lean toward ongoing. The rule text (17 CFR 248.30(a)(5)) requires written policies mandating "oversight, including through due diligence and monitoring, of service providers." The word monitoring is right there in the rule. That doesn't mean you must buy a real-time dashboard — it means your written program has to describe how you keep watching your providers over time, not just how you vetted them once. Reg S-P is also a named SEC Division of Examinations FY2026 priority, so this is a live question, not a someday one. A point-in-time report is the evidence; a described cadence for refreshing it is the program. You need both, and the second one is the part a pure snapshot doesn't give you.
If you're a credit union, the operative framework points the other way — toward proportionality. NCUA's vendor due-diligence expectations (07-CU-13 / SL 07-01, still operative; NCUA never adopted the 2023 interagency guidance) are explicitly scaled to risk: "reasonable alternative procedures," less analysis for non-complex, non-core vendors. NCUA also structurally can't examine your technology vendors directly — GAO confirmed as much (GAO-25-107197, May 2025), and Congress hasn't fixed it — so the diligence burden lands on you, but it lands proportionally. For a low-risk vendor, a point-in-time assessment reviewed on a sensible cadence is very likely "reasonable." Nobody is asking a credit union to monitor a marketing-copy tool in real time.
The honest synthesis: the examiner is asking for a defensible, repeatable process — not for a specific product. Continuous monitoring is one way to satisfy "ongoing." A point-in-time assessment on a documented refresh schedule is another. Both can pass. What fails is a single snapshot from eighteen months ago with no plan attached.
Where point-in-time is enough
Be suspicious of anyone who tells you monitoring is always the answer — that's the person selling the subscription. A snapshot is genuinely sufficient when:
- The vendor is low-risk and stable. A tool that never touches member or client data, with terms that don't change quarterly. A dated report plus an annual refresh is proportional and defensible.
- You're establishing a baseline. You can't monitor drift from a position you never measured. The first thing any program needs is one good snapshot — the "as of today, here's everything" report. Everything continuous is a delta from that.
- Your program can't action alerts yet. If it's you, a spreadsheet, and no time, a clean annual assessment you actually read beats a live feed you don't. Buying monitoring you can't staff is buying a liability with a timestamp.
- The artifact's job is to exist. Sometimes you need a thing to hand the examiner and file. A finished, dated report does that. A dashboard does not file.
Where the drift subscription earns its keep
And be equally suspicious of the opposite — that a once-a-year snapshot is "diligence." Continuous monitoring earns real money when:
- Your AI surface changes on its own. OAuth grants accrete quietly; people connect apps you never approved. Vendors ship AI features into products you already bought without a press release — we wrote about that silent expansion elsewhere. If your footprint moves between reviews, a snapshot ages fast, and the drift feed is how you catch the app that got connected in March.
- You have a higher-risk vendor touching real data. Proportionality cuts both ways: the vendor that processes member or client information with AI is exactly where "ongoing... monitoring" stops being optional language and starts being the thing an examiner probes.
- The breach clock is short. Reg S-P's incident-response requirements run on tight timelines — provider-to-firm notice measured in hours, customer notice in days. Knowing now that a provider's posture changed is worth more than finding out at your annual review.
- You can turn an alert into a decision. Monitoring pays off only if someone acts on it. If you (or a service that triages for you) can convert "this changed" into "here's what we did about it," the feed becomes evidence. If it just piles up, it's the opposite.
Side by side
| Point-in-time assessment | Continuous monitoring |
|---|---|---|
What it is | A dated snapshot you can file | A standing watch that flags change |
Best for | Baselines, low-risk/stable vendors, "give me an artifact" | Drifting footprints, higher-risk vendors, short breach clocks |
Examiner fit | Evidence — needs a refresh cadence around it | Satisfies "ongoing" — needs someone to action alerts |
Failure mode | Goes stale if never refreshed | Alert pile-up nobody has time to act on |
Reg S-P read | The evidence half of "due diligence and monitoring" | The monitoring half — but only if decisions attach |
A new OAuth grant is a new policy decision
Here is what "continuous" means in practice for AI tools. Your people can connect a new app on any day. Someone signs in to an AI note-taker with their work account, clicks "Allow", and the app now holds whatever scopes it asked for. Nothing was bought, and nobody filed a request.
That grant is a new tool in your environment. A new tool is a new policy decision, with three possible answers:
- Allowed. The scopes are acceptable and the vendor passes your review. Record the decision with a date.
- Needs approval. It's fine for some people or some uses. Name who signs off.
- Denied. Revoke the grant and write down why.
Revoking a grant doesn't keep it gone. Microsoft's own Entra documentation says "Revoking the current granted permission doesn't stop users from re-consenting to the application's requested permissions." Blocking takes its own setting. In Google Workspace, an admin can mark an app "Blocked", meaning it "can't access any Google data." In Entra, you configure how users consent to applications.
So the test for any monitoring, bought or homemade, is whether each new grant reaches a decision. A feed that says "new app connected" is only the alert. The dated entry that says allowed, needs approval or denied is the oversight. If you work on a refresh cadence instead of a live feed, the same rule applies: at each review, every grant that wasn't there last time gets a decision.
For how to turn the grants you already have into a first policy, see reading OAuth grants as your first policy draft.
The honest close
Neither one is more responsible than the other in the abstract. A point-in-time assessment you actually read and refresh beats continuous monitoring you can't staff, and continuous monitoring on a fast-moving, data-touching vendor beats a snapshot you'll forget by autumn. The right answer is almost always: one solid baseline, then a refresh cadence proportional to how fast each vendor actually changes — real-time for the risky and mobile, annual for the stable and boring.
That's the ladder we're built around, and we'll say plainly which rung you're on. The AI Trust Report is the point-in-time baseline: dated, and run with you. AI risk tracking is the watch. In the words of our pricing page: "Tracking keeps every scan and shows what changed. Part of the Enterprise plan." It's also sold as an add-on. Tracking shows you what changed; deciding what each new grant may do stays with you. Start with the snapshot, and add the watch only where it earns its keep.
Not sure a single report answers your questions in the first place? Start with AI vendor-risk assessment vs a free AI-risk checklist. If you haven't listed what's connected yet, read Before you write AI policy, find out what's connected. Request an AI Trust Report when you want the baseline in hand.

