Data residency
Keep the platform and data in your chosen region, private cloud or datacentre.
TRUST BY DESIGN
Private AI.
Accountable automation.
Keep sensitive security data inside your chosen environment, with controls over access, model decisions and response actions.
DATA PROTECTION
Control the security boundary.
Encryption & keys
Use encryption in transit and at rest, with customer-managed keys in the deployment design.
Identity & access
Apply role-based access, SSO, MFA and least privilege to operational roles.
Data minimisation
Mask PII before analysis and configure retention around your requirements.
Tenant isolation
Separate stores and keys across clients or business units in multi-tenant deployments.
Model data handling
Client data is not used to train shared models, as described in the platform design.
GOVERNED RESPONSE
Automation with a record.
Approval gates
Require analyst approval for high-impact actions and retain the ability to override decisions.
Reasoning trails
Review the evidence, confidence and investigation steps supporting a verdict.
Auditability
Log access, approvals, actions and model decisions for operational review.
Recovery controls
Define rollback and recovery options, then verify outcomes before incident closure.
GOVERNANCE
Evidence as part of the workflow.
Prajnera’s reporting scope includes control mapping, incident timelines, evidence collection and draft management reports. Teams can review detection coverage and gaps alongside operational outcomes.
Framework mappings described in the platform scope include ISO 27001, NIST CSF, PCI DSS and SOC 2. Framework alignment is distinct from certification; this website does not claim that Prajnera holds those certifications.
Review data flows, retention, access controls and deployment requirements with your security team during discovery.
YOUR NEXT STEP
Let’s discuss your SOC and AI agents.
Define the security workflows, agent visibility and human controls your environment needs.