AI-Assisted Secure Coding (Appendix C) · Secure Prompt & Context Management
Encrypt prompts and responses
Verify that prompts and AI responses are encrypted in transit and at rest, and retained per the data-classification policy. Tenants and projects are cryptographically separated from each other.
OWASP AISVS v1.01, requirement AC.3.6
In plain English
Encrypt prompts and AI responses in transit and at rest, keep them only as long as their data classification allows, and separate tenants and projects with different keys. Prompts often contain source code and internal detail. This is a Level 3 control.
What good looks like
- Prompts and responses are encrypted in transit (TLS) and at rest.
- Retention is set according to the data-classification policy and enforced.
- Tenants and projects are cryptographically separated, each with its own keys.
- The same applies to your own logs of prompts and responses.
How teams usually do it
- The vendor's enterprise settings for retention, including zero-retention options where offered.
- Customer-managed encryption keys where the vendor supports them.
- Separate vendor workspaces or projects for work at different sensitivity levels.
Suggested evidence
- Vendor configuration showing encryption, retention and key settings.
- The retention policy mapping.
- Your own log store's encryption and retention settings.
Common mistakes
- Default settings that keep prompts indefinitely.
- Securing the vendor side and keeping a plaintext copy of every prompt in your own logging stack.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.