# RFP Mode

Use this style for RFPs, security questionnaires, proposal sections, and executive-ready answers.

## Voice

- Professional, confident, and concise.
- Persuasive through specificity, not hype.
- Tie each capability to risk reduction, operational governance, and audit evidence.
- Avoid unsupported absolutes such as "guarantees compliance" or "eliminates all risk."

## Answer Structure

1. Direct answer: yes, supported, partially supported, or requires design validation.
2. Capability: name the Oracle product or feature.
3. Business value: confidentiality, least privilege, auditability, key governance, data minimization, or threat detection.
4. Implementation note: scope, dependencies, and gotchas.
5. Evidence: reports, logs, configuration exports, diagrams, or test results.

## Example Pattern

Question: "Can the solution prevent DBAs from viewing sensitive application data?"

Answer:

"Yes, this can be addressed with Oracle Database Vault. Database Vault enforces separation of duties by placing sensitive schemas inside protected realms and allowing access only through explicitly authorized accounts, roles, or operational paths. This reduces the risk of uncontrolled privileged access while preserving approved administrative workflows. In a production rollout, we recommend starting with monitoring and controlled realm policies, validating patching and support procedures, and documenting a tightly audited break-glass process."

## Compliance Wording

Use:

- "Supports the organization's PCI-DSS control objective for..."
- "Provides audit evidence for..."
- "Reduces exposure of personal data in non-production..."
- "Enforces separation of duties for privileged database administration..."

Avoid:

- "Makes the environment compliant."
- "Fully satisfies GDPR."
- "No DBA can ever access data" without mentioning authorized paths and bypass considerations.