How to Review a Vendor Acceptable-Use Policy Mid-Term

An ops lead at a 17-person UK SaaS is about to treat the vendor AUP as housekeeping because sales Slack said “standard AUP — we never suspend paying customers.” The PDF they emailed at signing is not the live URL. Knowing how to review a vendor acceptable-use policy mid-term means you open that live page, mark vague harm versus named acts, write suspicion versus notice and a cure, put the order-form use-case above the AUP, then pin, notice, or walk.

In September 2026, Holt — Ops at a 17-person UK SaaS — has Finance’s yes on an email and API vendor signed in April. The packet — the exact file set they will renew — is £1,200 a month plus “Customer may run scheduled security assessments of Customer’s own tenant.” The emailed AUP listed spam, phishing, malware. It was silent on tenant testing.

Clause 12.4 of the MSA — the master services agreement, the frame contract vendors hang order forms on — points at a live URL “as updated from time to time” and lets them suspend on reasonable belief that use is “harmful or offensive,” without a cure. Friday’s page, last updated 1 September 2026, now bans security testing without prior written approval. The pentest is 22 September. The emailed PDF is a souvenir.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Why does the emailed PDF fail as the AUP?

The emailed file is a snapshot. The MSA points at a URL that can move. If you only keep April’s PDF, you miss a September ban on the test you already booked. Write the last-updated date before you argue with sales.

Freeze the packet: MSA, order form, the emailed AUP PDF, and a dated print of the live URL. Diff the two files. If the live page moved and nobody emailed you, write “URL drifted — PDF is a souvenir.” Do not start a first-Accept clickwrap hunt. If the fight is ticking Accept on a website you have not signed, that is a different hunt.

In practice, the AUP they emailed is not the AUP that can take the service down. Morgan Lewis (27 October 2021, structure): an online AUP can move without consent, so current use can violate the live page. Changeflow (16 April 2026) saw AUPs change one to two times a year; fewer than 25% email when public terms move. AWS AUP still agrees by posting (1 July 2021; live 13 September 2026). Name England and Wales.

How do you mark vague harm versus named prohibited acts?

A named list is a map. “Harmful or offensive” is a blank the vendor fills when they want you offline. Write the acts that would hit this use — tenant pentest, scan, competitor scrape, own-API scrape — before you treat the block as colour.

Do mark vague versus named on the log. Do not let “just legal colour” close the row. Kioptrix (24 July 2026) writes from the vendor chair: a vague ban turns every call into a small courtroom drama. Read that as their playbook — a one-page list of default positions. For example, Google Cloud AUP bans testing “except as expressly permitted in the Agreement.” If the page only says “harmful,” write “vague — vendor’s favour.”

When to write suspicion versus notice and a cure?

“We never suspend paying customers” is Slack, not the kill-switch. Write whether they can cut you on reasonable belief with no cure, or only after notice and days to fix. Silence on this paper is immediate. That is Monday’s pressure.

Holt’s 12.4 is suspend-on-belief, no notice, no cure. AWS Customer Agreement is the same shape: suspend immediately if AWS reasonably determines a security risk. SuperSend TX (8 August 2026) : immediate suspension without refund. Do write “suspicion / no cure” when 12.4 matches. Do not treat AE Slack as the pause. Google Cloud’s security FAQ lets you pentest your own projects, but tests must stay inside the AUP.

What does the order form do if the AUP sits above it?

An order-form use-case wins only if the paper says the order form prevails on use-rights. Holt’s tenant-assessment sentence is a hidden nothing if the live AUP sits above it and now bans that test.

Do write “OF above AUP: yes / no / silent.” Do not assume the booked-test sentence survives a live ban. Surfacedd (20 April 2026, structure) prints Order Form > Addendum > MSA > AUP — only if this paper says so. If the fight is the whole MSA / order form / SOW / purchase-order stack, that is a different hunt. Scraping your own API is still abuse if this AUP names scraping.

Should material AUP edits use the same path as the MSA?

A tidy-up that adds a security-testing ban is not housekeeping. Ask for the same path as an MSA amendment. If they can post a new AUP and call continued use acceptance, Monday’s pack is stale.

Do mark freeze, notice plus no impact, or terminate with a pro rata refund if a material AUP edit blocks the original use. Do not let “tidy without reopening the MSA” close the row. Law Insider AUP Changes show posting-effective versus 30 days’ prior notice. If sales treats every posted policy as the same hunt, that is a different article. A URL update is not a signed variation; that path is the no-oral-modification hunt.

Can you pin, notice, or walk this live AUP?

Pin when you freeze this version and the order-form use-case sits above the AUP. Notice when material edits take the MSA path and suspicion is replaced by notice plus a cure except for named severe abuse. Walk when the live URL already bans the booked use, they can suspend on belief, refunds are out, and the order form does not prevail.

Kioptrix’s ladder — warn → restrict → throttle → suspend — is how good-faith customers stay up. Immediate action belongs on malware or phishing, not on a tenant test the order form already named. Pin this week: save the live AUP, write the notices inbox, and pause 22 September until they confirm in writing. Escalate live-URL drift plus suspend-on-belief to counsel — a qualified lawyer, not the chatbot.

Workflow: live URL vs emailed PDF → vague harm vs named acts → suspicion vs notice+cure → OF use-case above AUP → AUP change-control = MSA path → pin / notice / walk. Success bar: verify the one-page log before Monday’s pack. Point to one sentence that would pause the pentest. “Standard AUP” is not that sentence if the live page bans the booked test and allows suspend-on-belief. A first-pass — the first machine pass that extracts clauses before a human reads every page — can highlight acceptable use on the same file. A High flag — an item scored high severity — still needs a human to open the live URL.