App Compliance Automation Tool for Microsoft 365
In this article, you'll learn what the App Compliance Automation Tool for Microsoft 365 (ACAT) is, and how it simplifies compliance and obtaining the Microsoft 365 Certification.
Note
ACAT is currently in public preview and only supports apps built on Azure. In the future, it will also support applications built on other clouds or mix of different clouds.
Note
If you would like to provide feedback to ACAT public preview, please complete this form. The ACAT product team will follow up with you as soon as possible once we get your messages.
What is App Compliance Automation Tool for Microsoft 365
App Compliance Automation Tool for Microsoft 365 (ACAT) is a service in Azure portal that helps simplify the compliance journey for any app that consumes Microsoft 365 customer data and is published via Partner Center. It's an application-centric compliance automation tool that helps you complete Microsoft 365 Certification with greater ease and convenience. In Public Preview, ACAT is available to apps running on Azure.
With this tool, you'll quickly be able to define the compliance boundary for your applications, monitor the compliance results automatically, and complete the compliance audit more easily. The compliance boundary is the cloud infrastructure that supports delivery of the app and any backend systems that the app may be communicating with.
In addition to providing a faster track towards Microsoft 365 Certification, ACAT can help you in various compliance scenarios for Microsoft 365 applications:
- Detailed view and remediation steps for Microsoft 365 Certification responsibilities.
- Automatic daily reports to help you get compliance results continuously.
- Security and compliance best practices that can be used as guidance in the early phase of your application lifecycle.
Benefits of ACAT
Application-centric compliance journey.
- ACAT reports compliance status daily for the cloud environment of your applications, which you can integrate with your current cloud infrastructure compliance strategy.
- Developers can invoke ACAT even during the app development phase.
Accelerates the process of getting Microsoft 365 certified.
- ACAT fully automates certain Microsoft 365 Certification controls.
- There's a continuously growing automation list that is actively being developed by Microsoft.
Native integration with Microsoft 365 Certification workflow.
- ACAT is fully integrated with Partner Center for Microsoft 365 Certification purpose.
Concepts of ACAT
Regulatory Compliance Report
In ACAT, you can audit the application's compliance status by creating a compliance report for it. You can define the compliance boundary for your application by specifying the Azure resources that build the application. Create multiple reports for one application, based on different development environments and stages.
Once the report is created, ACAT will start to gather the compliance data on your pre-defined trigger time, and then generate the compliance results as a report for you. Meanwhile, ACAT will keep monitoring the compliance changes for your compliance report continuously, until you choose to delete the report.
Microsoft 365 Certification control
ACAT expediting the Microsoft 365 Certification by automating the compliance controls. Based on the automation status, there are three types of compliance controls defined in ACAT.
- Fully automated control: The Microsoft certification control is fully automated by ACAT.
- Partial automated manual control: ACAT could automate partial responsibilities of the Microsoft 365 Certification control. You'll need to follow the instructions provided by ACAT to complete the remaining responsibilities.
- Fully manual control: You need to follow the Microsoft 365 Certification submission guide to complete remaining responsibilities.
In long term, ACAT will improve the automation coverage of Microsoft 365 Certification controls continuously.
Customer responsibility
There's a set of customer responsibilities associated with each control that need to be satisfied. They're responsibilities retained by you in the following areas: data, endpoints, account, access management, etc.
ACAT collects data for each customer responsibility and returns an assessment result for it. It also provides you with a remediation action, which is our guidance that helps you align with Microsoft 365 Certification standards.
Understand the compliance state of the Microsoft 365 certification controls
In the Regulatory Compliance Report, ACAT defines customer responsibilities for each fully automated control and partial automated manual control. There are two compliance states for the customer responsibility.
- Passed: The cloud resources applicable for the customer responsibility are healthy or there's no cloud resources applicable in this compliance report.
- Failed: There is at least one cloud resource unhealthy. You could follow the remediation steps to resolve the unhealthy resources.
The compliance states of the Microsoft 365 Certification control are based on the compliance states of customer responsibilities.
- Passed: There are no failed customer responsibilities for the Microsoft 365 Certification controls.
- Failed: There are failed customer responsibilities for the Microsoft 365 Certification controls.
- Manual Review Required: The Microsoft 365 Certification controls require further actions to be completed in Microsoft Partner Network and review them with reviewer manually. Follow the Microsoft 365 Certification submission guide to complete remaining responsibilities.
Note
If the partial automated manual control has failed customer responsibility, the control state will be Failed. Once the failed customer responsibility is resolved, the control state will be changed to Manual Review Required since it still requires further actions to be completed.
FAQ
What are manual controls and partially automated controls?
Each compliance control is associated with a set of customer responsibilities, which ACAT collects compliance data for. However, not all controls for Microsoft 365 Certification are covered by ACAT as of now (there's an ongoing effort to expand the coverage). For the partially automated control, ACAT automates parts of the customer responsibilities. The assessment results of a partially automated control will be used in Microsoft 365 Certification audit, with further actions required by you to meet the remaining requirement. For the manual controls, ACAT currently doesn't automate any customer responsibilities.
How can I know whether the control is fully automated?
| Security Domain | Control Family | Control Number | ACAT Automation State |
|---|---|---|---|
| Operational Security / Secure Development | Malware Protection - Anti-Virus | Control 1 | Manual |
| Operational Security / Secure Development | Malware Protection - Anti-Virus | Control 2 | Fully Automated |
| Operational Security / Secure Development | Malware Protection - Anti-Virus | Control 3 | Fully Automated |
| Operational Security / Secure Development | Malware Protection - Anti-Virus | Control 4 | Fully Automated |
| Operational Security / Secure Development | Malware Protection - Anti-Virus | Control 5 | Fully Automated |
| Operational Security / Secure Development | Malware Protection - Application Control | Control 6 | Manual |
| Operational Security / Secure Development | Malware Protection - Application Control | Control 7 | Manual |
| Operational Security / Secure Development | Malware Protection - Application Control | Control 8 | Fully Automated |
| Operational Security / Secure Development | Malware Protection - Application Control | Control 9 | Fully Automated |
| Operational Security / Secure Development | Patch Management - Risk Ranking | Control 10 | Manual |
| Operational Security / Secure Development | Patch Management - Risk Ranking | Control 11 | Fully Automated |
| Operational Security / Secure Development | Patch Management - Risk Ranking | Control 12 | Manual |
| Operational Security / Secure Development | Patch Management - Patching | Control 13 | Manual |
| Operational Security / Secure Development | Patch Management - Patching | Control 14 | Manual |
| Operational Security / Secure Development | Patch Management - Patching | Control 15 | Partially Automated |
| Operational Security / Secure Development | Vulnerability Scanning | Control 16 | Manual |
| Operational Security / Secure Development | Vulnerability Scanning | Control 17 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 18 | Manual |
| Operational Security / Secure Development | Firewall - Firewalls | Control 19 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 20 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 21 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 22 | Manual |
| Operational Security / Secure Development | Firewall - Firewalls | Control 23 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 24 | Fully Automated |
| Operational Security / Secure Development | Firewall - Firewalls | Control 25 | Manual |
| Operational Security / Secure Development | Firewall - WAFs (OPTIONAL) | Control 26 | Fully Automated |
| Operational Security / Secure Development | Firewall - WAFs (OPTIONAL) | Control 27 | Fully Automated |
| Operational Security / Secure Development | Firewall - WAFs (OPTIONAL) | Control 28 | Fully Automated |
| Operational Security / Secure Development | Change Control | Control 29 | Manual |
| Operational Security / Secure Development | Change Control | Control 30 | Manual |
| Operational Security / Secure Development | Change Control | Control 31 | Manual |
| Operational Security / Secure Development | Change Control | Control 32 | Manual |
| Operational Security / Secure Development | Change Control | Control 33 | Manual |
| Operational Security / Secure Development | Secure Software Development/Deployment | Control 34 | Manual |
| Operational Security / Secure Development | Secure Software Development/Deployment | Control 35 | Manual |
| Operational Security / Secure Development | Secure Software Development/Deployment | Control 36 | Manual |
| Operational Security / Secure Development | Secure Software Development/Deployment | Control 37 | Manual |
| Operational Security / Secure Development | Secure Software Development/Deployment | Control 38 | Manual |
| Operational Security / Secure Development | Account Management | Control 39 | Manual |
| Operational Security / Secure Development | Account Management | Control 40 | Fully Automated |
| Operational Security / Secure Development | Account Management | Control 41 | Manual |
| Operational Security / Secure Development | Account Management | Control 42 | Fully Automated |
| Operational Security / Secure Development | Account Management | Control 43 | Fully Automated |
| Operational Security / Secure Development | Account Management | Control 44 | Manual |
| Operational Security / Secure Development | Account Management | Control 45 | Fully Automated |
| Operational Security / Secure Development | Account Management | Control 46 | Manual |
| Operational Security / Secure Development | Account Management | Control 47 | Fully Automated |
| Operational Security / Secure Development | Account Management | Control 48 | Manual |
| Operational Security / Secure Development | Account Management | Control 49 | Fully Automated |
| Operational Security / Secure Development | Intrusion Detection and Prevention (OPTIONAL) | Control 50 | Fully Automated |
| Operational Security / Secure Development | Intrusion Detection and Prevention (OPTIONAL) | Control 51 | Fully Automated |
| Operational Security / Secure Development | Intrusion Detection and Prevention (OPTIONAL) | Control 52 | Fully Automated |
| Operational Security / Secure Development | Intrusion Detection and Prevention (OPTIONAL) | Control 53 | Fully Automated |
| Operational Security / Secure Development | Intrusion Detection and Prevention (OPTIONAL) | Control 54 | Fully Automated |
| Operational Security / Secure Development | Security Event Logging | Control 55 | Manual |
| Operational Security / Secure Development | Security Event Logging | Control 56 | Fully Automated |
| Operational Security / Secure Development | Security Event Logging | Control 57 | Fully Automated |
| Operational Security / Secure Development | Security Event Logging | Control 58 | Fully Automated |
| Operational Security / Secure Development | Security Event Logging | Control 59 | Manual |
| Operational Security / Secure Development | Security Event Logging | Control 60 | Fully Automated |
| Operational Security / Secure Development | Security Event Logging | Control 61 | Fully Automated |
| Operational Security / Secure Development | Reviewing (Logging Data) | Control 62 | Manual |
| Operational Security / Secure Development | Reviewing (Logging Data) | Control 63 | Manual |
| Operational Security / Secure Development | Reviewing (Logging Data) | Control 64 | Manual |
| Operational Security / Secure Development | Security Event Alerting | Control 65 | Manual |
| Operational Security / Secure Development | Security Event Alerting | Control 66 | Fully Automated |
| Operational Security / Secure Development | Security Event Alerting | Control 67 | Manual |
| Operational Security / Secure Development | Information Security Risk Management | Control 68 | Manual |
| Operational Security / Secure Development | Information Security Risk Management | Control 69 | Manual |
| Operational Security / Secure Development | Information Security Risk Management | Control 70 | Manual |
| Operational Security / Secure Development | Information Security Risk Management | Control 71 | Manual |
| Operational Security / Secure Development | Information Security Risk Management | Control 72 | Manual |
| Operational Security / Secure Development | Incident Response | Control 73 | Manual |
| Operational Security / Secure Development | Incident Response | Control 74 | Manual |
| Operational Security / Secure Development | Incident Response | Control 75 | Manual |
| Operational Security / Secure Development | Incident Response | Control 76 | Manual |
| Data Handling Security and Privacy | Data in Transit | Control 1 | Fully Automated |
| Data Handling Security and Privacy | Data in Transit | Control 2 | Manual |
| Data Handling Security and Privacy | Data in Transit | Control 3 | Manual |
| Data Handling Security and Privacy | Data At Rest | Control 4 | Fully Automated |
| Data Handling Security and Privacy | Data At Rest | Control 5 | Fully Automated |
| Data Handling Security and Privacy | Data At Rest | Control 6 | Manual |
| Data Handling Security and Privacy | Data Retention and Disposal | Control 7 | Manual |
| Data Handling Security and Privacy | Data Retention and Disposal | Control 8 | Manual |
| Data Handling Security and Privacy | Data Retention and Disposal | Control 9 | Manual |
| Data Handling Security and Privacy | Data Access Management | Control 10 | Manual |
| Data Handling Security and Privacy | Data Access Management | Control 11 | Manual |
| Data Handling Security and Privacy | Data Access Management | Control 12 | Manual |
| Data Handling Security and Privacy | Data Access Management | Control 13 | Manual |
| Data Handling Security and Privacy | Data Access Management | Control 14 | Manual |
| Data Handling Security and Privacy | GDPR | Control 15 | Manual |
| Data Handling Security and Privacy | GDPR | Control 16 | Manual |
| Data Handling Security and Privacy | GDPR | Control 17 | Manual |
I made the suggested changes base on the remediation suggestion, yet the control is still failing
After you take action to resolve the failure, you need to wait for ACAT to fetch the refreshed assessment results to update the control status. Assessments are run every 24 hours at your pre-set trigger time.
How is the compliance report used in the certification process?
ACAT is seamlessly integrated with Partner Center to complete your Microsoft 365 Certification journey. During the compliance report creation, you can edit the Microsoft 365 Certification configuration that is, Offer GUID. It's optional during creation, and you can configure it later when you start publishing the application.