CISO Corner archive
AI securityRetrospective edition

The document your AI reads is not its manager

Keep untrusted content from becoming authority inside an AI workflow.

Office of CISO, GENELLIPSE

Business risk. Practical decisions. Evidence.

AI assistants can read emails, documents and retrieved records at a speed that changes business operations. Those inputs may also contain misleading instructions. The control challenge is to preserve the boundary between useful content and permission to act.

01 / UNDERSTAND

The business issue

OWASP describes prompt injection as input that changes a model’s intended behavior. Filtering alone is not a sufficient business approval system. A safer design restricts accessible data and tools, validates proposed actions and places consequential decisions behind enforceable controls.

02 / ACT

Your action guide

Explore each step, then use the questions with your business and technology teams.

DECISION INTO ACTION

Separate reading from acting

Identify external content and keep it distinct from trusted workflow instructions. Limit retrieval to information the current user and task are authorized to access.

Separate reading from acting

Identify external content and keep it distinct from trusted workflow instructions. Limit retrieval to information the current user and task are authorized to access.

Constrain the action surface

Give the assistant only the tools needed for the task. Validate destinations, parameters and authorization outside the model before a proposed action reaches a business system.

Test hostile context

Use approved test documents containing misleading instructions. Verify containment, human escalation and recovery; record failures as design findings, not simply inaccurate answers.

Review the evidence. Revisit the decision.
Ask the leadership team

If the model follows the wrong instruction, what independent control still protects the business?

03 / VERIFY

What to measure

Establish your baseline and agree targets for the service. These are suggested measures, not claimed results.

Action boundaries

Consequential tool actions protected by explicit external authorization.

Adversarial test coverage

Critical workflows tested with hostile or misleading context.

Unsafe attempts contained

Test actions blocked before they reach a business system.

Use this in your next risk review

Working prompts for your team. Selections stay in this page only and are not a security assessment.

04 / BUILD WITH US

How Genellipse helps

GeneSecure

GeneSecure can help bring AI-related risk findings and security evidence into a review workflow. Genellipse can assess the integration boundaries around retrieval, tools and sensitive data.

Explore GeneSecure

GeneComply

GeneComply can organize AI policies, test evidence and exception decisions. Combined with an agreed Cortex AI governance design, the approach supports traceability while keeping consequential approvals with authorized people.

Explore GeneComply

Choose one assistant with access to a business tool and test the boundary. A useful result demonstrates containment, not a claim that prompt injection has been eliminated.

Explore CISO Advisory

Office of CISO, GENELLIPSE

Sources & editorial notes

Original Genellipse analysis and practical recommendations. Primary guidance informs the technical context; linked organizations do not endorse Genellipse or its products.

Prepared for this archive on . Examples are illustrative. Product scope, integrations and responsibilities are confirmed for each engagement.