What you will be able to do after this session

• 1Read the clause. Parse your actual audit clause: notice, cooperation, scope, confidentiality, and cost.
• 2Know their rights. State what Oracle may genuinely require of you, without inflating it.
• 3Know yours. State the rights you hold in an audit, and use them without apologizing.
• 4Control the scope. Hold an audit to its named programs, entities, and time window.
• 5Answer data requests. Decide what to run, what to review, what to submit, and what to decline, on defensible grounds.

How the session works

A taught session with three knowledge checks: the remote console access request answered with information instead of keys, the out of scope subsidiary declined with the politest fence in enterprise software, and the invented ten day deadline countered with a written schedule the clause actually supports. It closes with one audit's six data requests negotiated line by line, zero bare refusals, and an audit that stayed exactly the size its letter described.

Homework before the next session, about one hour

• 1Annotate your clause. Your actual audit clause, marked up: what it grants, what it does not, where reasonable appears.
• 2Draft the scope minute. A template restating programs, entities, environments, and period, ready for any future kickoff.
• 3Write the decline letters. Three short templates: out of scope entity, access request, invented deadline. Calm, written, alternative attached.
• 4Read one script. Oracle's collection tool documentation for your main database version: what it gathers and its known false positives.
• 5Check the record habit. Could you produce minutes and a correspondence file from your last vendor dispute? Decide who keeps them in an audit.