> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/authentication.md). # Authentication Flosum uses a variety of authentication methods, including SAML 2.0 for SSO and IAM, to secure your data and provide the highest levels of security. Our policy supports integration with identity providers in a native way, and does not use intermediary authentication/authorization tools (e.g., Keycloak, Auth0, Cognito, etc.). The system uniquely identifies and authenticates each individual user. Anonymous authentication is prohibited. ### Single Sign On (SSO) We prioritize efficiency and security by implementing an SSO solution. SSO significantly improves security by reducing the risk associated with password-related vulnerabilities and ensuring a more robust and centralized authentication system that maintains the highest standards of data protection. \ \ IP restrictions require a customer-hosted instance and configuration of the attendant AWS or GCP environment. ### Multi-Factor Authentication (MFA) Security of our digital assets is paramount, and as part of our comprehensive security measures, we employ MFA. By implementing MFA, we significantly bolster our defense against unauthorized access, safeguard sensitive information, and fortify our systems against potential threats. This proactive approach to security not only aligns with industry best practices but also underscores our commitment to ensuring the utmost confidentiality and integrity of our network.\ \ Flosum has enabled Multi-factor Authentication (MFA) delete, which turns on the MFA delete capability to require additional authentication to delete objects in a versioned S3 bucket. We use access points and VPC endpoints. All access points and VPC endpoints allow access to S3 without exposing the entire bucket, which restricts what can be accessed in the S3 bucket. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/authentication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.