Security at FreNiMiGuard

Published October 11, 2026. These controls describe the product design. Request deployment-specific evidence before relying on a control for an assessment.

Workspace and access boundaries

The product uses application and database controls to separate organisations. It supports multi-factor authentication, role-based access and SAML single sign-on on the applicable plan. Workspace changes are recorded in the audit trail.

Endpoint actions require explicit trust

The endpoint agent is optional. Remote actions are disabled by default. The default approval policy requires a second administrator, and commands are signed. Administrators must review enrolment, signing-key trust and approval settings for their deployment.

Protecting stored information

Hosted connections use TLS. Passwords use one-way hashes; integration credentials and signing keys are encrypted in the database. See the DPA security schedule for the contractual description.

Deployment and data location

The hosted service stores data in the United States. Enterprise self-hosting is available. A self-hosted customer manages its infrastructure, updates, backups and network controls; review connected services separately.

Evidence and limitations

Vulnerability matches and control mappings support analyst decisions. Verification records and OSCAL exports help document those decisions. Using the product does not confer Cyber Essentials certification, CAF approval or automatic compliance.

Report a security concern

Contact info@frenimi.com with a high-level description and a safe way to reach you. Request a secure transfer method before sending sensitive evidence. Do not send passwords or customer data by email.