Introduction

Partners: This feature must be enabled on a per-client basis. Ensure that the Organization Selector is set to the appropriate client before continuing.

Some of the AROs you receive may impact your organization’s compliance with a given framework, and Field Effect MDR can map AROs to any compliance controls they affect. This article covers the following:

• Supported Frameworks
• Enable Compliance Mapping
• Disable Compliance Mapping

Supported Frameworks

Field Effect currently supports the following frameworks:

• ISO 27001
• Canadian Center for Cyber Security’s (CCCS) Baseline Controls v1
• NIST SP 800-171 v2
• The Field Effect Controls Framework:
  • Developed by our vCISO team, this framework is meant to help standardize our services and provide a great, well-rounded compliance specification for organizations that aren't already aligned with an existing policy. 

Once compliance mapping is enabled, future AROs will include a Compliance and Best Practices section that provides information about the controls the AROs impacts.

Enable Compliance Mapping

Navigate to the sidebar’s Service Profile page (Administration section). In the Compliance and Best Practices card, click the Frameworks button.

The Compliance Frameworks window will appear on your screen. Select the compliance framework(s) you want to map to and click Save.

You will be taken back to the Service Profile, and your selected framework(s) will be visible in the Compliance and Best Practices section.

Disable Compliance Mapping

To disable Compliance Mapping for AROs, uncheck all previously selected frameworks in the Service Profile’s Compliance and Best Practices section.