> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-features/compliance-mode.md). # Compliance mode ### **What is Compliance Mode?** Compliance Mode is an advanced security feature in FenixPyre that allows users to interact exclusively with encrypted data when enabled. It ensures sensitive files remain encrypted and inaccessible in their decrypted form, enforcing stringent control over data visibility and usage. *** ### **What Problem Does Compliance Mode Solve?** Compliance Mode directly addresses challenges in environments where sensitive data (such as Controlled Unclassified Information - CUI) and non-sensitive data coexist. It prevents accidental exposure or unauthorized access to sensitive decrypted data, significantly reducing data leakage risks and strengthening compliance with security standards like CMMC. *** ### **How Does It Work?** * **Enabled Compliance Mode**: * Users can only access encrypted files. * Attempting to open a decrypted file automatically encrypts it upon saving, maintaining compliance. * **Disabled Compliance Mode**: * Users have full access to decrypted files but cannot view or edit encrypted files, as they appear in ciphertext. Compliance Mode can be selectively activated for specific applications, enabling fine-grained control and flexibility without disrupting existing workflows or user experience. *** ### **Use Cases** Compliance Mode is specifically valuable in regulated industries and scenarios requiring strict data governance, including: * **Defense and Government Agencies (CMMC Compliance)**: * Managing Controlled Unclassified Information (CUI) alongside regular data without cross-contamination risks. * **Healthcare and Financial Services**: * Ensuring sensitive personal or financial data remains protected at all times. * **Enterprise Environments with Mixed Data Sensitivity**: * Safely using encrypted and unencrypted data within the same user environments, enhancing security posture without user friction. *** ### **Key Benefits** * Seamlessly maintains data encryption, enforcing security policies transparently. * Protects sensitive data automatically without additional user training or complexity. * Enables organizations to confidently comply with regulatory frameworks like CMMC. *** For more information on how to enable and setup compliance mode please contact [FenixPyre Support](mailto:support@fenixpyre.com). --- # 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.fenixpyre.com/fenixpyre-features/compliance-mode.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.