Customer control
Customers approve connected data, authorized users, workflows, retention and the professionals responsible for action.
Security & Trust
Heimdall is designed for high-consequence environments where data scope, access, evidence, accountability and deployment choice must be explicit.
Trust principles
Each deployment starts with its purpose, data, users and operating responsibilities. The control model is then aligned to the environment and the consequences of the decisions it supports.
Customers approve connected data, authorized users, workflows, retention and the professionals responsible for action.
Unique identities, multifactor authentication and role-based permissions restrict access according to responsibility.
Intelligence remains connected to supporting context, ownership, review, intervention and outcome.
Cloud and on-premises options support customer architecture, security and operating requirements.
Data protection and access
Controls are configured according to the agreed deployment model and sensitivity of the information involved.
Customers determine which systems and information are appropriate for the use case, who can access them and how long deployment information should be retained.
Where customer identity services are used, provisioning and revocation can remain connected to the customer’s access-management process.
Any external processing or AI service is evaluated and approved for the deployment. Public website language does not authorize a service to receive customer information.
Monitoring and accountability
Security-relevant events are logged according to the deployment so authorized teams can investigate access, configuration and application activity.
Authentication, administrative, application and data activity can be recorded at the appropriate layer.
findings and control status are reviewed through documented security processes and assigned for remediation.
Suspected security, privacy and legal events follow defined documentation, assessment, escalation and notification procedures.
Secure delivery
Standard source changes follow controlled review, testing and deployment practices, with proportionate review for approved exceptions.
Changes are authorized, peer reviewed and connected to documented work.
Automated checks evaluate code, dependencies, secrets and application security where applicable.
Material findings are resolved or formally risk reviewed before production use.
Deployment and security-relevant outcomes are logged, reviewed and tracked.
Deployment flexibility
Heimdall supports cloud and on-premises deployment options. The chosen model determines the detailed architecture and division of responsibilities.
Plan a Focused PilotCustomer responsibilitiesApprove data, users, policies, response authority, infrastructure choices and systems of record.
Davista responsibilitiesImplement and operate the licensed application, integrations, configuration, support and agreed controls.
Workflow and system integration
Customers decide where follow-through belongs. Action & Resolution can hold the working record, an external system can remain authoritative, or approved fields can synchronize through a specifically configured integration. Displaying information in another channel does not by itself imply write-back or synchronization.
Preserve evidence, ownership, tasks, remediation, decisions and closure in one reviewable workflow.
Deliver an approved finding, priority, assignment or status to the operational tool authorized for that workflow.
Receive configured ownership, corrections, action status and closure updates so the operating picture stays current.
The customer defines the authoritative system. Integration scope, permitted fields, update direction and conflict handling are agreed for each deployment.
Mission-specific assurance
Protect sensitive operations with restricted access, customer-defined retention and accountable intervention.
Explore Corporate Security →Limit inputs by purpose, preserve supporting evidence and keep employment decisions with authorized professionals.
Explore Human Risk Intelligence →Connect tasking, presence, observation, response and outcome in a verifiable service record.
Explore Guard Operations →Keep agency control over approved data, access, retention and operational authority while addressing applicable CJIS requirements.
Explore Law Enforcement →Let districts define approved sources, criteria, authorized teams and human-led intervention, including Student Sentinel safety and support workflows.
Explore Education Intelligence →Support customer procurement with consistent assurance, deployment flexibility and responsibility mapping.
Explore Partnership →Procurement and assurance
This page explains Davista’s framework. Detailed architecture, control evidence and customer-specific answers belong in a structured security review with the appropriate confidentiality protections.