Access control restricts who or what may use a system, document, database, or file, and limits the actions permitted. In AI-powered applications, it prevents model-triggered functions from reaching data or resources beyond their intended scope. section 13.4.2 section 6.8
Apply access control through practical restrictions:
- Run database functions with read-only accounts and limit file functions to specific directories. section 13.4.2
- Require human review before AI functions reach sensitive data, and use only company-approved tools for sensitive documents. section 13.4.2 section 6.2
- Record who initiated each function call and what data it accessed, then investigate unusual access attempts. section 13.4.2
A safer support-log workflow
A team needs to share customer support logs with an outside consultant. An approved enterprise anonymization tool processes the logs, while access controls limit the tool to the required files and prevent unauthorized data access. Staff test sample data, review edge cases, and verify the result before sharing it. section 6.8
Table 6.8 Document anonymization prompts
|
Scenario
|
Prompt
|
|---|---|
|
Database dumps
|
Change this database dump by replacing personal names, emails, and phone numbers with realistic fake data. Keep the field formats the same.
|
|
System logs
|
Process these system logs. Use placeholder IPs instead of real ones and change usernames/account IDs. Keep the structure and timestamps intact.
|
|
HR documents
|
Remove personal details from these HR documents. Use generic placeholders for employee names, Social Security numbers, and contact details. Keep job titles and departments as they are.
|
|
Financial reports
|
Clean up this financial report. Use generic IDs for account numbers and client names. Keep all financial figures and structure unchanged.
|
|
Medical records
|
Change these medical records for research use. Replace names, birth dates, and identifying details with coded IDs. Keep all medical conditions and treatments as they are.
|
Use the prompt patterns to plan controlled anonymization for database dumps, system logs, HR documents, financial reports, and medical records. section 6.8
