ASA Protocol
Aegis · Sentinel · Aria
ActiveFORVERA
ForVera's commitment to platform security, data protection, and operational transparency.
Last updated June 1, 2026
Aegis · Sentinel · Aria
Active
Image & Accessibility Protocol
Active
Command Center · Client Portal · Team Portal
Active
All Data Encrypted In Transit
Active
Storage-Layer Data Encryption
Active
Active Vulnerability Reporting Program
Active
Active Platform Uptime Monitoring
Active
Operating to SOC 2 Principles
ActiveAll client data is encrypted in transit using TLS and encrypted at rest at the storage layer. ForVera operates a dedicated database instance scoped exclusively to platform operations — client data is never commingled with third-party analytics or external services. Database access is restricted to authenticated application processes only; no direct public database exposure exists. Sensitive credentials are stored outside the application codebase in environment-isolated configuration files excluded from version control.
All three platform surfaces — the Command Center, Client Portal, and Team Portal — operate under completely isolated authentication realms. Sessions, tokens, and credentials are never shared across surfaces. Two-factor authentication is enforced platform-wide using time-sensitive verification codes delivered via email. Login attempts are rate-limited and monitored; accounts are automatically locked following repeated failed attempts. Role-based access control governs every action — users can only access the modules and data their role explicitly permits. All sensitive actions are logged to an append-only audit trail.
The AXIOM platform runs on enterprise-grade server infrastructure hosted in a European data center with physical security controls, redundant power, and network-level DDoS protection. All web traffic is served through an enterprise reverse proxy layer enforcing HTTPS-only access — unencrypted connections are rejected. The platform is actively monitored 24/7 by an external uptime monitoring service with automated alerting; ForVera staff are notified of any service disruption within minutes. Container-level monitoring provides real-time visibility into application health across all platform components.
The AXIOM platform is built on a custom PHP 8.3 MVC architecture with security enforced at every layer. All database queries use prepared statements exclusively — no raw user input is ever interpolated into SQL. CSRF protection is applied to every state-changing request across all surfaces. Output is escaped at the rendering layer to prevent injection attacks. The platform undergoes internal security review under the ASA Protocol — ForVera's named security audit framework encompassing threat modeling, access control verification, and hardening review. Session cookies are scoped, HttpOnly, and Secure in all production environments.
Every client's data is logically isolated within the platform using enforced tenant scoping at the repository layer. No query can return data across client boundaries — isolation is enforced in code, not only by convention. Client data belongs to the client. ForVera does not sell, share, or use client operational data for any purpose outside of delivering the platform services. Clients may request an export of their data at any time by contacting ForVera support. Upon contract termination, data retention and deletion terms are governed by the applicable Service Agreement and Data Processing Addendum.
All digital assets processed through the AXIOM platform are handled under the IRIS Standard — ForVera's internal image processing and accessibility protocol. This covers proper file naming conventions, alt text requirements, image compression and format optimization, and WCAG-aligned accessibility conformance for all client-facing web properties. The IRIS Standard ensures that client websites managed through ForVera meet baseline accessibility requirements and are optimized for performance across all device types.
ForVera operates an active responsible disclosure program. If you believe you have identified a security vulnerability in any ForVera platform surface, we ask that you report it to our security team directly before public disclosure. We commit to acknowledging verified reports promptly, investigating all credible submissions, and keeping reporters informed of remediation outcomes. We do not pursue legal action against good-faith security researchers who follow responsible disclosure practices. Contact: security@forverastudio.com
ForVera staff access to platform systems is governed by role-based permissions and enforced 2FA. Internal policies — including acceptable use, data handling, and access control standards — are maintained in the Trust & Security module and require documented staff acceptance. All staff operate under confidentiality obligations covering client data. Access to client data is limited to the minimum necessary to deliver contracted services. ForVera conducts periodic internal security reviews and maintains documented incident response procedures.
Full documents available to logged-in ForVera clients and team members.
ForVera has launched this Trust & Security page as part of our commitment to transparency with clients, partners, and the public. All platform policies, security posture documentation, and compliance information will be maintained and updated here. We will post updates to this page whenever meaningful changes occur — new audit reports, policy updates, security improvements, or incident summaries.
ForVera's ASA Protocol (Aegis · Sentinel · Aria) is now formally documented and active across the AXIOM platform. The protocol governs our internal security audit process, covering threat modeling, access control verification, session security, and application hardening review. The ASA Protocol is applied to all platform surfaces — Command Center, Client Portal, and Team Portal — on an ongoing basis.
Two-factor authentication is now enforced across all three AXIOM platform surfaces. All staff, client portal users, and team members are required to verify their identity using a time-sensitive code delivered to their registered email address at each login. This applies without exception — 2FA cannot be bypassed or disabled at the user level.