Security

Reporting and basic security controls.

Last updated: 2026-05-10
Security is a shared responsibility. If you believe you found an issue, report it through your engagement support contact with clear reproduction steps.
Back to portal
Quick links
FAQ
Common questions
Support
Ask Fop
Architecture
Deployment paths
RFS
Request a scenario
Security
Report concerns
Privacy
Data handling
Terms
Usage conditions
Accessibility
Feedback channel
Partners
CSP marketing
Legal
Policies & agreements
Report an issue
If you believe you found a security issue, report it through your engagement support contact. Provide clear reproduction steps and avoid including sensitive data.
Security controls in place

A layered set of customer-relevant controls protects your data from the browser to your own storage. Each control is summarised below with the specifics it enforces.

Secure transport & network boundary

Everything the portal sends travels over encrypted channels with hardened browser defaults.

  • HTTPS/TLS enforced for portal delivery and every API call
  • Security headers (HSTS, referrer, content-type) applied by default
  • Browser calls locked to a single public API base URL (CORS-scoped)
  • No inbound ports or privileged listeners exposed to the customer network

Minimal application surface

The portal ships as a static export, so there is no server runtime to attack.

  • Static-hosting-safe build (no server-only execution in the portal)
  • No tenant credentials or privileged secrets embedded in the UI
  • Client-side interaction only — no privileged admin sessions in the browser
  • Dependency hygiene and automated CodeQL scanning on every change

Customer-owned data destinations

Your artifacts land in storage you control — MSC does not park customer content.

  • Outputs routed to Azure Blob, AWS S3/GCS, SharePoint, or your file shares
  • No long-term storage of customer datasets on MSC infrastructure
  • Tenant admin credentials and privileged secrets are never retained
  • Retention, approvals, and governance stay under your policy model

Least-privilege access

Access is scoped to the engagement, with no hidden dependency on super-admin rights.

  • Least-privilege posture by design across the portal and API
  • No dependency on standing super-admin or global-admin access
  • Engagement-scoped access aligned to the work being performed
  • Clear separation between portal UI and backend API responsibilities

Provenance & auditability

Deterministic, ID-tracked artifacts make every run easy to review and sign off.

  • Journey IDs and operational metadata for every run
  • Deterministic artifact bundles — repeatable, reviewable outputs
  • Clear provenance from assessment through to export
  • Structured reporting metadata published at /.well-known/security.txt

Safe-use guardrails

The workflow steers sensitive data away from free-text and out of the browser.

  • Do not enter credentials, secrets, or regulated personal data in free-text fields
  • Sensitive data stays out of the browser and out of MSC storage
  • Report suspected issues through your engagement support contact
  • Provide clear reproduction steps without including sensitive data
Safe use
Do not enter credentials, secrets, or regulated personal data into free-text fields.
Structured reporting metadata is published at /.well-known/security.txt.