Operational Risk Intelligence · FortiSec Systems

Reason about what your
security posture fails to prove.

ORI separates what you can declare from what you can actually prove. It highlights possible evidence gaps and model-based exposure scenarios, helping you decide what to verify next.

01
Evidence over attestation
Every answer narrows or widens the set of hidden risks ORI cannot rule out.
02
Coherence detection
Claims that contradict your other answers are flagged — not silently accepted.
03
Actionable output
Findings suggest verification or remediation priorities based on available answers and model assumptions; they do not guarantee optimal risk reduction.

Organisation profile

Your profile determines which security domains are scored and their applicability weight. Domains not relevant to your infrastructure are excluded — not penalised.

Inference report
—
Observed
Maturity
—
Declared controls
Operational
Confidence
—
Evidence-backed
Evidence
Sufficiency
—
—
Claim-Evidence
Gap Pressure
—
Strong claims without proof
Hidden
Exposure
—
Residual risk level
Stability
Distance
—
Declared vs. proven gap
© 2026 FortiSec Systems Inc. All rights reserved. ORI v6 · Public assessment experience

Telemetry uploads

Upload operational exports from your environment.

Privacy model
Uploads are sent to the Fortisec server for in-memory parsing (maximum 10 MB). Normalized records and extracted observations can be returned to your browser and sent back for confirmation. Use synthetic data when exploring the product. Do not upload secrets or unnecessary personal data. Read our Security & Data Handling overview ↗.
Identity exports
CSV · JSON
Okta, Entra ID, AWS credential report, Google Workspace, GitHub org members, or generic identity CSV. ORI will check MFA coverage, stale accounts, and ownership gaps.
Cloud / IAM roles
CSV · JSON
AWS IAM roles, Azure role assignments, GCP IAM policies. ORI will check stale roles and cross-account trust relationships.
OAuth applications
CSV · JSON
OAuth app inventories from Google, Microsoft, Okta, or generic exports. ORI will check dormant grants and broad permission scopes.
Tier 2 files are operational records that may need field inference or text extraction before ORI can treat them as telemetry. They can validate some hidden states, but with lower confidence than structured CSV/JSON inventories.
Logs and semi-structured exports
TXT · LOG · CSV · JSON
SIEM exports, EDR coverage exports, audit logs, access logs, IAM text exports, or semi-structured operational records. ORI will extract structured signals where fields are reliable.
Documents can strengthen evidence but ORI only treats a hidden state as observed when the file contains extractable operational records, not just policy language.
Policies and reports
PDF · TXT
MFA policies, access review reports, audit findings, incident playbooks. ORI will extract signals and show what the document can and cannot prove.
Telemetry results are added to your report automatically.