Bring your MARS-E controls and evidence together in one place
MARS-E 2.0, the Minimum Acceptable Risk Standards for Exchanges, is the CMS document suite of security and privacy controls for systems that handle Affordable Care Act data, published on 10 November 2015. It adapts NIST SP 800-53 Rev. 4 and adds CMS implementation standards, ACA privacy requirements from 45 CFR 155.260 and IRS Publication 1075 rules for federal tax information. CMS later issued version 2.2 and has now replaced MARS-E with ARC-AMPE.
Is MARS-E right for your organisation?
MARS-E applied to ACA Administering Entities: federal and state Exchanges, state Medicaid and CHIP agencies, Basic Health Program agencies, and the contractors running their systems. These entities had to implement it to obtain an Authority to Connect to the CMS Data Services Hub. Today it matters mainly to teams with legacy MARS-E documentation moving to ARC-AMPE.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- Centers for Medicare & Medicaid Services (CMS)
- Published
- 10 November 2015 (version 2.0)
- Based on
- NIST SP 800-53 Rev. 4
- Applies to
- ACA Administering Entities and their contractors
- Legal basis
- 45 CFR 155.260 and 155.280
- Assessment route
- Evidence such as an SSP, security assessment report and POA&M reviewed by CMS for Authority to Connect to the Data Services Hub
- Status
- Superseded by version 2.2 (2021), then replaced by ARC-AMPE (2025)
- Type
- Standard (mandatory)
- Region
- US
- In OneClickComply
- Supported today
OneClickComply makes it simple
MARS-E 2.0 is mapped in OneClickComply's control library and available on request, so you can track its controls and evidence alongside your other frameworks. Because one set of controls is mapped across many standards, evidence collected for MARS-E also counts towards NIST SP 800-53, HIPAA and ISO 27001, which makes the move to ARC-AMPE a gap exercise rather than a rebuild.
Requirements covered
18 security control families (AC to PM) and 8 privacy control families (AP to UL) in Volume III, set out across 352 control tables with CMS implementation standards, plus an appendix of IRS requirements for safeguarding federal tax information.
Manual MARS-E vs. OneClickComply
- Hundreds of control tables tracked across spreadsheets and Word templates
- Evidence for the system security plan gathered by hand from every tool
- Policies for 26 control families written and kept current manually
- Configuration drift only found at the next assessment or scan
- Rework when moving legacy MARS-E documentation to ARC-AMPE
- Controls tracked in one platform with owners and status
- Evidence collected automatically from connected systems
- Policies generated from your real environment
- Alerts as soon as a monitored control drifts
- Mapped controls that carry evidence across to other frameworks
Everything you need for MARS-E
MARS-E 2.0 security and privacy control families mapped in the control library, available on request
Automated evidence collection for access control, audit logging and configuration controls
AutoComplete policies for the policy and procedure controls in each family
Continuous monitoring with alerts when controls drift between assessments
Control mapping to NIST SP 800-53, HIPAA and ISO 27001 to ease the move to ARC-AMPE
Risk register, vendor risk management and Ask an Auditor for expert guidance
Three steps to MARS-E compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against MARS-E and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates MARS-E-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
CMS MARS-E 2.0 requirements
The 18 security and 8 privacy control families in MARS-E 2.0 Volume III, which together contain 352 control tables, plus the appendix of IRS requirements for federal tax information.
| Reference | Requirement |
|---|---|
| AC | Access Control |
| AT | Awareness and Training |
| AU | Audit and Accountability |
| CA | Security Assessment and Authorization |
| CM | Configuration Management |
| CP | Contingency Planning |
| IA | Identification and Authentication |
| IR | Incident Response |
| MA | Maintenance |
| MP | Media Protection |
| PE | Physical and Environmental Protection |
| PL | Planning |
| PS | Personnel Security |
| RA | Risk Assessment |
| SA | System and Services Acquisition |
| SC | System and Communications Protection |
| SI | System and Information Integrity |
| PM | Program Management |
| AP | Authority and Purpose |
| AR | Accountability, Audit, and Risk Management |
Always check the official MARS-E text for the exact wording.
MARS-E FAQs
What is MARS-E 2.0?
MARS-E 2.0 is the Minimum Acceptable Risk Standards for Exchanges, a CMS document suite of security and privacy requirements for Affordable Care Act systems, published on 10 November 2015. It has four volumes: a harmonised framework, the standards themselves, a catalogue of controls and a system security plan template. The controls adapt NIST SP 800-53 Rev. 4 and add ACA and IRS Publication 1075 requirements.
Who must comply with MARS-E?
MARS-E applies to ACA Administering Entities: federal and state Exchanges or Marketplaces, state Medicaid agencies, Children's Health Insurance Program agencies and state agencies administering the Basic Health Program. Contractors that build or run systems for these entities are also expected to implement the controls. Compliance was a condition of CMS granting an Authority to Connect to the Data Services Hub.
Is MARS-E still in use?
No, MARS-E has been replaced. CMS issued MARS-E version 2.2 in 2021 and then published the Acceptable Risk Controls for ACA, Medicaid, and Partner Entities (ARC-AMPE) in March 2025. ARC-AMPE states that it supersedes and replaces MARS-E and the Non-Exchange Entity GRC Framework, and it is based on NIST SP 800-53 Rev. 5. MARS-E remains relevant for legacy documentation and transition work.
What happens if an Administering Entity does not meet MARS-E?
The main consequence is losing or being refused access to federal data. CMS used evidence such as the system security and privacy plan, security assessment report, penetration test results and plan of actions and milestones to decide whether to approve an Authority to Connect to the Data Services Hub. Unresolved findings can delay or block that connection, which Exchanges and Medicaid agencies need for eligibility checks.
How does MARS-E relate to NIST SP 800-53?
MARS-E 2.0 is built on NIST SP 800-53 Rev. 4. It uses the same 18 security control families and the 8 privacy families from Appendix J, then adds CMS implementation standards, ACA-specific controls such as email and fax usage, and IRS Publication 1075 requirements. If you already run an SP 800-53 programme, much of your existing control work carries across to MARS-E.
How does MARS-E relate to HIPAA and ISO 27001?
MARS-E is a separate CMS requirement, not a replacement for HIPAA or ISO 27001. HIPAA's Security Rule sets broader safeguards for health information, while MARS-E prescribes detailed NIST-based controls for ACA systems. ISO 27001 is a voluntary certifiable standard. Many controls overlap, such as access control, logging and incident response, so evidence can often be reused across all three.
How do you comply with MARS-E?
You comply by implementing the Volume III controls, documenting them in the system security plan from Volume IV, and having them independently assessed. Typical artefacts include a security assessment report, vulnerability scans, penetration test results, a privacy impact assessment and a plan of actions and milestones for open findings. New programmes should now work to ARC-AMPE, which has replaced MARS-E.
Does OneClickComply support MARS-E?
Yes, on request. MARS-E 2.0 is mapped in OneClickComply's control library and available on request, rather than being a standard framework you can switch on today. Once enabled, you can track its controls, collect evidence automatically and reuse that evidence across mapped frameworks such as NIST SP 800-53, HIPAA and ISO 27001. OneClickComply does not grant CMS authorisations.
Related standards
All standards- NIST SP 800-53 Rev. 5Standard · US
- NIST SP 800-53 Rev. 4Standard · US
- SOC 2 (Trust Services Criteria)Standard · US
- FBI CJIS Security Policy v6.0Standard · US
- NIST SP 800-171 Rev. 3Standard · US
- NIST SP 800-53B Privacy BaselineStandard · US
- Texas DIR Security Control Standards Catalog v2.2Standard · US
- NERC CIPStandard · US
Get MARS-E ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.