Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Monthly High Watermark
Cyber Security

Monthly High Watermark

← Back to Glossary
By NHI Mgmt Group Updated November 4, 2026 Domain: Cyber Security

The monthly high watermark is the highest number of users present in a client organisation at any point during a billing month. MSPs use this value to determine the billing quantity, so charges reflect peak usage rather than end-of-month headcount. It is a common control for avoiding underbilling when users are added and removed within the same cycle.

How Monthly High Watermark Billing Works

Monthly high watermark billing measures the peak number of active users reached at any point during a billing month, then uses that peak as the charge basis. That makes the pricing model more sensitive to maximum concurrent or active usage than to the number of users left at month-end.

This approach is common in managed service arrangements because it reduces the chance that a client briefly adds users, removes them before invoice close, and still pays only for the lower end-of-month count. The billing logic therefore depends on a clear, auditable definition of what counts as a user and when that count is sampled.

Why Providers Use a High Watermark Model

The main purpose of a high watermark is revenue protection and billing fairness. It aligns charges with peak consumption, which is often closer to the real service load the provider had to support during the month. It also discourages disputes caused by short-lived user churn around invoice dates.

For the customer, the model can be easier to understand when user counts change frequently, because it removes incentives to game timing. For the provider, it creates a stable billing rule that can be documented in the contract and applied consistently across cycles.

What Must Be Measured and Recorded

A defensible watermark process needs a reliable user inventory, a consistent sampling rule, and a record of when the peak occurred. The billing team should know whether the count includes named users, enabled accounts, temporary access, guest users, or suspended accounts, because those distinctions can materially change the bill.

Accuracy depends on the upstream identity and access records that feed the count, even though the billing concept itself is financial rather than technical. If provisioning or deprovisioning is delayed, the watermark may overstate or understate the true active population for part of the month.

Contractual and Operational Implications

Monthly high watermark terms should be defined tightly enough that both sides can reproduce the number from source records. If the contract does not specify the counting method, organisations can end up arguing over whether a transient account, duplicate record, or disabled login should have been included.

In practice, this makes the watermark a governance control as much as a pricing one. It is best treated as part of the service definition, with ownership for how the count is generated, reviewed, disputed, and archived.

Risk and Threat Considerations

High watermark billing can create exposure when user counts are derived from incomplete inventories, delayed deprovisioning, or inconsistent definitions of active use. Those weaknesses can lead to systematic overbilling, underbilling, or dispute conditions that are hard to reconstruct after the fact.

Failure mechanism: If the source system records accounts differently from the contract language, the monthly peak can be inflated by stale users, duplicate identities, or short-lived access that should not count, or suppressed by missing records.

Impact: The organisation may pay for capacity it did not intend to consume, lose trust in the billing record, or miss a charge if the provider cannot demonstrate how the watermark was calculated.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AU-6 — Audit Review, Analysis, and ReportingMonthly watermark counts need auditable records and review of source data changes.
Recommendation — Review user-count logs and exceptions so billing peaks can be reconciled to authoritative records.
NIST CSF 2.0ID.AM-01 — Physical devices and systems within the organization are inventoriedA watermark depends on an accurate inventory of active user records feeding the count.
Recommendation — Maintain an authoritative inventory of user records that drive billing measurements.
ISO/IEC 27001:2022A.5.9 — Inventory of information and other associated assetsThe billing model relies on governed records of who is active at each point in the month.
Recommendation — Define and maintain the authoritative user inventory used for billing and reconciliation.

Practitioner Guidance

Governance implication: Define the counting rules before the first invoice, including which account states count toward the watermark and which source system is authoritative. That removes ambiguity when the peak changes during onboarding, offboarding, or temporary access events.

What to watch for: Reconcile monthly invoice counts against provisioning and deprovisioning records, especially where user churn is high or shared administrative processes can delay account removal. A short exception review is usually enough to catch most billing drift before it becomes a recurring dispute.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org