Enterprise AI. Governed.
iTmethods is the trust layer for enterprise AI. This page documents the security posture across the Fortress Family — Reign, Forge, and BioCompute — including certifications, security headers, encryption, tenant isolation, and our vulnerability disclosure policy.
Certifications & frameworks
One architecture. Many regulators.
Forge maintains SOC 2 Type II audit posture continuously. Reign produces regulator-grade evidence mapped to global frameworks. BioCompute extends the same evidence model into FDA, EMA, and HIPAA scope.
Certified
Audit posture maintained continuously since 2018.
Audit posture
Aligned to the AWS Advanced Tier Services Partner audit posture.
Evidence-ready
BioCompute deployments and Reign Evidence Engine produce HIPAA-aligned artifacts.
Evidence-ready
Reign produces evidence aligned to FedRAMP Moderate/High control families.
Evidence-ready
Reign Regulator Packs map to AI Act Article 9, 10, 12, 14, 15 obligations.
Evidence-ready
Third-party ICT risk evidence and incident reporting mapped to DORA articles.
Evidence-ready
Reign maps to all 25 AIGF risk categories including the six agentic AI risks.
Evidence-ready
GxP validation and electronic records aligned to FDA 21 CFR Part 11.
Data practices
Encryption. Isolation. Evidence.
The architectural choices regulated enterprises actually need a vendor to be specific about.
Encryption in transit
TLS 1.3 with HSTS preload across itmethods.com and all subdomains. No mixed content. Certificate transparency monitored.
Encryption at rest
AES-256 across managed infrastructure. Customer-managed keys (BYOK) supported in Forge and BioCompute single-tenant deployments.
Tenant isolation
Reign and BioCompute deploy single-tenant by default. Forge supports both managed multi-tenant and dedicated single-tenant operating models.
Evidence by design
Reign's Evidence Engine produces tamper-resistant, identity-attributed audit artifacts continuously — not as an end-of-quarter compliance ritual.
Security headers
What we send on every response.
Defense in depth on the marketing surface — verifiable from any browser dev-tools network tab.
Strict-Transport-Securitymax-age=63072000; includeSubDomains; preloadHSTS preload — 2-year max-age, all subdomains, browser-baked
X-Frame-OptionsDENYClickjacking protection — itmethods.com cannot be framed
X-Content-Type-OptionsnosniffMIME-sniffing disabled
Referrer-Policystrict-origin-when-cross-originReferer leak prevention
Permissions-Policycamera=(), microphone=(), geolocation=()All sensitive APIs disabled by default
Content-Security-PolicyReport-Only (telemetry mode)Active on every response — enforced mode rolling out per Cycle 3.2
Static assets (/_next/static/*) and the dynamic OG image endpoint (/api/og) carry additional cache-control headers tuned for CDN edge serving.
Reporting & contact
Three ways to reach us.
Researchers, customers, and audit committees each have a direct path.
Vulnerability disclosure
RFC 9116 security.txt at /.well-known/security.txt. Email security@itmethods.com. We acknowledge within 2 business days, triage within 5, and communicate a resolution timeline within 10.
Read security.txtCompliance & audit evidence
Customers under contract can request SOC 2, ISO 27001, HIPAA, and DORA evidence through their account team or by emailing trust@itmethods.com.
Request evidenceAudit-committee briefing
Board and audit-committee briefings on the Reign evidence architecture, EU AI Act readiness, and DORA third-party AI risk are available on request.
Brief our committeeDirect contact
- Vulnerability reports: security@itmethods.com
- Compliance & evidence requests: trust@itmethods.com
- General security questions: via contact form with topic “AI Governance Assessment”
Safe-harbor language and response targets are documented in security.txt.
Where we operate
iTmethods Inc. is headquartered in Toronto, Canada. We operate in Austin, TX (US Sales & Customer Success) and have engineering, support, and compliance resources in Dublin (Ireland), Bangalore (India), and Eastern Europe. Customer workloads run in regions selected for jurisdiction and data-residency requirements — AWS regions for Forge and Reign, FedRAMP-aligned regions where required, and on-prem or sovereign cloud for BioCompute and Reign single-tenant deployments.
Read the company overview at itmethods.com/about.
