Who this helps
Application and security teams adding AI assistants, retrieval, or agent tools to cloud applications.
Application and security teams adding AI assistants, retrieval, or agent tools to cloud applications.
A new AI feature, retrieval across customer boundaries, tools with consequential permissions, or concerns about prompt injection and sensitive-data exposure.
The use case, model and hosting providers, data sources, user roles, connected tools, and a general description of expected allowed and denied actions.
01 / ENGAGEMENT SCOPE
Map users, data flows, model endpoints, dependencies, and trust boundaries. Review authentication, authorization, output handling, and abuse cases within an agreed testing scope.
Assess direct and indirect prompt injection through user input, retrieved documents, and tool responses. Verify that generated output cannot bypass authorization or trigger unsafe execution.
Review tenant isolation, document permissions, sensitive-data exposure, secrets, retention, and redacted logging. Test denied access and revoked permissions before data reaches the model.
Review least-privilege identities, tool allowlists, execution-time authorization, independent approval for consequential actions, egress boundaries, resource limits, and stop mechanisms.
02 / PRACTICAL OUTPUTS
Deliverables are tailored to the agreed systems, assessment boundary, and engagement objectives.
WORKING TOGETHER
Access, timing, deliverables, and any implementation or retest work are agreed before the engagement begins.
Define goals, systems, access, permitted work, deliverables, and operational constraints.
Review the agreed architecture, controls, and evidence; prioritize actionable gaps.
Connect corrective actions to owners, dependencies, due dates, and acceptance criteria.
Retest agreed changes, summarize remaining decisions, and hand evidence to the maintaining team.
COMMON QUESTIONS
A prompt can guide behavior, but authorization and tool permissions must be enforced by the application and execution environment. A scoped assessment examines those boundaries and their evidence.
Yes. Agreed scope can include document access at retrieval time, tenant isolation, output handling, tool identities, execution-time authorization, and approval boundaries.
Review AI-enabled applications across models, retrieval, APIs, and connected tools. Apply application-security and cloud-architecture discipline to identify exploitable gaps and verify practical fixes across AWS, OpenShift, and hybrid environments.
Explore this serviceReview AWS and hybrid cloud architecture across identity, network segmentation, data protection, and operational visibility. Connect design decisions to practical implementation and verification.
Explore this serviceReview OpenShift and Kubernetes architecture across private and hybrid cloud, from cluster access and workload isolation to AWS integration and verifiable controls.
Explore this serviceAssess applicable Security Technical Implementation Guide requirements, organize supporting evidence, and guide remediation through verification.
Explore this serviceConnect cloud application architecture, workload identities, dependency risks, and delivery controls across AWS and OpenShift to a remediation process your engineering team can use.
Explore this serviceAI SECURITY / WATCH & APPLY
Bring application-security discipline to AI features. Explore prompt injection, retrieval data protection, and agent permissions through an OWASP AI Exchange video and interactive review scenarios.
Explore AI security learning ↗An attributed overview paired with questions for your architecture review.
Work through practical AWS, OpenShift, and application security scenarios.
Connect access boundaries, secure delivery, and verification evidence.