Security requirements for AI Workflow Implementation & Managed Operations. OMEGANEON Hosted Cloud is the default; customer-owned cloud (BYOC) is an optional add-on.
Agent Permission Boundaries (APB) define authorization through six permission primitives. The framework requires each protected operation to be checked against the applicable constraints and required approval before execution.
Enforcement belongs in the execution infrastructure. Agents must not grant themselves additional permissions, and delegation must not expand their authority.
System
Which applications, services and environments an agent can access.
Data
Which records, fields and information categories it can use.
Action
Which operations it can perform.
Limit
What volume, frequency, financial and operational limits apply.
Duration
When authorization starts and expires.
Identity
Which authenticated identity acts, and on whose behalf.
OVERSIGHT, ACCESS & ACCOUNTABILITY
Controls around the whole operation.
02 / HUMAN-IN-THE-LOOP
Keep consequential decisions with people.
The framework requires low-risk work to stay within approved APB and conditional operations to follow agreed rules and limits. High-impact actions require explicit human approval, tied to the exact action or defined batch.
Missing, expired or rejected approvals block execution. Agents cannot approve their own restricted actions.
03 / HOSTED DEFAULT · OPTIONAL BYOC
Two deployment models. One security baseline.
Hosted Cloud is the default: OMEGANEON provisions and manages the agreed infrastructure and workflows. You do not need to supply or administer a cloud account. BYOC is an optional add-on with ongoing OMEGANEON management in your cloud account.
Both models require APB, human approval, restricted engineer access and audit controls. BYOC customers retain cloud-account authority and can revoke delegated access. Deployment scope, support coverage, billing and exit duties are agreed in the SOW.
04 / RESTRICTED ENGINEER ACCESS
Operate through a controlled platform.
The framework requires engineering operations to use approved functions of the OMEGANEON Engineering Platform. Engineers must not receive direct access to raw customer records, production databases or production secrets.
Troubleshooting uses authorized operational metadata and sanitized diagnostics. Runtime permissions, deployment artifacts and outbound data transfers must also be constrained against indirect data extraction.
05 / AUDIT LOGS & PERMISSION LIFECYCLE
Make access and actions reviewable.
Record permission changes, protected operations, approvals, denials and execution outcomes with relevant identities, timestamps and policy versions. Protect records from unauthorized modification and unnecessary sensitive-data exposure.
Authorized administrators can restrict permissions or suspend workflows. Development Logs show implementation progress; security audit records document security-relevant activity.
DEPLOYMENT & VERIFICATION
Agree the controls. Verify them before launch.
The framework defines required controls for both deployment models. Applicable controls must be implemented and pass documented acceptance checks before production Go-Live, then maintained during Managed Operations.
Verify APB, approval gates, revocation and audit logging in both models
Test tenant isolation, restricted engineer access and outbound data boundaries
Agree monitoring, maintenance, incident response and recovery responsibilities
Document coverage, cloud costs, data handling and handover in the SOW
Customer-specific commitments are established in the applicable PSA, SOW, DPA and AI Addendum. Publishing this framework does not establish a certification, independent security attestation or completed implementation. Service hours and response targets are agreed per engagement for both Hosted and BYOC. Implementation and verification status is established per deployment.
The public website uses server-side field validation, same-origin submission checks, one-use form tokens, a honeypot, minimum completion time and rate limits. No public endpoint lists or retrieves inquiries. No advertising pixels or third-party analytics are enabled by the application.