[{"data":1,"prerenderedAt":11935},["ShallowReactive",2],{"\u002Fframeworks\u002Fcmmc":3,"framework-hub-topics-cmmc":536,"related-glossary-cmmc":3707,"related-frameworks-cmmc":8852},{"id":4,"title":5,"advantages":6,"body":28,"checklist":455,"cta":464,"description":436,"extension":467,"faq":468,"hero":486,"lastUpdated":502,"meta":503,"name":504,"navigation":505,"path":506,"resources":507,"seo":520,"slug":523,"stats":524,"stem":534,"__hash__":535},"frameworks\u002F5.frameworks\u002Fcmmc.md","Cmmc",[7,14,21],{"title":8,"description":9,"bullets":10},"NIST 800-171 control mapping","Every CMMC Level 2 practice is linked to its NIST SP 800-171 source requirement with pre-written narratives.",[11,12,13],"14 control families mapped to 110 security requirements","AI-drafted implementation narratives and testing procedures","Gap analysis highlights missing controls before your assessment",{"title":15,"description":16,"bullets":17},"Assessment preparation workspace","Whether you self-assess or engage a C3PAO, episki organizes evidence and scoring in one place.",[18,19,20],"POA&M tracking with 180-day close-out reminders","Scoring methodology aligned to DoD assessment guide","Assessor portal with scoped read-only access",{"title":22,"description":23,"bullets":24},"Cross-framework reuse","Controls mapped to CMMC automatically satisfy overlapping NIST CSF, ISO 27001, and FedRAMP requirements.",[25,26,27],"Unified control graph eliminates duplicate documentation","Evidence collected once, reused across every framework","Framework coverage dashboard shows gaps at a glance",{"type":29,"value":30,"toc":435},"minimark",[31,36,40,43,48,56,67,78,82,91,125,128,132,144,157,161,164,181,194,197,201,204,215,222,226,241,244,248,256,282,286,314,318,326,330,338,342,350,354,357,396,400,432],[32,33,35],"h2",{"id":34},"what-is-cmmc","What is CMMC?",[37,38,39],"p",{},"The Cybersecurity Maturity Model Certification (CMMC) is the Department of Defense's verification program for ensuring that every organization in the defense industrial base adequately protects sensitive federal information. CMMC takes the cybersecurity standards the DoD has required for years and turns them into a verifiable certification that contractors must hold before a contract can be awarded.",[37,41,42],{},"Before CMMC, defense contractors were expected to comply with DFARS clause 252.204-7012 and the 110 security requirements in NIST SP 800-171 on the honor system. They self-attested. A 2018 DoD Inspector General report and the 2019 MITRE \"Deliver Uncompromised\" study both found the self-attestation model was failing — contractors claimed compliance they had not achieved, and nation-state adversaries were quietly stealing terabytes of Controlled Unclassified Information (CUI) from the supply chain. CMMC is the DoD's response: instead of trust, the Pentagon now requires verification.",[44,45,47],"h3",{"id":46},"cmmc-10-to-cmmc-20","CMMC 1.0 to CMMC 2.0",[37,49,50,51,55],{},"The first version of CMMC — sometimes called CMMC 1.0 — was announced in January 2020. It had ",[52,53,54],"strong",{},"five maturity levels",", added its own unique practices and maturity processes on top of NIST SP 800-171, and would have required third-party assessment for almost everyone in the defense supply chain. Industry pushback was substantial. Small businesses said the compliance burden was unaffordable. Cybersecurity teams argued that the custom CMMC practices and \"maturity processes\" diverged from established standards without clear security benefit.",[37,57,58,59,62,63,66],{},"In November 2021 the DoD announced ",[52,60,61],{},"CMMC 2.0",", a streamlined successor. CMMC 2.0 collapsed the five levels into ",[52,64,65],{},"three",", eliminated the custom CMMC practices, and aligned Level 2 directly with NIST SP 800-171 so there is no daylight between the two. It also re-introduced self-assessment as a compliant path for many contracts — a concession to cost that CMMC 1.0 did not allow.",[37,68,69,70,73,74,77],{},"The CMMC 2.0 program rule (32 CFR Part 170) was published in the Federal Register on October 15, 2024, and took effect on ",[52,71,72],{},"December 16, 2024",". The companion DFARS rule (48 CFR) was published on September 10, 2025, and took effect on ",[52,75,76],{},"November 10, 2025"," — the moment CMMC moved from a program on paper to an enforceable contract requirement. When we talk about \"CMMC\" today, we mean CMMC 2.0 as enforced through DFARS.",[44,79,81],{"id":80},"the-three-cmmc-levels","The three CMMC levels",[37,83,84,85,90],{},"CMMC uses a tiered model so that a small contractor handling a bill of materials gets a proportionate requirement, while a prime contractor engineering a weapons system gets a much heavier one. Each CMMC level builds on the one below it. ",[86,87,89],"a",{"href":88},"\u002Fframeworks\u002Fcmmc\u002Flevels","See the full breakdown of CMMC levels"," for control counts, assessment types, and scoping rules.",[92,93,94,105,115],"ul",{},[95,96,97,100,101,104],"li",{},[52,98,99],{},"Level 1 — Foundational."," Covers the basic safeguarding of Federal Contract Information (FCI). It requires 17 practices drawn directly from FAR 52.204-21. Any organization that processes FCI under a DoD contract must meet Level 1. It is verified through an ",[52,102,103],{},"annual self-assessment"," with a senior official affirming the results in the Supplier Performance Risk System (SPRS).",[95,106,107,110,111,114],{},[52,108,109],{},"Level 2 — Advanced."," Protects Controlled Unclassified Information (CUI). It requires all ",[52,112,113],{},"110 security requirements"," from NIST SP 800-171 Rev 2 across 14 control families. Level 2 has two assessment paths — self-assessment for less sensitive CUI, and third-party C3PAO assessment for more sensitive CUI or critical programs. Level 2 is where most defense contractors will land.",[95,116,117,120,121,124],{},[52,118,119],{},"Level 3 — Expert."," Reserved for the most sensitive DoD programs where advanced persistent threats are a credible risk. It includes every Level 2 requirement ",[52,122,123],{},"plus 24 enhanced requirements"," selected from NIST SP 800-172. Level 3 is verified through a government-led DIBCAC assessment and requires a valid Level 2 C3PAO certification as a prerequisite.",[37,126,127],{},"The CMMC level you need is determined by the specific solicitation or contract — not by company size or industry. A small engineering firm with a CUI-sensitive subcontract may need Level 2 C3PAO, while a larger prime on a less sensitive contract may only need Level 1.",[44,129,131],{"id":130},"nist-sp-800-171-is-the-heart-of-cmmc","NIST SP 800-171 is the heart of CMMC",[37,133,134,135,138,139,143],{},"CMMC Level 2 is a ",[52,136,137],{},"direct one-to-one mapping"," to NIST SP 800-171 Rev 2. There are no extra practices, no CMMC-specific maturity processes, no layered-on requirements. Every CMMC Level 2 practice corresponds to a single NIST SP 800-171 security requirement. This alignment was intentional: it made CMMC easier to implement and easier to audit, and it meant organizations that had been working toward ",[86,140,142],{"href":141},"\u002Fglossary\u002Fnist","NIST"," SP 800-171 compliance since 2017 did not have to start over.",[37,145,146,147,151,152,156],{},"The 110 requirements are organized into 14 control families including Access Control, Audit and Accountability, Configuration Management, Identification and Authentication, Incident Response, System and Communications Protection, and System and Information Integrity. CMMC Level 3 layers 24 additional enhanced requirements on top, drawn from NIST SP 800-172. ",[86,148,150],{"href":149},"\u002Fframeworks\u002Fcmmc\u002Fnist-800-171-mapping","See the detailed NIST SP 800-171 mapping"," for the full control family breakdown and cross-framework overlap with ",[86,153,155],{"href":154},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," and ISO 27001.",[44,158,160],{"id":159},"who-needs-cmmc","Who needs CMMC?",[37,162,163],{},"Any organization that processes, stores, or transmits FCI or CUI as part of a DoD contract or subcontract will need CMMC certification. That is a much broader population than \"defense contractors\" in the traditional sense. CMMC applies to:",[92,165,166,169,172,175,178],{},[95,167,168],{},"Prime contractors holding contracts directly with the DoD",[95,170,171],{},"Subcontractors at every tier in the supply chain",[95,173,174],{},"Cloud service providers hosting DoD contractor data",[95,176,177],{},"Managed service providers and IT vendors with access to FCI or CUI",[95,179,180],{},"Foreign suppliers in the defense industrial base handling covered information",[37,182,183,184,188,189,193],{},"CMMC flow-down is one of the most important operational realities. If a prime contractor shares CUI with a subcontractor, that subcontractor must hold the same CMMC level. If that subcontractor further shares CUI with a tier-three supplier, the tier-three supplier must also be certified. CMMC's reach extends deep into the supply chain. ",[86,185,187],{"href":186},"\u002Fframeworks\u002Fcmmc\u002Fwho-needs-cmmc","See who needs CMMC"," for detailed scoping guidance, and our ",[86,190,192],{"href":191},"\u002Findustry\u002Fgovernment","government industry page"," for broader public-sector compliance context.",[37,195,196],{},"Roughly 80,000 organizations are expected to pursue CMMC Level 2, and a few thousand the most stringent CMMC Level 3 — numbers from the DoD's own economic analysis of the CMMC rule.",[44,198,200],{"id":199},"the-cmmc-assessment-process","The CMMC assessment process",[37,202,203],{},"CMMC assessments come in three flavors that align to the three CMMC levels: self-assessment, C3PAO third-party assessment, and DIBCAC government-led assessment. Regardless of type, the assessment methodology is the same — scoring is based on the DoD Assessment Methodology and NIST SP 800-171A objectives.",[37,205,206,207,210,211,214],{},"A CMMC Level 2 C3PAO assessment typically runs through five stages: scoping, readiness review, evidence collection and review, on-site or virtual assessment, and scoring with any final findings. A Level 2 assessment starts with a score of 110 and subtracts points for each unmet objective. A score of 110 yields full certification. A score of ",[52,208,209],{},"88 or above"," with remaining gaps documented in a Plan of Action and Milestones (POA&M) yields a ",[52,212,213],{},"conditional"," certification with a 180-day remediation window. A score below 88 yields no certification at all.",[37,216,217,221],{},[86,218,220],{"href":219},"\u002Fframeworks\u002Fcmmc\u002Fassessment-process","See the full CMMC assessment process"," for scoring details, POA&M rules, and what you can and cannot defer.",[44,223,225],{"id":224},"c3paos-and-certified-assessors","C3PAOs and certified assessors",[37,227,228,229,232,233,236,237,240],{},"Third-party CMMC assessments are conducted by ",[52,230,231],{},"CMMC Third-Party Assessment Organizations (C3PAOs)"," accredited by the Cyber AB (the Cyber Accreditation Body, formerly the CMMC Accreditation Body). C3PAOs employ ",[52,234,235],{},"Certified CMMC Assessors (CCAs)"," and ",[52,238,239],{},"Certified CMMC Professionals (CCPs)"," who conduct the actual assessment work. CCAs must pass a certification exam administered by the Cyber AB and complete ongoing professional development.",[37,242,243],{},"The pool of accredited C3PAOs is deliberately limited — growing from just a handful at the start of 2024 to several dozen by early 2026. That scarcity matters. As CMMC Phase 2 enforcement begins in November 2026 and more contracts require C3PAO assessment, assessor availability will tighten. Organizations that wait to begin CMMC preparation until a contract requires it will likely find assessment slots booked six to twelve months out.",[44,245,247],{"id":246},"cmmc-implementation-timeline","CMMC implementation timeline",[37,249,250,251,255],{},"CMMC enforcement follows a four-phase rollout under the DFARS rule. The rollout gradually expands CMMC requirements over four years so the assessor ecosystem can scale and contractors have time to prepare. ",[86,252,254],{"href":253},"\u002Fframeworks\u002Fcmmc\u002Fimplementation-timeline","See the full CMMC implementation timeline"," for dates and milestones.",[92,257,258,264,270,276],{},[95,259,260,263],{},[52,261,262],{},"Phase 1 (November 2025 – November 2026)."," Active now. CMMC Level 1 and Level 2 self-assessments appear as conditions of award in select solicitations. A limited number of contracts require Level 2 C3PAO assessments at DoD discretion.",[95,265,266,269],{},[52,267,268],{},"Phase 2 (November 2026 – November 2027)."," CMMC Level 2 C3PAO certification requirements expand significantly. Level 3 requirements begin appearing in select solicitations.",[95,271,272,275],{},[52,273,274],{},"Phase 3 (November 2027 – November 2028)."," CMMC Level 2 and Level 3 requirements appear broadly across applicable DoD contracts.",[95,277,278,281],{},[52,279,280],{},"Phase 4 (November 2028 onward)."," All DoD contracts requiring FCI or CUI handling include the appropriate CMMC level as a condition of award. Full CMMC enforcement.",[44,283,285],{"id":284},"cmmc-and-dfars","CMMC and DFARS",[37,287,288,289,292,293,236,296,299,300,303,304,308,309,313],{},"CMMC is the certification. DFARS is the contractual mechanism that makes the certification binding. ",[52,290,291],{},"DFARS 252.204-7012"," has required safeguarding of covered defense information and rapid incident reporting since 2017. ",[52,294,295],{},"DFARS 252.204-7019",[52,297,298],{},"-7020"," added the requirement to post NIST SP 800-171 assessment scores to SPRS. ",[52,301,302],{},"DFARS 252.204-7021",", effective November 10, 2025, added the requirement to hold the specific CMMC level called out in the solicitation before contract award. ",[86,305,307],{"href":306},"\u002Fframeworks\u002Fcmmc\u002Fdfars-relationship","See how CMMC and DFARS relate"," for the full clause-by-clause picture. For blog-length coverage of DFARS and CMMC in context, see our ",[86,310,312],{"href":311},"\u002Fnow\u002Fcompliance-framework-comparison","compliance framework comparison",".",[44,315,317],{"id":316},"self-assessment-vs-third-party-assessment","Self-assessment vs third-party assessment",[37,319,320,321,325],{},"Not every CMMC obligation requires bringing in a C3PAO. CMMC Level 1 is always a self-assessment. CMMC Level 2 splits — some contracts accept self-assessment, and some require C3PAO certification. CMMC Level 3 is always government-led by DIBCAC. Self-assessment is cheaper and faster, but it comes with False Claims Act exposure if the attestation misrepresents your posture. Third-party CMMC assessment is more expensive but produces a defensible certification. ",[86,322,324],{"href":323},"\u002Fframeworks\u002Fcmmc\u002Fself-assessment-vs-third-party","Compare CMMC self-assessment vs third-party"," to decide which applies to you and how to budget.",[44,327,329],{"id":328},"handling-cui-the-cmmc-way","Handling CUI the CMMC way",[37,331,332,333,337],{},"Controlled Unclassified Information sits at the center of CMMC Level 2 and CMMC Level 3. Identifying CUI in your environment, marking it correctly, applying the right access controls, and documenting the CUI boundary are all preconditions for a successful CMMC assessment. FCI and CUI are not the same thing, and the differences drive which CMMC level you need. ",[86,334,336],{"href":335},"\u002Fframeworks\u002Fcmmc\u002Fcui-handling","See CUI handling under CMMC"," for marking rules, scoping guidance, and common mistakes.",[44,339,341],{"id":340},"subcontractor-requirements","Subcontractor requirements",[37,343,344,345,349],{},"CMMC flow-down affects nearly every defense prime. If you share FCI or CUI with a subcontractor, the subcontractor must hold the required CMMC level before you share the data. That means primes need to track subcontractor CMMC status across their supply chain, verify SPRS entries, and plan for the long tail of small suppliers that may not have started their CMMC journey. ",[86,346,348],{"href":347},"\u002Fframeworks\u002Fcmmc\u002Fsubcontractor-requirements","See CMMC subcontractor requirements"," for the full flow-down model and how to reduce the burden.",[44,351,353],{"id":352},"getting-cmmc-ready","Getting CMMC ready",[37,355,356],{},"CMMC readiness is not a last-mile sprint. Most organizations need 6 to 18 months to close gaps across all 110 NIST SP 800-171 requirements and prepare for CMMC Level 2. The high-leverage moves to start today:",[358,359,360,366,372,378,384,390],"ol",{},[95,361,362,365],{},[52,363,364],{},"Scope your CMMC environment."," Map where FCI and CUI enter, flow through, and are stored in your systems. Your CMMC assessment boundary is only as good as your scoping work.",[95,367,368,371],{},[52,369,370],{},"Complete your SSP."," A System Security Plan that documents every NIST SP 800-171 requirement — implementation status, responsible party, and evidence reference — is the backbone of any CMMC assessment.",[95,373,374,377],{},[52,375,376],{},"Submit a SPRS score."," Even before any contract requires CMMC, a current SPRS score demonstrates good faith and exposes gaps early. DoD agencies increasingly reference SPRS scores in source selection.",[95,379,380,383],{},[52,381,382],{},"Stand up a POA&M register."," Track every gap with an owner, a remediation plan, and a 180-day countdown. CMMC conditional certification lives or dies on POA&M closure.",[95,385,386,389],{},[52,387,388],{},"Review your flow-down."," Inventory every subcontractor, cloud service provider, and managed service provider that touches FCI or CUI. Confirm they are on their own CMMC path.",[95,391,392,395],{},[52,393,394],{},"Schedule a readiness review."," A mock CMMC assessment — internal or with a consultant or C3PAO — surfaces problems while there is still time to fix them.",[44,397,399],{"id":398},"common-cmmc-challenges","Common CMMC challenges",[92,401,402,408,414,420,426],{},[95,403,404,407],{},[52,405,406],{},"Scoping complexity."," Determining which systems, people, and processes handle CUI is often the hardest first step and the source of the most CMMC assessment rework.",[95,409,410,413],{},[52,411,412],{},"NIST SP 800-171 gaps."," Many contractors self-attested NIST SP 800-171 compliance for years but never closed all 110 requirements. CMMC exposes that gap.",[95,415,416,419],{},[52,417,418],{},"POA&M management."," Tracking remediation across teams within a 180-day window is hard without tooling. CMMC conditional certifications are revoked when POA&Ms go stale.",[95,421,422,425],{},[52,423,424],{},"Subcontractor flow-down."," Primes must verify subcontractor CMMC status continuously, not once at onboarding.",[95,427,428,431],{},[52,429,430],{},"Evidence organization."," A CMMC assessment can touch hundreds of evidence artifacts. Without a single source of truth, assessors burn billable hours chasing documents.",[37,433,434],{},"A structured approach that maps controls to NIST SP 800-171, reuses evidence across CMMC and other frameworks, tracks POA&M progress, and monitors the assessment timeline removes most of this friction — and that is exactly what the episki CMMC workspace is designed for.",{"title":436,"searchDepth":437,"depth":437,"links":438},"",2,[439],{"id":34,"depth":437,"text":35,"children":440},[441,443,444,445,446,447,448,449,450,451,452,453,454],{"id":46,"depth":442,"text":47},3,{"id":80,"depth":442,"text":81},{"id":130,"depth":442,"text":131},{"id":159,"depth":442,"text":160},{"id":199,"depth":442,"text":200},{"id":224,"depth":442,"text":225},{"id":246,"depth":442,"text":247},{"id":284,"depth":442,"text":285},{"id":316,"depth":442,"text":317},{"id":328,"depth":442,"text":329},{"id":340,"depth":442,"text":341},{"id":352,"depth":442,"text":353},{"id":398,"depth":442,"text":399},{"title":456,"description":457,"items":458},"CMMC readiness checklist inside episki","Everything is preloaded in your free trial so you can start scoping your assessment and closing gaps immediately.",[459,460,461,462,463],"NIST SP 800-171 control library with mapped CMMC practices","Level 1, 2, and 3 scoping guidance and practice sets","POA&M register with risk-ranked remediation priorities","System Security Plan (SSP) template with AI drafting","Evidence library organized by control family",{"title":465,"description":466},"Launch your CMMC workspace today","Import your NIST 800-171 controls, map them to CMMC levels, and start closing gaps before your next assessment.","md",{"title":469,"items":470},"CMMC frequently asked questions",[471,474,477,480,483],{"label":472,"content":473},"What is CMMC 2.0?","CMMC 2.0 (Cybersecurity Maturity Model Certification) is the Department of Defense's program for verifying that defense contractors protect Federal Contract Information (FCI) and Controlled Unclassified Information (CUI). The final program rule took effect December 16, 2024, and DFARS contract enforcement began November 10, 2025.",{"label":475,"content":476},"What are the three CMMC levels?","Level 1 requires 17 basic safeguarding practices for FCI based on FAR 52.204-21. Level 2 requires 110 security practices aligned to NIST SP 800-171 Rev 2 for CUI. Level 3 adds 24 enhanced practices from NIST SP 800-172 for the most sensitive programs. Each level builds on the one below it.",{"label":478,"content":479},"How much does CMMC certification cost?","Costs vary by level and organization size. Level 1 requires only an annual self-assessment. Level 2 self-assessments are free but require significant preparation effort. Level 2 C3PAO assessments typically range from $50,000 to $150,000+ depending on scope. episki reduces preparation costs by automating evidence collection and control documentation.",{"label":481,"content":482},"When will CMMC be required in contracts?","CMMC is being phased into DoD contracts over four phases. Phase 1 began November 10, 2025, requiring Level 1 and Level 2 self-assessments in select solicitations. Phase 2 (November 2026) expands Level 2 C3PAO requirements. Phase 3 (November 2027) adds Level 3. By Phase 4 (November 2028), all applicable DoD contracts will require the appropriate CMMC level.",{"label":484,"content":485},"Who needs CMMC certification?","Any organization that processes, stores, or transmits FCI or CUI as part of a DoD contract or subcontract needs CMMC certification. This includes prime contractors, subcontractors at all tiers, and cloud service providers hosting DoD data. The required level depends on the sensitivity of information handled.",{"headline":487,"title":488,"description":489,"links":490},"CMMC without the guesswork","Get assessment-ready for CMMC without rebuilding your security program","episki maps NIST SP 800-171 and 800-172 controls to CMMC levels, automates evidence collection, and keeps your POA&M current so your team can focus on winning contracts.",[491,495],{"label":492,"icon":493,"to":494},"Start CMMC trial","i-lucide-rocket","https:\u002F\u002Fepiski.app\u002Fauth\u002Fregister",{"label":496,"icon":497,"color":498,"variant":499,"to":500,"target":501},"Book a demo","i-lucide-message-circle","neutral","subtle","\u002Fdemo","_blank","2026-04-27",{},"CMMC",true,"\u002Fframeworks\u002Fcmmc",{"headline":508,"title":508,"description":509,"items":510},"CMMC acceleration resources","Give leadership and contracting officers visibility into your cybersecurity posture at every stage.",[511,514,517],{"title":512,"description":513},"Executive scorecard","Translate control work into CMMC readiness percentages and contract eligibility status.",{"title":515,"description":516},"Assessment readiness kit","Pre-assessment checklist, evidence package review, and mock scoring aligned to DIBCAC methodology.",{"title":518,"description":519},"Subcontractor flow-down tracker","Monitor which subcontractors need their own CMMC certification and track their progress.",{"title":521,"description":522},"CMMC Compliance Software","Prepare for CMMC Level 1, 2, and 3 assessments with pre-mapped NIST 800-171 controls, automated evidence collection, and C3PAO-ready workspaces. Start your free 14-day trial.","cmmc",[525,528,531],{"value":526,"description":527},"3 maturity levels","Pre-mapped practices for Level 1, Level 2, and Level 3 with assessment-type guidance for each.",{"value":529,"description":530},"110 practices","Full NIST SP 800-171 Rev 2 control set mapped to CMMC Level 2 objectives out of the box.",{"value":532,"description":533},"Phase 1 live now","DFARS enforcement began November 2025. Level 1 and Level 2 self-assessments already required in select solicitations.","5.frameworks\u002Fcmmc","p5hUeZMYUGNFyYF4xjERSy0kHoJW_1ZFhsORUKeU3is",[537,938,1422,1751,2110,2465,2798,3102,3425],{"id":538,"title":539,"body":540,"description":923,"extension":467,"faq":924,"frameworkSlug":523,"lastUpdated":925,"meta":926,"navigation":505,"path":219,"relatedTerms":927,"relatedTopics":930,"seo":933,"stem":936,"__hash__":937},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fassessment-process.md","CMMC Assessment Process",{"type":29,"value":541,"toc":905},[542,546,549,553,556,561,593,596,600,603,607,671,675,678,683,691,695,698,702,706,709,713,716,738,752,756,759,763,766,786,790,826,830,833,847,851,854,892,896],[32,543,545],{"id":544},"cmmc-assessment-types","CMMC assessment types",[37,547,548],{},"CMMC 2.0 uses three assessment types that correspond to the certification levels. The assessment type for your organization is determined by the CMMC level specified in your contract.",[44,550,552],{"id":551},"self-assessment-level-1-and-level-2","Self-assessment (Level 1 and Level 2)",[37,554,555],{},"Self-assessments are conducted internally by the organization. They are required for all Level 1 certifications and for Level 2 certifications on contracts involving less sensitive CUI.",[37,557,558],{},[52,559,560],{},"How it works:",[358,562,563,569,575,581,587],{},[95,564,565,568],{},[52,566,567],{},"Scope your environment"," — identify the systems, people, and processes that handle FCI (Level 1) or CUI (Level 2) within the assessment boundary.",[95,570,571,574],{},[52,572,573],{},"Evaluate each practice"," — assess whether your organization meets each required practice using the DoD Assessment Methodology.",[95,576,577,580],{},[52,578,579],{},"Calculate your score"," — Level 1 is pass\u002Ffail across 17 practices. Level 2 uses a scoring methodology based on 110 objectives, starting at 110 and subtracting points for unmet requirements.",[95,582,583,586],{},[52,584,585],{},"Submit to SPRS"," — enter your assessment score into the Supplier Performance Risk System.",[95,588,589,592],{},[52,590,591],{},"Affirm annually"," — a senior official must sign an annual affirmation confirming continued compliance.",[37,594,595],{},"Self-assessments must be conducted with the same rigor as third-party assessments. The DoD reserves the right to audit self-assessment scores, and material misrepresentation can result in False Claims Act liability.",[44,597,599],{"id":598},"c3pao-assessment-level-2","C3PAO assessment (Level 2)",[37,601,602],{},"Third-party assessments are conducted by CMMC Third-Party Assessment Organizations (C3PAOs) accredited by the Cyber AB (formerly the CMMC Accreditation Body). They are required for Level 2 certifications on contracts involving more sensitive CUI or critical programs.",[37,604,605],{},[52,606,560],{},[358,608,609,615,621,627,633,639,665],{},[95,610,611,614],{},[52,612,613],{},"Select a C3PAO"," — choose from the list of accredited C3PAOs published by the Cyber AB. The C3PAO assigns certified CMMC assessors to your engagement.",[95,616,617,620],{},[52,618,619],{},"Pre-assessment readiness review"," (optional but recommended) — many C3PAOs offer a readiness review to identify gaps before the formal assessment begins.",[95,622,623,626],{},[52,624,625],{},"Assessment planning"," — the C3PAO works with your organization to define scope, schedule, and logistics. This includes identifying assessment boundaries, CUI data flows, and inherited controls.",[95,628,629,632],{},[52,630,631],{},"Evidence collection and review"," — assessors review your System Security Plan (SSP), policies, procedures, and evidence artifacts. This typically takes two to four weeks depending on scope.",[95,634,635,638],{},[52,636,637],{},"On-site or virtual assessment"," — assessors interview personnel, observe processes, and test controls. Most assessments include both documentation review and interactive sessions.",[95,640,641,644,645],{},[52,642,643],{},"Scoring and findings"," — the C3PAO scores each of the 110 objectives and documents any deficiencies. You receive one of three results:\n",[92,646,647,653,659],{},[95,648,649,652],{},[52,650,651],{},"Met"," — all 110 objectives satisfied. Full certification issued.",[95,654,655,658],{},[52,656,657],{},"Conditional"," — score of 88 or above with documented POA&M items. Conditional certification issued with a 180-day remediation window.",[95,660,661,664],{},[52,662,663],{},"Not met"," — score below 88. No certification issued. You must remediate and re-engage the C3PAO.",[95,666,667,670],{},[52,668,669],{},"Certification validity"," — a full or conditional certification is valid for three years with annual affirmation of continued compliance.",[44,672,674],{"id":673},"dibcac-assessment-level-3","DIBCAC assessment (Level 3)",[37,676,677],{},"Government-led assessments are conducted by the Defense Contract Management Agency (DCMA) Defense Industrial Base Cybersecurity Assessment Center (DIBCAC). They are required for Level 3 certifications.",[37,679,680],{},[52,681,682],{},"Prerequisites:",[92,684,685,688],{},[95,686,687],{},"A valid Level 2 C3PAO certification must be in place before a Level 3 assessment can begin",[95,689,690],{},"The organization must demonstrate compliance with all 110 NIST SP 800-171 requirements plus the 24 selected NIST SP 800-172 enhanced requirements",[37,692,693],{},[52,694,560],{},[37,696,697],{},"DIBCAC assessments follow a similar structure to C3PAO assessments but are conducted by government assessors with additional focus on advanced threat scenarios, penetration-resistant architecture, and operational resilience. The assessment scope, timeline, and logistics are coordinated directly with DIBCAC.",[32,699,701],{"id":700},"scoring-methodology","Scoring methodology",[44,703,705],{"id":704},"level-1-scoring","Level 1 scoring",[37,707,708],{},"Level 1 uses a simple pass\u002Ffail model. All 17 practices must be met. There is no partial scoring or POA&M allowance for Level 1.",[44,710,712],{"id":711},"level-2-scoring","Level 2 scoring",[37,714,715],{},"The DoD Assessment Methodology for Level 2 evaluates 110 objectives (one per NIST SP 800-171 requirement). Scoring starts at 110 and subtracts points for each unmet objective:",[92,717,718,725,735],{},[95,719,720,721,724],{},"Most objectives subtract ",[52,722,723],{},"1 point"," if not met",[95,726,727,728,731,732],{},"Some higher-impact objectives subtract ",[52,729,730],{},"3 points"," or ",[52,733,734],{},"5 points",[95,736,737],{},"The specific point values are defined in the NIST SP 800-171A assessment objectives",[37,739,740,741,744,745,747,748,751],{},"A score of ",[52,742,743],{},"110"," means all requirements are met. A score of ",[52,746,209],{}," (with POA&M) qualifies for conditional certification. A score ",[52,749,750],{},"below 88"," does not qualify for any certification.",[44,753,755],{"id":754},"level-3-scoring","Level 3 scoring",[37,757,758],{},"Level 3 scoring evaluates the 24 enhanced requirements from NIST SP 800-172 in addition to the Level 2 baseline. The scoring methodology is determined by DIBCAC and follows government assessment procedures.",[32,760,762],{"id":761},"plan-of-action-and-milestones-poam","Plan of Action and Milestones (POA&M)",[37,764,765],{},"A POA&M documents security requirements that are not yet fully met and the organization's plan to remediate them. Under CMMC 2.0:",[92,767,768,774,780],{},[95,769,770,773],{},[52,771,772],{},"Level 1"," does not allow POA&Ms — all 17 practices must be met",[95,775,776,779],{},[52,777,778],{},"Level 2"," allows POA&Ms for conditional certification if the score is 88 or above",[95,781,782,785],{},[52,783,784],{},"Level 3"," allows limited POA&Ms under DIBCAC discretion",[44,787,789],{"id":788},"poam-rules-for-level-2","POA&M rules for Level 2",[92,791,792,799,806,813,816,823],{},[95,793,794,795,798],{},"Maximum of ",[52,796,797],{},"22 unmet objectives"," (score of 88+)",[95,800,801,802,805],{},"Certain critical requirements ",[52,803,804],{},"cannot"," be placed on a POA&M regardless of score",[95,807,808,809,812],{},"All POA&M items must be ",[52,810,811],{},"closed within 180 days"," of the conditional certification date",[95,814,815],{},"A C3PAO must verify POA&M closure through a close-out assessment",[95,817,818,819,822],{},"Failure to close POA&M items within 180 days ",[52,820,821],{},"revokes"," the conditional certification",[95,824,825],{},"The organization must then undergo a new full assessment",[44,827,829],{"id":828},"what-cannot-go-on-a-poam","What cannot go on a POA&M",[37,831,832],{},"The DoD has identified specific high-impact requirements that cannot be deferred via POA&M. These typically include:",[92,834,835,838,841,844],{},[95,836,837],{},"Multifactor authentication requirements",[95,839,840],{},"FIPS-validated encryption requirements",[95,842,843],{},"Requirements related to incident reporting to the DoD",[95,845,846],{},"Other requirements designated by the DoD as non-deferrable",[32,848,850],{"id":849},"preparing-for-your-assessment","Preparing for your assessment",[37,852,853],{},"Regardless of assessment type, preparation follows a similar pattern:",[358,855,856,862,868,874,880,886],{},[95,857,858,861],{},[52,859,860],{},"Define your CUI boundary"," — identify where CUI enters, flows through, and is stored in your environment. This defines your assessment scope.",[95,863,864,867],{},[52,865,866],{},"Complete your SSP"," — document every NIST SP 800-171 requirement with your implementation status, responsible parties, and evidence.",[95,869,870,873],{},[52,871,872],{},"Conduct a gap analysis"," — compare your current controls against all required practices and identify shortfalls.",[95,875,876,879],{},[52,877,878],{},"Remediate or document"," — close gaps where possible. For remaining gaps, create POA&M items with realistic remediation timelines.",[95,881,882,885],{},[52,883,884],{},"Organize evidence"," — collect and catalog evidence artifacts (screenshots, configs, policies, logs) mapped to each requirement.",[95,887,888,891],{},[52,889,890],{},"Perform a mock assessment"," — walk through the assessment process internally or with a consultant to identify weaknesses.",[32,893,895],{"id":894},"how-episki-helps","How episki helps",[37,897,898,899,904],{},"episki automates the heaviest parts of assessment preparation. The platform generates a pre-mapped SSP template aligned to NIST SP 800-171, tracks your SPRS score in real time as you close gaps, and organizes evidence by control family. POA&M items are tracked with 180-day countdown timers and assigned owners. When your C3PAO arrives, they get a scoped portal with everything organized by assessment objective — reducing assessment time and back-and-forth. ",[86,900,903],{"href":494,"rel":901},[902],"nofollow","Start a free trial"," to see your current assessment readiness.",{"title":436,"searchDepth":437,"depth":437,"links":906},[907,912,917,921,922],{"id":544,"depth":437,"text":545,"children":908},[909,910,911],{"id":551,"depth":442,"text":552},{"id":598,"depth":442,"text":599},{"id":673,"depth":442,"text":674},{"id":700,"depth":437,"text":701,"children":913},[914,915,916],{"id":704,"depth":442,"text":705},{"id":711,"depth":442,"text":712},{"id":754,"depth":442,"text":755},{"id":761,"depth":437,"text":762,"children":918},[919,920],{"id":788,"depth":442,"text":789},{"id":828,"depth":442,"text":829},{"id":849,"depth":437,"text":850},{"id":894,"depth":437,"text":895},"How CMMC assessments work — self-assessments, C3PAO third-party assessments, and DIBCAC government-led assessments including scoring, POA&Ms, and conditional certification.",null,"2026-04-16",{},[523,928,929],"grc","audit",[931,932,159],"levels","nist-800-171-mapping",{"title":934,"description":935},"CMMC Assessment Process — Self-Assessment, C3PAO, and DIBCAC Guide","Step-by-step guide to CMMC assessment types, scoring methodology, POA&M requirements, and what to expect during a C3PAO or DIBCAC assessment.","5.frameworks\u002Fcmmc\u002Fassessment-process","yKDypkTFwQoLdWiTOACXalnWiwTYLKu-4YYu3A5uDlU",{"id":939,"title":940,"body":941,"description":1394,"extension":467,"faq":1395,"frameworkSlug":523,"lastUpdated":925,"meta":1409,"navigation":505,"path":335,"relatedTerms":1410,"relatedTopics":1415,"seo":1417,"stem":1420,"__hash__":1421},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fcui-handling.md","CUI Handling Under CMMC",{"type":29,"value":942,"toc":1375},[943,947,950,953,957,960,964,967,972,986,992,996,1004,1007,1048,1053,1057,1060,1064,1067,1102,1105,1109,1112,1144,1148,1151,1195,1198,1202,1205,1249,1253,1256,1288,1292,1299,1302,1306,1309,1312,1316,1366,1368],[32,944,946],{"id":945},"cui-is-the-center-of-gravity-for-cmmc","CUI is the center of gravity for CMMC",[37,948,949],{},"CMMC exists because of CUI. The entire program — CMMC Level 2 requirements, CMMC Level 3 enhanced controls, DFARS 252.204-7012, NIST SP 800-171 — is built to protect Controlled Unclassified Information as it flows through the defense industrial base. Get CUI handling right and most of your CMMC obligations fall into place. Get it wrong and you fail assessments, miss contract awards, or worse, leak sensitive information that nation-state adversaries spend careers trying to collect.",[37,951,952],{},"This page walks through how to identify CUI, how to mark it, how to handle it, and how to scope your systems so CMMC assessors can see exactly where CUI lives in your environment.",[32,954,956],{"id":955},"fci-vs-cui-the-bright-line","FCI vs CUI: the bright line",[37,958,959],{},"The first move in any CMMC program is distinguishing Federal Contract Information (FCI) from Controlled Unclassified Information (CUI). They are related but distinct categories with very different CMMC implications.",[44,961,963],{"id":962},"federal-contract-information-fci","Federal Contract Information (FCI)",[37,965,966],{},"FCI is information provided by or generated for the government under a contract to develop or deliver a product or service — and that is not intended for public release. It excludes public-facing information (like contract award announcements) and simple transactional information (like invoices).",[37,968,969],{},[52,970,971],{},"Examples of FCI:",[92,973,974,977,980,983],{},[95,975,976],{},"Internal correspondence about a DoD contract",[95,978,979],{},"Performance reports generated for the government under contract",[95,981,982],{},"Unclassified technical specifications shared to support a contract",[95,984,985],{},"Contract deliverables that have not been released publicly",[37,987,988,991],{},[52,989,990],{},"CMMC impact:"," FCI triggers CMMC Level 1 — 17 practices, annual self-assessment.",[44,993,995],{"id":994},"controlled-unclassified-information-cui","Controlled Unclassified Information (CUI)",[37,997,998,999,313],{},"CUI is a narrower, more sensitive category. Under 32 CFR Part 2002, CUI is information the government creates or possesses — or that an entity creates or possesses for or on behalf of the government — that requires safeguarding or dissemination controls pursuant to law, regulation, or government-wide policy. CUI is defined through the ",[86,1000,1003],{"href":1001,"rel":1002},"https:\u002F\u002Fwww.archives.gov\u002Fcui",[902],"CUI Registry maintained by the National Archives",[37,1005,1006],{},"CUI categories relevant to defense contractors include:",[92,1008,1009,1015,1021,1026,1031,1036,1042],{},[95,1010,1011,1014],{},[52,1012,1013],{},"Controlled Technical Information (CTI)"," — technical data with military or space application",[95,1016,1017,1020],{},[52,1018,1019],{},"Export Controlled"," — information controlled under ITAR or EAR",[95,1022,1023],{},[52,1024,1025],{},"Naval Nuclear Propulsion Information (NNPI)",[95,1027,1028],{},[52,1029,1030],{},"Critical Infrastructure Security Information",[95,1032,1033],{},[52,1034,1035],{},"Operations Security Information",[95,1037,1038,1041],{},[52,1039,1040],{},"Procurement and Acquisition"," (specific subcategories)",[95,1043,1044,1047],{},[52,1045,1046],{},"Source Selection"," information during contract competitions",[37,1049,1050,1052],{},[52,1051,990],{}," CUI triggers CMMC Level 2 at minimum. More sensitive CUI or critical programs trigger CMMC Level 3.",[44,1054,1056],{"id":1055},"the-relationship","The relationship",[37,1058,1059],{},"All CUI is also FCI. But not all FCI is CUI. If your contract involves CUI, you are automatically dealing with FCI too — and your CMMC level is set by the most sensitive category. That usually means CMMC Level 2, which includes the 17 Level 1 FCI practices by virtue of being built on top of them.",[32,1061,1063],{"id":1062},"cui-marking-and-identification","CUI marking and identification",[37,1065,1066],{},"Proper CUI marking is a government responsibility, but it is also the place where marking most often breaks down. The official rules under 32 CFR Part 2002 require:",[92,1068,1069,1084,1090,1096],{},[95,1070,1071,1074,1075,1079,1080,1083],{},[52,1072,1073],{},"Banner marking"," at the top of every page: ",[1076,1077,1078],"code",{},"CUI"," followed by applicable categories (e.g., ",[1076,1081,1082],{},"CUI\u002F\u002FSP-EXPT",")",[95,1085,1086,1089],{},[52,1087,1088],{},"Portion marking"," on individual paragraphs, charts, and attachments where CUI content appears",[95,1091,1092,1095],{},[52,1093,1094],{},"Source and decontrolling information"," in designated marking blocks",[95,1097,1098,1101],{},[52,1099,1100],{},"Distribution limitation statements"," where applicable",[37,1103,1104],{},"In practice, marking discipline varies widely. Many contractors receive unmarked information that meets the CUI definition. The safe posture is to treat unmarked-but-apparently-CUI information as CUI and confirm with the contracting officer. When in doubt, treat it as CUI — the cost of over-protection is far lower than the cost of an under-protected CUI spill.",[44,1106,1108],{"id":1107},"identifying-cui-you-already-have","Identifying CUI you already have",[37,1110,1111],{},"If you are not sure whether CUI lives in your environment today, start with these signals:",[92,1113,1114,1120,1126,1132,1138],{},[95,1115,1116,1119],{},[52,1117,1118],{},"DFARS 252.204-7012 in your contract."," If your contract includes 7012, the DoD has effectively told you CUI is present.",[95,1121,1122,1125],{},[52,1123,1124],{},"Drawings or technical data from government customers."," CTI is pervasive in engineering and manufacturing contracts.",[95,1127,1128,1131],{},[52,1129,1130],{},"Export-controlled markings."," ITAR or EAR controlled material is CUI.",[95,1133,1134,1137],{},[52,1135,1136],{},"Information labeled \"For Official Use Only\" (FOUO)."," FOUO is a legacy marking that in most cases has been reclassified as CUI under the current regime.",[95,1139,1140,1143],{},[52,1141,1142],{},"Source selection documents during contract competitions."," Source Selection Sensitive information is CUI while the competition is active.",[32,1145,1147],{"id":1146},"cui-access-controls-under-nist-sp-800-171","CUI access controls under NIST SP 800-171",[37,1149,1150],{},"NIST SP 800-171 — and therefore CMMC Level 2 — imposes specific access controls on CUI. The Access Control family (3.1) alone contains 22 requirements, many of which directly address how CUI is accessed. Key obligations include:",[92,1152,1153,1159,1165,1171,1177,1183,1189],{},[95,1154,1155,1158],{},[52,1156,1157],{},"Authorized users only."," Limit system access to authorized users, processes acting on behalf of authorized users, and authorized devices.",[95,1160,1161,1164],{},[52,1162,1163],{},"Least privilege."," Users should have only the access necessary to perform their duties.",[95,1166,1167,1170],{},[52,1168,1169],{},"Need-to-know enforcement."," Not every authorized user should see all CUI — access should be segmented by need.",[95,1172,1173,1176],{},[52,1174,1175],{},"Multifactor authentication."," MFA is required for local and network access to systems handling CUI.",[95,1178,1179,1182],{},[52,1180,1181],{},"Encrypted mobile devices."," CUI on laptops, phones, and tablets must be encrypted with FIPS-validated cryptography.",[95,1184,1185,1188],{},[52,1186,1187],{},"Session controls."," Sessions must lock after inactivity and terminate on logout.",[95,1190,1191,1194],{},[52,1192,1193],{},"Remote access controls."," Remote access to CUI must be controlled, monitored, and encrypted.",[37,1196,1197],{},"These requirements map to specific System and Communications Protection (3.13) controls as well, particularly FIPS-validated cryptography for CUI at rest and in transit.",[32,1199,1201],{"id":1200},"cui-handling-across-the-data-lifecycle","CUI handling across the data lifecycle",[37,1203,1204],{},"Good CUI handling covers the full lifecycle of the information:",[92,1206,1207,1213,1219,1225,1231,1237,1243],{},[95,1208,1209,1212],{},[52,1210,1211],{},"Receipt."," When CUI arrives from the government or a prime contractor, verify the marking, confirm the category, and route it to a CUI-authorized system.",[95,1214,1215,1218],{},[52,1216,1217],{},"Storage."," CUI lives only on systems inside your CMMC assessment boundary. That means encrypted storage with access controls — typically a FedRAMP Moderate-equivalent environment.",[95,1220,1221,1224],{},[52,1222,1223],{},"Processing."," Tools that process CUI (CAD software, ERP systems, email, collaboration platforms) need to be part of the CMMC boundary and configured to support the required controls.",[95,1226,1227,1230],{},[52,1228,1229],{},"Transmission."," CUI in transit requires FIPS-validated encryption. This affects email (S\u002FMIME or TLS 1.2+), file transfer (SFTP, HTTPS with appropriate cipher suites), and internal network traffic segments.",[95,1232,1233,1236],{},[52,1234,1235],{},"Sharing."," Before sharing CUI with anyone — employees, subcontractors, cloud vendors — verify they are authorized. For subcontractors, that means verifying their CMMC certification.",[95,1238,1239,1242],{},[52,1240,1241],{},"Retention."," CUI retention should follow contractual requirements. Over-retention expands risk; under-retention can breach contract terms.",[95,1244,1245,1248],{},[52,1246,1247],{},"Destruction."," CUI media must be sanitized before disposal or reuse, consistent with NIST SP 800-88 media sanitization guidelines.",[32,1250,1252],{"id":1251},"system-scoping-for-cmmc-cui-boundaries","System scoping for CMMC CUI boundaries",[37,1254,1255],{},"Scoping is where CMMC assessments most often go wrong. Your CMMC assessment boundary includes every system that processes, stores, or transmits CUI, plus every system that can affect the security of those systems. The DoD's CMMC Assessment Scope guidance categorizes assets into several buckets:",[92,1257,1258,1264,1270,1276,1282],{},[95,1259,1260,1263],{},[52,1261,1262],{},"CUI Assets."," Process, store, or transmit CUI directly. Fully in scope. All NIST SP 800-171 requirements apply.",[95,1265,1266,1269],{},[52,1267,1268],{},"Security Protection Assets."," Provide security services (firewalls, SIEM, identity providers) to CUI assets. In scope. Requirements apply based on function.",[95,1271,1272,1275],{},[52,1273,1274],{},"Contractor Risk Managed Assets."," Not required to support CUI protection but could impact it if compromised. Documented but not fully assessed.",[95,1277,1278,1281],{},[52,1279,1280],{},"Specialized Assets."," Government Furnished Equipment, IoT, OT, test equipment. Documented in the SSP with appropriate protections.",[95,1283,1284,1287],{},[52,1285,1286],{},"Out-of-Scope Assets."," Cannot process, store, or transmit CUI and cannot affect CUI confidentiality. Physically or logically isolated from CUI assets.",[44,1289,1291],{"id":1290},"the-enclave-strategy","The enclave strategy",[37,1293,1294,1295,1298],{},"Many organizations reduce their CMMC scope by creating a ",[52,1296,1297],{},"CUI enclave"," — a dedicated environment (physical, virtual, or cloud-based) where CUI is concentrated and the rest of the business sits outside the CMMC boundary. Microsoft 365 GCC High is the most common enclave choice for defense contractors, but purpose-built on-premises environments and specialized cloud services are also used.",[37,1300,1301],{},"Enclaves work when they are genuinely isolated. If CUI routinely leaves the enclave into unauthorized systems — pasted into a non-CUI email, stored on a non-CUI file share, accessed from a personal device — the enclave fails and the rest of the environment becomes in-scope.",[32,1303,1305],{"id":1304},"how-this-fits-into-your-cmmc-program","How this fits into your CMMC program",[37,1307,1308],{},"CUI handling is the thread that runs through every other CMMC topic. Your SSP describes how CUI is protected. Your assessment scope is defined by where CUI lives. Your subcontractor flow-down decisions depend on which subs see CUI. Your POA&M items are prioritized based on which gaps expose CUI. Your incident response obligations under DFARS 252.204-7012 center on CUI breach reporting.",[37,1310,1311],{},"Getting CUI handling right early — especially the scoping decisions — makes the rest of the program tractable. Getting it wrong means rework on a scale that can delay certification by months.",[32,1313,1315],{"id":1314},"common-mistakes","Common mistakes",[92,1317,1318,1324,1330,1336,1342,1348,1354,1360],{},[95,1319,1320,1323],{},[52,1321,1322],{},"Treating all FCI as CUI (or vice versa)."," Over-protection wastes resources; under-protection fails assessments. Classify accurately.",[95,1325,1326,1329],{},[52,1327,1328],{},"Accepting unmarked information without verification."," If it looks like CUI, treat it as CUI and confirm with the contracting officer.",[95,1331,1332,1335],{},[52,1333,1334],{},"Over-broad scoping."," Bringing every system into the CMMC boundary when an enclave strategy would isolate CUI to a fraction of the environment.",[95,1337,1338,1341],{},[52,1339,1340],{},"Under-broad scoping."," Declaring systems out of scope that in fact touch CUI. Assessors find this quickly and it turns into a finding.",[95,1343,1344,1347],{},[52,1345,1346],{},"Using commercial Microsoft 365 for CUI."," Commercial M365 does not meet FedRAMP Moderate equivalency for CUI. Organizations handling CUI need GCC High or an equivalent authorized environment.",[95,1349,1350,1353],{},[52,1351,1352],{},"Forgetting the CUI lifecycle."," Strong access controls on storage but weak controls on transmission, sharing, or destruction still leak CUI.",[95,1355,1356,1359],{},[52,1357,1358],{},"Ignoring paper and physical CUI."," CUI can exist on paper, on whiteboards, in physical drawings, and in conversations. Physical and procedural controls matter as much as technical ones.",[95,1361,1362,1365],{},[52,1363,1364],{},"Letting CUI leave the enclave."," The strongest enclave fails if users routinely copy CUI outside it. Technical controls plus user training plus monitoring are all required.",[32,1367,895],{"id":894},[37,1369,1370,1371,1374],{},"episki maps your CMMC assessment boundary as a first-class object. You declare which systems are CUI assets, security protection assets, or contractor risk managed assets, and the platform uses that scoping to focus evidence collection and control attestations where they matter. When a system moves in or out of scope, the impact on your NIST SP 800-171 score is visible immediately. For organizations using a CUI enclave strategy, episki tracks the enclave separately from the rest of the environment and supports the documentation an assessor will expect to see. ",[86,1372,903],{"href":494,"rel":1373},[902]," to map your CUI boundary.",{"title":436,"searchDepth":437,"depth":437,"links":1376},[1377,1378,1383,1386,1387,1388,1391,1392,1393],{"id":945,"depth":437,"text":946},{"id":955,"depth":437,"text":956,"children":1379},[1380,1381,1382],{"id":962,"depth":442,"text":963},{"id":994,"depth":442,"text":995},{"id":1055,"depth":442,"text":1056},{"id":1062,"depth":437,"text":1063,"children":1384},[1385],{"id":1107,"depth":442,"text":1108},{"id":1146,"depth":437,"text":1147},{"id":1200,"depth":437,"text":1201},{"id":1251,"depth":437,"text":1252,"children":1389},[1390],{"id":1290,"depth":442,"text":1291},{"id":1304,"depth":437,"text":1305},{"id":1314,"depth":437,"text":1315},{"id":894,"depth":437,"text":895},"Controlled Unclassified Information (CUI) under CMMC — FCI vs CUI, CUI marking, handling, access controls, and defining your CMMC system scope.",{"items":1396},[1397,1400,1403,1406],{"label":1398,"content":1399},"What is the difference between FCI and CUI?","FCI (Federal Contract Information) is any information provided by or generated for the government under contract that is not intended for public release. CUI (Controlled Unclassified Information) is more sensitive — information that requires safeguarding or dissemination controls under law, regulation, or government-wide policy. All CUI is FCI, but not all FCI is CUI. FCI triggers CMMC Level 1; CUI triggers Level 2 or higher.",{"label":1401,"content":1402},"Who is responsible for marking CUI?","The originator of the information — typically the government or the prime contractor on its behalf — is responsible for marking CUI. In practice, marking is often missing or inconsistent. Contractors receiving unmarked information that appears to meet the CUI definition should treat it as CUI and contact the contracting officer for confirmation.",{"label":1404,"content":1405},"Does CUI need to be encrypted?","Yes. NIST SP 800-171 requires FIPS-validated cryptography for CUI at rest and in transit on non-federal systems. This is one of the requirements that cannot be deferred via POA&M for CMMC Level 2 conditional certification.",{"label":1407,"content":1408},"Can CUI be stored in standard Microsoft 365 or Google Workspace?","Generally no. Commercial Microsoft 365 and Google Workspace do not meet the FedRAMP Moderate equivalency required for CUI. Organizations handling CUI typically need Microsoft 365 GCC High, Google Workspace with specific FedRAMP authorizations, or a dedicated CUI enclave. Check the specific tenant's authorization before assuming coverage.",{},[1411,1412,1413,1414],"nist","data-classification","access-control","encryption",[931,159,932,1416],"assessment-process",{"title":1418,"description":1419},"CUI Handling Under CMMC: FCI vs CUI, Marking, Scoping, and Controls","How to identify, mark, handle, and scope Controlled Unclassified Information (CUI) for CMMC compliance. FCI vs CUI explained, access control requirements, and common scoping mistakes.","5.frameworks\u002Fcmmc\u002Fcui-handling","079g6EcUkr3PREZ49XZw_WBF023HlI6VeB_1h_OdPak",{"id":1423,"title":1424,"body":1425,"description":1724,"extension":467,"faq":1725,"frameworkSlug":523,"lastUpdated":925,"meta":1739,"navigation":505,"path":306,"relatedTerms":1740,"relatedTopics":1743,"seo":1746,"stem":1749,"__hash__":1750},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fdfars-relationship.md","CMMC and DFARS — How They Relate",{"type":29,"value":1426,"toc":1712},[1427,1431,1434,1437,1441,1448,1462,1465,1472,1476,1482,1485,1499,1502,1506,1512,1515,1541,1544,1548,1551,1571,1574,1578,1581,1584,1588,1591,1623,1625,1628,1666,1669,1671,1703,1705],[32,1428,1430],{"id":1429},"cmmc-is-verification-dfars-is-enforcement","CMMC is verification; DFARS is enforcement",[37,1432,1433],{},"It is easy to talk about CMMC and DFARS as if they are separate programs. They are not. CMMC is the Department of Defense's certification framework. DFARS — the Defense Federal Acquisition Regulation Supplement — is the set of contract clauses that actually imposes CMMC (and the NIST SP 800-171 controls beneath it) on defense contractors. Without DFARS, CMMC is a program on paper. With DFARS, CMMC is an enforceable requirement that can kill a contract award.",[37,1435,1436],{},"This page walks through the DFARS clauses that matter for CMMC, how they relate, and what each one obliges you to do.",[32,1438,1440],{"id":1439},"dfars-252204-7012-the-foundation","DFARS 252.204-7012: the foundation",[37,1442,1443,1444,1447],{},"DFARS 252.204-7012 — \"Safeguarding Covered Defense Information and Cyber Incident Reporting\" — has been in effect since December 31, 2017. It applies to any DoD contract that involves ",[52,1445,1446],{},"covered defense information"," (essentially CUI as the DoD defines it) and it does two things:",[358,1449,1450,1456],{},[95,1451,1452,1455],{},[52,1453,1454],{},"Requires implementation of NIST SP 800-171."," Contractors must implement the 110 security requirements in NIST SP 800-171 Rev 2 to protect covered defense information processed, stored, or transmitted on non-federal systems.",[95,1457,1458,1461],{},[52,1459,1460],{},"Requires cyber incident reporting within 72 hours."," If a cyber incident affects covered defense information or the systems handling it, the contractor must report to the DoD through the DoD Cyber Crime Center (DC3) within 72 hours of discovery.",[37,1463,1464],{},"7012 also flows down to subcontractors at every tier that process covered defense information. That flow-down language — unchanged since 2017 — is why primes have a long-established responsibility to require NIST SP 800-171 compliance from their subs.",[37,1466,1467,1468,1471],{},"What 7012 did ",[52,1469,1470],{},"not"," do was verify compliance. Contractors self-attested. There was no audit. There was no score. That gap is exactly what CMMC closed.",[32,1473,1475],{"id":1474},"dfars-252204-7019-and-7020-the-scoring-clauses","DFARS 252.204-7019 and -7020: the scoring clauses",[37,1477,1478,1479,313],{},"In November 2020, the DoD added DFARS 252.204-7019 (\"Notice of NIST SP 800-171 DoD Assessment Requirements\") and DFARS 252.204-7020 (\"NIST SP 800-171 DoD Assessment Requirements\"). Together, they imposed a new obligation on contractors with 7012 in their contracts: conduct a NIST SP 800-171 self-assessment and post the score to the ",[52,1480,1481],{},"Supplier Performance Risk System (SPRS)",[37,1483,1484],{},"The mechanics:",[92,1486,1487,1490,1493,1496],{},[95,1488,1489],{},"The self-assessment uses the DoD Assessment Methodology — the same scoring method CMMC Level 2 self-assessments use today.",[95,1491,1492],{},"Scoring starts at 110 and subtracts points for unmet requirements.",[95,1494,1495],{},"The score is posted to SPRS and is visible to contracting officers during source selection.",[95,1497,1498],{},"Scores more than three years old are considered expired.",[37,1500,1501],{},"7019 and 7020 were the bridge between 7012 and CMMC. They introduced the scoring methodology, they stood up SPRS as the authoritative repository, and they normalized the idea that a specific numerical measure of NIST SP 800-171 compliance would factor into contract decisions. When CMMC 2.0 arrived, it could plug into the mechanism 7019 and 7020 had already built.",[32,1503,1505],{"id":1504},"dfars-252204-7021-the-cmmc-clause","DFARS 252.204-7021: the CMMC clause",[37,1507,1508,1509,313],{},"DFARS 252.204-7021 — \"Cybersecurity Maturity Model Certification Requirements\" — is the clause that makes CMMC a contract requirement. Originally published in 2020 (briefly, under CMMC 1.0), it was revised and republished alongside the CMMC 2.0 program rule and ",[52,1510,1511],{},"took effect November 10, 2025",[37,1513,1514],{},"7021 does four things:",[358,1516,1517,1523,1529,1535],{},[95,1518,1519,1522],{},[52,1520,1521],{},"Requires a current CMMC certification at contract award."," Before an award can be made, the contractor must hold a valid CMMC certification at the level specified in the solicitation. No certification, no award.",[95,1524,1525,1528],{},[52,1526,1527],{},"Requires the certification to remain current."," Certifications must not expire during performance, and annual affirmations must be submitted on time.",[95,1530,1531,1534],{},[52,1532,1533],{},"Requires flow-down."," The CMMC requirement flows to subcontractors at the level appropriate for the covered information they will handle.",[95,1536,1537,1540],{},[52,1538,1539],{},"Specifies the assessment type."," The solicitation identifies whether the required certification is Level 1 self, Level 2 self, Level 2 C3PAO, or Level 3 DIBCAC.",[37,1542,1543],{},"7021 does not replace 7012, 7019, or 7020. All four clauses operate simultaneously. A contractor with a Level 2 C3PAO contract is subject to 7012 (safeguarding and incident reporting), 7019 and 7020 (scoring and SPRS), and 7021 (certification before award). Each clause addresses a different mechanism of the same program.",[32,1545,1547],{"id":1546},"how-the-clauses-work-together","How the clauses work together",[37,1549,1550],{},"Think of the DFARS cyber clauses as a stack:",[92,1552,1553,1559,1565],{},[95,1554,1555,1558],{},[52,1556,1557],{},"7012 sets the control standard."," NIST SP 800-171. Incident reporting within 72 hours. Flow-down to subs.",[95,1560,1561,1564],{},[52,1562,1563],{},"7019 and 7020 introduce scoring."," DoD Assessment Methodology. SPRS submission. Visibility during source selection.",[95,1566,1567,1570],{},[52,1568,1569],{},"7021 adds certification."," A formal CMMC credential at the right level, verified at award.",[37,1572,1573],{},"Each clause is additive. 7012 still requires 800-171 implementation. 7019 and 7020 still require SPRS scoring. 7021 adds the requirement that your scoring translate into a recognized CMMC certification before a DoD agency can put contract dollars behind you.",[32,1575,1577],{"id":1576},"nist-sp-800-171-is-the-common-thread","NIST SP 800-171 is the common thread",[37,1579,1580],{},"Every DFARS cyber clause points back to the same underlying control standard: NIST SP 800-171 Rev 2. The 14 control families and 110 security requirements are what you actually implement. Everything else — the scoring methodology, the SPRS entry, the C3PAO certification — is downstream machinery for verifying your NIST SP 800-171 posture.",[37,1582,1583],{},"This is why investing in a strong NIST SP 800-171 program is the highest-leverage move a defense contractor can make. It satisfies DFARS 252.204-7012. It produces the score for SPRS under 7019 and 7020. It is the pre-work for any CMMC Level 2 assessment under 7021. One control implementation, four DFARS obligations satisfied.",[32,1585,1587],{"id":1586},"contractual-enforcement-what-happens-when-you-miss","Contractual enforcement: what happens when you miss",[37,1589,1590],{},"The DFARS clauses are not advisory. Enforcement mechanisms include:",[92,1592,1593,1599,1605,1611,1617],{},[95,1594,1595,1598],{},[52,1596,1597],{},"Contract ineligibility."," Under 7021, no CMMC certification means no award. The contracting officer cannot legally make the award.",[95,1600,1601,1604],{},[52,1602,1603],{},"Stop-work or termination."," A certification that lapses mid-contract can trigger cure periods or, in the worst case, termination for default.",[95,1606,1607,1610],{},[52,1608,1609],{},"False Claims Act exposure."," A misrepresented SPRS score under 7019 or 7020 is a false claim. Multiple defense contractors have settled FCA cases tied to inflated NIST SP 800-171 scores, with settlements in the hundreds of thousands to tens of millions of dollars.",[95,1612,1613,1616],{},[52,1614,1615],{},"Suspension and debarment."," Egregious cybersecurity failures can trigger suspension or debarment from federal contracting.",[95,1618,1619,1622],{},[52,1620,1621],{},"Incident reporting failures."," Under 7012, missing the 72-hour reporting window is itself a contractual breach, independent of any underlying cybersecurity posture.",[32,1624,1305],{"id":1304},[37,1626,1627],{},"The DFARS clauses give you a concrete obligations map. Every CMMC readiness activity should be traceable to one or more of them:",[92,1629,1630,1636,1642,1648,1654,1660],{},[95,1631,1632,1635],{},[52,1633,1634],{},"SSP development"," → 7012 (NIST SP 800-171 implementation).",[95,1637,1638,1641],{},[52,1639,1640],{},"SPRS score submission"," → 7019 and 7020.",[95,1643,1644,1647],{},[52,1645,1646],{},"C3PAO assessment"," → 7021 at Level 2.",[95,1649,1650,1653],{},[52,1651,1652],{},"DIBCAC assessment"," → 7021 at Level 3.",[95,1655,1656,1659],{},[52,1657,1658],{},"Incident response program"," → 7012 (72-hour reporting).",[95,1661,1662,1665],{},[52,1663,1664],{},"Subcontractor flow-down"," → 7012 and 7021 flow-down language.",[37,1667,1668],{},"Using the clauses as the organizing frame makes the obligations tangible. \"Because DFARS 252.204-7012 requires 72-hour incident reporting, we need an incident response plan that can meet a 72-hour clock\" is a more actionable statement than \"we need an incident response plan.\"",[32,1670,1315],{"id":1314},[92,1672,1673,1679,1685,1691,1697],{},[95,1674,1675,1678],{},[52,1676,1677],{},"Assuming CMMC replaces the older clauses."," It does not. 7012, 7019, and 7020 all continue to apply.",[95,1680,1681,1684],{},[52,1682,1683],{},"Ignoring 7012 incident reporting."," Many contractors focus on controls and forget that 7012 also requires rapid reporting to DC3. Missing the 72-hour window is its own breach.",[95,1686,1687,1690],{},[52,1688,1689],{},"Treating SPRS as optional."," Under 7019 and 7020, an SPRS score is a prerequisite for being considered for many DoD contracts. Organizations without scores are self-disqualifying.",[95,1692,1693,1696],{},[52,1694,1695],{},"Flowing down 7021 without the data to justify it."," CMMC clauses should flow to subcontractors based on the information actually shared. Overflow creates unnecessary subcontractor obligations; underflow is an enforcement risk.",[95,1698,1699,1702],{},[52,1700,1701],{},"Confusing CUI scope with contract scope."," The DFARS clauses apply because of how covered information flows, not because of the contract's dollar value. A small contract with CUI triggers the clauses; a large contract without CUI may not.",[32,1704,895],{"id":894},[37,1706,1707,1708,1711],{},"episki maps each DFARS obligation to the specific NIST SP 800-171 controls and CMMC practices that satisfy it. When a new DFARS clause is modified or a new solicitation cites a specific requirement, the platform shows you exactly what you already have coverage for and what you still need. Incident response workflows are pre-configured to meet the 72-hour reporting clock under 7012, and SPRS score submissions under 7019 and 7020 are generated from the same control evidence that feeds your CMMC assessment. ",[86,1709,903],{"href":494,"rel":1710},[902]," to align your DFARS obligations in one workspace.",{"title":436,"searchDepth":437,"depth":437,"links":1713},[1714,1715,1716,1717,1718,1719,1720,1721,1722,1723],{"id":1429,"depth":437,"text":1430},{"id":1439,"depth":437,"text":1440},{"id":1474,"depth":437,"text":1475},{"id":1504,"depth":437,"text":1505},{"id":1546,"depth":437,"text":1547},{"id":1576,"depth":437,"text":1577},{"id":1586,"depth":437,"text":1587},{"id":1304,"depth":437,"text":1305},{"id":1314,"depth":437,"text":1315},{"id":894,"depth":437,"text":895},"How CMMC relates to DFARS 252.204-7012, 7019, 7020, and 7021, how contractual enforcement actually works, and how NIST SP 800-171 ties the two together.",{"items":1726},[1727,1730,1733,1736],{"label":1728,"content":1729},"What is DFARS 252.204-7012?","DFARS 252.204-7012 — 'Safeguarding Covered Defense Information and Cyber Incident Reporting' — has been in effect since 2017. It requires contractors that process covered defense information to implement the security requirements in NIST SP 800-171 and to report cyber incidents to the DoD within 72 hours. CMMC builds on top of 7012 rather than replacing it.",{"label":1731,"content":1732},"What is DFARS 252.204-7021?","DFARS 252.204-7021 is the clause that imposes CMMC certification as a contract requirement. It took effect November 10, 2025, and specifies the CMMC level and assessment type (self, C3PAO, or DIBCAC) that a contractor must hold before award. Without 7021, CMMC existed only as a program; with 7021, it is a binding contractual obligation.",{"label":1734,"content":1735},"Does NIST SP 800-171 still apply now that CMMC exists?","Yes. NIST SP 800-171 remains the underlying control standard. CMMC Level 2 maps to NIST SP 800-171 directly, and DFARS 252.204-7012 continues to require NIST SP 800-171 implementation for any contractor handling covered defense information. CMMC did not replace 800-171 — CMMC is the verification mechanism for it.",{"label":1737,"content":1738},"Do all DoD contracts include DFARS CMMC clauses?","Only contracts that involve covered defense information, FCI, or CUI trigger the DFARS cyber clauses. Contracts that do not involve covered information — for example, a purely commercial-item purchase unrelated to defense information handling — do not include 7012 or 7021. The clauses flow from the data, not the contract dollar value.",{},[1411,1741,1742],"framework","control-framework",[1744,1416,1745,340],"implementation-timeline","self-assessment-vs-third-party",{"title":1747,"description":1748},"CMMC and DFARS: 252.204-7012, 7019, 7020, 7021 Explained","The DFARS clauses behind CMMC. How 252.204-7012, 7019, 7020, and 7021 enforce CMMC, NIST SP 800-171, and incident reporting obligations in DoD contracts.","5.frameworks\u002Fcmmc\u002Fdfars-relationship","AcL6HsfS0U9dnU6bRJWDbXP0BQKnQNpHqVuM2616QD8",{"id":1752,"title":1753,"body":1754,"description":2099,"extension":467,"faq":924,"frameworkSlug":523,"lastUpdated":925,"meta":2100,"navigation":505,"path":253,"relatedTerms":2101,"relatedTopics":2104,"seo":2105,"stem":2108,"__hash__":2109},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fimplementation-timeline.md","CMMC Implementation Timeline",{"type":29,"value":1755,"toc":2087},[1756,1760,1763,1783,1786,1790,1793,1797,1802,1805,1828,1833,1844,1848,1851,1867,1871,1882,1886,1889,1904,1908,1916,1920,1923,1937,1941,1949,1953,2039,2043,2046,2078,2080],[32,1757,1759],{"id":1758},"cmmc-rulemaking-timeline","CMMC rulemaking timeline",[37,1761,1762],{},"CMMC's path to enforcement involved two separate rulemakings:",[92,1764,1765,1774],{},[95,1766,1767,1770,1771,1773],{},[52,1768,1769],{},"CMMC Program Rule (32 CFR Part 170)"," — published in the Federal Register on October 15, 2024, and effective ",[52,1772,72],{},". This rule established the CMMC program structure, assessment requirements, and certification processes.",[95,1775,1776,1779,1780,1782],{},[52,1777,1778],{},"DFARS Rule (48 CFR)"," — published on September 10, 2025, and effective ",[52,1781,76],{},". This rule amended the Defense Federal Acquisition Regulation Supplement to incorporate CMMC requirements into actual DoD contracts.",[37,1784,1785],{},"The DFARS rule is what triggers enforcement. Without it, CMMC existed as a program but could not be contractually required. With the DFARS rule in effect, the DoD can now include CMMC level requirements as conditions of contract award.",[32,1787,1789],{"id":1788},"the-four-phases","The four phases",[37,1791,1792],{},"The DFARS rule implements CMMC through a phased approach that gradually expands requirements over four years.",[44,1794,1796],{"id":1795},"phase-1-november-10-2025-to-november-9-2026","Phase 1 — November 10, 2025 to November 9, 2026",[37,1798,1799],{},[52,1800,1801],{},"Status: Active now",[37,1803,1804],{},"Phase 1 introduces CMMC requirements into select DoD solicitations and contracts:",[92,1806,1807,1813,1819,1825],{},[95,1808,1809,1812],{},[52,1810,1811],{},"Level 1 self-assessments"," may be required as a condition of award for contracts involving FCI",[95,1814,1815,1818],{},[52,1816,1817],{},"Level 2 self-assessments"," may be required as a condition of award for contracts involving CUI",[95,1820,1821,1824],{},[52,1822,1823],{},"Level 2 C3PAO assessments"," may be required at the DoD's discretion for a limited number of contracts involving more sensitive CUI",[95,1826,1827],{},"The DoD has discretion over which solicitations include CMMC requirements during this phase",[37,1829,1830],{},[52,1831,1832],{},"What this means for contractors:",[92,1834,1835,1838,1841],{},[95,1836,1837],{},"If your contract is selected for CMMC requirements, you must have a valid self-assessment score in SPRS before contract award",[95,1839,1840],{},"Begin preparing now even if your current contracts do not yet require CMMC — new solicitations and recompetes will increasingly include requirements",[95,1842,1843],{},"Organizations that have been maintaining NIST SP 800-171 compliance and submitting SPRS scores are well positioned",[44,1845,1847],{"id":1846},"phase-2-november-10-2026-to-november-9-2027","Phase 2 — November 10, 2026 to November 9, 2027",[37,1849,1850],{},"Phase 2 broadens CMMC requirements:",[92,1852,1853,1858,1864],{},[95,1854,1855,1857],{},[52,1856,1823],{}," become more widely required. Contracts involving CUI that was previously eligible for self-assessment may now require third-party certification.",[95,1859,1860,1863],{},[52,1861,1862],{},"Level 3 DIBCAC assessments"," may be required at the DoD's discretion for a limited number of the most sensitive programs",[95,1865,1866],{},"The scope of solicitations including CMMC requirements expands significantly",[37,1868,1869],{},[52,1870,1832],{},[92,1872,1873,1876,1879],{},[95,1874,1875],{},"Organizations handling CUI should plan for C3PAO assessment timelines. Engaging a C3PAO early is critical — the pool of accredited assessors will be stretched.",[95,1877,1878],{},"C3PAO assessments typically require two to six months of preparation plus the assessment itself",[95,1880,1881],{},"Budget for assessment costs, which typically range from $50,000 to $150,000+ depending on scope",[44,1883,1885],{"id":1884},"phase-3-november-10-2027-to-november-9-2028","Phase 3 — November 10, 2027 to November 9, 2028",[37,1887,1888],{},"Phase 3 adds Level 3 requirements broadly:",[92,1890,1891,1896,1901],{},[95,1892,1893,1895],{},[52,1894,1823],{}," continue expanding across applicable contracts",[95,1897,1898,1900],{},[52,1899,1862],{}," become more widely required for contracts involving the most sensitive CUI and critical programs",[95,1902,1903],{},"Most new DoD solicitations involving FCI or CUI will include CMMC requirements",[37,1905,1906],{},[52,1907,1832],{},[92,1909,1910,1913],{},[95,1911,1912],{},"Organizations on the most sensitive programs should already be preparing for Level 3",[95,1914,1915],{},"Level 3 requires a valid Level 2 C3PAO certification as a prerequisite, so the certification chain must be planned well in advance",[44,1917,1919],{"id":1918},"phase-4-november-10-2028-onward","Phase 4 — November 10, 2028 onward",[37,1921,1922],{},"Phase 4 represents full implementation:",[92,1924,1925,1931,1934],{},[95,1926,1927,1930],{},[52,1928,1929],{},"All DoD contracts"," that require the processing, storage, or transmission of FCI or CUI must include the appropriate CMMC level as a condition of award",[95,1932,1933],{},"No exceptions or discretionary application — CMMC is a universal contract requirement for covered information",[95,1935,1936],{},"Option periods and extensions on existing contracts will also incorporate CMMC requirements",[37,1938,1939],{},[52,1940,1832],{},[92,1942,1943,1946],{},[95,1944,1945],{},"By Phase 4, any organization without the appropriate CMMC certification will be ineligible for DoD contract awards involving FCI or CUI",[95,1947,1948],{},"This is the hard deadline. Organizations that have not achieved certification by this point will lose the ability to compete for affected contracts.",[32,1950,1952],{"id":1951},"key-dates-summary","Key dates summary",[1954,1955,1956,1969],"table",{},[1957,1958,1959],"thead",{},[1960,1961,1962,1966],"tr",{},[1963,1964,1965],"th",{},"Date",[1963,1967,1968],{},"Milestone",[1970,1971,1972,1981,1988,1996,2006,2017,2028],"tbody",{},[1960,1973,1974,1978],{},[1975,1976,1977],"td",{},"October 15, 2024",[1975,1979,1980],{},"CMMC Program Rule published",[1960,1982,1983,1985],{},[1975,1984,72],{},[1975,1986,1987],{},"CMMC Program Rule effective",[1960,1989,1990,1993],{},[1975,1991,1992],{},"September 10, 2025",[1975,1994,1995],{},"DFARS Rule published",[1960,1997,1998,2000],{},[1975,1999,76],{},[1975,2001,2002,2005],{},[52,2003,2004],{},"Phase 1 begins"," — CMMC in select contracts",[1960,2007,2008,2011],{},[1975,2009,2010],{},"November 10, 2026",[1975,2012,2013,2016],{},[52,2014,2015],{},"Phase 2 begins"," — C3PAO requirements expand",[1960,2018,2019,2022],{},[1975,2020,2021],{},"November 10, 2027",[1975,2023,2024,2027],{},[52,2025,2026],{},"Phase 3 begins"," — Level 3 requirements expand",[1960,2029,2030,2033],{},[1975,2031,2032],{},"November 10, 2028",[1975,2034,2035,2038],{},[52,2036,2037],{},"Phase 4 begins"," — full CMMC enforcement",[32,2040,2042],{"id":2041},"why-you-should-not-wait","Why you should not wait",[37,2044,2045],{},"Although full enforcement is phased, several factors make early action critical:",[358,2047,2048,2054,2060,2066,2072],{},[95,2049,2050,2053],{},[52,2051,2052],{},"C3PAO availability"," — the number of accredited C3PAOs is limited and growing slowly. As Phase 2 approaches, demand for assessments will spike, and wait times will increase.",[95,2055,2056,2059],{},[52,2057,2058],{},"Remediation takes time"," — closing gaps in 110 NIST SP 800-171 requirements is not a quick project. Most organizations need 6 to 18 months of sustained effort.",[95,2061,2062,2065],{},[52,2063,2064],{},"Contract competitiveness"," — DoD agencies can add CMMC requirements to any solicitation at their discretion even during Phase 1. Organizations that are already certified will have a competitive advantage.",[95,2067,2068,2071],{},[52,2069,2070],{},"Subcontract flow-down"," — prime contractors are increasingly requiring CMMC readiness from their subcontractors ahead of the DFARS timeline to reduce their own supply chain risk.",[95,2073,2074,2077],{},[52,2075,2076],{},"False Claims Act exposure"," — submitting inaccurate SPRS scores has already resulted in enforcement actions under the False Claims Act. The stakes of self-attestation are real.",[32,2079,895],{"id":894},[37,2081,2082,2083,2086],{},"episki gives your team a real-time view of where you stand against each phase's requirements. The platform tracks your SPRS score, monitors POA&M remediation progress, and alerts you when assessment deadlines approach. As phases shift and requirements expand, episki updates your workspace to reflect the new obligations — so you are never caught off guard. ",[86,2084,903],{"href":494,"rel":2085},[902]," to see your phase readiness today.",{"title":436,"searchDepth":437,"depth":437,"links":2088},[2089,2090,2096,2097,2098],{"id":1758,"depth":437,"text":1759},{"id":1788,"depth":437,"text":1789,"children":2091},[2092,2093,2094,2095],{"id":1795,"depth":442,"text":1796},{"id":1846,"depth":442,"text":1847},{"id":1884,"depth":442,"text":1885},{"id":1918,"depth":442,"text":1919},{"id":1951,"depth":437,"text":1952},{"id":2041,"depth":437,"text":2042},{"id":894,"depth":437,"text":895},"The four-phase CMMC rollout from November 2025 through November 2028, including what each phase requires for Level 1, Level 2, and Level 3 contractors.",{},[523,2102,2103],"dfars","cui",[931,159,1416],{"title":2106,"description":2107},"CMMC Timeline 2025–2028: All 4 Phases & Deadlines","CMMC phased rollout from Phase 1 (Nov 2025) through Phase 4 (Nov 2028). Know exactly when each level requirement kicks in for your DoD contracts.","5.frameworks\u002Fcmmc\u002Fimplementation-timeline","Ad6K16LwtfWSkuNM3UZqkl1Q5_Q_CT6KUJ_aLYOZvu4",{"id":2111,"title":2112,"body":2113,"description":2455,"extension":467,"faq":924,"frameworkSlug":523,"lastUpdated":925,"meta":2456,"navigation":505,"path":88,"relatedTerms":2457,"relatedTopics":2459,"seo":2460,"stem":2463,"__hash__":2464},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Flevels.md","CMMC Levels Explained",{"type":29,"value":2114,"toc":2435},[2115,2119,2122,2126,2132,2136,2147,2151,2168,2172,2175,2219,2223,2229,2232,2242,2245,2248,2261,2263,2270,2281,2284,2288,2295,2298,2315,2318,2332,2336,2339,2362,2366,2369,2423,2426,2428],[32,2116,2118],{"id":2117},"overview-of-cmmc-20-levels","Overview of CMMC 2.0 levels",[37,2120,2121],{},"CMMC 2.0 replaced the original five-level model with three streamlined levels. Each level builds on the one below it, adding more practices and more rigorous assessment requirements. The level your organization needs is determined by the type of information you handle under your DoD contract.",[32,2123,2125],{"id":2124},"level-1-foundational","Level 1 — Foundational",[37,2127,2128,2129,2131],{},"Level 1 applies to organizations that handle ",[52,2130,963],{}," — information provided by or generated for the government under contract that is not intended for public release.",[44,2133,2135],{"id":2134},"requirements","Requirements",[92,2137,2138,2144],{},[95,2139,2140,2143],{},[52,2141,2142],{},"17 practices"," drawn from FAR 52.204-21, \"Basic Safeguarding of Covered Contractor Information Systems\"",[95,2145,2146],{},"Practices cover fundamental cyber hygiene: access control, identification and authentication, media protection, physical protection, system and communications protection, and system and information integrity",[44,2148,2150],{"id":2149},"assessment-type","Assessment type",[92,2152,2153,2159,2162,2165],{},[95,2154,2155,2158],{},[52,2156,2157],{},"Annual self-assessment"," performed by the organization",[95,2160,2161],{},"Results entered into the Supplier Performance Risk System (SPRS)",[95,2163,2164],{},"A senior official must affirm compliance annually",[95,2166,2167],{},"No third-party assessment required",[44,2169,2171],{"id":2170},"what-level-1-covers","What Level 1 covers",[37,2173,2174],{},"Level 1 practices are baseline security measures that most organizations should already have in place:",[92,2176,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2207,2210,2213,2216],{},[95,2178,2179],{},"Limit system access to authorized users",[95,2181,2182],{},"Limit system access to the types of transactions and functions that authorized users are permitted to execute",[95,2184,2185],{},"Verify and control connections to external systems",[95,2187,2188],{},"Control information posted on publicly accessible systems",[95,2190,2191],{},"Identify and authenticate users before granting access",[95,2193,2194],{},"Sanitize or destroy media before disposal or reuse",[95,2196,2197],{},"Limit physical access to systems and equipment",[95,2199,2200],{},"Escort visitors and monitor visitor activity",[95,2202,2203],{},"Monitor and control communications at system boundaries",[95,2205,2206],{},"Implement subnetworks for publicly accessible system components",[95,2208,2209],{},"Identify, report, and correct information system flaws in a timely manner",[95,2211,2212],{},"Provide protection from malicious code at appropriate locations",[95,2214,2215],{},"Update malicious code protection mechanisms as new releases are available",[95,2217,2218],{},"Perform periodic scans and real-time scans of files from external sources",[32,2220,2222],{"id":2221},"level-2-advanced","Level 2 — Advanced",[37,2224,2225,2226,2228],{},"Level 2 applies to organizations that handle ",[52,2227,995],{}," — information that requires safeguarding or dissemination controls pursuant to law, regulation, or government-wide policy.",[44,2230,2135],{"id":2231},"requirements-1",[92,2233,2234,2239],{},[95,2235,2236,2238],{},[52,2237,113],{}," aligned to all 14 control families in NIST SP 800-171 Rev 2",[95,2240,2241],{},"Covers access control, awareness and training, audit and accountability, configuration management, identification and authentication, incident response, maintenance, media protection, personnel security, physical protection, risk assessment, security assessment, system and communications protection, and system and information integrity",[44,2243,2150],{"id":2244},"assessment-type-1",[37,2246,2247],{},"Level 2 has two assessment paths depending on the sensitivity of the CUI:",[92,2249,2250,2256],{},[95,2251,2252,2255],{},[52,2253,2254],{},"Self-assessment"," — for contracts involving less sensitive CUI. The organization conducts its own assessment, scores it using the DoD Assessment Methodology, and submits the score to SPRS. A senior official must affirm compliance annually.",[95,2257,2258,2260],{},[52,2259,1646],{}," — for contracts involving more sensitive CUI or critical programs. A CMMC Third-Party Assessment Organization (C3PAO) conducts the assessment. Certification is valid for three years, with annual affirmation of continued compliance required.",[44,2262,701],{"id":700},[37,2264,2265,2266,2269],{},"The DoD Assessment Methodology assigns a score out of 110 based on the number of objectives met. Organizations that do not meet all 110 requirements may receive a ",[52,2267,2268],{},"conditional certification"," if they:",[92,2271,2272,2275,2278],{},[95,2273,2274],{},"Score at least 80% (88 out of 110)",[95,2276,2277],{},"Document unmet requirements in a Plan of Action and Milestones (POA&M)",[95,2279,2280],{},"Close all POA&M items within 180 days of the conditional certification",[37,2282,2283],{},"Failure to close POA&M items within 180 days revokes the conditional certification.",[32,2285,2287],{"id":2286},"level-3-expert","Level 3 — Expert",[37,2289,2290,2291,2294],{},"Level 3 applies to organizations working on the ",[52,2292,2293],{},"most sensitive DoD programs"," where advanced persistent threats (APTs) are a concern.",[44,2296,2135],{"id":2297},"requirements-2",[92,2299,2300,2306,2312],{},[95,2301,2302,2303],{},"All 110 NIST SP 800-171 Rev 2 requirements from Level 2, ",[52,2304,2305],{},"plus",[95,2307,2308,2311],{},[52,2309,2310],{},"24 additional requirements"," selected from NIST SP 800-172, \"Enhanced Security Requirements for Protecting Controlled Unclassified Information\"",[95,2313,2314],{},"Enhanced requirements focus on penetration-resistant architecture, damage-limiting operations, and designing for cyber resiliency",[44,2316,2150],{"id":2317},"assessment-type-2",[92,2319,2320,2326,2329],{},[95,2321,2322,2325],{},[52,2323,2324],{},"Government-led assessment"," conducted by the Defense Contract Management Agency (DCMA) Defense Industrial Base Cybersecurity Assessment Center (DIBCAC)",[95,2327,2328],{},"Requires a valid Level 2 C3PAO certification as a prerequisite",[95,2330,2331],{},"Certification is valid for three years with annual affirmation",[44,2333,2335],{"id":2334},"level-3-enhanced-focus-areas","Level 3 enhanced focus areas",[37,2337,2338],{},"The 24 additional requirements from NIST SP 800-172 emphasize:",[92,2340,2341,2344,2347,2350,2353,2356,2359],{},[95,2342,2343],{},"Dual authorization for critical actions",[95,2345,2346],{},"Advanced threat hunting and monitoring",[95,2348,2349],{},"Automated response to security events",[95,2351,2352],{},"Network segmentation and micro-segmentation",[95,2354,2355],{},"Supply chain risk management",[95,2357,2358],{},"Penetration testing and red team exercises",[95,2360,2361],{},"System resilience and recovery capabilities",[32,2363,2365],{"id":2364},"how-to-determine-your-required-level","How to determine your required level",[37,2367,2368],{},"Your required CMMC level is specified in the solicitation or contract. As a general guide:",[1954,2370,2371,2383],{},[1957,2372,2373],{},[1960,2374,2375,2378,2381],{},[1963,2376,2377],{},"Information type",[1963,2379,2380],{},"Typical CMMC level",[1963,2382,2150],{},[1970,2384,2385,2394,2403,2413],{},[1960,2386,2387,2390,2392],{},[1975,2388,2389],{},"FCI only",[1975,2391,772],{},[1975,2393,2254],{},[1960,2395,2396,2399,2401],{},[1975,2397,2398],{},"CUI (less sensitive)",[1975,2400,778],{},[1975,2402,2254],{},[1960,2404,2405,2408,2410],{},[1975,2406,2407],{},"CUI (more sensitive or critical programs)",[1975,2409,778],{},[1975,2411,2412],{},"C3PAO",[1960,2414,2415,2418,2420],{},[1975,2416,2417],{},"CUI on highest-priority programs",[1975,2419,784],{},[1975,2421,2422],{},"DIBCAC",[37,2424,2425],{},"If you are unsure which level applies, review your contract's DFARS clause 252.204-7021 or consult your contracting officer.",[32,2427,895],{"id":894},[37,2429,2430,2431,2434],{},"episki provides pre-mapped practice sets for all three CMMC levels. During onboarding, select your target level and the platform generates a tailored workspace with the right controls, narratives, and evidence requirements. As you close gaps, your SPRS score updates in real time. If you hold multiple contracts at different levels, episki maintains separate scoping views while reusing shared controls — so Level 1 work automatically counts toward Level 2 readiness. ",[86,2432,903],{"href":494,"rel":2433},[902]," to see your current readiness posture.",{"title":436,"searchDepth":437,"depth":437,"links":2436},[2437,2438,2443,2448,2453,2454],{"id":2117,"depth":437,"text":2118},{"id":2124,"depth":437,"text":2125,"children":2439},[2440,2441,2442],{"id":2134,"depth":442,"text":2135},{"id":2149,"depth":442,"text":2150},{"id":2170,"depth":442,"text":2171},{"id":2221,"depth":437,"text":2222,"children":2444},[2445,2446,2447],{"id":2231,"depth":442,"text":2135},{"id":2244,"depth":442,"text":2150},{"id":700,"depth":442,"text":701},{"id":2286,"depth":437,"text":2287,"children":2449},[2450,2451,2452],{"id":2297,"depth":442,"text":2135},{"id":2317,"depth":442,"text":2150},{"id":2334,"depth":442,"text":2335},{"id":2364,"depth":437,"text":2365},{"id":894,"depth":437,"text":895},"A complete guide to the three CMMC 2.0 maturity levels — Level 1 (Foundational), Level 2 (Advanced), and Level 3 (Expert) — with practice counts, assessment types, and scoping guidance.",{},[523,2458,2103],"nist-800-171",[1416,159,932],{"title":2461,"description":2462},"CMMC 2.0 Levels Explained (2026): Level 1 vs 2 vs 3 Requirements & Costs","CMMC 2.0 maturity levels compared — practice counts, assessment types, costs, and how to determine which level your DoD contract requires.","5.frameworks\u002Fcmmc\u002Flevels","8gqyHHG0u8w-zYk-RDhj3lhi-RR5Ex1SnkudAMzBhNk",{"id":2466,"title":2467,"body":2468,"description":2788,"extension":467,"faq":924,"frameworkSlug":523,"lastUpdated":925,"meta":2789,"navigation":505,"path":149,"relatedTerms":2790,"relatedTopics":2792,"seo":2793,"stem":2796,"__hash__":2797},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fnist-800-171-mapping.md","NIST SP 800-171 Mapping",{"type":29,"value":2469,"toc":2762},[2470,2474,2481,2484,2488,2491,2495,2498,2503,2517,2521,2524,2528,2531,2535,2538,2542,2545,2549,2560,2564,2567,2571,2574,2578,2581,2585,2588,2592,2595,2599,2602,2606,2609,2613,2616,2620,2631,2635,2638,2642,2645,2649,2654,2716,2719,2723,2730,2734,2737,2741,2748,2750],[32,2471,2473],{"id":2472},"cmmc-level-2-and-nist-sp-800-171","CMMC Level 2 and NIST SP 800-171",[37,2475,2476,2477,2480],{},"CMMC Level 2 is a direct mapping to ",[52,2478,2479],{},"NIST SP 800-171 Rev 2",", \"Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.\" Every one of the 110 CMMC Level 2 practices corresponds to a NIST SP 800-171 security requirement. There are no additions, modifications, or deletions — the mapping is one-to-one.",[37,2482,2483],{},"This alignment was a deliberate design choice in CMMC 2.0. The original CMMC 1.0 introduced unique practices and maturity processes on top of NIST standards. CMMC 2.0 eliminated those additions, making NIST SP 800-171 the single authoritative source for Level 2 requirements.",[32,2485,2487],{"id":2486},"the-14-control-families","The 14 control families",[37,2489,2490],{},"NIST SP 800-171 organizes its 110 security requirements into 14 families. Each family addresses a specific domain of cybersecurity:",[44,2492,2494],{"id":2493},"_31-access-control-22-requirements","3.1 Access Control (22 requirements)",[37,2496,2497],{},"The largest family. Covers how organizations limit system access to authorized users, processes, and devices. Key areas include account management, access enforcement, remote access, and wireless access restrictions.",[37,2499,2500],{},[52,2501,2502],{},"Example requirements:",[92,2504,2505,2508,2511,2514],{},[95,2506,2507],{},"Limit system access to authorized users (3.1.1)",[95,2509,2510],{},"Employ the principle of least privilege (3.1.5)",[95,2512,2513],{},"Use multifactor authentication for network access (3.1.8)",[95,2515,2516],{},"Encrypt CUI on mobile devices and mobile computing platforms (3.1.19)",[44,2518,2520],{"id":2519},"_32-awareness-and-training-3-requirements","3.2 Awareness and Training (3 requirements)",[37,2522,2523],{},"Ensures personnel are aware of security risks and trained on their responsibilities. Includes role-based training for users with elevated privileges or security-sensitive roles.",[44,2525,2527],{"id":2526},"_33-audit-and-accountability-9-requirements","3.3 Audit and Accountability (9 requirements)",[37,2529,2530],{},"Covers creation, protection, and review of system audit logs. Organizations must create and retain system audit logs sufficient to enable monitoring, analysis, investigation, and reporting of unauthorized activity.",[44,2532,2534],{"id":2533},"_34-configuration-management-9-requirements","3.4 Configuration Management (9 requirements)",[37,2536,2537],{},"Addresses baseline configurations, change control, and least functionality. Organizations must establish and enforce security configuration settings and track changes to systems.",[44,2539,2541],{"id":2540},"_35-identification-and-authentication-11-requirements","3.5 Identification and Authentication (11 requirements)",[37,2543,2544],{},"Requires unique identification of users and devices, multifactor authentication, and credential management. This family includes some of the most technically demanding requirements.",[37,2546,2547],{},[52,2548,2502],{},[92,2550,2551,2554,2557],{},[95,2552,2553],{},"Authenticate (or verify) the identities of users, processes, or devices (3.5.2)",[95,2555,2556],{},"Use multifactor authentication for local and network access (3.5.3)",[95,2558,2559],{},"Employ replay-resistant authentication mechanisms (3.5.4)",[44,2561,2563],{"id":2562},"_36-incident-response-3-requirements","3.6 Incident Response (3 requirements)",[37,2565,2566],{},"Organizations must establish incident handling capabilities including preparation, detection, analysis, containment, recovery, and reporting. Incidents involving CUI must be reported to the DoD within 72 hours.",[44,2568,2570],{"id":2569},"_37-maintenance-6-requirements","3.7 Maintenance (6 requirements)",[37,2572,2573],{},"Covers system maintenance procedures, maintenance tools, and remote maintenance controls. Includes requirements for supervising maintenance personnel and sanitizing equipment removed for off-site maintenance.",[44,2575,2577],{"id":2576},"_38-media-protection-9-requirements","3.8 Media Protection (9 requirements)",[37,2579,2580],{},"Addresses protection of system media — both digital and physical — containing CUI. Includes marking, storage, transport, sanitization, and destruction requirements.",[44,2582,2584],{"id":2583},"_39-personnel-security-2-requirements","3.9 Personnel Security (2 requirements)",[37,2586,2587],{},"Requires screening individuals before granting access to systems containing CUI and ensuring CUI access is revoked when personnel are terminated or transferred.",[44,2589,2591],{"id":2590},"_310-physical-protection-6-requirements","3.10 Physical Protection (6 requirements)",[37,2593,2594],{},"Covers physical access controls to systems, equipment, and operating environments. Includes visitor management, monitoring, and protection of physical access devices.",[44,2596,2598],{"id":2597},"_311-risk-assessment-3-requirements","3.11 Risk Assessment (3 requirements)",[37,2600,2601],{},"Organizations must periodically assess risk to operations, assets, and individuals. Includes vulnerability scanning and remediation requirements.",[44,2603,2605],{"id":2604},"_312-security-assessment-4-requirements","3.12 Security Assessment (4 requirements)",[37,2607,2608],{},"Requires periodic assessment of security controls, monitoring for control effectiveness, and a plan of action for addressing deficiencies. This family directly supports the CMMC assessment process itself.",[44,2610,2612],{"id":2611},"_313-system-and-communications-protection-16-requirements","3.13 System and Communications Protection (16 requirements)",[37,2614,2615],{},"The second-largest family. Covers boundary protection, CUI confidentiality during transmission and at rest, network segmentation, and cryptographic protections. FIPS-validated encryption is required for CUI at rest and in transit.",[37,2617,2618],{},[52,2619,2502],{},[92,2621,2622,2625,2628],{},[95,2623,2624],{},"Implement FIPS-validated cryptography for CUI (3.13.11)",[95,2626,2627],{},"Prohibit remote activation of collaborative computing devices (3.13.12)",[95,2629,2630],{},"Control and monitor the use of mobile code (3.13.13)",[44,2632,2634],{"id":2633},"_314-system-and-information-integrity-7-requirements","3.14 System and Information Integrity (7 requirements)",[37,2636,2637],{},"Addresses flaw remediation, malicious code protection, security alerts, and system monitoring. Organizations must identify, report, and correct system flaws in a timely manner.",[32,2639,2641],{"id":2640},"cross-framework-overlap","Cross-framework overlap",[37,2643,2644],{},"Organizations pursuing CMMC Level 2 alongside other frameworks can reuse significant portions of their control implementation.",[44,2646,2648],{"id":2647},"cmmc-and-nist-csf","CMMC and NIST CSF",[37,2650,2651,2653],{},[86,2652,155],{"href":154}," provides a high-level risk management framework organized around six functions: Govern, Identify, Protect, Detect, Respond, and Recover. NIST SP 800-171 requirements map across these functions:",[1954,2655,2656,2666],{},[1957,2657,2658],{},[1960,2659,2660,2663],{},[1963,2661,2662],{},"NIST CSF function",[1963,2664,2665],{},"NIST SP 800-171 families",[1970,2667,2668,2676,2684,2692,2700,2708],{},[1960,2669,2670,2673],{},[1975,2671,2672],{},"Govern",[1975,2674,2675],{},"Security Assessment, Risk Assessment",[1960,2677,2678,2681],{},[1975,2679,2680],{},"Identify",[1975,2682,2683],{},"Risk Assessment, Configuration Management",[1960,2685,2686,2689],{},[1975,2687,2688],{},"Protect",[1975,2690,2691],{},"Access Control, Awareness and Training, Configuration Management, Identification and Authentication, Maintenance, Media Protection, Personnel Security, Physical Protection, System and Communications Protection",[1960,2693,2694,2697],{},[1975,2695,2696],{},"Detect",[1975,2698,2699],{},"Audit and Accountability, System and Information Integrity",[1960,2701,2702,2705],{},[1975,2703,2704],{},"Respond",[1975,2706,2707],{},"Incident Response",[1960,2709,2710,2713],{},[1975,2711,2712],{},"Recover",[1975,2714,2715],{},"Incident Response, System and Information Integrity",[37,2717,2718],{},"An organization with a mature NIST CSF implementation will have significant coverage toward CMMC Level 2, though the specific implementation details and evidence requirements differ.",[44,2720,2722],{"id":2721},"cmmc-and-iso-27001","CMMC and ISO 27001",[37,2724,2725,2729],{},[86,2726,2728],{"href":2727},"\u002Fframeworks\u002Fiso27001","ISO 27001"," Annex A controls overlap substantially with NIST SP 800-171 requirements. Key areas of overlap include access control, cryptography, operations security, communications security, and incident management. Organizations already ISO 27001 certified will find that many of their existing controls satisfy CMMC Level 2 practices — though CUI-specific handling requirements and DoD incident reporting obligations are unique to CMMC.",[44,2731,2733],{"id":2732},"cmmc-and-fedramp","CMMC and FedRAMP",[37,2735,2736],{},"Cloud service providers supporting DoD contracts often need both FedRAMP authorization and CMMC certification. FedRAMP is based on NIST SP 800-53, which is more comprehensive than NIST SP 800-171. A FedRAMP-authorized system at the Moderate baseline will satisfy the majority of CMMC Level 2 requirements, but organizations must still verify coverage and produce CMMC-specific documentation.",[32,2738,2740],{"id":2739},"nist-sp-800-171-rev-3","NIST SP 800-171 Rev 3",[37,2742,2743,2744,2747],{},"NIST published SP 800-171 Rev 3 in May 2024 with significant restructuring. However, ",[52,2745,2746],{},"CMMC 2.0 Level 2 currently maps to Rev 2",", not Rev 3. The DoD has indicated it will update CMMC to align with Rev 3 in a future rulemaking, but no timeline has been announced. Organizations should implement against Rev 2 for current CMMC compliance while monitoring for updates.",[32,2749,895],{"id":894},[37,2751,2752,2753,731,2755,2757,2758,2761],{},"episki maps every CMMC Level 2 practice to its NIST SP 800-171 Rev 2 source requirement with pre-written narratives and evidence templates. When you also pursue ",[86,2754,155],{"href":154},[86,2756,2728],{"href":2727},", the unified control graph highlights overlap automatically — one control satisfies multiple frameworks without duplicating documentation. As NIST SP 800-171 Rev 3 alignment is announced, episki will provide migration guidance showing what changes. ",[86,2759,903],{"href":494,"rel":2760},[902]," to see the full mapping.",{"title":436,"searchDepth":437,"depth":437,"links":2763},[2764,2765,2781,2786,2787],{"id":2472,"depth":437,"text":2473},{"id":2486,"depth":437,"text":2487,"children":2766},[2767,2768,2769,2770,2771,2772,2773,2774,2775,2776,2777,2778,2779,2780],{"id":2493,"depth":442,"text":2494},{"id":2519,"depth":442,"text":2520},{"id":2526,"depth":442,"text":2527},{"id":2533,"depth":442,"text":2534},{"id":2540,"depth":442,"text":2541},{"id":2562,"depth":442,"text":2563},{"id":2569,"depth":442,"text":2570},{"id":2576,"depth":442,"text":2577},{"id":2583,"depth":442,"text":2584},{"id":2590,"depth":442,"text":2591},{"id":2597,"depth":442,"text":2598},{"id":2604,"depth":442,"text":2605},{"id":2611,"depth":442,"text":2612},{"id":2633,"depth":442,"text":2634},{"id":2640,"depth":437,"text":2641,"children":2782},[2783,2784,2785],{"id":2647,"depth":442,"text":2648},{"id":2721,"depth":442,"text":2722},{"id":2732,"depth":442,"text":2733},{"id":2739,"depth":437,"text":2740},{"id":894,"depth":437,"text":895},"How CMMC Level 2 maps to NIST SP 800-171 Rev 2's 14 control families and 110 security requirements, plus overlap with NIST CSF and ISO 27001.",{},[523,2458,2791],"nistcsf",[931,1416,1744],{"title":2794,"description":2795},"CMMC to NIST SP 800-171 Mapping — Control Families and Overlap Guide","Complete mapping of CMMC Level 2 practices to NIST SP 800-171 Rev 2 control families. Understand cross-framework overlap with NIST CSF and ISO 27001.","5.frameworks\u002Fcmmc\u002Fnist-800-171-mapping","g6SHRIJZ5YlpzIpR_uCUJVULPl590tRWJnn6TS4V2sA",{"id":2799,"title":2800,"body":2801,"description":3078,"extension":467,"faq":3079,"frameworkSlug":523,"lastUpdated":925,"meta":3093,"navigation":505,"path":323,"relatedTerms":3094,"relatedTopics":3095,"seo":3097,"stem":3100,"__hash__":3101},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fself-assessment-vs-third-party.md","CMMC Self-Assessment vs Third-Party (C3PAO)",{"type":29,"value":2802,"toc":3060},[2803,2807,2810,2814,2818,2821,2825,2828,2831,2835,2838,2842,2845,2883,2886,2890,2893,2896,2900,2903,2906,2948,2951,2955,2962,2969,2972,2976,2979,3004,3006,3009,3012,3014,3052,3054],[32,2804,2806],{"id":2805},"two-paths-to-cmmc-when-self-assessment-works-and-when-it-does-not","Two paths to CMMC: when self-assessment works and when it does not",[37,2808,2809],{},"CMMC 2.0 allows two assessment paths for most contractors: self-assessment performed internally, and third-party assessment performed by a CMMC Third-Party Assessment Organization (C3PAO). Choosing — or being assigned — the right path depends on your CMMC level and the sensitivity of the information your contract involves. This page explains when each path applies, what each costs, how long each takes, and the risks that come with each.",[32,2811,2813],{"id":2812},"when-self-assessment-is-sufficient","When self-assessment is sufficient",[44,2815,2817],{"id":2816},"cmmc-level-1-always-self-assessment","CMMC Level 1: always self-assessment",[37,2819,2820],{},"Level 1 is always a self-assessment. The 17 practices from FAR 52.204-21 are fundamental cyber hygiene — things like limiting system access to authorized users, sanitizing media before disposal, and using malware protection. The DoD decided these controls are straightforward enough to verify internally. Organizations handling only Federal Contract Information (FCI) — the broad category of contract-related information that is not intended for public release — stay at Level 1 and self-assess annually.",[44,2822,2824],{"id":2823},"cmmc-level-2-self-assessment-for-less-sensitive-cui","CMMC Level 2: self-assessment for less sensitive CUI",[37,2826,2827],{},"Level 2 splits. Contracts involving less sensitive Controlled Unclassified Information (CUI) accept self-assessment. Contracts involving more sensitive CUI, critical programs, or certain categories of controlled technical information require third-party certification. The split is intentional: self-assessment keeps costs down for the long tail of defense suppliers, while third-party certification provides verified assurance where the stakes are highest.",[37,2829,2830],{},"The contracting officer tells you which path applies by pointing at DFARS 252.204-7021 and specifying the required level and assessment type in the solicitation. The decision is not yours to make.",[44,2832,2834],{"id":2833},"cmmc-level-3-never-self-assessment","CMMC Level 3: never self-assessment",[37,2836,2837],{},"Level 3 is government-led, conducted by the Defense Contract Management Agency's DIBCAC assessors. Level 3 requires a valid Level 2 C3PAO certification as a prerequisite. There is no self-assessment path at Level 3.",[32,2839,2841],{"id":2840},"the-self-assessment-path-what-it-actually-entails","The self-assessment path: what it actually entails",[37,2843,2844],{},"Self-assessment is cheaper and faster than a C3PAO engagement, but it is not the low-effort option some contractors hope for. A credible self-assessment involves:",[358,2846,2847,2853,2859,2865,2871,2877],{},[95,2848,2849,2852],{},[52,2850,2851],{},"Scoping the environment"," — defining which systems, people, and processes handle FCI (Level 1) or CUI (Level 2) and therefore fall within the assessment boundary.",[95,2854,2855,2858],{},[52,2856,2857],{},"Documenting the System Security Plan (SSP)"," — a narrative description of how each required practice or NIST SP 800-171 requirement is implemented.",[95,2860,2861,2864],{},[52,2862,2863],{},"Collecting evidence"," — screenshots, configurations, policies, logs, and other artifacts supporting each requirement.",[95,2866,2867,2870],{},[52,2868,2869],{},"Scoring against the DoD Assessment Methodology"," — starting at 110 for Level 2 and subtracting 1, 3, or 5 points for each unmet objective.",[95,2872,2873,2876],{},[52,2874,2875],{},"Submitting to SPRS"," — entering the score in the Supplier Performance Risk System.",[95,2878,2879,2882],{},[52,2880,2881],{},"Affirming annually"," — a senior official signs an annual affirmation of continued compliance.",[37,2884,2885],{},"The DoD expects self-assessments to be conducted with the same rigor as a third-party assessment. It reserves the right to audit SPRS submissions and has already pursued False Claims Act cases against contractors who submitted inflated scores.",[44,2887,2889],{"id":2888},"self-assessment-cost-and-timeline","Self-assessment cost and timeline",[37,2891,2892],{},"The direct cost of a self-assessment is staff time. Organizations new to NIST SP 800-171 typically need 6 to 18 months to stand up controls, document them, and produce defensible evidence. Organizations already operating against NIST SP 800-171 can usually complete a self-assessment in 4 to 8 weeks once the control set is in place.",[37,2894,2895],{},"External consulting help is common. Expect $15,000 to $50,000 for a consultant-supported Level 2 self-assessment project, including SSP drafting, gap analysis, and evidence organization. Large environments with complex scope can run higher.",[32,2897,2899],{"id":2898},"the-c3pao-path-what-it-actually-entails","The C3PAO path: what it actually entails",[37,2901,2902],{},"A C3PAO assessment is a formal third-party engagement. Assessors from a Cyber AB-accredited C3PAO evaluate your organization against the same NIST SP 800-171 objectives a self-assessment uses, but with an independent, documented, and externally defensible methodology.",[37,2904,2905],{},"A typical C3PAO engagement runs:",[358,2907,2908,2914,2920,2925,2931,2937,2942],{},[95,2909,2910,2913],{},[52,2911,2912],{},"C3PAO selection"," — choose from the published list of accredited C3PAOs. Look at their experience with organizations your size, their assessor availability, and their readiness review services.",[95,2915,2916,2919],{},[52,2917,2918],{},"Contracting and scoping"," — the C3PAO defines the scope of the assessment, the timeline, and the logistics.",[95,2921,2922,2924],{},[52,2923,619],{}," (optional but common) — a formal mock assessment that identifies gaps before the real assessment begins. This is typically a separate engagement.",[95,2926,2927,2930],{},[52,2928,2929],{},"Evidence collection and document review"," — two to four weeks of the C3PAO reviewing your SSP, policies, procedures, and evidence artifacts.",[95,2932,2933,2936],{},[52,2934,2935],{},"Assessment execution"," — one to three weeks of on-site or virtual assessor work including interviews, observations, and control testing.",[95,2938,2939,2941],{},[52,2940,643],{}," — the C3PAO scores each of the 110 objectives and issues one of three results: Met (full certification), Conditional (score of 88+ with a POA&M and 180-day remediation window), or Not Met (below 88, no certification).",[95,2943,2944,2947],{},[52,2945,2946],{},"Close-out"," (if Conditional) — once the POA&M items are closed within 180 days, a close-out assessment converts the Conditional into full certification.",[37,2949,2950],{},"Certification from a C3PAO is valid for three years, with annual affirmations required each year between full assessments.",[44,2952,2954],{"id":2953},"c3pao-cost-and-timeline","C3PAO cost and timeline",[37,2956,2957,2958,2961],{},"A Level 2 C3PAO assessment typically costs ",[52,2959,2960],{},"$50,000 to $150,000",", with larger or distributed environments running well above that range. The cost is driven primarily by assessor time, which scales with scope. A single-site small business with a tightly bounded CUI enclave can come in under $50,000; a multi-site defense prime can pay several hundred thousand.",[37,2963,2964,2965,2968],{},"On timeline: plan for ",[52,2966,2967],{},"9 to 12 months"," from the decision to engage a C3PAO to a certification in hand. That accounts for readiness work, scheduling (C3PAO assessors are in high demand as enforcement ramps), the assessment itself, and any POA&M remediation.",[37,2970,2971],{},"Readiness reviews are a separate cost — typically $20,000 to $75,000 — and are strongly recommended. Going into a formal C3PAO assessment without a readiness review often means learning about gaps the expensive way.",[32,2973,2975],{"id":2974},"how-to-decide","How to decide",[37,2977,2978],{},"For most organizations, there is no decision to make — the contracting officer tells you which path applies. But where you do have latitude (for example, when you are preparing in advance of a contract being awarded), consider:",[92,2980,2981,2987,2993,2998],{},[95,2982,2983,2986],{},[52,2984,2985],{},"Contract eligibility."," If you want to be competitive on contracts that require C3PAO certification, you need C3PAO certification. A self-assessment does not let you bid on those contracts.",[95,2988,2989,2992],{},[52,2990,2991],{},"Customer expectations."," Some primes require their subcontractors to hold C3PAO certification even when the prime itself could self-assess, because they want independent verification across their supply chain.",[95,2994,2995,2997],{},[52,2996,1609],{}," Self-assessments are government representations. Organizations that are uncertain about their NIST SP 800-171 posture may prefer the defensibility of a third-party assessment.",[95,2999,3000,3003],{},[52,3001,3002],{},"Budget and timeline."," Self-assessment is cheaper and faster. For organizations where a Level 2 self-assessment is genuinely acceptable, it is the rational choice.",[32,3005,1305],{"id":1304},[37,3007,3008],{},"The self-assessment vs C3PAO decision shapes everything downstream: your budget, your hiring plan, your vendor selection (C3PAOs, readiness consultants, tooling), your evidence rigor, and your internal audit cadence. Organizations that assume \"we'll just self-assess\" and then discover a key contract requires C3PAO certification are typically 9 to 18 months away from being bid-eligible on that contract. That timeline is rarely recoverable in a tight competition.",[37,3010,3011],{},"The defensive move is to run your program as if C3PAO certification is coming, even if you start on the self-assessment path. Your evidence quality, SSP rigor, and POA&M hygiene will all be better — and if the path changes, you are ready.",[32,3013,1315],{"id":1314},[92,3015,3016,3022,3028,3034,3040,3046],{},[95,3017,3018,3021],{},[52,3019,3020],{},"Treating self-assessment as a lighter bar."," The assessment methodology is identical. Self-assessment is cheaper because you skip the C3PAO fees, not because the work is smaller.",[95,3023,3024,3027],{},[52,3025,3026],{},"Inflating the SPRS score."," Every over-scored objective is a potential False Claims Act exposure. Conservative scoring is the safe posture.",[95,3029,3030,3033],{},[52,3031,3032],{},"Waiting to engage a C3PAO."," Assessor availability is the constraint. Organizations that wait until a contract requires certification typically cannot schedule in time.",[95,3035,3036,3039],{},[52,3037,3038],{},"Skipping the readiness review."," A formal readiness review surfaces problems when you can still fix them cheaply. A failed C3PAO assessment is a much more expensive way to find the same gaps.",[95,3041,3042,3045],{},[52,3043,3044],{},"Ignoring the 180-day POA&M window."," Conditional certifications revoke automatically if POA&M items are not closed. Track closures like a deadline because that is what they are.",[95,3047,3048,3051],{},[52,3049,3050],{},"Forgetting the annual affirmation."," Between C3PAO assessments, a senior official must affirm continued compliance each year. Missing an affirmation lapses your certification.",[32,3053,895],{"id":894},[37,3055,3056,3057,2434],{},"episki supports both CMMC assessment paths. For self-assessments, the platform drafts your SSP, tracks your SPRS score in real time, and produces the evidence package a DoD audit would expect. For C3PAO engagements, episki provides a scoped assessor portal — your C3PAO gets read-only access organized by assessment objective, which cuts assessor billable hours substantially. POA&M items are tracked with 180-day countdowns and owners so conditional certifications do not lapse. ",[86,3058,903],{"href":494,"rel":3059},[902],{"title":436,"searchDepth":437,"depth":437,"links":3061},[3062,3063,3068,3071,3074,3075,3076,3077],{"id":2805,"depth":437,"text":2806},{"id":2812,"depth":437,"text":2813,"children":3064},[3065,3066,3067],{"id":2816,"depth":442,"text":2817},{"id":2823,"depth":442,"text":2824},{"id":2833,"depth":442,"text":2834},{"id":2840,"depth":437,"text":2841,"children":3069},[3070],{"id":2888,"depth":442,"text":2889},{"id":2898,"depth":437,"text":2899,"children":3072},[3073],{"id":2953,"depth":442,"text":2954},{"id":2974,"depth":437,"text":2975},{"id":1304,"depth":437,"text":1305},{"id":1314,"depth":437,"text":1315},{"id":894,"depth":437,"text":895},"When CMMC Level 1 or Level 2 self-assessment is acceptable vs when a C3PAO third-party assessment is required, including costs, timelines, and False Claims Act exposure.",{"items":3080},[3081,3084,3087,3090],{"label":3082,"content":3083},"Is CMMC Level 2 self-assessment always an option?","No. Level 2 splits into two paths based on the sensitivity of the CUI involved in the contract. Less sensitive CUI can be verified via self-assessment. More sensitive CUI and most critical programs require C3PAO third-party certification. The contracting officer specifies which path applies in the solicitation.",{"label":3085,"content":3086},"How long does a C3PAO assessment take?","Expect two to six months of preparation plus the assessment itself, which is typically a two- to four-week engagement. Most organizations start engaging a C3PAO nine to twelve months before they need a certification in hand.",{"label":3088,"content":3089},"What does a C3PAO assessment cost?","CMMC Level 2 C3PAO assessments typically run $50,000 to $150,000 or more depending on scope, the number of sites, and the complexity of the environment. Small organizations with a tightly scoped CUI boundary fall at the low end; larger organizations with distributed environments pay significantly more.",{"label":3091,"content":3092},"What is the False Claims Act risk of self-assessment?","A self-assessment submitted to SPRS is a representation to the government. If the score is materially inaccurate, the organization and its officers face False Claims Act liability. Several defense contractors have settled FCA claims specifically tied to misrepresented NIST SP 800-171 scores — with settlements ranging from hundreds of thousands to tens of millions of dollars.",{},[1411,929,928],[1416,931,3096,340],"dfars-relationship",{"title":3098,"description":3099},"CMMC Self-Assessment vs C3PAO: When to Do Which, Costs & Timeline","Deciding between CMMC self-assessment and C3PAO third-party certification. Level 1 and Level 2 paths compared with realistic costs, timeline expectations, and FCA risk.","5.frameworks\u002Fcmmc\u002Fself-assessment-vs-third-party","VYYrIKbdgMK3-DnN-xxyvUJdV5WICVSFnaDuSdsoe0I",{"id":3103,"title":3104,"body":3105,"description":3400,"extension":467,"faq":3401,"frameworkSlug":523,"lastUpdated":925,"meta":3415,"navigation":505,"path":347,"relatedTerms":3416,"relatedTopics":3419,"seo":3420,"stem":3423,"__hash__":3424},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fsubcontractor-requirements.md","CMMC Subcontractor Requirements",{"type":29,"value":3106,"toc":3385},[3107,3111,3114,3117,3121,3124,3135,3138,3142,3145,3149,3152,3156,3159,3197,3200,3204,3207,3239,3243,3246,3266,3270,3273,3305,3308,3310,3313,3333,3336,3338,3376,3378],[32,3108,3110],{"id":3109},"cmmc-flow-down-the-one-rule-every-prime-must-internalize","CMMC flow-down: the one rule every prime must internalize",[37,3112,3113],{},"If you are a prime contractor holding a DoD contract that requires CMMC, the certification is not a you problem — it is a supply chain problem. The moment you share Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) with a subcontractor, your subcontractor inherits the same CMMC-driven obligations you carry. That is flow-down, and it is the operational cornerstone of the entire CMMC program.",[37,3115,3116],{},"Flow-down is not new to defense contracting. DFARS 252.204-7012 has required flow-down of safeguarding obligations since 2017. What CMMC adds is the verification step: before you share covered information with a subcontractor, you must confirm the subcontractor holds the CMMC level the data demands. This page walks through how that works in practice and where it goes wrong.",[32,3118,3120],{"id":3119},"how-cmmc-flow-down-works","How CMMC flow-down works",[37,3122,3123],{},"The CMMC flow-down model is straightforward in principle. Every time a contractor shares FCI or CUI with another organization, three things must be true:",[358,3125,3126,3129,3132],{},[95,3127,3128],{},"The receiving organization must hold a CMMC certification at the appropriate level for the information being shared.",[95,3130,3131],{},"The receiving organization's certification must be current and visible in the Supplier Performance Risk System (SPRS).",[95,3133,3134],{},"The flow-down obligation cascades — if the receiving organization then shares covered information with another tier, they face the same verification duty.",[37,3136,3137],{},"This last point is what gives CMMC its depth. A prime may have ten direct subcontractors, but each of those subcontractors may have their own subs. If CUI is flowing through the chain, every layer needs certification. The DoD's economic analysis assumed this reach when estimating that roughly 80,000 organizations would pursue CMMC Level 2.",[44,3139,3141],{"id":3140},"the-level-is-set-by-the-data-not-the-contract","The level is set by the data, not the contract",[37,3143,3144],{},"A common misconception is that every subcontractor on a Level 2 contract needs Level 2 certification. That is only true for subcontractors that actually handle CUI. If a prime subcontracts a janitorial services company that will never see CUI, no certification is required. If the prime shares only FCI (not CUI) with a small parts vendor, the parts vendor only needs Level 1. The CMMC level is determined by the sensitivity of the information flowed to the subcontractor, not by the prime's own level.",[44,3146,3148],{"id":3147},"the-assessment-type-is-set-by-the-level-not-the-tier","The assessment type is set by the level, not the tier",[37,3150,3151],{},"Likewise, tier depth does not change assessment rigor. A tier-three subcontractor that handles sensitive CUI on a contract requiring Level 2 C3PAO certification needs Level 2 C3PAO certification — the same as the prime. Being further down the chain does not unlock a lighter assessment.",[32,3153,3155],{"id":3154},"prime-contractor-responsibilities","Prime contractor responsibilities",[37,3157,3158],{},"The prime carries most of the operational burden in CMMC flow-down. At a minimum, a prime must:",[92,3160,3161,3167,3173,3179,3185,3191],{},[95,3162,3163,3166],{},[52,3164,3165],{},"Include CMMC clauses in every subcontract that touches covered information."," The subcontract should pass through DFARS 252.204-7012, -7019, -7020, and -7021 where applicable, and should specify the CMMC level the subcontractor must hold.",[95,3168,3169,3172],{},[52,3170,3171],{},"Minimize the CUI footprint."," Only share CUI with subcontractors that genuinely need it. Every additional subcontractor with CUI access is another CMMC certification to verify and monitor.",[95,3174,3175,3178],{},[52,3176,3177],{},"Verify CMMC status before sharing covered information."," Check SPRS. Do not rely on a subcontractor's word or a dated certificate PDF.",[95,3180,3181,3184],{},[52,3182,3183],{},"Track certification expirations."," CMMC certifications expire after three years (with annual affirmations in between). A certification current at contract award may lapse mid-contract.",[95,3186,3187,3190],{},[52,3188,3189],{},"Document the flow-down decisions."," If you choose not to flow CMMC down to a particular subcontractor because they will not see covered information, document that decision. If the DoD ever audits the flow-down, you want a paper trail.",[95,3192,3193,3196],{},[52,3194,3195],{},"Respond to supply chain risk."," If a subcontractor loses certification, is breached, or fails an annual affirmation, the prime needs a plan. That may mean substituting suppliers or isolating the at-risk subcontractor from CUI flows.",[37,3198,3199],{},"Most primes centralize these duties in a supply chain security function or a joint responsibility between procurement and GRC. Automation helps — tracking certification status across dozens or hundreds of subcontractors is not a spreadsheet-friendly exercise.",[32,3201,3203],{"id":3202},"subcontractor-responsibilities","Subcontractor responsibilities",[37,3205,3206],{},"If you are the subcontractor, the obligations are symmetrical:",[92,3208,3209,3215,3221,3227,3233],{},[95,3210,3211,3214],{},[52,3212,3213],{},"Understand which contract clauses apply to you."," Ask the prime for the flow-down language explicitly. Assume DFARS 252.204-7012 at minimum; the other clauses depend on the data you will see.",[95,3216,3217,3220],{},[52,3218,3219],{},"Identify the CMMC level you need."," Based on whether you will see FCI, less-sensitive CUI, or more-sensitive CUI, determine whether Level 1, Level 2 self-assessment, or Level 2 C3PAO applies.",[95,3222,3223,3226],{},[52,3224,3225],{},"Keep your SPRS entry current."," This is how the prime will verify you. A stale SPRS score is a flow-down failure even if your posture is strong.",[95,3228,3229,3232],{},[52,3230,3231],{},"Flow-down further if you engage your own subs."," If you sub-subcontract CUI work, you become the \"prime\" for your own flow-down obligations.",[95,3234,3235,3238],{},[52,3236,3237],{},"Report incidents upstream."," DFARS 252.204-7012 requires rapid (72-hour) incident reporting to the DoD. In practice, most primes require subcontractors to notify them first so the prime can coordinate.",[44,3240,3242],{"id":3241},"cmmc-for-small-subcontractors","CMMC for small subcontractors",[37,3244,3245],{},"Small businesses are the group most strained by CMMC flow-down. Many small suppliers do not have dedicated security staff, have never submitted an SPRS score, and lack the budget for a C3PAO assessment. There are a few practical levers:",[92,3247,3248,3254,3260],{},[95,3249,3250,3253],{},[52,3251,3252],{},"Reduce scope."," If the small subcontractor can do their work without touching CUI, structure the engagement that way. Send redacted drawings. Use an enclave.",[95,3255,3256,3259],{},[52,3257,3258],{},"Pursue Level 1 only."," Many small suppliers can limit their exposure to FCI only, which keeps them at Level 1 (self-assessment) and sidesteps Level 2 entirely.",[95,3261,3262,3265],{},[52,3263,3264],{},"Share infrastructure."," Some primes offer subcontractors access to a CUI enclave — a shared, pre-certified environment where the subcontractor can do CUI work without hosting CUI on their own systems. This transfers much of the certification burden to the enclave operator.",[32,3267,3269],{"id":3268},"tier-based-assessment-in-practice","Tier-based assessment in practice",[37,3271,3272],{},"Tiered CMMC flow-down looks simple on a diagram and complicated in reality. Consider a typical example:",[92,3274,3275,3281,3287,3293,3299],{},[95,3276,3277,3280],{},[52,3278,3279],{},"Prime:"," Large defense integrator holding a Level 2 C3PAO contract. Certified at Level 2 C3PAO.",[95,3282,3283,3286],{},[52,3284,3285],{},"Tier-1 sub:"," Engineering firm designing a subsystem. Receives CUI (drawings, specifications). Needs Level 2 C3PAO.",[95,3288,3289,3292],{},[52,3290,3291],{},"Tier-2 sub:"," Machine shop fabricating parts from the drawings. Receives CUI (drawings only). Needs Level 2 — possibly self-assessment if the contract allows.",[95,3294,3295,3298],{},[52,3296,3297],{},"Tier-2 sub (separate):"," Tooling vendor providing fixtures. Receives FCI (basic contract info) but no CUI. Needs Level 1.",[95,3300,3301,3304],{},[52,3302,3303],{},"Tier-3 sub:"," Heat treatment service used by the machine shop. Receives no covered information (parts only, no drawings). No CMMC required.",[37,3306,3307],{},"The prime does not verify the tier-3 heat treater directly — that is the tier-2 machine shop's flow-down duty. But the prime is still exposed if any link in the chain mishandles covered information, which is why supply chain visibility is a board-level concern for large defense integrators.",[32,3309,1305],{"id":1304},[37,3311,3312],{},"Subcontractor flow-down is not a one-time project. It lives in three operational rhythms:",[92,3314,3315,3321,3327],{},[95,3316,3317,3320],{},[52,3318,3319],{},"Pre-award."," Every new subcontract that might involve covered information needs a CMMC flow-down decision before the contract is signed. Do not award first and reconcile later.",[95,3322,3323,3326],{},[52,3324,3325],{},"In-flight."," Certifications expire. Subcontractors merge, spin off divisions, or lose key personnel. Your flow-down register needs to live alongside your broader third-party risk program.",[95,3328,3329,3332],{},[52,3330,3331],{},"At renewal."," Contract option years and recompetes are the moment to re-verify every supplier's CMMC status and close any drift.",[37,3334,3335],{},"Organizations that already run a mature vendor risk management program have a head start — CMMC flow-down is a specialization of the same discipline. Organizations without that foundation will need to stand one up.",[32,3337,1315],{"id":1314},[92,3339,3340,3346,3352,3358,3364,3370],{},[95,3341,3342,3345],{},[52,3343,3344],{},"Assuming certification status is static."," A subcontractor that was Level 2 certified last year may not be today. Check SPRS on a recurring schedule.",[95,3347,3348,3351],{},[52,3349,3350],{},"Over-sharing CUI."," Primes sometimes flow CUI to subcontractors who do not need it \"just in case.\" Every unnecessary share creates a new CMMC obligation to track.",[95,3353,3354,3357],{},[52,3355,3356],{},"Forgetting the CMMC clauses at subcontract modification."," When an existing subcontract is modified to add scope involving CUI, the CMMC clauses must be added too. A modification is the easiest place for flow-down to be missed.",[95,3359,3360,3363],{},[52,3361,3362],{},"Relying on certificates instead of SPRS."," PDF certificates can be doctored or stale. SPRS is the authoritative source.",[95,3365,3366,3369],{},[52,3367,3368],{},"Treating COTS vendors as subcontractors."," Commercial off-the-shelf product providers are explicitly excluded from CMMC. Do not burn effort chasing certifications that are not required.",[95,3371,3372,3375],{},[52,3373,3374],{},"Ignoring cloud service providers."," The cloud providers hosting your CUI are inside your CMMC boundary. They need their own FedRAMP authorization or CMMC certification at the appropriate level.",[32,3377,895],{"id":894},[37,3379,3380,3381,3384],{},"episki maintains a subcontractor flow-down register inside your CMMC workspace. Each supplier is tracked with their required CMMC level, current SPRS score, certification expiration, and the specific subcontracts where CUI flows. When a certification is expiring or a score drifts, episki alerts you before it affects an active contract. For primes running dozens or hundreds of subcontractor relationships, this turns CMMC flow-down from a spreadsheet problem into a managed program. ",[86,3382,903],{"href":494,"rel":3383},[902]," to map your flow-down obligations.",{"title":436,"searchDepth":437,"depth":437,"links":3386},[3387,3388,3392,3393,3396,3397,3398,3399],{"id":3109,"depth":437,"text":3110},{"id":3119,"depth":437,"text":3120,"children":3389},[3390,3391],{"id":3140,"depth":442,"text":3141},{"id":3147,"depth":442,"text":3148},{"id":3154,"depth":437,"text":3155},{"id":3202,"depth":437,"text":3203,"children":3394},[3395],{"id":3241,"depth":442,"text":3242},{"id":3268,"depth":437,"text":3269},{"id":1304,"depth":437,"text":1305},{"id":1314,"depth":437,"text":1315},{"id":894,"depth":437,"text":895},"How CMMC flow-down works — what primes must require of subcontractors, how tiered certification applies, SPRS verification, and common flow-down mistakes.",{"items":3402},[3403,3406,3409,3412],{"label":3404,"content":3405},"Do all subcontractors need CMMC certification?","Only subcontractors that process, store, or transmit FCI or CUI as part of their subcontract need CMMC certification. Subcontractors that provide commercial off-the-shelf products or perform work that never touches covered information are excluded.",{"label":3407,"content":3408},"Does a subcontractor need the same CMMC level as the prime?","Not necessarily. The subcontractor needs the CMMC level that corresponds to the information the prime flows down to them. A prime at Level 2 can share only FCI with a subcontractor, which means that subcontractor only needs Level 1. The level is tied to the data shared, not the prime's certification.",{"label":3410,"content":3411},"Who is responsible for verifying subcontractor CMMC status?","The prime contractor — or any higher-tier contractor flowing information down — is responsible for verifying that the receiving subcontractor holds the required CMMC level before sharing FCI or CUI. Verification is done through SPRS, which displays current assessment scores and certification status.",{"label":3413,"content":3414},"Can a prime flow down more than one CMMC clause?","Yes. DFARS 252.204-7012 (safeguarding), 252.204-7019 and -7020 (SPRS scoring), and 252.204-7021 (CMMC certification) all flow down when covered information is shared. Primes typically include the full set in their subcontracts so the subcontractor inherits the same framework of obligations.",{},[1411,3417,3418],"third-party-risk","vendor-risk-management",[159,931,3096,1745],{"title":3421,"description":3422},"CMMC Subcontractor Requirements: Flow-Down Rules and Prime Obligations","CMMC flow-down explained. What prime contractors must require of subcontractors, tier-based CMMC certification, SPRS verification, and practical guidance for supply chain compliance.","5.frameworks\u002Fcmmc\u002Fsubcontractor-requirements","Xyw8pJB_I5UgbqnvZPaHAi8jHkMjkr20WBPhy9V9BX0",{"id":3426,"title":3427,"body":3428,"description":3697,"extension":467,"faq":924,"frameworkSlug":523,"lastUpdated":925,"meta":3698,"navigation":505,"path":186,"relatedTerms":3699,"relatedTopics":3701,"seo":3702,"stem":3705,"__hash__":3706},"frameworkTopics\u002F5.frameworks\u002Fcmmc\u002Fwho-needs-cmmc.md","Who Needs CMMC",{"type":29,"value":3429,"toc":3677},[3430,3434,3442,3445,3449,3453,3456,3460,3463,3469,3473,3476,3480,3483,3487,3490,3494,3497,3499,3502,3506,3519,3525,3527,3530,3549,3554,3558,3561,3587,3591,3594,3614,3618,3621,3641,3645,3648,3668,3670],[32,3431,3433],{"id":3432},"who-is-required-to-get-cmmc-certified","Who is required to get CMMC certified?",[37,3435,3436,3437,731,3439,3441],{},"Any organization that processes, stores, or transmits ",[52,3438,963],{},[52,3440,995],{}," as part of a Department of Defense contract or subcontract will need CMMC certification. The required level depends on the type of information handled.",[37,3443,3444],{},"This is not limited to large defense primes. The requirement flows down through the entire supply chain, reaching small and mid-size businesses that may be several tiers removed from the DoD.",[32,3446,3448],{"id":3447},"organizations-that-need-cmmc","Organizations that need CMMC",[44,3450,3452],{"id":3451},"prime-contractors","Prime contractors",[37,3454,3455],{},"Organizations that contract directly with the DoD are the most obvious candidates. If your contract involves handling FCI or CUI — which the vast majority of DoD contracts do — you will need CMMC certification at the level specified in the solicitation.",[44,3457,3459],{"id":3458},"subcontractors-all-tiers","Subcontractors (all tiers)",[37,3461,3462],{},"CMMC requirements flow down to subcontractors at every tier. If a prime contractor shares FCI or CUI with a subcontractor, that subcontractor must hold the appropriate CMMC certification. This flow-down continues through every layer of the supply chain.",[37,3464,3465,3468],{},[52,3466,3467],{},"Example:"," A DoD contract requires Level 2 certification. The prime contractor engages a subcontractor to build a software component and shares CUI design specifications. That subcontractor must also achieve Level 2. If the subcontractor further subcontracts work and shares CUI, the next-tier sub must also be certified.",[44,3470,3472],{"id":3471},"cloud-service-providers","Cloud service providers",[37,3474,3475],{},"Cloud service providers (CSPs) that host, process, or store FCI or CUI for DoD contractors need CMMC certification at the level corresponding to the information they handle. CSPs supporting CUI workloads typically need to be FedRAMP authorized at the Moderate baseline or higher, which provides significant overlap with CMMC Level 2 requirements.",[44,3477,3479],{"id":3478},"managed-service-providers-and-it-vendors","Managed service providers and IT vendors",[37,3481,3482],{},"Organizations providing managed IT services, managed security services, or IT infrastructure to defense contractors may need CMMC certification if they have access to FCI or CUI through their service delivery. This includes managed SOC providers, helpdesk services with access to contractor systems, and backup or disaster recovery providers handling contractor data.",[44,3484,3486],{"id":3485},"foreign-suppliers","Foreign suppliers",[37,3488,3489],{},"CMMC applies to foreign organizations in the defense supply chain that handle FCI or CUI. However, the Cyber AB is working to establish mutual recognition agreements and international assessment frameworks. Foreign suppliers should monitor Cyber AB guidance for their specific country and engage early with their prime contractor to understand requirements.",[32,3491,3493],{"id":3492},"understanding-fci-and-cui","Understanding FCI and CUI",[37,3495,3496],{},"The distinction between FCI and CUI determines your minimum CMMC level.",[44,3498,963],{"id":962},[37,3500,3501],{},"FCI is information that is provided by or generated for the government under a contract to develop or deliver a product or service. It does not include information provided by the government to the public or simple transactional information (like contract award data).",[37,3503,3504],{},[52,3505,971],{},[92,3507,3508,3511,3514,3516],{},[95,3509,3510],{},"Contract specifications and requirements documents",[95,3512,3513],{},"Technical drawings shared by the government for manufacturing",[95,3515,979],{},[95,3517,3518],{},"Internal communications about contract deliverables",[37,3520,3521,3524],{},[52,3522,3523],{},"Minimum CMMC level:"," Level 1 (17 practices, self-assessment)",[44,3526,995],{"id":994},[37,3528,3529],{},"CUI is information that requires safeguarding or dissemination controls pursuant to law, regulation, or government-wide policy. It is more sensitive than FCI but not classified. CUI categories relevant to defense include:",[92,3531,3532,3534,3537,3540,3543,3546],{},[95,3533,1013],{},[95,3535,3536],{},"Export-controlled information (ITAR, EAR)",[95,3538,3539],{},"Critical infrastructure security information",[95,3541,3542],{},"Naval nuclear propulsion information",[95,3544,3545],{},"Operations security information",[95,3547,3548],{},"Personnel security information",[37,3550,3551,3553],{},[52,3552,3523],{}," Level 2 (110 practices, self-assessment or C3PAO depending on sensitivity)",[44,3555,3557],{"id":3556},"how-to-identify-cui-in-your-environment","How to identify CUI in your environment",[37,3559,3560],{},"CUI should be marked by the originator with CUI markings per 32 CFR Part 2002. In practice, marking is inconsistent. To identify CUI in your environment:",[358,3562,3563,3569,3575,3581],{},[95,3564,3565,3568],{},[52,3566,3567],{},"Review your contract"," — look for DFARS clause 252.204-7012 (Safeguarding Covered Defense Information), which indicates CUI is present",[95,3570,3571,3574],{},[52,3572,3573],{},"Check data received from the DoD"," — look for CUI markings, export control notices, or distribution limitation statements",[95,3576,3577,3580],{},[52,3578,3579],{},"Ask your contracting officer"," — if you are unsure whether information qualifies as CUI, request clarification",[95,3582,3583,3586],{},[52,3584,3585],{},"Err on the side of caution"," — treat ambiguous information as CUI until confirmed otherwise",[32,3588,3590],{"id":3589},"flow-down-requirements","Flow-down requirements",[37,3592,3593],{},"Flow-down is one of the most operationally complex aspects of CMMC. When a prime contractor (or any tier) shares FCI or CUI with a subcontractor, they must:",[358,3595,3596,3602,3608],{},[95,3597,3598,3601],{},[52,3599,3600],{},"Include CMMC requirements in the subcontract"," — the subcontract must specify the required CMMC level",[95,3603,3604,3607],{},[52,3605,3606],{},"Verify subcontractor certification"," — before sharing FCI or CUI, confirm the subcontractor holds a valid CMMC certification at the required level via SPRS",[95,3609,3610,3613],{},[52,3611,3612],{},"Monitor ongoing compliance"," — subcontractor certifications expire and must be renewed. Primes should track subcontractor certification status",[44,3615,3617],{"id":3616},"reducing-flow-down-burden","Reducing flow-down burden",[37,3619,3620],{},"Organizations can limit the number of subcontractors that need CMMC certification by:",[92,3622,3623,3629,3635],{},[95,3624,3625,3628],{},[52,3626,3627],{},"Minimizing CUI sharing"," — only share CUI with subcontractors that genuinely need it for their work",[95,3630,3631,3634],{},[52,3632,3633],{},"Using secure enclaves"," — provide subcontractors access to CUI through controlled environments rather than transferring data to their systems",[95,3636,3637,3640],{},[52,3638,3639],{},"Consolidating suppliers"," — fewer suppliers with CUI access means fewer CMMC certifications to track",[32,3642,3644],{"id":3643},"who-does-not-need-cmmc","Who does NOT need CMMC?",[37,3646,3647],{},"CMMC is not required for:",[92,3649,3650,3656,3662],{},[95,3651,3652,3655],{},[52,3653,3654],{},"Commercially available off-the-shelf (COTS) suppliers"," — organizations that only provide COTS products are explicitly excluded from CMMC requirements",[95,3657,3658,3661],{},[52,3659,3660],{},"Contracts that do not involve FCI or CUI"," — purely public information or non-sensitive contract work does not trigger CMMC",[95,3663,3664,3667],{},[52,3665,3666],{},"Non-DoD federal contracts"," — CMMC is a DoD program. Other federal agencies have their own cybersecurity requirements (though some are considering adopting CMMC-like models)",[32,3669,895],{"id":894},[37,3671,3672,3673,3676],{},"episki simplifies CMMC scoping by helping you identify where FCI and CUI flow through your environment and which systems fall within your assessment boundary. The subcontractor flow-down tracker monitors certification status across your supply chain and alerts you when a subcontractor's certification is expiring. For organizations at multiple supply chain tiers, episki maintains separate scoping views for each contract while reusing shared controls. ",[86,3674,903],{"href":494,"rel":3675},[902]," to map your CMMC scope.",{"title":436,"searchDepth":437,"depth":437,"links":3678},[3679,3680,3687,3692,3695,3696],{"id":3432,"depth":437,"text":3433},{"id":3447,"depth":437,"text":3448,"children":3681},[3682,3683,3684,3685,3686],{"id":3451,"depth":442,"text":3452},{"id":3458,"depth":442,"text":3459},{"id":3471,"depth":442,"text":3472},{"id":3478,"depth":442,"text":3479},{"id":3485,"depth":442,"text":3486},{"id":3492,"depth":437,"text":3493,"children":3688},[3689,3690,3691],{"id":962,"depth":442,"text":963},{"id":994,"depth":442,"text":995},{"id":3556,"depth":442,"text":3557},{"id":3589,"depth":437,"text":3590,"children":3693},[3694],{"id":3616,"depth":442,"text":3617},{"id":3643,"depth":437,"text":3644},{"id":894,"depth":437,"text":895},"Which organizations need CMMC certification — prime contractors, subcontractors, cloud service providers, and anyone handling FCI or CUI for the Department of Defense.",{},[523,2103,3700],"fci",[931,1744,1416],{"title":3703,"description":3704},"Who Needs CMMC Certification — Contractors, Subcontractors, and Suppliers","Determine whether your organization needs CMMC certification. Covers prime contractors, subcontractors, cloud providers, and flow-down requirements for the defense supply chain.","5.frameworks\u002Fcmmc\u002Fwho-needs-cmmc","5GwCg1yaY6XzaYvy6_KyjXso4s9zfiZUmnymQ6MXrw4",[3708,4270,4518,4800,5028,5293,5491,5622,5859,6399,6527,7057,7188,7309,7430,7563,7818,8434,8670],{"id":3709,"title":3710,"body":3711,"description":436,"extension":467,"lastUpdated":925,"meta":4254,"navigation":505,"path":4255,"relatedFrameworks":4256,"relatedTerms":4261,"seo":4265,"slug":1413,"stem":4268,"term":3716,"__hash__":4269},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":29,"value":3712,"toc":4240},[3713,3717,3720,3724,3727,3753,3757,3763,3769,3775,3781,3785,3788,3794,3811,3817,3831,3837,3848,3852,3855,3908,3912,3915,3929,3933,3936,3959,3963,3966,4015,4019,4022,4136,4139,4142,4171,4175,4181,4184,4220,4223,4226,4229,4233],[32,3714,3716],{"id":3715},"what-is-access-control","What is Access Control?",[37,3718,3719],{},"Access control is the set of policies, procedures, and technical mechanisms that regulate who can access systems, data, and resources within an organization. It ensures that only authorized individuals can view, modify, or interact with sensitive information and critical systems. Access control is one of the most fundamental and universally required security controls across every major compliance framework.",[44,3721,3723],{"id":3722},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[37,3725,3726],{},"Access control is built on several foundational principles:",[92,3728,3729,3735,3741,3747],{},[95,3730,3731,3734],{},[52,3732,3733],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[95,3736,3737,3740],{},[52,3738,3739],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[95,3742,3743,3746],{},[52,3744,3745],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[95,3748,3749,3752],{},[52,3750,3751],{},"Default deny"," — access is denied by default unless explicitly granted",[44,3754,3756],{"id":3755},"what-are-the-types-of-access-control","What are the types of access control?",[37,3758,3759,3762],{},[52,3760,3761],{},"Role-Based Access Control (RBAC)"," — access is determined by the user's role within the organization. Roles are defined with specific permissions, and users are assigned to roles. This is the most common model in enterprise environments.",[37,3764,3765,3768],{},[52,3766,3767],{},"Attribute-Based Access Control (ABAC)"," — access decisions are based on attributes of the user, the resource, and the environment (e.g., department, location, time of day, device type).",[37,3770,3771,3774],{},[52,3772,3773],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[37,3776,3777,3780],{},[52,3778,3779],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[44,3782,3784],{"id":3783},"what-are-access-control-components","What are access control components?",[37,3786,3787],{},"A complete access control program addresses:",[37,3789,3790,3793],{},[52,3791,3792],{},"Authentication"," — verifying the identity of users:",[92,3795,3796,3799,3802,3805,3808],{},[95,3797,3798],{},"Passwords and passphrases",[95,3800,3801],{},"Multi-factor authentication (MFA)",[95,3803,3804],{},"Single sign-on (SSO)",[95,3806,3807],{},"Biometric authentication",[95,3809,3810],{},"Certificate-based authentication",[37,3812,3813,3816],{},[52,3814,3815],{},"Authorization"," — determining what authenticated users can do:",[92,3818,3819,3822,3825,3828],{},[95,3820,3821],{},"Permission assignments",[95,3823,3824],{},"Role definitions",[95,3826,3827],{},"Access control lists",[95,3829,3830],{},"Policy enforcement points",[37,3832,3833,3836],{},[52,3834,3835],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[92,3838,3839,3842,3845],{},[95,3840,3841],{},"Provisioning (granting access when hired or role changes)",[95,3843,3844],{},"Review (periodic access certification)",[95,3846,3847],{},"Deprovisioning (revoking access upon termination or role change)",[44,3849,3851],{"id":3850},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[37,3853,3854],{},"Every major framework requires access control:",[92,3856,3857,3866,3878,3892,3901],{},[95,3858,3859,3865],{},[52,3860,3861],{},[86,3862,3864],{"href":3863},"\u002Fframeworks\u002Fsoc2","SOC 2"," — CC6.1 through CC6.8 cover logical and physical access controls",[95,3867,3868,3872,3873,3877],{},[52,3869,3870],{},[86,3871,2728],{"href":2727}," — ",[86,3874,3876],{"href":3875},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[95,3879,3880,3886,3887,3891],{},[52,3881,3882],{},[86,3883,3885],{"href":3884},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[86,3888,3890],{"href":3889},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[95,3893,3894,3900],{},[52,3895,3896],{},[86,3897,3899],{"href":3898},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[95,3902,3903,3907],{},[52,3904,3905],{},[86,3906,155],{"href":154}," — PR.AC covers identity management, authentication, and access control",[44,3909,3911],{"id":3910},"what-are-access-reviews","What are access reviews?",[37,3913,3914],{},"Regular access reviews (also called access certifications) are a critical control:",[92,3916,3917,3920,3923,3926],{},[95,3918,3919],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[95,3921,3922],{},"Verify that access aligns with current job responsibilities",[95,3924,3925],{},"Identify and remove excessive or unnecessary access",[95,3927,3928],{},"Document review results and remediation actions",[44,3930,3932],{"id":3931},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[37,3934,3935],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[92,3937,3938,3941,3944,3947,3950,3953,3956],{},[95,3939,3940],{},"Excessive permissions that accumulate over time (privilege creep)",[95,3942,3943],{},"Shared or generic accounts that prevent individual accountability",[95,3945,3946],{},"Delayed deprovisioning when employees leave or change roles",[95,3948,3949],{},"Lack of MFA on critical systems and remote access paths",[95,3951,3952],{},"Inconsistent access review processes with no documented remediation",[95,3954,3955],{},"Service accounts with standing privileged access and no rotation schedule",[95,3957,3958],{},"Lack of visibility into SaaS application access outside the corporate IdP",[44,3960,3962],{"id":3961},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[37,3964,3965],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[358,3967,3968,3974,3980,3986,3992,3998,4009],{},[95,3969,3970,3973],{},[52,3971,3972],{},"Map your environment"," — inventory all systems, applications, and data repositories that require access controls. You cannot protect what you have not identified. Include SaaS applications, cloud infrastructure, on-premises servers, databases, file shares, and third-party integrations.",[95,3975,3976,3979],{},[52,3977,3978],{},"Define roles based on job functions"," — create roles that reflect organizational responsibilities, not individual users. Align roles to the principle of least privilege so each role includes only the permissions required for that function. Review role definitions annually and whenever organizational structure changes.",[95,3981,3982,3985],{},[52,3983,3984],{},"Centralize authentication with SSO"," — implement single sign-on using SAML 2.0 or OpenID Connect (OIDC) to unify identity across cloud and on-premises systems. Centralized authentication reduces password sprawl and gives security teams a single point of enforcement. Ensure all business-critical applications are integrated with your SSO provider before considering the rollout complete.",[95,3987,3988,3991],{},[52,3989,3990],{},"Layer MFA on all critical systems"," — require multi-factor authentication for remote access, privileged accounts, email, cloud consoles, and any system that touches sensitive data. Phishing-resistant methods such as FIDO2 hardware keys are preferred over SMS-based codes. At a minimum, enforce MFA on identity providers, admin consoles, and VPN access.",[95,3993,3994,3997],{},[52,3995,3996],{},"Automate provisioning and deprovisioning"," — connect your HR system to your identity provider (IdP) and use SCIM or directory sync to automate account creation, role assignment, and account removal. When an employee is terminated in the HR system, access should be revoked within minutes, not days. Automation eliminates the human error that leads to orphaned accounts and privilege creep.",[95,3999,4000,4003,4004,4008],{},[52,4001,4002],{},"Build an access request and approval workflow"," — establish a formal process where users request access with documented business justification, managers approve, and the request is logged for audit. This creates an ",[86,4005,4007],{"href":4006},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[95,4010,4011,4014],{},[52,4012,4013],{},"Monitor and log access events"," — collect authentication and authorization logs centrally. Monitor for anomalies such as failed login attempts, access from unusual locations, and privilege escalation. Logs are essential for incident response and audit evidence.",[44,4016,4018],{"id":4017},"what-are-the-access-control-requirements","What are the access control requirements?",[37,4020,4021],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[1954,4023,4024,4041],{},[1957,4025,4026],{},[1960,4027,4028,4031,4033,4035,4037,4039],{},[1963,4029,4030],{},"Requirement",[1963,4032,3864],{},[1963,4034,2728],{},[1963,4036,3885],{},[1963,4038,3899],{},[1963,4040,155],{},[1970,4042,4043,4063,4082,4102,4119],{},[1960,4044,4045,4048,4051,4054,4057,4060],{},[1975,4046,4047],{},"Unique user IDs",[1975,4049,4050],{},"CC6.1",[1975,4052,4053],{},"A.5.16",[1975,4055,4056],{},"§164.312(a)(2)(i)",[1975,4058,4059],{},"Req 8.2.1",[1975,4061,4062],{},"PR.AC-1",[1960,4064,4065,4068,4070,4073,4076,4079],{},[1975,4066,4067],{},"MFA",[1975,4069,4050],{},[1975,4071,4072],{},"A.8.5",[1975,4074,4075],{},"Addressable",[1975,4077,4078],{},"Req 8.4",[1975,4080,4081],{},"PR.AC-7",[1960,4083,4084,4087,4090,4093,4096,4099],{},[1975,4085,4086],{},"Access reviews",[1975,4088,4089],{},"CC6.2",[1975,4091,4092],{},"A.5.18",[1975,4094,4095],{},"§164.312(a)(1)",[1975,4097,4098],{},"Req 7.2",[1975,4100,4101],{},"PR.AC-4",[1960,4103,4104,4106,4109,4112,4114,4117],{},[1975,4105,3733],{},[1975,4107,4108],{},"CC6.3",[1975,4110,4111],{},"A.5.15",[1975,4113,4095],{},[1975,4115,4116],{},"Req 7.1",[1975,4118,4101],{},[1960,4120,4121,4124,4126,4128,4131,4134],{},[1975,4122,4123],{},"Deprovisioning",[1975,4125,4089],{},[1975,4127,4092],{},[1975,4129,4130],{},"§164.312(a)(2)(ii)",[1975,4132,4133],{},"Req 8.2.6",[1975,4135,4062],{},[37,4137,4138],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[37,4140,4141],{},"A few notes on framework-specific nuances:",[92,4143,4144,4149,4157,4164],{},[95,4145,4146,4148],{},[52,4147,3885],{}," treats MFA as an \"addressable\" implementation specification, meaning covered entities must implement it or document why an equivalent alternative is reasonable. In practice, most organizations implement MFA because the risk of not doing so is difficult to justify.",[95,4150,4151,4156],{},[52,4152,4153,4155],{},[86,4154,3899],{"href":3898}," v4.0"," expanded MFA requirements (Req 8.4) to include all access into the cardholder data environment, not just remote access. Organizations processing card data should verify their MFA coverage meets the updated scope.",[95,4158,4159,4163],{},[52,4160,4161],{},[86,4162,3864],{"href":3863}," does not prescribe specific technologies but evaluates whether the controls in place are suitably designed and operating effectively. Auditors will look for evidence that access control policies are enforced consistently.",[95,4165,4166,4170],{},[52,4167,4168],{},[86,4169,155],{"href":154}," provides a flexible, risk-based approach. The PR.AC subcategory identifiers map to more detailed controls in NIST SP 800-53, which organizations can reference for implementation guidance.",[44,4172,4174],{"id":4173},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[37,4176,4177,4178,313],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[52,4179,4180],{},"never trust, always verify",[37,4182,4183],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[92,4185,4186,4192,4198,4208,4214],{},[95,4187,4188,4191],{},[52,4189,4190],{},"Continuous verification"," — access decisions are re-evaluated throughout a session, not just at login. Changes in user behavior, location, or risk score can trigger step-up authentication or session termination.",[95,4193,4194,4197],{},[52,4195,4196],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[95,4199,4200,4203,4204,4207],{},[52,4201,4202],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[86,4205,1414],{"href":4206},"\u002Fglossary\u002Fencryption",") is evaluated before access is granted.",[95,4209,4210,4213],{},[52,4211,4212],{},"Identity-centric perimeter"," — the network perimeter is replaced by identity as the primary security boundary. Every user, device, and workload must prove its identity before accessing any resource.",[95,4215,4216,4219],{},[52,4217,4218],{},"Least privilege enforcement at the session level"," — access grants are scoped to the specific resource and action needed, and they expire when the session ends or conditions change.",[37,4221,4222],{},"NIST SP 800-207 defines the zero trust architecture and provides guidance on implementation. Many compliance frameworks are increasingly aligning their access control requirements with zero trust principles, making it a forward-looking strategy for organizations building or modernizing their access control programs.",[37,4224,4225],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[37,4227,4228],{},"Adopting zero trust does not require replacing your existing access control infrastructure overnight. Most organizations begin by enforcing MFA universally, segmenting their most sensitive assets, and adding device posture checks to their conditional access policies. Over time, these incremental improvements compound into a mature zero trust posture.",[44,4230,4232],{"id":4231},"how-does-episki-help-with-access-control","How does episki help with access control?",[37,4234,4235,4236,313],{},"episki tracks access control policies, monitors review schedules, and documents access provisioning and deprovisioning activities. The platform sends reminders for periodic access reviews and maintains evidence for auditors. Learn more on our ",[86,4237,4239],{"href":4238},"\u002Fframeworks","compliance platform",{"title":436,"searchDepth":437,"depth":437,"links":4241},[4242],{"id":3715,"depth":437,"text":3716,"children":4243},[4244,4245,4246,4247,4248,4249,4250,4251,4252,4253],{"id":3722,"depth":442,"text":3723},{"id":3755,"depth":442,"text":3756},{"id":3783,"depth":442,"text":3784},{"id":3850,"depth":442,"text":3851},{"id":3910,"depth":442,"text":3911},{"id":3931,"depth":442,"text":3932},{"id":3961,"depth":442,"text":3962},{"id":4017,"depth":442,"text":4018},{"id":4173,"depth":442,"text":4174},{"id":4231,"depth":442,"text":4232},{},"\u002Fglossary\u002Faccess-control",[523,4257,4258,4259,4260,2791],"soc2","iso27001","hipaa","pci",[4262,4263,1414,4264],"minimum-necessary-rule","audit-trail","user-entity-controls",{"title":4266,"description":4267},"Access Control in Compliance: RBAC, MFA & Least Privilege","Access control restricts system and data access to authorized users. Learn RBAC, MFA, least privilege, and requirements across SOC 2, ISO 27001, HIPAA, and PCI DSS.","8.glossary\u002Faccess-control","06FHtOe5hEs65vhNnMjZcNgPP9NXCQTnLD9llz_jEjM",{"id":4271,"title":4272,"body":4273,"description":436,"extension":467,"lastUpdated":925,"meta":4506,"navigation":505,"path":4507,"relatedFrameworks":4508,"relatedTerms":4509,"seo":4512,"slug":4515,"stem":4516,"term":4278,"__hash__":4517},"glossary\u002F8.glossary\u002Fchange-management.md","Change Management",{"type":29,"value":4274,"toc":4495},[4275,4279,4282,4286,4289,4306,4310,4313,4319,4339,4345,4359,4365,4376,4382,4393,4399,4410,4414,4431,4435,4455,4459,4462,4466,4469,4486,4490],[32,4276,4278],{"id":4277},"what-is-change-management","What is Change Management?",[37,4280,4281],{},"Change management is the structured process of planning, approving, implementing, and reviewing changes to an organization's information systems, infrastructure, and applications. The goal is to ensure that changes are made in a controlled manner, minimizing the risk of unintended disruptions, security vulnerabilities, or compliance violations.",[44,4283,4285],{"id":4284},"why-does-change-management-matter","Why does change management matter?",[37,4287,4288],{},"Uncontrolled changes are a leading cause of system outages, security incidents, and compliance failures. Without a formal change management process:",[92,4290,4291,4294,4297,4300,4303],{},[95,4292,4293],{},"Untested changes can introduce bugs or vulnerabilities",[95,4295,4296],{},"Unauthorized modifications can compromise security controls",[95,4298,4299],{},"Conflicting changes can cause system instability",[95,4301,4302],{},"Auditors cannot verify that changes were properly authorized and tested",[95,4304,4305],{},"Troubleshooting becomes difficult without a record of what changed",[44,4307,4309],{"id":4308},"what-are-the-components-of-a-change-management-process","What are the components of a change management process?",[37,4311,4312],{},"An effective change management program includes:",[37,4314,4315,4318],{},[52,4316,4317],{},"Change request"," — a formal submission describing the proposed change, including:",[92,4320,4321,4324,4327,4330,4333,4336],{},[95,4322,4323],{},"Description of the change",[95,4325,4326],{},"Business justification",[95,4328,4329],{},"Risk assessment",[95,4331,4332],{},"Rollback plan",[95,4334,4335],{},"Testing plan",[95,4337,4338],{},"Implementation timeline",[37,4340,4341,4344],{},[52,4342,4343],{},"Review and approval"," — changes are reviewed by appropriate stakeholders:",[92,4346,4347,4350,4353,4356],{},[95,4348,4349],{},"Technical review for feasibility and impact",[95,4351,4352],{},"Security review for potential risks",[95,4354,4355],{},"Management approval based on risk and priority",[95,4357,4358],{},"Change Advisory Board (CAB) review for significant changes",[37,4360,4361,4364],{},[52,4362,4363],{},"Testing"," — changes are tested in a non-production environment before deployment:",[92,4366,4367,4370,4373],{},[95,4368,4369],{},"Functional testing to verify the change works as intended",[95,4371,4372],{},"Regression testing to confirm existing functionality is not broken",[95,4374,4375],{},"Security testing when the change affects security-relevant systems",[37,4377,4378,4381],{},[52,4379,4380],{},"Implementation"," — changes are deployed following the approved plan:",[92,4383,4384,4387,4390],{},[95,4385,4386],{},"During designated maintenance windows when appropriate",[95,4388,4389],{},"With monitoring for unexpected issues",[95,4391,4392],{},"With rollback procedures ready if problems occur",[37,4394,4395,4398],{},[52,4396,4397],{},"Post-implementation review"," — after deployment, verify:",[92,4400,4401,4404,4407],{},[95,4402,4403],{},"The change achieved its intended outcome",[95,4405,4406],{},"No unintended side effects occurred",[95,4408,4409],{},"Documentation is updated to reflect the change",[44,4411,4413],{"id":4412},"how-do-compliance-frameworks-address-change-management","How do compliance frameworks address change management?",[92,4415,4416,4421,4426],{},[95,4417,4418,4420],{},[52,4419,3864],{}," — CC8.1 requires that changes to infrastructure, data, software, and procedures are authorized, designed, developed, configured, documented, tested, approved, and implemented",[95,4422,4423,4425],{},[52,4424,2728],{}," — control A.8.32 addresses change management, requiring that changes to information processing facilities and systems be subject to change management procedures",[95,4427,4428,4430],{},[52,4429,3899],{}," — Requirement 6.5 requires change control processes for all system components in the cardholder data environment",[44,4432,4434],{"id":4433},"what-are-the-types-of-changes-in-change-management","What are the types of changes in change management?",[92,4436,4437,4443,4449],{},[95,4438,4439,4442],{},[52,4440,4441],{},"Standard changes"," — pre-approved, low-risk, routine changes that follow a documented procedure (e.g., updating a standard software package)",[95,4444,4445,4448],{},[52,4446,4447],{},"Normal changes"," — changes that require the full change management process including review and approval",[95,4450,4451,4454],{},[52,4452,4453],{},"Emergency changes"," — urgent changes needed to resolve incidents or critical issues, typically with streamlined approval followed by retrospective documentation",[44,4456,4458],{"id":4457},"how-does-separation-of-duties-apply-to-change-management","How does separation of duties apply to change management?",[37,4460,4461],{},"A key control within change management is separation of duties — the person who develops a change should not be the same person who approves or deploys it to production. This prevents unauthorized or untested changes from reaching production systems.",[44,4463,4465],{"id":4464},"what-change-management-evidence-do-auditors-look-for","What change management evidence do auditors look for?",[37,4467,4468],{},"Auditors reviewing change management look for:",[92,4470,4471,4474,4477,4480,4483],{},[95,4472,4473],{},"Change request records with documented approvals",[95,4475,4476],{},"Evidence of testing before production deployment",[95,4478,4479],{},"Separation of duties between development, approval, and deployment",[95,4481,4482],{},"Rollback plans for significant changes",[95,4484,4485],{},"Post-implementation reviews",[44,4487,4489],{"id":4488},"how-does-episki-help-with-change-management","How does episki help with change management?",[37,4491,4492,4493,313],{},"episki tracks change management activities, integrates with ticketing and CI\u002FCD systems, and maintains audit-ready evidence of change approvals, testing, and deployment. The platform maps change management controls to SOC 2, ISO 27001, and PCI DSS requirements. Learn more on our ",[86,4494,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":4496},[4497],{"id":4277,"depth":437,"text":4278,"children":4498},[4499,4500,4501,4502,4503,4504,4505],{"id":4284,"depth":442,"text":4285},{"id":4308,"depth":442,"text":4309},{"id":4412,"depth":442,"text":4413},{"id":4433,"depth":442,"text":4434},{"id":4457,"depth":442,"text":4458},{"id":4464,"depth":442,"text":4465},{"id":4488,"depth":442,"text":4489},{},"\u002Fglossary\u002Fchange-management",[523,4257,4258,4260],[4263,1413,4510,4511],"evidence-collection","control-objectives",{"title":4513,"description":4514},"What is Change Management? Definition & Compliance Guide","Change management is the process of controlling modifications to systems and infrastructure to prevent unauthorized changes and maintain security and stability.","change-management","8.glossary\u002Fchange-management","xeecemxPeYwPVCVxeZ0eZXpmSOlKMkCLQoUsX4dbaQA",{"id":4519,"title":4520,"body":4521,"description":436,"extension":467,"lastUpdated":925,"meta":4788,"navigation":505,"path":4789,"relatedFrameworks":4790,"relatedTerms":4791,"seo":4794,"slug":4797,"stem":4798,"term":4526,"__hash__":4799},"glossary\u002F8.glossary\u002Fcontinuous-monitoring.md","Continuous Monitoring",{"type":29,"value":4522,"toc":4777},[4523,4527,4530,4534,4537,4557,4561,4564,4569,4583,4588,4602,4607,4618,4623,4637,4641,4664,4668,4723,4727,4730,4744,4747,4751,4768,4772],[32,4524,4526],{"id":4525},"what-is-continuous-monitoring","What is Continuous Monitoring?",[37,4528,4529],{},"Continuous monitoring is the practice of maintaining ongoing awareness of an organization's security posture, vulnerabilities, and threats through automated and manual observation of systems, controls, and processes. Rather than assessing security at periodic intervals, continuous monitoring provides real-time or near-real-time visibility into the effectiveness of security controls and the current threat landscape.",[44,4531,4533],{"id":4532},"why-does-continuous-monitoring-matter","Why does continuous monitoring matter?",[37,4535,4536],{},"Traditional point-in-time assessments (such as annual audits or quarterly scans) provide snapshots of security posture but miss what happens between assessments. Continuous monitoring fills this gap by:",[92,4538,4539,4542,4545,4548,4551,4554],{},[95,4540,4541],{},"Detecting threats and vulnerabilities as they emerge, not months later",[95,4543,4544],{},"Verifying that controls remain effective on an ongoing basis",[95,4546,4547],{},"Identifying configuration drift and unauthorized changes",[95,4549,4550],{},"Providing evidence of sustained compliance for auditors",[95,4552,4553],{},"Enabling faster response to security incidents",[95,4555,4556],{},"Reducing the risk of surprises during audit cycles",[44,4558,4560],{"id":4559},"what-should-you-monitor-continuously","What should you monitor continuously?",[37,4562,4563],{},"Continuous monitoring spans multiple domains:",[37,4565,4566],{},[52,4567,4568],{},"Security controls:",[92,4570,4571,4574,4577,4580],{},[95,4572,4573],{},"Are access controls still properly configured?",[95,4575,4576],{},"Are encryption mechanisms active and using current standards?",[95,4578,4579],{},"Are security policies being followed?",[95,4581,4582],{},"Are patches being applied within defined timeframes?",[37,4584,4585],{},[52,4586,4587],{},"Systems and infrastructure:",[92,4589,4590,4593,4596,4599],{},[95,4591,4592],{},"Are systems operating normally?",[95,4594,4595],{},"Are there unauthorized configuration changes?",[95,4597,4598],{},"Are there new vulnerabilities affecting your environment?",[95,4600,4601],{},"Are all endpoints protected with current security agents?",[37,4603,4604],{},[52,4605,4606],{},"User activity:",[92,4608,4609,4612,4615],{},[95,4610,4611],{},"Are there unusual access patterns or privilege escalations?",[95,4613,4614],{},"Are terminated users' accounts being deactivated promptly?",[95,4616,4617],{},"Are there failed authentication attempts indicating brute-force attacks?",[37,4619,4620],{},[52,4621,4622],{},"Compliance status:",[92,4624,4625,4628,4631,4634],{},[95,4626,4627],{},"Are all required controls implemented and operating?",[95,4629,4630],{},"Is evidence being collected on schedule?",[95,4632,4633],{},"Are policy reviews and updates happening as planned?",[95,4635,4636],{},"Are vendor assessments current?",[44,4638,4640],{"id":4639},"how-do-compliance-frameworks-address-continuous-monitoring","How do compliance frameworks address continuous monitoring?",[92,4642,4643,4648,4653,4658],{},[95,4644,4645,4647],{},[52,4646,3864],{}," — CC4.1 and CC4.2 require ongoing monitoring of the internal control system and evaluation of deficiencies",[95,4649,4650,4652],{},[52,4651,2728],{}," — clause 9 (Performance evaluation) requires monitoring, measurement, analysis, and evaluation of the ISMS",[95,4654,4655,4657],{},[52,4656,155],{}," — DE.CM (Continuous Monitoring) specifically addresses monitoring information systems and assets for cybersecurity events",[95,4659,4660,4663],{},[52,4661,4662],{},"NIST SP 800-137"," provides detailed guidance on Information Security Continuous Monitoring (ISCM)",[44,4665,4667],{"id":4666},"how-do-you-implement-continuous-monitoring","How do you implement continuous monitoring?",[358,4669,4670,4676,4699,4705,4711,4717],{},[95,4671,4672,4675],{},[52,4673,4674],{},"Define monitoring objectives"," — determine what needs to be monitored based on risk assessment and compliance requirements",[95,4677,4678,4681,4682],{},[52,4679,4680],{},"Select monitoring tools"," — deploy appropriate technologies:\n",[92,4683,4684,4687,4690,4693,4696],{},[95,4685,4686],{},"SIEM (Security Information and Event Management) for log aggregation and correlation",[95,4688,4689],{},"EDR (Endpoint Detection and Response) for endpoint monitoring",[95,4691,4692],{},"Vulnerability scanners for continuous vulnerability assessment",[95,4694,4695],{},"Configuration management tools for drift detection",[95,4697,4698],{},"GRC platforms for compliance monitoring",[95,4700,4701,4704],{},[52,4702,4703],{},"Establish baselines"," — define normal operating parameters so deviations can be detected",[95,4706,4707,4710],{},[52,4708,4709],{},"Configure alerts"," — set meaningful alert thresholds to balance detection with alert fatigue",[95,4712,4713,4716],{},[52,4714,4715],{},"Define response procedures"," — establish processes for responding to monitoring alerts",[95,4718,4719,4722],{},[52,4720,4721],{},"Review and improve"," — regularly assess monitoring effectiveness and adjust as needed",[44,4724,4726],{"id":4725},"what-is-the-difference-between-continuous-monitoring-and-continuous-compliance","What is the difference between continuous monitoring and continuous compliance?",[37,4728,4729],{},"While related, these concepts differ:",[92,4731,4732,4738],{},[95,4733,4734,4737],{},[52,4735,4736],{},"Continuous monitoring"," focuses on security — detecting threats, vulnerabilities, and anomalies in real time",[95,4739,4740,4743],{},[52,4741,4742],{},"Continuous compliance"," focuses on maintaining compliance posture — ensuring controls remain effective and evidence stays current",[37,4745,4746],{},"An effective program addresses both. Security monitoring feeds compliance evidence, and compliance monitoring ensures security controls do not degrade.",[44,4748,4750],{"id":4749},"what-are-common-challenges-with-continuous-monitoring","What are common challenges with continuous monitoring?",[92,4752,4753,4756,4759,4762,4765],{},[95,4754,4755],{},"Alert fatigue from too many low-priority notifications",[95,4757,4758],{},"Gaps in monitoring coverage across all systems",[95,4760,4761],{},"Insufficient resources to investigate and respond to alerts",[95,4763,4764],{},"Monitoring tools that generate data but lack actionable insights",[95,4766,4767],{},"Difficulty correlating events across disparate systems",[44,4769,4771],{"id":4770},"how-does-episki-help-with-continuous-monitoring","How does episki help with continuous monitoring?",[37,4773,4774,4775,313],{},"episki provides continuous compliance monitoring by tracking control effectiveness, evidence collection status, and policy review schedules. The platform integrates with security tools to pull monitoring data into your compliance program and alerts you when controls need attention. Learn more on our ",[86,4776,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":4778},[4779],{"id":4525,"depth":437,"text":4526,"children":4780},[4781,4782,4783,4784,4785,4786,4787],{"id":4532,"depth":442,"text":4533},{"id":4559,"depth":442,"text":4560},{"id":4639,"depth":442,"text":4640},{"id":4666,"depth":442,"text":4667},{"id":4725,"depth":442,"text":4726},{"id":4749,"depth":442,"text":4750},{"id":4770,"depth":442,"text":4771},{},"\u002Fglossary\u002Fcontinuous-monitoring",[523,4257,4258,2791],[4510,4263,4792,4793,1742],"incident-response","remediation",{"title":4795,"description":4796},"Continuous Monitoring for Compliance: Tools & Best Practices","Continuous monitoring tracks security controls in real time to detect threats and verify compliance. Learn how to implement it for SOC 2, ISO 27001, and NIST CSF.","continuous-monitoring","8.glossary\u002Fcontinuous-monitoring","YFq0Sck1IHoKfMLlSRFboyiO1yOmbJP8o3dmYFvhgGk",{"id":4801,"title":4802,"body":4803,"description":436,"extension":467,"lastUpdated":925,"meta":5016,"navigation":505,"path":5017,"relatedFrameworks":5018,"relatedTerms":5019,"seo":5023,"slug":1412,"stem":5026,"term":4808,"__hash__":5027},"glossary\u002F8.glossary\u002Fdata-classification.md","Data Classification",{"type":29,"value":4804,"toc":5006},[4805,4809,4812,4816,4819,4851,4855,4858,4887,4890,4894,4916,4920,4976,4980,4997,5001],[32,4806,4808],{"id":4807},"what-is-data-classification","What is Data Classification?",[37,4810,4811],{},"Data classification is the process of organizing data into categories based on its sensitivity, value, and regulatory requirements so that appropriate security controls can be applied. Rather than applying the same level of protection to all data — which is either too costly or insufficient — classification enables organizations to allocate security resources proportionally to the risk associated with each data category.",[44,4813,4815],{"id":4814},"why-does-data-classification-matter","Why does data classification matter?",[37,4817,4818],{},"Data classification is foundational to an effective security program for several reasons:",[92,4820,4821,4827,4833,4839,4845],{},[95,4822,4823,4826],{},[52,4824,4825],{},"Proportional protection"," — sensitive data receives stronger controls while less sensitive data does not burden operations with unnecessary restrictions",[95,4828,4829,4832],{},[52,4830,4831],{},"Regulatory compliance"," — many regulations require specific handling of certain data types (PHI under HIPAA, PAN under PCI DSS, personal data under GDPR)",[95,4834,4835,4838],{},[52,4836,4837],{},"Access control"," — classification determines who should have access to what data",[95,4840,4841,4844],{},[52,4842,4843],{},"Incident response"," — knowing the classification of compromised data helps determine the severity of an incident and notification requirements",[95,4846,4847,4850],{},[52,4848,4849],{},"Data lifecycle management"," — classification informs retention, archival, and destruction decisions",[44,4852,4854],{"id":4853},"what-are-the-common-data-classification-levels","What are the common data classification levels?",[37,4856,4857],{},"Most organizations use three to five classification levels:",[92,4859,4860,4866,4872,4878],{},[95,4861,4862,4865],{},[52,4863,4864],{},"Public"," — information intended for public consumption with no restrictions (marketing materials, public website content)",[95,4867,4868,4871],{},[52,4869,4870],{},"Internal"," — information for internal use that is not sensitive but should not be shared externally without authorization (internal memos, non-sensitive policies)",[95,4873,4874,4877],{},[52,4875,4876],{},"Confidential"," — sensitive business information that could cause harm if disclosed (financial data, strategic plans, customer lists)",[95,4879,4880,731,4883,4886],{},[52,4881,4882],{},"Restricted",[52,4884,4885],{},"Highly Confidential"," — the most sensitive data requiring the strongest protections (PHI, PAN, trade secrets, credentials, encryption keys)",[37,4888,4889],{},"Some organizations add additional levels or use different labels, but the principle remains: categorize data by the impact of unauthorized disclosure.",[44,4891,4893],{"id":4892},"how-do-compliance-frameworks-address-classification","How do compliance frameworks address classification?",[92,4895,4896,4901,4906,4911],{},[95,4897,4898,4900],{},[52,4899,2728],{}," — control A.5.12 requires classification of information, and A.5.13 requires labeling. The risk assessment process should consider data sensitivity when evaluating risks.",[95,4902,4903,4905],{},[52,4904,155],{}," — the Identify function (ID.AM-5) addresses classification of resources based on criticality and business value",[95,4907,4908,4910],{},[52,4909,3885],{}," — while HIPAA does not prescribe a classification scheme, PHI is inherently a \"restricted\" classification that requires specific safeguards",[95,4912,4913,4915],{},[52,4914,3899],{}," — cardholder data (particularly PAN) must be identified and protected with specific controls",[44,4917,4919],{"id":4918},"how-do-you-implement-data-classification","How do you implement data classification?",[358,4921,4922,4928,4934,4940,4946,4952,4958,4964,4970],{},[95,4923,4924,4927],{},[52,4925,4926],{},"Define classification levels"," — establish clear, understandable categories with examples",[95,4929,4930,4933],{},[52,4931,4932],{},"Create a classification policy"," — document the scheme, responsibilities, and handling requirements for each level",[95,4935,4936,4939],{},[52,4937,4938],{},"Inventory data"," — identify what data the organization holds and where it resides",[95,4941,4942,4945],{},[52,4943,4944],{},"Classify data"," — assign classification levels to data based on sensitivity criteria",[95,4947,4948,4951],{},[52,4949,4950],{},"Label data"," — apply labels (metadata, headers, visual markings) to classified data",[95,4953,4954,4957],{},[52,4955,4956],{},"Define handling rules"," — specify how each classification level should be stored, transmitted, shared, and destroyed",[95,4959,4960,4963],{},[52,4961,4962],{},"Train employees"," — ensure all staff understand the classification scheme and their responsibilities",[95,4965,4966,4969],{},[52,4967,4968],{},"Enforce through controls"," — implement technical controls (DLP, access controls, encryption) aligned with classification levels",[95,4971,4972,4975],{},[52,4973,4974],{},"Review periodically"," — reassess classifications as data, regulations, and business needs change",[44,4977,4979],{"id":4978},"what-are-common-challenges-with-data-classification","What are common challenges with data classification?",[92,4981,4982,4985,4988,4991,4994],{},[95,4983,4984],{},"Data is distributed across many systems and formats, making classification difficult",[95,4986,4987],{},"Employees may not consistently apply classification labels",[95,4989,4990],{},"Automated classification tools have limitations, especially with unstructured data",[95,4992,4993],{},"Over-classification can reduce productivity while under-classification creates risk",[95,4995,4996],{},"Classification needs to be maintained as data evolves",[44,4998,5000],{"id":4999},"how-does-episki-help-with-data-classification","How does episki help with data classification?",[37,5002,5003,5004,313],{},"episki helps organizations define data classification policies, map classification levels to security controls, and track compliance with handling requirements. The platform links classification to framework requirements across ISO 27001, NIST CSF, and other standards. Learn more on our ",[86,5005,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":5007},[5008],{"id":4807,"depth":437,"text":4808,"children":5009},[5010,5011,5012,5013,5014,5015],{"id":4814,"depth":442,"text":4815},{"id":4853,"depth":442,"text":4854},{"id":4892,"depth":442,"text":4893},{"id":4918,"depth":442,"text":4919},{"id":4978,"depth":442,"text":4979},{"id":4999,"depth":442,"text":5000},{},"\u002Fglossary\u002Fdata-classification",[523,4258,2791],[1414,1413,5020,5021,5022],"phi","pan","risk-register",{"title":5024,"description":5025},"What is Data Classification? Definition & Compliance Guide","Data classification is the process of categorizing data by sensitivity level to apply appropriate security controls. Learn how to build a classification scheme.","8.glossary\u002Fdata-classification","i7_WFqWjV-QN-2udK8JC1fF_Blw81yHdx6_cQyOh7lA",{"id":5029,"title":5030,"body":5031,"description":436,"extension":467,"lastUpdated":925,"meta":5282,"navigation":505,"path":5283,"relatedFrameworks":5284,"relatedTerms":5285,"seo":5287,"slug":5290,"stem":5291,"term":5036,"__hash__":5292},"glossary\u002F8.glossary\u002Fdisaster-recovery.md","Disaster Recovery",{"type":29,"value":5032,"toc":5271},[5033,5037,5040,5044,5050,5056,5062,5066,5069,5095,5098,5102,5105,5155,5159,5162,5200,5204,5226,5230,5233,5259,5262,5266],[32,5034,5036],{"id":5035},"what-is-disaster-recovery","What is Disaster Recovery?",[37,5038,5039],{},"Disaster recovery (DR) is the set of policies, tools, and procedures designed to restore IT infrastructure, systems, and data following a disruptive event. While business continuity addresses the broad ability to maintain operations, disaster recovery focuses specifically on the technology layer — getting systems back online and data restored after an incident.",[44,5041,5043],{"id":5042},"what-are-the-key-disaster-recovery-concepts","What are the key disaster recovery concepts?",[37,5045,5046,5049],{},[52,5047,5048],{},"Recovery Time Objective (RTO)"," — the maximum acceptable amount of time that a system or application can be down after a disaster before the business impact becomes unacceptable. An RTO of 4 hours means the system must be restored within 4 hours.",[37,5051,5052,5055],{},[52,5053,5054],{},"Recovery Point Objective (RPO)"," — the maximum acceptable amount of data loss measured in time. An RPO of 1 hour means the organization can tolerate losing up to 1 hour of data, so backups must occur at least every hour.",[37,5057,5058,5061],{},[52,5059,5060],{},"Recovery Level Objective (RLO)"," — the minimum level of service or functionality that must be restored. Not all features of a system may need to be available immediately.",[44,5063,5065],{"id":5064},"what-are-common-disaster-recovery-strategies","What are common disaster recovery strategies?",[37,5067,5068],{},"DR strategies vary in cost, complexity, and recovery speed:",[92,5070,5071,5077,5083,5089],{},[95,5072,5073,5076],{},[52,5074,5075],{},"Backup and restore"," — the simplest approach: maintain regular backups and restore them to new or repaired infrastructure when needed. Lowest cost but highest RTO.",[95,5078,5079,5082],{},[52,5080,5081],{},"Pilot light"," — maintain a minimal version of the production environment in a secondary location that can be scaled up quickly during a disaster.",[95,5084,5085,5088],{},[52,5086,5087],{},"Warm standby"," — run a scaled-down but fully functional copy of the production environment that can be scaled to full capacity during failover.",[95,5090,5091,5094],{},[52,5092,5093],{},"Hot standby \u002F active-active"," — run full production environments in multiple locations simultaneously. Provides near-zero RTO but at the highest cost.",[37,5096,5097],{},"The right strategy depends on the business's RTO and RPO requirements and budget.",[44,5099,5101],{"id":5100},"what-are-the-components-of-a-disaster-recovery-plan","What are the components of a disaster recovery plan?",[37,5103,5104],{},"A comprehensive DR plan includes:",[92,5106,5107,5113,5119,5125,5131,5137,5143,5149],{},[95,5108,5109,5112],{},[52,5110,5111],{},"Scope"," — which systems and applications are covered",[95,5114,5115,5118],{},[52,5116,5117],{},"RTO and RPO targets"," — recovery objectives for each system",[95,5120,5121,5124],{},[52,5122,5123],{},"Roles and responsibilities"," — who is responsible for each aspect of recovery",[95,5126,5127,5130],{},[52,5128,5129],{},"Recovery procedures"," — step-by-step instructions for restoring each system",[95,5132,5133,5136],{},[52,5134,5135],{},"Communication plan"," — how to notify stakeholders during a disaster",[95,5138,5139,5142],{},[52,5140,5141],{},"Vendor contacts"," — contact information for infrastructure and service providers",[95,5144,5145,5148],{},[52,5146,5147],{},"Dependencies"," — system interdependencies that affect recovery sequence",[95,5150,5151,5154],{},[52,5152,5153],{},"Testing schedule"," — how and when the plan will be tested",[44,5156,5158],{"id":5157},"how-do-you-manage-backups-for-disaster-recovery","How do you manage backups for disaster recovery?",[37,5160,5161],{},"Backups are the foundation of disaster recovery. Best practices include:",[92,5163,5164,5170,5176,5182,5188,5194],{},[95,5165,5166,5169],{},[52,5167,5168],{},"3-2-1 rule"," — maintain 3 copies of data, on 2 different types of media, with 1 copy offsite",[95,5171,5172,5175],{},[52,5173,5174],{},"Automated backups"," — schedule backups to run automatically at intervals aligned with RPO",[95,5177,5178,5181],{},[52,5179,5180],{},"Encryption"," — encrypt backups to protect data at rest",[95,5183,5184,5187],{},[52,5185,5186],{},"Regular testing"," — periodically restore from backups to verify they work",[95,5189,5190,5193],{},[52,5191,5192],{},"Monitoring"," — monitor backup jobs for failures and address issues immediately",[95,5195,5196,5199],{},[52,5197,5198],{},"Immutable backups"," — protect backups from ransomware by using immutable storage",[44,5201,5203],{"id":5202},"how-do-compliance-frameworks-address-disaster-recovery","How do compliance frameworks address disaster recovery?",[92,5205,5206,5211,5216,5221],{},[95,5207,5208,5210],{},[52,5209,2728],{}," — control A.5.30 addresses ICT readiness for business continuity, including DR planning and testing",[95,5212,5213,5215],{},[52,5214,155],{}," — RC.RP (Recovery Planning) addresses establishing and testing recovery processes",[95,5217,5218,5220],{},[52,5219,3864],{}," — the Availability criterion covers system recovery capabilities",[95,5222,5223,5225],{},[52,5224,3899],{}," — while not explicitly requiring a DR plan, requirements around data protection and system availability support DR practices",[44,5227,5229],{"id":5228},"how-do-you-test-a-disaster-recovery-plan","How do you test a disaster recovery plan?",[37,5231,5232],{},"DR testing is essential and should include:",[92,5234,5235,5241,5247,5253],{},[95,5236,5237,5240],{},[52,5238,5239],{},"Backup restoration tests"," — regularly restore data from backups to verify integrity",[95,5242,5243,5246],{},[52,5244,5245],{},"Failover tests"," — practice switching to secondary systems",[95,5248,5249,5252],{},[52,5250,5251],{},"Full DR tests"," — simulate a complete disaster and execute the full recovery plan",[95,5254,5255,5258],{},[52,5256,5257],{},"Tabletop exercises"," — walk through DR scenarios with the team",[37,5260,5261],{},"Testing should occur at least annually, with backup restoration tests performed more frequently.",[44,5263,5265],{"id":5264},"how-does-episki-help-with-disaster-recovery","How does episki help with disaster recovery?",[37,5267,5268,5269,313],{},"episki tracks disaster recovery plans, backup schedules, test results, and recovery objectives. The platform sends reminders for DR testing, documents test outcomes, and maintains evidence for compliance auditors. Learn more on our ",[86,5270,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":5272},[5273],{"id":5035,"depth":437,"text":5036,"children":5274},[5275,5276,5277,5278,5279,5280,5281],{"id":5042,"depth":442,"text":5043},{"id":5064,"depth":442,"text":5065},{"id":5100,"depth":442,"text":5101},{"id":5157,"depth":442,"text":5158},{"id":5202,"depth":442,"text":5203},{"id":5228,"depth":442,"text":5229},{"id":5264,"depth":442,"text":5265},{},"\u002Fglossary\u002Fdisaster-recovery",[523,4258,2791],[5286,4792,5022,1414],"business-continuity",{"title":5288,"description":5289},"What is Disaster Recovery? Definition & Compliance Guide","Disaster recovery is the process of restoring IT systems and data after a disruption. Learn about DR planning, RTO, RPO, and compliance requirements.","disaster-recovery","8.glossary\u002Fdisaster-recovery","asnxcfYjct8iYic-NvOoNvliB3CqOtNwVc19GAVgxkw",{"id":5294,"title":5180,"body":5295,"description":436,"extension":467,"lastUpdated":925,"meta":5482,"navigation":505,"path":4206,"relatedFrameworks":5483,"relatedTerms":5484,"seo":5486,"slug":1414,"stem":5489,"term":5300,"__hash__":5490},"glossary\u002F8.glossary\u002Fencryption.md",{"type":29,"value":5296,"toc":5471},[5297,5301,5304,5308,5314,5320,5326,5330,5333,5336,5350,5354,5357,5359,5376,5380,5383,5415,5419,5441,5445,5462,5466],[32,5298,5300],{"id":5299},"what-is-encryption","What is Encryption?",[37,5302,5303],{},"Encryption is the process of converting readable data (plaintext) into an unreadable format (ciphertext) using a cryptographic algorithm and a key. Only authorized parties with the correct decryption key can convert the ciphertext back to plaintext. Encryption is one of the most important technical controls for protecting the confidentiality of sensitive data and is required by virtually every compliance framework.",[44,5305,5307],{"id":5306},"what-are-the-types-of-encryption","What are the types of encryption?",[37,5309,5310,5313],{},[52,5311,5312],{},"Symmetric encryption"," — uses the same key for both encryption and decryption. It is fast and efficient for large volumes of data. Common algorithms include AES-256 (the current standard) and AES-128.",[37,5315,5316,5319],{},[52,5317,5318],{},"Asymmetric encryption"," — uses a pair of keys: a public key for encryption and a private key for decryption. It is used for key exchange, digital signatures, and scenarios where parties cannot share a secret key in advance. Common algorithms include RSA and elliptic curve cryptography (ECC).",[37,5321,5322,5325],{},[52,5323,5324],{},"Hashing"," — technically not encryption (it is one-way and cannot be reversed), but often discussed alongside encryption. Hashing produces a fixed-length output from any input, used for password storage and data integrity verification. Common algorithms include SHA-256 and bcrypt.",[44,5327,5329],{"id":5328},"what-is-encryption-at-rest","What is encryption at rest?",[37,5331,5332],{},"Encryption at rest protects data stored in databases, file systems, backups, and storage media. If a storage device is stolen or improperly decommissioned, encryption prevents unauthorized access to the data.",[37,5334,5335],{},"Common implementations include:",[92,5337,5338,5341,5344,5347],{},[95,5339,5340],{},"Full disk encryption (BitLocker, FileVault, LUKS)",[95,5342,5343],{},"Database encryption (Transparent Data Encryption)",[95,5345,5346],{},"File-level encryption",[95,5348,5349],{},"Cloud storage encryption (most cloud providers offer encryption at rest by default)",[44,5351,5353],{"id":5352},"what-is-encryption-in-transit","What is encryption in transit?",[37,5355,5356],{},"Encryption in transit protects data as it moves between systems over networks. It prevents eavesdropping, man-in-the-middle attacks, and data interception.",[37,5358,5335],{},[92,5360,5361,5364,5367,5370,5373],{},[95,5362,5363],{},"TLS 1.2 or 1.3 for web traffic (HTTPS)",[95,5365,5366],{},"TLS for email (SMTP with STARTTLS)",[95,5368,5369],{},"VPN tunnels for site-to-site or remote access connections",[95,5371,5372],{},"SSH for administrative access",[95,5374,5375],{},"IPsec for network-level encryption",[44,5377,5379],{"id":5378},"how-does-key-management-support-encryption","How does key management support encryption?",[37,5381,5382],{},"Encryption is only as strong as its key management. Poor key management undermines the protection encryption provides. Key management best practices include:",[92,5384,5385,5391,5397,5403,5409],{},[95,5386,5387,5390],{},[52,5388,5389],{},"Key generation"," — use cryptographically secure random number generators",[95,5392,5393,5396],{},[52,5394,5395],{},"Key storage"," — store keys separately from the data they protect, using hardware security modules (HSMs) or key management services",[95,5398,5399,5402],{},[52,5400,5401],{},"Key rotation"," — rotate keys periodically to limit exposure if a key is compromised",[95,5404,5405,5408],{},[52,5406,5407],{},"Key access control"," — restrict key access to authorized personnel and systems",[95,5410,5411,5414],{},[52,5412,5413],{},"Key destruction"," — securely destroy keys when no longer needed",[44,5416,5418],{"id":5417},"what-are-the-encryption-requirements","What are the encryption requirements?",[92,5420,5421,5426,5431,5436],{},[95,5422,5423,5425],{},[52,5424,3864],{}," — CC6.1 and CC6.7 address protection of data through encryption and other mechanisms",[95,5427,5428,5430],{},[52,5429,2728],{}," — control A.8.24 addresses use of cryptography",[95,5432,5433,5435],{},[52,5434,3885],{}," — encryption is an addressable implementation specification for ePHI at rest (45 CFR 164.312(a)(2)(iv)) and a requirement for ePHI in transit (45 CFR 164.312(e)(1))",[95,5437,5438,5440],{},[52,5439,3899],{}," — Requirement 3 requires encryption of stored PAN, and Requirement 4 requires encryption of PAN in transit over open networks",[44,5442,5444],{"id":5443},"what-are-common-mistakes-with-encryption","What are common mistakes with encryption?",[92,5446,5447,5450,5453,5456,5459],{},[95,5448,5449],{},"Using outdated algorithms (DES, 3DES, RC4, SSL, TLS 1.0\u002F1.1)",[95,5451,5452],{},"Storing encryption keys alongside encrypted data",[95,5454,5455],{},"Failing to encrypt backups",[95,5457,5458],{},"Not encrypting data in transit within internal networks",[95,5460,5461],{},"Hardcoding keys in application source code",[44,5463,5465],{"id":5464},"how-does-episki-help-with-encryption","How does episki help with encryption?",[37,5467,5468,5469,313],{},"episki tracks your encryption implementations across systems, monitors certificate expirations, and documents encryption policies and key management practices for audit evidence. Learn more on our ",[86,5470,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":5472},[5473],{"id":5299,"depth":437,"text":5300,"children":5474},[5475,5476,5477,5478,5479,5480,5481],{"id":5306,"depth":442,"text":5307},{"id":5328,"depth":442,"text":5329},{"id":5352,"depth":442,"text":5353},{"id":5378,"depth":442,"text":5379},{"id":5417,"depth":442,"text":5418},{"id":5443,"depth":442,"text":5444},{"id":5464,"depth":442,"text":5465},{},[523,4257,4258,4259,4260],[5021,5020,5485,1413,1412],"tokenization",{"title":5487,"description":5488},"What is Encryption? Definition & Compliance Guide","Encryption transforms data into unreadable ciphertext to protect confidentiality. Learn about encryption at rest, in transit, and compliance requirements.","8.glossary\u002Fencryption","8HTAhzLPBjGJKnlguz6mBT1ob6J8h2KVZGzAJtWJEHM",{"id":5492,"title":5493,"body":5494,"description":436,"extension":467,"lastUpdated":925,"meta":5610,"navigation":505,"path":5611,"relatedFrameworks":5612,"relatedTerms":5613,"seo":5616,"slug":5619,"stem":5620,"term":5499,"__hash__":5621},"glossary\u002F8.glossary\u002Ffirewall.md","Firewall",{"type":29,"value":5495,"toc":5602},[5496,5500,5503,5507,5539,5543,5546,5568,5572,5593,5597],[32,5497,5499],{"id":5498},"what-is-a-firewall","What is a Firewall?",[37,5501,5502],{},"A firewall is a security system that monitors and controls network traffic based on predefined rules. It acts as a barrier between trusted internal networks and untrusted external ones, inspecting incoming and outgoing packets to enforce an organization's security policy.",[44,5504,5506],{"id":5505},"what-are-the-types-of-firewalls","What are the types of firewalls?",[92,5508,5509,5515,5521,5527,5533],{},[95,5510,5511,5514],{},[52,5512,5513],{},"Packet-filtering firewalls"," — inspect individual packets against a set of rules based on IP addresses, ports, and protocols. Simple and fast but limited in context.",[95,5516,5517,5520],{},[52,5518,5519],{},"Stateful inspection firewalls"," — track the state of active connections and make decisions based on the context of traffic, not just individual packets.",[95,5522,5523,5526],{},[52,5524,5525],{},"Next-generation firewalls (NGFW)"," — combine traditional firewall capabilities with intrusion prevention, application awareness, and deep packet inspection.",[95,5528,5529,5532],{},[52,5530,5531],{},"Web application firewalls (WAF)"," — specifically protect web applications by filtering and monitoring HTTP traffic between the application and the internet.",[95,5534,5535,5538],{},[52,5536,5537],{},"Cloud firewalls"," — delivered as a service to protect cloud-based infrastructure and applications.",[44,5540,5542],{"id":5541},"how-do-compliance-frameworks-address-firewalls","How do compliance frameworks address firewalls?",[37,5544,5545],{},"Firewalls are a foundational control across compliance standards:",[92,5547,5548,5553,5558,5563],{},[95,5549,5550,5552],{},[52,5551,3899],{}," — Requirement 1 mandates installing and maintaining firewall configurations to protect cardholder data.",[95,5554,5555,5557],{},[52,5556,2728],{}," — Network security controls (A.8.20, A.8.21) require network segmentation and filtering.",[95,5559,5560,5562],{},[52,5561,155],{}," — PR.AC and PR.PT cover network protection and access enforcement.",[95,5564,5565,5567],{},[52,5566,3864],{}," — CC6.6 requires restricting access through network security controls.",[44,5569,5571],{"id":5570},"what-are-best-practices-for-firewalls","What are best practices for firewalls?",[92,5573,5574,5577,5580,5583,5586],{},[95,5575,5576],{},"Define explicit allow and deny rules rather than relying on default configurations",[95,5578,5579],{},"Segment networks to limit lateral movement in the event of a breach",[95,5581,5582],{},"Review and update firewall rules regularly to remove stale or overly permissive entries",[95,5584,5585],{},"Log all firewall activity and monitor logs for anomalies",[95,5587,5588,5589],{},"Test firewall configurations as part of regular ",[86,5590,5592],{"href":5591},"\u002Fglossary\u002Fpenetration-testing","penetration testing",[44,5594,5596],{"id":5595},"how-does-episki-help-with-firewalls","How does episki help with firewalls?",[37,5598,5599,5600,313],{},"episki tracks firewall-related controls, links them to evidence like configuration exports and rule reviews, and sends reminders when periodic reviews are due. Learn more on our ",[86,5601,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":5603},[5604],{"id":5498,"depth":437,"text":5499,"children":5605},[5606,5607,5608,5609],{"id":5505,"depth":442,"text":5506},{"id":5541,"depth":442,"text":5542},{"id":5570,"depth":442,"text":5571},{"id":5595,"depth":442,"text":5596},{},"\u002Fglossary\u002Ffirewall",[523,4260,4258,2791],[1413,5614,5615],"network-security","penetration-testing",{"title":5617,"description":5618},"What is a Firewall? Definition & Compliance Guide","A firewall is a security system that monitors and controls network traffic based on predefined rules, acting as a barrier between trusted internal networks and untrusted external ones.","firewall","8.glossary\u002Ffirewall","d_tDCxyFul3bT18aYdQvTB0Erzn8iM00wNVDbeNQM1Y",{"id":5623,"title":2707,"body":5624,"description":436,"extension":467,"lastUpdated":925,"meta":5849,"navigation":505,"path":5850,"relatedFrameworks":5851,"relatedTerms":5852,"seo":5854,"slug":4792,"stem":5857,"term":5629,"__hash__":5858},"glossary\u002F8.glossary\u002Fincident-response.md",{"type":29,"value":5625,"toc":5839},[5626,5630,5633,5637,5640,5645,5665,5670,5687,5692,5709,5714,5731,5735,5738,5776,5780,5802,5806,5809,5813,5830,5834],[32,5627,5629],{"id":5628},"what-is-incident-response","What is Incident Response?",[37,5631,5632],{},"Incident response (IR) is the organized approach to detecting, managing, and recovering from security incidents such as data breaches, malware infections, unauthorized access, and denial-of-service attacks. An effective incident response program minimizes damage, reduces recovery time, and preserves evidence for investigation and compliance purposes.",[44,5634,5636],{"id":5635},"what-is-the-incident-response-lifecycle","What is the incident response lifecycle?",[37,5638,5639],{},"Most incident response programs follow the NIST SP 800-61 framework, which defines four phases:",[37,5641,5642],{},[52,5643,5644],{},"1. Preparation",[92,5646,5647,5650,5653,5656,5659,5662],{},[95,5648,5649],{},"Develop and document the incident response plan",[95,5651,5652],{},"Establish the incident response team and define roles",[95,5654,5655],{},"Deploy detection and monitoring tools",[95,5657,5658],{},"Conduct training and tabletop exercises",[95,5660,5661],{},"Establish communication channels and escalation procedures",[95,5663,5664],{},"Prepare forensic tools and evidence collection procedures",[37,5666,5667],{},[52,5668,5669],{},"2. Detection and analysis",[92,5671,5672,5675,5678,5681,5684],{},[95,5673,5674],{},"Monitor systems for indicators of compromise (IOCs)",[95,5676,5677],{},"Triage alerts to distinguish real incidents from false positives",[95,5679,5680],{},"Determine the scope, severity, and impact of the incident",[95,5682,5683],{},"Classify the incident (data breach, malware, unauthorized access, etc.)",[95,5685,5686],{},"Document findings and initial assessment",[37,5688,5689],{},[52,5690,5691],{},"3. Containment, eradication, and recovery",[92,5693,5694,5697,5700,5703,5706],{},[95,5695,5696],{},"Contain the incident to prevent further damage (short-term and long-term containment)",[95,5698,5699],{},"Eradicate the root cause (remove malware, close vulnerabilities, revoke compromised credentials)",[95,5701,5702],{},"Recover affected systems to normal operations",[95,5704,5705],{},"Verify that systems are clean and functioning properly",[95,5707,5708],{},"Monitor for signs of recurring activity",[37,5710,5711],{},[52,5712,5713],{},"4. Post-incident activity",[92,5715,5716,5719,5722,5725,5728],{},[95,5717,5718],{},"Conduct a lessons-learned review",[95,5720,5721],{},"Document the incident timeline, actions taken, and outcomes",[95,5723,5724],{},"Identify improvements to prevent similar incidents",[95,5726,5727],{},"Update the incident response plan based on lessons learned",[95,5729,5730],{},"Fulfill any regulatory notification requirements",[44,5732,5734],{"id":5733},"who-should-be-on-the-incident-response-team","Who should be on the incident response team?",[37,5736,5737],{},"An incident response team typically includes:",[92,5739,5740,5746,5752,5758,5764,5770],{},[95,5741,5742,5745],{},[52,5743,5744],{},"Incident commander"," — leads the response effort and makes key decisions",[95,5747,5748,5751],{},[52,5749,5750],{},"Security analysts"," — perform technical investigation and containment",[95,5753,5754,5757],{},[52,5755,5756],{},"IT operations"," — support system recovery and infrastructure changes",[95,5759,5760,5763],{},[52,5761,5762],{},"Legal counsel"," — advise on regulatory obligations and liability",[95,5765,5766,5769],{},[52,5767,5768],{},"Communications"," — manage internal and external communications",[95,5771,5772,5775],{},[52,5773,5774],{},"Executive sponsor"," — provides management authority and resources",[44,5777,5779],{"id":5778},"how-do-compliance-frameworks-address-incident-response","How do compliance frameworks address incident response?",[92,5781,5782,5787,5792,5797],{},[95,5783,5784,5786],{},[52,5785,3864],{}," — CC7.3 and CC7.4 require procedures for responding to identified security events and recovering from incidents",[95,5788,5789,5791],{},[52,5790,2728],{}," — controls A.5.24 through A.5.28 address incident management planning, assessment, response, and learning",[95,5793,5794,5796],{},[52,5795,3885],{}," — the Security Rule requires security incident procedures (45 CFR 164.308(a)(6)), and the Breach Notification Rule mandates notification following PHI breaches",[95,5798,5799,5801],{},[52,5800,155],{}," — the Respond function (RS) addresses response planning, communications, analysis, mitigation, and improvements",[44,5803,5805],{"id":5804},"what-is-an-incident-response-tabletop-exercise","What is an incident response tabletop exercise?",[37,5807,5808],{},"Regular tabletop exercises test the incident response plan in a low-pressure setting. The team walks through a hypothetical scenario, discussing decisions and actions at each stage. Tabletop exercises help identify gaps in the plan, clarify roles, and build team readiness without the stress of a real incident.",[44,5810,5812],{"id":5811},"what-are-common-pitfalls-with-incident-response","What are common pitfalls with incident response?",[92,5814,5815,5818,5821,5824,5827],{},[95,5816,5817],{},"No documented incident response plan",[95,5819,5820],{},"Team members unsure of their roles during an incident",[95,5822,5823],{},"Failure to preserve evidence for investigation",[95,5825,5826],{},"Delayed or incomplete regulatory notification",[95,5828,5829],{},"Not conducting post-incident reviews",[44,5831,5833],{"id":5832},"how-does-episki-help-with-incident-response","How does episki help with incident response?",[37,5835,5836,5837,313],{},"episki provides incident response plan templates, tracks tabletop exercises, and maintains documentation for compliance evidence. The platform includes breach notification workflows with timeline tracking to ensure regulatory deadlines are met. Learn more on our ",[86,5838,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":5840},[5841],{"id":5628,"depth":437,"text":5629,"children":5842},[5843,5844,5845,5846,5847,5848],{"id":5635,"depth":442,"text":5636},{"id":5733,"depth":442,"text":5734},{"id":5778,"depth":442,"text":5779},{"id":5804,"depth":442,"text":5805},{"id":5811,"depth":442,"text":5812},{"id":5832,"depth":442,"text":5833},{},"\u002Fglossary\u002Fincident-response",[523,4257,4258,4259,2791],[5853,4263,4793,5286,5290],"breach-notification",{"title":5855,"description":5856},"What is Incident Response? Definition & Compliance Guide","Incident response is the organized process of detecting, containing, and recovering from security incidents. Learn the phases, team roles, and compliance needs.","8.glossary\u002Fincident-response","3d1Zo1hC_y8Yl5qVJHyBrOH6lbXC5sqShRom8maKwxc",{"id":5860,"title":5861,"body":5862,"description":436,"extension":467,"lastUpdated":925,"meta":6389,"navigation":505,"path":6390,"relatedFrameworks":6391,"relatedTerms":6392,"seo":6393,"slug":6396,"stem":6397,"term":5867,"__hash__":6398},"glossary\u002F8.glossary\u002Fkey-management.md","Key Management",{"type":29,"value":5863,"toc":6377},[5864,5868,5871,5875,5913,5917,5920,5923,5949,5952,5956,5959,5964,5967,5993,6001,6004,6008,6011,6034,6037,6056,6059,6063,6066,6080,6083,6094,6100,6111,6115,6118,6212,6217,6244,6248,6251,6301,6305,6347,6351,6368,6372],[32,5865,5867],{"id":5866},"what-is-key-management","What is Key Management?",[37,5869,5870],{},"Key management is the process of creating, storing, distributing, rotating, and retiring cryptographic keys used to protect encrypted data. Effective key management ensures that encryption actually delivers the confidentiality and integrity it promises — poorly managed keys can render even strong encryption useless.",[44,5872,5874],{"id":5873},"what-are-the-stages-of-the-key-lifecycle","What are the stages of the key lifecycle?",[92,5876,5877,5883,5889,5895,5901,5907],{},[95,5878,5879,5882],{},[52,5880,5881],{},"Generation"," — creating keys using cryptographically secure methods with appropriate key lengths",[95,5884,5885,5888],{},[52,5886,5887],{},"Distribution"," — securely delivering keys to authorized systems or users",[95,5890,5891,5894],{},[52,5892,5893],{},"Storage"," — protecting keys at rest using hardware security modules (HSMs), key vaults, or other secure storage",[95,5896,5897,5900],{},[52,5898,5899],{},"Rotation"," — periodically replacing keys to limit the impact of a potential compromise",[95,5902,5903,5906],{},[52,5904,5905],{},"Revocation"," — disabling keys that are no longer trusted or have been compromised",[95,5908,5909,5912],{},[52,5910,5911],{},"Destruction"," — securely deleting keys that are no longer needed, ensuring they cannot be recovered",[44,5914,5916],{"id":5915},"why-does-key-management-matter-for-security","Why does key management matter for security?",[37,5918,5919],{},"Encryption is only as strong as the key management behind it. A 256-bit AES key offers no protection if it's stored in the same database as the data it encrypts — an attacker who compromises the database gets both the ciphertext and the key to decrypt it. This is not a theoretical concern; it's one of the most common encryption failures found in penetration tests and compliance assessments.",[37,5921,5922],{},"Key management failures create several categories of risk:",[92,5924,5925,5931,5937,5943],{},[95,5926,5927,5930],{},[52,5928,5929],{},"Exposure of historical data"," — Without regular key rotation, a single key compromise exposes every record encrypted with that key, potentially spanning years of sensitive data. Rotating keys limits the blast radius of any individual compromise.",[95,5932,5933,5936],{},[52,5934,5935],{},"Insider threats"," — If one administrator holds all key material with no split knowledge or dual control, that person can access every encrypted record in the organization. Proper key management distributes trust across multiple individuals.",[95,5938,5939,5942],{},[52,5940,5941],{},"Compliance failures"," — Auditors don't just check that encryption is enabled. They verify that keys are managed according to documented procedures, rotated on schedule, and protected with controls proportional to the sensitivity of the data they protect.",[95,5944,5945,5948],{},[52,5946,5947],{},"Incident response gaps"," — Organizations that lack documented key management procedures often cannot determine which data was exposed during a breach, which keys need emergency rotation, or how to restore encrypted backups after a key custodian leaves the company.",[37,5950,5951],{},"The bottom line: encryption without proper key management is security theater. It checks a box on a checklist without actually reducing risk. Organizations that invest in strong encryption algorithms but neglect key management are protecting data with a lock and then leaving the key under the doormat.",[44,5953,5955],{"id":5954},"what-are-common-key-management-architectures","What are common key management architectures?",[37,5957,5958],{},"There are three primary approaches to key management, each suited to different risk profiles, compliance requirements, and operational maturity levels. The right choice depends on what data you're protecting, which frameworks you're subject to, and how much operational complexity you can absorb.",[5960,5961,5963],"h4",{"id":5962},"cloud-kms","Cloud KMS",[37,5965,5966],{},"Cloud key management services — including AWS KMS, Azure Key Vault, and GCP Cloud KMS — are the most common starting point for organizations running workloads in the cloud. These services provide:",[92,5968,5969,5975,5981,5987],{},[95,5970,5971,5974],{},[52,5972,5973],{},"Envelope encryption"," — Data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a key encryption key (KEK) managed by the cloud provider. This limits the number of calls to the KMS while keeping the master key material protected.",[95,5976,5977,5980],{},[52,5978,5979],{},"Customer-managed keys (CMK)"," — You control key rotation schedules, access policies, and deletion. The cloud provider manages the underlying infrastructure but cannot use the key without your authorization.",[95,5982,5983,5986],{},[52,5984,5985],{},"Provider-managed keys"," — The cloud provider handles all key management automatically. Simpler to operate, but offers less control and may not satisfy compliance requirements that mandate customer-controlled keys.",[95,5988,5989,5992],{},[52,5990,5991],{},"Bring Your Own Key (BYOK)"," — You generate keys in your own environment (often an on-premises HSM) and import them into the cloud KMS. This satisfies requirements for key generation in a controlled environment while still leveraging cloud-native encryption integration.",[37,5994,5995,5996,731,5998,6000],{},"Cloud KMS is appropriate for most SaaS applications, internal systems, and workloads where the cloud provider is already part of the trust boundary. For organizations subject to ",[86,5997,3899],{"href":3898},[86,5999,3864],{"href":3863},", cloud KMS with customer-managed keys typically satisfies key management requirements when combined with proper access policies and rotation schedules.",[37,6002,6003],{},"Most cloud KMS services also provide detailed audit logs of every key operation, which simplifies compliance evidence collection during assessments.",[5960,6005,6007],{"id":6006},"hardware-security-modules-hsms","Hardware Security Modules (HSMs)",[37,6009,6010],{},"HSMs are dedicated hardware devices designed to generate, store, and manage cryptographic keys in a tamper-resistant environment. They are validated against FIPS 140-2 or FIPS 140-3 standards at various levels:",[92,6012,6013,6018,6023,6028],{},[95,6014,6015,6017],{},[52,6016,772],{}," — Basic security requirements, no physical tamper resistance",[95,6019,6020,6022],{},[52,6021,778],{}," — Tamper-evident coatings or seals, role-based authentication",[95,6024,6025,6027],{},[52,6026,784],{}," — Tamper-resistant with active response mechanisms (e.g., zeroization of keys upon detection of physical intrusion)",[95,6029,6030,6033],{},[52,6031,6032],{},"Level 4"," — Full physical security envelope with environmental failure protection",[37,6035,6036],{},"HSMs are required or strongly recommended in several contexts:",[92,6038,6039,6044,6050],{},[95,6040,6041,6043],{},[52,6042,3899],{}," — Strongly recommended for protecting cardholder data encryption keys, and effectively required for PIN-based transaction processing",[95,6045,6046,6049],{},[52,6047,6048],{},"Government and defense"," — CMMC, FedRAMP, and similar frameworks often require FIPS 140-2 Level 3 or higher for cryptographic key storage",[95,6051,6052,6055],{},[52,6053,6054],{},"Certificate authorities"," — Root and intermediate CA private keys must be stored in HSMs per industry standards",[37,6057,6058],{},"Cloud-based HSM options (AWS CloudHSM, Azure Dedicated HSM, GCP Cloud HSM) provide FIPS 140-2 Level 3 validated hardware in cloud data centers, bridging the gap between on-premises HSM security and cloud operational convenience.",[5960,6060,6062],{"id":6061},"software-based-key-stores","Software-based key stores",[37,6064,6065],{},"Software-based solutions like HashiCorp Vault, CyberArk Conjur, or application-level key management provide flexibility without dedicated hardware. These tools offer:",[92,6067,6068,6071,6074,6077],{},[95,6069,6070],{},"Centralized secret and key management across multiple applications and environments",[95,6072,6073],{},"Dynamic secrets that are generated on demand and automatically revoked after use",[95,6075,6076],{},"Audit logging of all key access and operations",[95,6078,6079],{},"Integration with identity providers for policy-based access control",[37,6081,6082],{},"Software key stores are appropriate when:",[92,6084,6085,6088,6091],{},[95,6086,6087],{},"Compliance requirements do not mandate HSMs",[95,6089,6090],{},"You need to manage secrets and keys across hybrid or multi-cloud environments",[95,6092,6093],{},"Your threat model does not include sophisticated physical or hardware-level attacks",[37,6095,6096,6097,6099],{},"They are ",[52,6098,1470],{}," appropriate when:",[92,6101,6102,6105,6108],{},[95,6103,6104],{},"Regulations explicitly require hardware-based key protection (e.g., PCI PIN security, certain government classifications)",[95,6106,6107],{},"Your risk assessment identifies nation-state or advanced persistent threats targeting cryptographic material",[95,6109,6110],{},"You need to provide cryptographic proof that keys have never been exposed to software",[44,6112,6114],{"id":6113},"what-are-the-key-management-requirements","What are the key management requirements?",[37,6116,6117],{},"Different compliance frameworks impose different key management requirements. Understanding these differences is critical when an organization is subject to multiple frameworks simultaneously — which is increasingly common. The following table provides a practical comparison across five major frameworks:",[1954,6119,6120,6136],{},[1957,6121,6122],{},[1960,6123,6124,6126,6128,6130,6132,6134],{},[1963,6125,4030],{},[1963,6127,3899],{},[1963,6129,2728],{},[1963,6131,3885],{},[1963,6133,3864],{},[1963,6135,504],{},[1970,6137,6138,6156,6175,6194],{},[1960,6139,6140,6143,6146,6149,6151,6153],{},[1975,6141,6142],{},"Documented key management procedures",[1975,6144,6145],{},"Req 3.6",[1975,6147,6148],{},"A.8.24",[1975,6150,4075],{},[1975,6152,4050],{},[1975,6154,6155],{},"SC.L2-3.13.10",[1960,6157,6158,6161,6164,6167,6170,6172],{},[1975,6159,6160],{},"Key rotation schedule",[1975,6162,6163],{},"Annual minimum",[1975,6165,6166],{},"Risk-based",[1975,6168,6169],{},"Not specified",[1975,6171,6166],{},[1975,6173,6174],{},"Per NIST 800-171",[1960,6176,6177,6180,6183,6186,6188,6191],{},[1975,6178,6179],{},"Split knowledge \u002F dual control",[1975,6181,6182],{},"Required for manual keys",[1975,6184,6185],{},"Recommended",[1975,6187,6169],{},[1975,6189,6190],{},"Expected",[1975,6192,6193],{},"Required",[1960,6195,6196,6199,6202,6204,6207,6209],{},[1975,6197,6198],{},"HSM or equivalent",[1975,6200,6201],{},"Strongly recommended",[1975,6203,6166],{},[1975,6205,6206],{},"Not required",[1975,6208,6166],{},[1975,6210,6211],{},"Varies by level",[37,6213,6214],{},[52,6215,6216],{},"Reading this table:",[92,6218,6219,6224,6229,6234,6239],{},[95,6220,6221,6223],{},[52,6222,3899],{}," is the most prescriptive. Requirement 3.6 specifies exactly what key management procedures must include, from key generation through destruction. Annual key rotation is a minimum baseline, and split knowledge\u002Fdual control is mandatory whenever keys are managed manually.",[95,6225,6226,6228],{},[52,6227,2728],{}," takes a risk-based approach. Annex A control A.8.24 requires a policy on the use of cryptographic controls including key management, but the specific controls depend on your risk assessment and Statement of Applicability.",[95,6230,6231,6233],{},[52,6232,3885],{}," is the least prescriptive on key management specifically. Encryption of ePHI is an \"addressable\" implementation specification, meaning organizations must implement it or document why an equivalent alternative is appropriate. Key management requirements follow from the encryption decision.",[95,6235,6236,6238],{},[52,6237,3864],{}," addresses key management through the Common Criteria, particularly CC6.1 (logical access) and CC6.7 (data transmission). The specific expectations depend on the trust services criteria in scope and the auditor's interpretation.",[95,6240,6241,6243],{},[52,6242,504],{}," references NIST SP 800-171 for key management requirements. At Level 2, control SC.L2-3.13.10 requires establishing and managing cryptographic keys when cryptography is employed. Higher levels add additional requirements.",[44,6245,6247],{"id":6246},"what-are-common-key-management-mistakes","What are common key management mistakes?",[37,6249,6250],{},"Even organizations with mature security programs make key management errors. These mistakes are found repeatedly in audit findings, penetration test reports, and breach post-mortems. The most frequent include:",[92,6252,6253,6259,6265,6271,6277,6283,6289,6295],{},[95,6254,6255,6258],{},[52,6256,6257],{},"Storing keys alongside encrypted data"," — Placing encryption keys in the same database, file system, or backup as the data they protect. If an attacker gains access to the data store, they get the keys too. Keys must be stored in a separate system with independent access controls.",[95,6260,6261,6264],{},[52,6262,6263],{},"Hardcoding keys in source code"," — Embedding encryption keys, API keys, or other secrets directly in application code. These keys end up in version control history, CI\u002FCD logs, and developer laptops. Use a secrets manager or environment variable injection instead.",[95,6266,6267,6270],{},[52,6268,6269],{},"No key rotation policy"," — Using the same encryption keys indefinitely. Without rotation, a single compromise exposes all data ever encrypted with that key. Define rotation schedules based on data sensitivity and framework requirements.",[95,6272,6273,6276],{},[52,6274,6275],{},"Single person with all key access"," — Concentrating key custody in one individual with no split knowledge or dual control. This creates both a security risk (insider threat) and an operational risk (key unavailability if that person is unreachable).",[95,6278,6279,6282],{},[52,6280,6281],{},"No documented recovery procedures"," — Failing to plan for key loss, corruption, or custodian departure. Organizations discover this gap during an incident, when they cannot decrypt backups or rotate compromised keys because the procedure was never written down or tested.",[95,6284,6285,6288],{},[52,6286,6287],{},"Using weak or predictable key generation"," — Generating keys with insufficient entropy, predictable seeds, or non-cryptographic random number generators. Always use cryptographically secure random number generators (CSPRNGs) and key lengths appropriate for the algorithm and data sensitivity.",[95,6290,6291,6294],{},[52,6292,6293],{},"Ignoring key state tracking"," — Not maintaining an inventory of which keys are active, retired, or compromised. Without a key inventory, organizations cannot answer basic questions during an audit or incident: how many keys exist, who has access, and when they were last rotated.",[95,6296,6297,6300],{},[52,6298,6299],{},"Failing to test key recovery"," — Having a documented recovery procedure that has never been exercised. Recovery procedures degrade over time as infrastructure changes, personnel rotate, and backup systems are modified. Regular testing is the only way to ensure recovery will work when it matters.",[44,6302,6304],{"id":6303},"how-do-compliance-frameworks-address-key-management","How do compliance frameworks address key management?",[92,6306,6307,6318,6327,6337],{},[95,6308,6309,6313,6314],{},[52,6310,6311],{},[86,6312,3899],{"href":3898}," — Requirement 3.5 and 3.6 detail specific key management procedures for protecting ",[86,6315,6317],{"href":6316},"\u002Fglossary\u002Fpan","cardholder data (PAN)",[95,6319,6320,3872,6324,6326],{},[52,6321,6322],{},[86,6323,2728],{"href":2727},[86,6325,3876],{"href":3875}," control A.8.24 covers the use of cryptography including key management policies",[95,6328,6329,6333,6334,6336],{},[52,6330,6331],{},[86,6332,3885],{"href":3884}," — the Security Rule requires ",[86,6335,1414],{"href":4206}," of ePHI, which implies proper key management",[95,6338,6339,6343,6344],{},[52,6340,6341],{},[86,6342,3864],{"href":3863}," — CC6.1 and CC6.7 address encryption and key management as part of logical ",[86,6345,6346],{"href":4255},"access controls",[44,6348,6350],{"id":6349},"what-are-best-practices-for-key-management","What are best practices for key management?",[92,6352,6353,6356,6359,6362,6365],{},[95,6354,6355],{},"Use hardware security modules (HSMs) or cloud key management services (AWS KMS, Azure Key Vault, GCP Cloud KMS) rather than storing keys in application code or configuration files",[95,6357,6358],{},"Enforce separation of duties so that key custodians cannot access the data those keys protect",[95,6360,6361],{},"Document key rotation schedules and automate rotation where possible",[95,6363,6364],{},"Maintain an inventory of all cryptographic keys, their owners, and their expiration dates",[95,6366,6367],{},"Test key recovery procedures regularly",[44,6369,6371],{"id":6370},"how-does-episki-help-with-key-management","How does episki help with key management?",[37,6373,6374,6375,313],{},"episki tracks key management policies, links them to encryption controls, and monitors rotation schedules to ensure cryptographic practices stay compliant. Learn more on our ",[86,6376,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":6378},[6379],{"id":5866,"depth":437,"text":5867,"children":6380},[6381,6382,6383,6384,6385,6386,6387,6388],{"id":5873,"depth":442,"text":5874},{"id":5915,"depth":442,"text":5916},{"id":5954,"depth":442,"text":5955},{"id":6113,"depth":442,"text":6114},{"id":6246,"depth":442,"text":6247},{"id":6303,"depth":442,"text":6304},{"id":6349,"depth":442,"text":6350},{"id":6370,"depth":442,"text":6371},{},"\u002Fglossary\u002Fkey-management",[523,4257,4258,4260,4259],[1414,1412,1413],{"title":6394,"description":6395},"Key Management: What It Is & Why Compliance Requires It","Key management covers creating, storing, rotating, and retiring cryptographic keys. Learn requirements across SOC 2, ISO 27001, HIPAA, and PCI DSS.","key-management","8.glossary\u002Fkey-management","1dvRJIXp6Ctc7SOVhg5O-XyVT22CTyhIb0o8RWTqqng",{"id":6400,"title":6401,"body":6402,"description":436,"extension":467,"lastUpdated":925,"meta":6516,"navigation":505,"path":6517,"relatedFrameworks":6518,"relatedTerms":6519,"seo":6521,"slug":6524,"stem":6525,"term":6407,"__hash__":6526},"glossary\u002F8.glossary\u002Fleast-privilege.md","Least Privilege",{"type":29,"value":6403,"toc":6508},[6404,6408,6411,6415,6418,6432,6436,6468,6472,6499,6503],[32,6405,6407],{"id":6406},"what-is-least-privilege","What is Least Privilege?",[37,6409,6410],{},"Least privilege is a security principle that limits user, application, and system access to only the resources and permissions necessary to perform a specific function — nothing more. By minimizing the access footprint, organizations reduce the potential damage from compromised accounts, insider threats, and accidental misuse.",[44,6412,6414],{"id":6413},"why-does-least-privilege-matter","Why does least privilege matter?",[37,6416,6417],{},"Excessive permissions are one of the most common security weaknesses. When users have more access than they need:",[92,6419,6420,6423,6426,6429],{},[95,6421,6422],{},"A compromised account gives attackers a wider attack surface",[95,6424,6425],{},"Accidental changes to sensitive systems become more likely",[95,6427,6428],{},"Insider threats are harder to detect and contain",[95,6430,6431],{},"Audit findings for excessive access are common compliance gaps",[44,6433,6435],{"id":6434},"how-do-you-implement-least-privilege","How do you implement least privilege?",[92,6437,6438,6444,6450,6456,6462],{},[95,6439,6440,6443],{},[52,6441,6442],{},"Start with zero access"," — new accounts should have no permissions by default, with access granted based on documented role requirements",[95,6445,6446,6449],{},[52,6447,6448],{},"Use role-based access control (RBAC)"," — define roles with specific permission sets rather than assigning permissions individually",[95,6451,6452,6455],{},[52,6453,6454],{},"Conduct regular access reviews"," — quarterly reviews of user permissions help identify and remove access that is no longer needed",[95,6457,6458,6461],{},[52,6459,6460],{},"Remove access promptly"," — revoke permissions immediately when employees change roles or leave the organization",[95,6463,6464,6467],{},[52,6465,6466],{},"Apply to systems and applications too"," — service accounts, APIs, and automated processes should also follow least privilege",[44,6469,6471],{"id":6470},"how-do-compliance-frameworks-address-least-privilege","How do compliance frameworks address least privilege?",[92,6473,6474,6479,6484,6489,6494],{},[95,6475,6476,6478],{},[52,6477,3864],{}," — CC6.1 through CC6.3 require logical access controls based on least privilege",[95,6480,6481,6483],{},[52,6482,2728],{}," — A.5.15 (access control) and A.8.2 (privileged access rights) explicitly reference least privilege",[95,6485,6486,6488],{},[52,6487,3885],{}," — the minimum necessary standard (45 CFR 164.502(b)) is the healthcare equivalent of least privilege",[95,6490,6491,6493],{},[52,6492,3899],{}," — Requirement 7 restricts access to cardholder data on a need-to-know basis",[95,6495,6496,6498],{},[52,6497,155],{}," — PR.AC-4 addresses access permissions based on least privilege",[44,6500,6502],{"id":6501},"how-does-episki-help-with-least-privilege","How does episki help with least privilege?",[37,6504,6505,6506,313],{},"episki tracks access control policies, schedules periodic access reviews, and documents evidence of least privilege enforcement for auditors. Learn more on our ",[86,6507,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":6509},[6510],{"id":6406,"depth":437,"text":6407,"children":6511},[6512,6513,6514,6515],{"id":6413,"depth":442,"text":6414},{"id":6434,"depth":442,"text":6435},{"id":6470,"depth":442,"text":6471},{"id":6501,"depth":442,"text":6502},{},"\u002Fglossary\u002Fleast-privilege",[523,4257,4258,4259,4260,2791],[1413,6520,4264],"job-separation",{"title":6522,"description":6523},"What is Least Privilege? Definition & Compliance Guide","Least privilege is a security principle that limits user access to only what they need to perform their job — nothing more.","least-privilege","8.glossary\u002Fleast-privilege","BuEghGm4HKbs1Es9DQ4mpHlellA4mL_s5KedD9Qs9_s",{"id":6528,"title":6529,"body":6530,"description":436,"extension":467,"lastUpdated":925,"meta":7047,"navigation":505,"path":7048,"relatedFrameworks":7049,"relatedTerms":7050,"seo":7051,"slug":7054,"stem":7055,"term":6535,"__hash__":7056},"glossary\u002F8.glossary\u002Flog-management.md","Log Management",{"type":29,"value":6531,"toc":7035},[6532,6536,6539,6543,6546,6584,6588,6591,6595,6598,6636,6640,6643,6675,6679,6682,6708,6712,6715,6741,6745,6748,6814,6817,6821,6824,6828,6842,6846,6860,6864,6878,6882,6896,6900,6923,6927,6930,6974,6978,7005,7009,7026,7030],[32,6533,6535],{"id":6534},"what-is-log-management","What is Log Management?",[37,6537,6538],{},"Log management is the process of collecting, storing, analyzing, and retaining system activity records to detect security incidents, troubleshoot issues, and support compliance audits. Logs provide a chronological record of events across servers, applications, network devices, and security tools.",[44,6540,6542],{"id":6541},"what-gets-logged-in-a-log-management-program","What gets logged in a log management program?",[37,6544,6545],{},"Effective log management covers:",[92,6547,6548,6554,6560,6566,6572,6578],{},[95,6549,6550,6553],{},[52,6551,6552],{},"Authentication events"," — successful and failed login attempts, password changes, MFA challenges",[95,6555,6556,6559],{},[52,6557,6558],{},"Authorization events"," — access grants, denials, privilege escalations",[95,6561,6562,6565],{},[52,6563,6564],{},"System events"," — configuration changes, service starts and stops, errors",[95,6567,6568,6571],{},[52,6569,6570],{},"Network events"," — firewall decisions, DNS queries, connection attempts",[95,6573,6574,6577],{},[52,6575,6576],{},"Application events"," — user actions, API calls, data access patterns",[95,6579,6580,6583],{},[52,6581,6582],{},"Security events"," — malware detections, vulnerability scan results, intrusion alerts",[44,6585,6587],{"id":6586},"what-is-log-management-architecture","What is log management architecture?",[37,6589,6590],{},"A mature log management program combines multiple components into a pipeline that moves raw event data from source to searchable, retained storage.",[5960,6592,6594],{"id":6593},"log-sources","Log sources",[37,6596,6597],{},"Logs originate from every layer of the technology stack:",[92,6599,6600,6606,6612,6618,6624,6630],{},[95,6601,6602,6605],{},[52,6603,6604],{},"Servers and operating systems"," — Linux auth logs, Windows Event Log, macOS Unified Log",[95,6607,6608,6611],{},[52,6609,6610],{},"Cloud platforms"," — AWS CloudTrail, Azure Activity Log, GCP Admin Activity audit logs",[95,6613,6614,6617],{},[52,6615,6616],{},"SaaS applications"," — Microsoft 365 Unified Audit Log, Google Workspace audit logs, Salesforce event monitoring",[95,6619,6620,6623],{},[52,6621,6622],{},"Endpoints"," — EDR telemetry, local application logs, mobile device management events",[95,6625,6626,6629],{},[52,6627,6628],{},"Network devices"," — firewalls, routers, switches, load balancers, VPN concentrators",[95,6631,6632,6635],{},[52,6633,6634],{},"Security tools"," — IDS\u002FIPS alerts, vulnerability scanners, DLP engines, email gateways",[5960,6637,6639],{"id":6638},"collection-methods","Collection methods",[37,6641,6642],{},"Getting logs from source to a central platform requires reliable collection mechanisms:",[92,6644,6645,6651,6657,6663,6669],{},[95,6646,6647,6650],{},[52,6648,6649],{},"Agents"," — lightweight forwarders installed on hosts (Fluentd, Filebeat, NXLog, Splunk Universal Forwarder) that ship logs in near real time",[95,6652,6653,6656],{},[52,6654,6655],{},"Syslog"," — the legacy standard (RFC 5424) still widely used by network devices; syslog-ng and rsyslog add filtering and reliable delivery",[95,6658,6659,6662],{},[52,6660,6661],{},"API polling"," — scheduled calls to SaaS and cloud provider APIs to pull audit logs (e.g., Microsoft Graph API, AWS CloudTrail Lake queries)",[95,6664,6665,6668],{},[52,6666,6667],{},"Cloud-native streams"," — managed pipelines like AWS Kinesis Data Firehose, Azure Event Hubs, or GCP Pub\u002FSub that deliver logs without managing agents",[95,6670,6671,6674],{},[52,6672,6673],{},"Webhooks"," — event-driven push from SaaS applications that support real-time notification (Slack audit API, GitHub audit log streaming)",[5960,6676,6678],{"id":6677},"centralization","Centralization",[37,6680,6681],{},"Logs are only useful when they are searchable in one place:",[92,6683,6684,6690,6696,6702],{},[95,6685,6686,6689],{},[52,6687,6688],{},"Commercial SIEM"," — Splunk Enterprise Security, Microsoft Sentinel, IBM QRadar provide correlation, detection rules, and case management",[95,6691,6692,6695],{},[52,6693,6694],{},"Cloud-native logging"," — AWS CloudWatch Logs, Azure Monitor, Google Cloud Logging offer tight integration with their respective platforms",[95,6697,6698,6701],{},[52,6699,6700],{},"Open-source stacks"," — the Elastic Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, and OpenSearch provide cost-effective alternatives with community-driven detection content",[95,6703,6704,6707],{},[52,6705,6706],{},"Security data lakes"," — Snowflake, Amazon Security Lake, and similar platforms store massive volumes at low cost using the Open Cybersecurity Schema Framework (OCSF) for normalization",[5960,6709,6711],{"id":6710},"storage-tiers","Storage tiers",[37,6713,6714],{},"Log storage strategies balance search speed against cost and compliance retention:",[92,6716,6717,6723,6729,6735],{},[95,6718,6719,6722],{},[52,6720,6721],{},"Hot storage"," — fully indexed, real-time searchable data for active investigations and alerting (typically 30–90 days)",[95,6724,6725,6728],{},[52,6726,6727],{},"Warm storage"," — recent history available for on-demand search with slightly slower query times (typically 90 days to 12 months)",[95,6730,6731,6734],{},[52,6732,6733],{},"Cold storage"," — compressed, archived logs in object storage (S3, Azure Blob, GCS) retained for compliance and forensic purposes (1–7 years depending on framework requirements)",[95,6736,6737,6740],{},[52,6738,6739],{},"Immutable storage"," — write-once, read-many storage that prevents tampering, critical for audit trail integrity and legal hold requirements",[44,6742,6744],{"id":6743},"what-are-the-log-retention-requirements","What are the log retention requirements?",[37,6746,6747],{},"Different compliance frameworks set varying expectations for how long logs must be kept. The table below summarizes key requirements:",[1954,6749,6750,6763],{},[1957,6751,6752],{},[1960,6753,6754,6757,6760],{},[1963,6755,6756],{},"Framework",[1963,6758,6759],{},"Minimum retention",[1963,6761,6762],{},"Key requirements",[1970,6764,6765,6775,6785,6794,6804],{},[1960,6766,6767,6769,6772],{},[1975,6768,3899],{},[1975,6770,6771],{},"12 months (3 months immediately available)",[1975,6773,6774],{},"Req 10.7 — retain audit trail history",[1960,6776,6777,6779,6782],{},[1975,6778,3864],{},[1975,6780,6781],{},"Based on risk assessment",[1975,6783,6784],{},"CC7.2 — monitor system components",[1960,6786,6787,6789,6791],{},[1975,6788,2728],{},[1975,6790,6781],{},[1975,6792,6793],{},"A.8.15 — log retention policy required",[1960,6795,6796,6798,6801],{},[1975,6797,3885],{},[1975,6799,6800],{},"6 years for policies; log retention not specified but implied",[1975,6802,6803],{},"Audit controls for ePHI access",[1960,6805,6806,6808,6811],{},[1975,6807,155],{},[1975,6809,6810],{},"Based on organizational needs",[1975,6812,6813],{},"DE.CM — continuous monitoring",[37,6815,6816],{},"Organizations subject to multiple frameworks should align retention to the most stringent requirement. For most companies handling payment card data alongside health information, a 12-month hot\u002Fwarm retention period with 6-year cold archival provides adequate coverage.",[44,6818,6820],{"id":6819},"what-should-you-alert-on-in-log-management","What should you alert on in log management?",[37,6822,6823],{},"Collecting logs without monitoring them defeats the purpose. Effective alerting focuses on high-fidelity signals across several categories:",[5960,6825,6827],{"id":6826},"authentication-anomalies","Authentication anomalies",[92,6829,6830,6833,6836,6839],{},[95,6831,6832],{},"Brute-force attempts — multiple failed logins against the same account within a short window",[95,6834,6835],{},"Impossible travel — successful logins from geographically distant locations within an implausible time frame",[95,6837,6838],{},"New device or location — first-time access from an unrecognized device, IP range, or country",[95,6840,6841],{},"Credential stuffing patterns — failed logins across many accounts from a small set of source IPs",[5960,6843,6845],{"id":6844},"privilege-escalation","Privilege escalation",[92,6847,6848,6851,6854,6857],{},[95,6849,6850],{},"Sudo or run-as usage outside of expected maintenance windows",[95,6852,6853],{},"Admin role assignments or membership changes in identity providers (Azure AD, Okta, Google Workspace)",[95,6855,6856],{},"Permission changes on sensitive resources — S3 bucket policies, database grants, file share ACLs",[95,6858,6859],{},"Service account creation or key generation",[5960,6861,6863],{"id":6862},"data-exfiltration-signals","Data exfiltration signals",[92,6865,6866,6869,6872,6875],{},[95,6867,6868],{},"Unusual download volumes — user downloading significantly more data than their baseline",[95,6870,6871],{},"Access outside business hours — especially to sensitive repositories, databases, or file shares",[95,6873,6874],{},"Mass file access — sequential reads across large numbers of records in short succession",[95,6876,6877],{},"Outbound data transfers to uncommon destinations — cloud storage services, personal email, file-sharing sites",[5960,6879,6881],{"id":6880},"configuration-changes","Configuration changes",[92,6883,6884,6887,6890,6893],{},[95,6885,6886],{},"Firewall rule modifications — new allow rules, disabled security groups, removed deny entries",[95,6888,6889],{},"Security group changes in cloud environments — opening ports, widening IP ranges",[95,6891,6892],{},"IAM policy changes — new inline policies, permission boundary modifications, role trust policy updates",[95,6894,6895],{},"DNS changes — new records, zone transfers, nameserver modifications",[5960,6897,6899],{"id":6898},"compliance-specific-events","Compliance-specific events",[92,6901,6902,6910,6917,6920],{},[95,6903,6904,6905,6909],{},"Access to ",[86,6906,6908],{"href":6907},"\u002Fglossary\u002Fpci-dss","cardholder data"," environments — any read, write, or copy operation",[95,6911,6912,6913,6916],{},"PHI access in ",[86,6914,3885],{"href":6915},"\u002Fglossary\u002Fhipaa","-regulated systems — views, exports, or modifications of protected health information",[95,6918,6919],{},"Encryption key operations — key creation, rotation, deletion, or export",[95,6921,6922],{},"Audit log access or modification attempts — anyone trying to read, delete, or alter the logs themselves",[44,6924,6926],{"id":6925},"what-are-common-log-management-mistakes","What are common log management mistakes?",[37,6928,6929],{},"Even organizations that invest in logging often fall into patterns that undermine the value of their program:",[358,6931,6932,6938,6944,6950,6956,6962,6968],{},[95,6933,6934,6937],{},[52,6935,6936],{},"Logging too much"," — capturing every debug-level event creates massive storage costs and drowns analysts in noise. Focus on security-relevant events and tune verbosity by source.",[95,6939,6940,6943],{},[52,6941,6942],{},"Logging too little"," — the opposite problem is equally dangerous. Missing authentication events, not capturing cloud control plane activity, or skipping DNS logs leaves blind spots that attackers exploit.",[95,6945,6946,6949],{},[52,6947,6948],{},"Not protecting log integrity"," — if an attacker can delete or modify logs, they can cover their tracks. Logs should be forwarded to a separate system with immutable storage, and access to log management platforms should be tightly controlled.",[95,6951,6952,6955],{},[52,6953,6954],{},"No correlation across sources"," — reviewing logs from individual systems in isolation misses the bigger picture. A failed VPN login followed by a successful cloud console login from the same IP tells a story that neither log tells alone.",[95,6957,6958,6961],{},[52,6959,6960],{},"Alert fatigue from untuned rules"," — deploying default SIEM detection rules without tuning them to the environment generates hundreds of false positives per day. Analysts stop investigating, and real incidents get buried.",[95,6963,6964,6967],{},[52,6965,6966],{},"Not testing log pipeline reliability"," — log collection silently fails more often than most teams realize. Agents crash, API tokens expire, syslog forwarding breaks after a network change. Regularly validate that expected log sources are still delivering data.",[95,6969,6970,6973],{},[52,6971,6972],{},"Ignoring time synchronization"," — logs from systems with drifting clocks are nearly impossible to correlate during incident response. Enforce NTP across all log sources and normalize timestamps to UTC.",[44,6975,6977],{"id":6976},"how-do-compliance-frameworks-address-log-management","How do compliance frameworks address log management?",[92,6979,6980,6985,6990,6995,7000],{},[95,6981,6982,6984],{},[52,6983,3864],{}," — CC7.1 through CC7.4 require monitoring, detection, and response capabilities that depend on logging",[95,6986,6987,6989],{},[52,6988,2728],{}," — A.8.15 (logging) and A.8.16 (monitoring activities) address log collection and analysis",[95,6991,6992,6994],{},[52,6993,3885],{}," — the Security Rule requires audit controls to record and examine activity in systems containing ePHI",[95,6996,6997,6999],{},[52,6998,3899],{}," — Requirement 10 mandates logging and monitoring all access to network resources and cardholder data",[95,7001,7002,7004],{},[52,7003,155],{}," — DE.CM (continuous monitoring) and DE.AE (anomaly detection) rely on log data",[44,7006,7008],{"id":7007},"what-are-best-practices-for-log-management","What are best practices for log management?",[92,7010,7011,7014,7017,7020,7023],{},[95,7012,7013],{},"Centralize logs in a SIEM or log aggregation platform for correlation and analysis",[95,7015,7016],{},"Set retention periods that meet both compliance requirements and operational needs (typically 90 days to one year)",[95,7018,7019],{},"Protect log integrity with immutable storage or tamper-evident mechanisms",[95,7021,7022],{},"Establish alerting rules for high-risk events like failed authentication spikes or unauthorized access attempts",[95,7024,7025],{},"Regularly review and tune logging to ensure coverage without excessive noise",[44,7027,7029],{"id":7028},"how-does-episki-help-with-log-management","How does episki help with log management?",[37,7031,7032,7033,313],{},"episki documents log management policies, tracks retention schedules, and links logging controls to evidence for audit readiness. Learn more on our ",[86,7034,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7036},[7037],{"id":6534,"depth":437,"text":6535,"children":7038},[7039,7040,7041,7042,7043,7044,7045,7046],{"id":6541,"depth":442,"text":6542},{"id":6586,"depth":442,"text":6587},{"id":6743,"depth":442,"text":6744},{"id":6819,"depth":442,"text":6820},{"id":6925,"depth":442,"text":6926},{"id":6976,"depth":442,"text":6977},{"id":7007,"depth":442,"text":7008},{"id":7028,"depth":442,"text":7029},{},"\u002Fglossary\u002Flog-management",[523,4257,4258,4259,4260,2791],[4263,4797,4792],{"title":7052,"description":7053},"What is Log Management? Definition & Compliance Guide","Log management is the process of collecting, storing, and analyzing system activity records to detect security incidents and support compliance audits.","log-management","8.glossary\u002Flog-management","B9IH1ixHXCqDKqAdQBwGDpwLFnfLwuxW5KyltQCbFmk",{"id":7058,"title":7059,"body":7060,"description":436,"extension":467,"lastUpdated":925,"meta":7178,"navigation":505,"path":7179,"relatedFrameworks":7180,"relatedTerms":7181,"seo":7182,"slug":7185,"stem":7186,"term":7065,"__hash__":7187},"glossary\u002F8.glossary\u002Fmalware.md","Malware",{"type":29,"value":7061,"toc":7170},[7062,7066,7069,7073,7111,7115,7137,7141,7161,7165],[32,7063,7065],{"id":7064},"what-is-malware","What is Malware?",[37,7067,7068],{},"Malware (malicious software) is any software intentionally designed to damage, disrupt, or gain unauthorized access to computer systems, networks, or data. Malware is one of the most persistent threats organizations face and a primary driver behind many compliance requirements for endpoint protection and monitoring.",[44,7070,7072],{"id":7071},"what-are-the-types-of-malware","What are the types of malware?",[92,7074,7075,7081,7087,7093,7099,7105],{},[95,7076,7077,7080],{},[52,7078,7079],{},"Viruses"," — attach to legitimate programs and spread when the infected program runs",[95,7082,7083,7086],{},[52,7084,7085],{},"Ransomware"," — encrypts data and demands payment for the decryption key",[95,7088,7089,7092],{},[52,7090,7091],{},"Trojans"," — disguise themselves as legitimate software to trick users into installation",[95,7094,7095,7098],{},[52,7096,7097],{},"Spyware"," — silently collects information about user activity and sends it to an attacker",[95,7100,7101,7104],{},[52,7102,7103],{},"Worms"," — self-replicate across networks without requiring user interaction",[95,7106,7107,7110],{},[52,7108,7109],{},"Rootkits"," — hide deep within the operating system to maintain persistent, undetected access",[44,7112,7114],{"id":7113},"how-do-compliance-frameworks-address-malware-protection","How do compliance frameworks address malware protection?",[92,7116,7117,7122,7127,7132],{},[95,7118,7119,7121],{},[52,7120,3864],{}," — CC6.8 requires controls to prevent and detect malicious software",[95,7123,7124,7126],{},[52,7125,2728],{}," — A.8.7 addresses protection against malware",[95,7128,7129,7131],{},[52,7130,3899],{}," — Requirement 5 mandates deploying anti-malware solutions on all commonly affected systems",[95,7133,7134,7136],{},[52,7135,155],{}," — DE.CM-4 specifically addresses malicious code detection",[44,7138,7140],{"id":7139},"what-are-common-malware-defense-strategies","What are common malware defense strategies?",[92,7142,7143,7146,7149,7152,7155,7158],{},[95,7144,7145],{},"Deploy endpoint detection and response (EDR) tools across all endpoints",[95,7147,7148],{},"Keep operating systems and applications patched and up to date",[95,7150,7151],{},"Implement email filtering to block phishing and malicious attachments",[95,7153,7154],{},"Restrict administrative privileges to reduce malware installation risk",[95,7156,7157],{},"Train employees to recognize social engineering and phishing attempts",[95,7159,7160],{},"Maintain tested backup and recovery procedures to mitigate ransomware impact",[44,7162,7164],{"id":7163},"how-does-episki-help-with-malware","How does episki help with malware?",[37,7166,7167,7168,313],{},"episki tracks anti-malware controls, monitors policy compliance, and documents endpoint protection evidence for auditors. Learn more on our ",[86,7169,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7171},[7172],{"id":7064,"depth":437,"text":7065,"children":7173},[7174,7175,7176,7177],{"id":7071,"depth":442,"text":7072},{"id":7113,"depth":442,"text":7114},{"id":7139,"depth":442,"text":7140},{"id":7163,"depth":442,"text":7164},{},"\u002Fglossary\u002Fmalware",[523,4257,4258,4260,2791],[4792,5615,4797],{"title":7183,"description":7184},"What is Malware? Definition & Compliance Guide","Malware is malicious software designed to damage, disrupt, or gain unauthorized access to systems. It includes viruses, ransomware, spyware, and trojans.","malware","8.glossary\u002Fmalware","YC-GrrHk9-an6NjJOaLQttw4tAbXovhasUaJzWZ9d-4",{"id":7189,"title":5192,"body":7190,"description":436,"extension":467,"lastUpdated":925,"meta":7299,"navigation":505,"path":7300,"relatedFrameworks":7301,"relatedTerms":7302,"seo":7303,"slug":7306,"stem":7307,"term":7195,"__hash__":7308},"glossary\u002F8.glossary\u002Fmonitoring.md",{"type":29,"value":7191,"toc":7291},[7192,7196,7199,7203,7235,7239,7261,7265,7282,7286],[32,7193,7195],{"id":7194},"what-is-monitoring","What is Monitoring?",[37,7197,7198],{},"Monitoring is the continuous observation of systems, networks, and controls to detect threats, unusual activity, or compliance gaps in real time. In a security and compliance context, monitoring goes beyond uptime checks — it encompasses the processes and tools that ensure an organization's security posture remains effective over time.",[44,7200,7202],{"id":7201},"what-are-the-types-of-monitoring","What are the types of monitoring?",[92,7204,7205,7211,7217,7223,7229],{},[95,7206,7207,7210],{},[52,7208,7209],{},"Security monitoring"," — detecting threats, intrusions, and malicious activity through SIEM tools, IDS\u002FIPS, and endpoint detection",[95,7212,7213,7216],{},[52,7214,7215],{},"Compliance monitoring"," — tracking whether controls are operating effectively and whether the organization remains aligned with framework requirements",[95,7218,7219,7222],{},[52,7220,7221],{},"Infrastructure monitoring"," — observing system health, performance, and availability across servers, networks, and cloud services",[95,7224,7225,7228],{},[52,7226,7227],{},"User activity monitoring"," — tracking user behavior to detect insider threats, policy violations, or compromised accounts",[95,7230,7231,7234],{},[52,7232,7233],{},"Vulnerability monitoring"," — continuously scanning for known vulnerabilities across the technology stack",[44,7236,7238],{"id":7237},"how-do-compliance-frameworks-address-monitoring","How do compliance frameworks address monitoring?",[92,7240,7241,7246,7251,7256],{},[95,7242,7243,7245],{},[52,7244,3864],{}," — CC7.1 requires the use of detection and monitoring activities to identify anomalies",[95,7247,7248,7250],{},[52,7249,2728],{}," — A.8.16 covers monitoring activities across networks and systems",[95,7252,7253,7255],{},[52,7254,3899],{}," — Requirement 10 and 11 address logging, monitoring, and regular security testing",[95,7257,7258,7260],{},[52,7259,155],{}," — the Detect function (DE.CM, DE.AE) is entirely focused on continuous monitoring and anomaly detection",[44,7262,7264],{"id":7263},"what-are-best-practices-for-monitoring","What are best practices for monitoring?",[92,7266,7267,7270,7273,7276,7279],{},[95,7268,7269],{},"Define clear thresholds and alerting rules to minimize alert fatigue",[95,7271,7272],{},"Centralize monitoring data for correlation across systems",[95,7274,7275],{},"Establish escalation procedures so alerts lead to timely investigation",[95,7277,7278],{},"Review and tune monitoring rules regularly as the environment changes",[95,7280,7281],{},"Document monitoring coverage and gaps as part of risk assessments",[44,7283,7285],{"id":7284},"how-does-episki-help-with-monitoring","How does episki help with monitoring?",[37,7287,7288,7289,313],{},"episki tracks monitoring controls, documents coverage, and links monitoring evidence to framework requirements for continuous audit readiness. Learn more on our ",[86,7290,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7292},[7293],{"id":7194,"depth":437,"text":7195,"children":7294},[7295,7296,7297,7298],{"id":7201,"depth":442,"text":7202},{"id":7237,"depth":442,"text":7238},{"id":7263,"depth":442,"text":7264},{"id":7284,"depth":442,"text":7285},{},"\u002Fglossary\u002Fmonitoring",[523,4257,4258,4260,2791],[4797,7054,4792],{"title":7304,"description":7305},"What is Monitoring? Definition & Compliance Guide","Monitoring is the continuous observation of systems and controls to detect threats, unusual activity, or compliance gaps in real time.","monitoring","8.glossary\u002Fmonitoring","QXZ4W_vuU7Y88VE8xwlReLlBVCa0cNFk0XPiqgd_4bc",{"id":7310,"title":7311,"body":7312,"description":436,"extension":467,"lastUpdated":925,"meta":7420,"navigation":505,"path":7421,"relatedFrameworks":7422,"relatedTerms":7423,"seo":7424,"slug":7427,"stem":7428,"term":7317,"__hash__":7429},"glossary\u002F8.glossary\u002Fmulti-factor-authentication.md","Multi Factor Authentication",{"type":29,"value":7313,"toc":7412},[7314,7318,7321,7325,7328,7348,7352,7355,7382,7386,7403,7407],[32,7315,7317],{"id":7316},"what-is-multi-factor-authentication","What is Multi-Factor Authentication?",[37,7319,7320],{},"Multi-Factor Authentication (MFA) is a security mechanism that requires users to verify their identity using two or more independent factors before gaining access to a system or application. By combining multiple factors, MFA significantly reduces the risk of unauthorized access even if one factor (such as a password) is compromised.",[44,7322,7324],{"id":7323},"what-are-the-authentication-factors-used-in-mfa","What are the authentication factors used in MFA?",[37,7326,7327],{},"MFA combines factors from different categories:",[92,7329,7330,7336,7342],{},[95,7331,7332,7335],{},[52,7333,7334],{},"Something you know"," — passwords, PINs, security questions",[95,7337,7338,7341],{},[52,7339,7340],{},"Something you have"," — mobile phones (SMS or authenticator apps), hardware tokens, smart cards",[95,7343,7344,7347],{},[52,7345,7346],{},"Something you are"," — biometrics such as fingerprints, facial recognition, or iris scans",[44,7349,7351],{"id":7350},"how-do-compliance-frameworks-address-mfa","How do compliance frameworks address MFA?",[37,7353,7354],{},"MFA is required or strongly recommended across all major frameworks:",[92,7356,7357,7362,7367,7372,7377],{},[95,7358,7359,7361],{},[52,7360,3864],{}," — CC6.1 requires multi-factor authentication for access to sensitive systems",[95,7363,7364,7366],{},[52,7365,2728],{}," — A.8.5 addresses secure authentication including multi-factor methods",[95,7368,7369,7371],{},[52,7370,3885],{}," — while not explicitly mandating MFA, the Security Rule requires access controls that effectively necessitate it for ePHI systems",[95,7373,7374,7376],{},[52,7375,3899],{}," — Requirement 8.3 mandates MFA for all remote access to the cardholder data environment",[95,7378,7379,7381],{},[52,7380,155],{}," — PR.AC-7 recommends multi-factor authentication as part of identity management",[44,7383,7385],{"id":7384},"what-are-implementation-best-practices","What are implementation best practices?",[92,7387,7388,7391,7394,7397,7400],{},[95,7389,7390],{},"Require MFA for all user accounts, not just administrators",[95,7392,7393],{},"Prefer authenticator apps or hardware tokens over SMS-based codes (which are vulnerable to SIM swapping)",[95,7395,7396],{},"Implement MFA on VPN, cloud console, email, and any system containing sensitive data",[95,7398,7399],{},"Provide backup recovery methods (recovery codes, backup devices) to prevent lockouts",[95,7401,7402],{},"Monitor and alert on MFA bypass attempts or disabled MFA",[44,7404,7406],{"id":7405},"how-does-episki-help-with-mfa","How does episki help with MFA?",[37,7408,7409,7410,313],{},"episki tracks MFA policies, monitors enforcement across systems, and documents MFA evidence for compliance audits. Learn more on our ",[86,7411,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7413},[7414],{"id":7316,"depth":437,"text":7317,"children":7415},[7416,7417,7418,7419],{"id":7323,"depth":442,"text":7324},{"id":7350,"depth":442,"text":7351},{"id":7384,"depth":442,"text":7385},{"id":7405,"depth":442,"text":7406},{},"\u002Fglossary\u002Fmulti-factor-authentication",[523,4257,4258,4259,4260,2791],[1413,6524,1414],{"title":7425,"description":7426},"What is Multi-Factor Authentication (MFA)? Definition & Compliance Guide","Multi-Factor Authentication (MFA) is a login method that requires users to verify their identity using two or more factors, such as a password plus a code sent to their phone.","multi-factor-authentication","8.glossary\u002Fmulti-factor-authentication","UJQZ8l9dqE7trtvjUWb1iVTulmNQa1j2-kVTUOaUB34",{"id":7431,"title":7432,"body":7433,"description":436,"extension":467,"lastUpdated":925,"meta":7554,"navigation":505,"path":7555,"relatedFrameworks":7556,"relatedTerms":7557,"seo":7558,"slug":5614,"stem":7561,"term":7438,"__hash__":7562},"glossary\u002F8.glossary\u002Fnetwork-security.md","Network Security",{"type":29,"value":7434,"toc":7546},[7435,7439,7442,7446,7484,7488,7510,7514,7537,7541],[32,7436,7438],{"id":7437},"what-is-network-security","What is Network Security?",[37,7440,7441],{},"Network security refers to the tools, policies, and practices used to protect the integrity, confidentiality, and availability of a computer network and its data. It encompasses both hardware and software technologies as well as the processes organizations use to prevent unauthorized access, misuse, and disruption of network resources.",[44,7443,7445],{"id":7444},"what-are-the-core-components-of-network-security","What are the core components of network security?",[92,7447,7448,7454,7460,7466,7472,7478],{},[95,7449,7450,7453],{},[52,7451,7452],{},"Firewalls"," — filter traffic between trusted and untrusted networks based on security rules",[95,7455,7456,7459],{},[52,7457,7458],{},"Intrusion detection and prevention systems (IDS\u002FIPS)"," — monitor network traffic for suspicious activity and can automatically block threats",[95,7461,7462,7465],{},[52,7463,7464],{},"Network segmentation"," — divides the network into isolated zones to contain breaches and limit lateral movement",[95,7467,7468,7471],{},[52,7469,7470],{},"Virtual private networks (VPN)"," — encrypt traffic between remote users and the corporate network",[95,7473,7474,7477],{},[52,7475,7476],{},"Network access control (NAC)"," — enforces policies about which devices and users can connect to the network",[95,7479,7480,7483],{},[52,7481,7482],{},"DNS security"," — protects against DNS-based attacks like spoofing and cache poisoning",[44,7485,7487],{"id":7486},"how-do-compliance-frameworks-address-network-security","How do compliance frameworks address network security?",[92,7489,7490,7495,7500,7505],{},[95,7491,7492,7494],{},[52,7493,3899],{}," — Requirements 1 and 2 address firewall configuration and secure network architecture",[95,7496,7497,7499],{},[52,7498,2728],{}," — A.8.20 (network security), A.8.21 (security of network services), and A.8.22 (segregation of networks)",[95,7501,7502,7504],{},[52,7503,3864],{}," — CC6.6 requires security controls for network boundaries",[95,7506,7507,7509],{},[52,7508,155],{}," — PR.AC and PR.PT cover network access control and protective technology",[44,7511,7513],{"id":7512},"what-are-best-practices-for-network-security","What are best practices for network security?",[92,7515,7516,7519,7522,7525,7528,7531],{},[95,7517,7518],{},"Implement defense in depth with multiple layers of network controls",[95,7520,7521],{},"Regularly scan for open ports and unnecessary services",[95,7523,7524],{},"Encrypt data in transit using TLS\u002FSSL",[95,7526,7527],{},"Monitor network traffic for anomalies and potential intrusions",[95,7529,7530],{},"Document network architecture and maintain up-to-date network diagrams",[95,7532,7533,7534,7536],{},"Conduct regular ",[86,7535,5592],{"href":5591}," to identify network vulnerabilities",[44,7538,7540],{"id":7539},"how-does-episki-help-with-network-security","How does episki help with network security?",[37,7542,7543,7544,313],{},"episki tracks network security controls, links them to framework requirements, and documents evidence like network diagrams and firewall reviews for auditors. Learn more on our ",[86,7545,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7547},[7548],{"id":7437,"depth":437,"text":7438,"children":7549},[7550,7551,7552,7553],{"id":7444,"depth":442,"text":7445},{"id":7486,"depth":442,"text":7487},{"id":7512,"depth":442,"text":7513},{"id":7539,"depth":442,"text":7540},{},"\u002Fglossary\u002Fnetwork-security",[523,4257,4258,4260,2791],[5619,1413,1414,5615],{"title":7559,"description":7560},"What is Network Security? Definition & Compliance Guide","Network security refers to the tools, policies, and practices used to protect the integrity and confidentiality of a computer network and its data.","8.glossary\u002Fnetwork-security","X-GwLwvpQPWv1-bV4i1pW3X_eNNKctzmhG2CWCYFOe8",{"id":7564,"title":7565,"body":7566,"description":436,"extension":467,"lastUpdated":925,"meta":7809,"navigation":505,"path":5591,"relatedFrameworks":7810,"relatedTerms":7811,"seo":7813,"slug":5615,"stem":7816,"term":7571,"__hash__":7817},"glossary\u002F8.glossary\u002Fpenetration-testing.md","Penetration Testing",{"type":29,"value":7567,"toc":7799},[7568,7572,7575,7579,7582,7587,7631,7636,7656,7660,7663,7713,7717,7720,7742,7746,7766,7770,7773,7790,7794],[32,7569,7571],{"id":7570},"what-is-penetration-testing","What is Penetration Testing?",[37,7573,7574],{},"Penetration testing (pen testing) is a controlled, simulated cyberattack conducted by security professionals to identify vulnerabilities and weaknesses in an organization's systems, networks, and applications before malicious actors can exploit them. Unlike automated vulnerability scanning, penetration testing involves manual techniques, creative thinking, and the ability to chain multiple findings together to demonstrate real-world attack scenarios.",[44,7576,7578],{"id":7577},"what-are-the-types-of-penetration-testing","What are the types of penetration testing?",[37,7580,7581],{},"Penetration tests are categorized by scope and approach:",[37,7583,7584],{},[52,7585,7586],{},"By target:",[92,7588,7589,7595,7601,7607,7613,7619,7625],{},[95,7590,7591,7594],{},[52,7592,7593],{},"External testing"," — targets internet-facing assets such as web applications, APIs, email servers, and firewalls",[95,7596,7597,7600],{},[52,7598,7599],{},"Internal testing"," — simulates an attacker who has gained access to the internal network",[95,7602,7603,7606],{},[52,7604,7605],{},"Web application testing"," — focuses specifically on web application vulnerabilities (injection, authentication flaws, etc.)",[95,7608,7609,7612],{},[52,7610,7611],{},"API testing"," — evaluates the security of application programming interfaces",[95,7614,7615,7618],{},[52,7616,7617],{},"Mobile application testing"," — assesses mobile apps for security weaknesses",[95,7620,7621,7624],{},[52,7622,7623],{},"Wireless testing"," — tests wireless network security",[95,7626,7627,7630],{},[52,7628,7629],{},"Social engineering"," — tests human vulnerabilities through phishing, pretexting, or physical access attempts",[37,7632,7633],{},[52,7634,7635],{},"By knowledge level:",[92,7637,7638,7644,7650],{},[95,7639,7640,7643],{},[52,7641,7642],{},"Black box"," — the tester has no prior knowledge of the target environment, simulating an external attacker",[95,7645,7646,7649],{},[52,7647,7648],{},"White box"," — the tester has full access to source code, architecture documentation, and credentials",[95,7651,7652,7655],{},[52,7653,7654],{},"Gray box"," — the tester has partial knowledge, such as user-level credentials or limited documentation",[44,7657,7659],{"id":7658},"what-is-the-penetration-testing-process","What is the penetration testing process?",[37,7661,7662],{},"A professional penetration test follows a structured methodology:",[358,7664,7665,7671,7677,7683,7689,7695,7701,7707],{},[95,7666,7667,7670],{},[52,7668,7669],{},"Scoping"," — define the targets, objectives, rules of engagement, and testing window",[95,7672,7673,7676],{},[52,7674,7675],{},"Reconnaissance"," — gather information about the target through passive and active techniques",[95,7678,7679,7682],{},[52,7680,7681],{},"Vulnerability identification"," — discover potential weaknesses using automated tools and manual analysis",[95,7684,7685,7688],{},[52,7686,7687],{},"Exploitation"," — attempt to exploit identified vulnerabilities to demonstrate real-world impact",[95,7690,7691,7694],{},[52,7692,7693],{},"Post-exploitation"," — if access is gained, assess how far an attacker could go (lateral movement, data access, privilege escalation)",[95,7696,7697,7700],{},[52,7698,7699],{},"Reporting"," — document all findings with severity ratings, evidence, and remediation recommendations",[95,7702,7703,7706],{},[52,7704,7705],{},"Remediation support"," — assist the organization in understanding and addressing findings",[95,7708,7709,7712],{},[52,7710,7711],{},"Retest"," — verify that remediation efforts have effectively addressed the vulnerabilities",[44,7714,7716],{"id":7715},"how-do-compliance-frameworks-address-penetration-testing","How do compliance frameworks address penetration testing?",[37,7718,7719],{},"Multiple frameworks require or recommend penetration testing:",[92,7721,7722,7727,7732,7737],{},[95,7723,7724,7726],{},[52,7725,3864],{}," — while not explicitly mandated, penetration testing supports CC7.1 (detection of vulnerabilities) and CC4.1 (monitoring)",[95,7728,7729,7731],{},[52,7730,3899],{}," — Requirement 11.4 requires annual penetration testing of the CDE, plus testing after significant changes",[95,7733,7734,7736],{},[52,7735,155],{}," — DE.CM (continuous monitoring) and ID.RA (risk assessment) are supported by penetration testing",[95,7738,7739,7741],{},[52,7740,2728],{}," — control A.8.8 addresses management of technical vulnerabilities, which penetration testing supports",[44,7743,7745],{"id":7744},"how-often-should-penetration-tests-be-performed","How often should penetration tests be performed?",[92,7747,7748,7754,7760],{},[95,7749,7750,7753],{},[52,7751,7752],{},"Annual testing"," is the minimum standard for most compliance frameworks",[95,7755,7756,7759],{},[52,7757,7758],{},"After significant changes"," — major infrastructure changes, application releases, or acquisitions should trigger additional testing",[95,7761,7762,7765],{},[52,7763,7764],{},"Continuous testing programs"," — some organizations implement bug bounty programs or periodic testing throughout the year",[44,7767,7769],{"id":7768},"how-do-you-select-a-penetration-testing-firm","How do you select a penetration testing firm?",[37,7771,7772],{},"When choosing a penetration testing provider:",[92,7774,7775,7778,7781,7784,7787],{},[95,7776,7777],{},"Look for relevant certifications (OSCP, OSCE, CREST, GPEN)",[95,7779,7780],{},"Request sample reports to evaluate reporting quality",[95,7782,7783],{},"Verify the firm carries appropriate insurance",[95,7785,7786],{},"Confirm experience with your technology stack and industry",[95,7788,7789],{},"Ensure clear rules of engagement and communication protocols",[44,7791,7793],{"id":7792},"how-does-episki-help-with-penetration-testing","How does episki help with penetration testing?",[37,7795,7796,7797,313],{},"episki tracks penetration testing schedules, stores reports, and manages remediation of identified findings. The platform links pen test results to compliance framework requirements and monitors remediation progress. Learn more on our ",[86,7798,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":7800},[7801],{"id":7570,"depth":437,"text":7571,"children":7802},[7803,7804,7805,7806,7807,7808],{"id":7577,"depth":442,"text":7578},{"id":7658,"depth":442,"text":7659},{"id":7715,"depth":442,"text":7716},{"id":7744,"depth":442,"text":7745},{"id":7768,"depth":442,"text":7769},{"id":7792,"depth":442,"text":7793},{},[523,4257,4260,2791],[7812,4793,4797,1413],"asv",{"title":7814,"description":7815},"What is Penetration Testing? Definition & Compliance Guide","Penetration testing is a simulated cyberattack that identifies vulnerabilities in your systems before real attackers can exploit them. Learn the types and process.","8.glossary\u002Fpenetration-testing","-DYPrBzNiyBknfyn7jeCgBrDE39XjynFvEKprLlba4U",{"id":7819,"title":7820,"body":7821,"description":436,"extension":467,"lastUpdated":925,"meta":8424,"navigation":505,"path":8425,"relatedFrameworks":8426,"relatedTerms":8427,"seo":8429,"slug":5022,"stem":8432,"term":7826,"__hash__":8433},"glossary\u002F8.glossary\u002Frisk-register.md","Risk Register",{"type":29,"value":7822,"toc":8409},[7823,7827,7830,7834,7837,7911,7915,7918,7968,7972,7975,8007,8011,8014,8020,8026,8032,8039,8043,8046,8133,8136,8140,8148,8174,8177,8181,8184,8220,8224,8227,8330,8333,8337,8340,8370,8374,8377,8397,8400,8404],[32,7824,7826],{"id":7825},"what-is-a-risk-register","What is a Risk Register?",[37,7828,7829],{},"A risk register is a centralized document or tool that records identified risks, their assessment (likelihood and impact), assigned treatments, owners, and current status. It serves as the foundation of an organization's risk management program and is a key artifact required by frameworks including ISO 27001, SOC 2, and NIST CSF.",[44,7831,7833],{"id":7832},"what-does-a-risk-register-contain","What does a risk register contain?",[37,7835,7836],{},"A well-structured risk register typically includes the following fields for each risk:",[92,7838,7839,7845,7851,7857,7863,7869,7875,7881,7887,7893,7899,7905],{},[95,7840,7841,7844],{},[52,7842,7843],{},"Risk ID"," — a unique identifier for tracking",[95,7846,7847,7850],{},[52,7848,7849],{},"Risk description"," — a clear statement of the risk, typically describing the threat, vulnerability, and potential impact",[95,7852,7853,7856],{},[52,7854,7855],{},"Risk category"," — classification such as operational, technical, compliance, strategic, or third-party",[95,7858,7859,7862],{},[52,7860,7861],{},"Likelihood"," — the probability of the risk materializing (often rated on a scale such as 1-5 or low\u002Fmedium\u002Fhigh)",[95,7864,7865,7868],{},[52,7866,7867],{},"Impact"," — the potential consequence if the risk materializes (rated similarly)",[95,7870,7871,7874],{},[52,7872,7873],{},"Risk score"," — calculated from likelihood and impact (e.g., likelihood x impact)",[95,7876,7877,7880],{},[52,7878,7879],{},"Risk owner"," — the person accountable for managing the risk",[95,7882,7883,7886],{},[52,7884,7885],{},"Treatment option"," — mitigate, accept, transfer, or avoid",[95,7888,7889,7892],{},[52,7890,7891],{},"Controls"," — the specific controls implemented to address the risk",[95,7894,7895,7898],{},[52,7896,7897],{},"Residual risk"," — the remaining risk level after treatment is applied",[95,7900,7901,7904],{},[52,7902,7903],{},"Status"," — current state (open, in treatment, accepted, closed)",[95,7906,7907,7910],{},[52,7908,7909],{},"Review date"," — when the risk was last reviewed or when the next review is due",[44,7912,7914],{"id":7913},"how-do-you-build-a-risk-register","How do you build a risk register?",[37,7916,7917],{},"Creating a risk register follows a systematic process:",[358,7919,7920,7926,7932,7938,7944,7950,7956,7962],{},[95,7921,7922,7925],{},[52,7923,7924],{},"Identify risks"," — gather risks through workshops, interviews, threat modeling, vulnerability assessments, incident reviews, and industry threat intelligence",[95,7927,7928,7931],{},[52,7929,7930],{},"Assess each risk"," — evaluate the likelihood and impact of each risk to determine its severity",[95,7933,7934,7937],{},[52,7935,7936],{},"Prioritize"," — rank risks by their risk score to focus attention and resources on the most significant threats",[95,7939,7940,7943],{},[52,7941,7942],{},"Assign ownership"," — designate a responsible owner for each risk",[95,7945,7946,7949],{},[52,7947,7948],{},"Determine treatment"," — decide how each risk will be handled",[95,7951,7952,7955],{},[52,7953,7954],{},"Document controls"," — record the specific controls that address each risk",[95,7957,7958,7961],{},[52,7959,7960],{},"Calculate residual risk"," — assess the remaining risk after controls are applied",[95,7963,7964,7967],{},[52,7965,7966],{},"Review and approve"," — have management review and approve the register",[44,7969,7971],{"id":7970},"how-do-you-maintain-the-risk-register","How do you maintain the risk register?",[37,7973,7974],{},"A risk register is only valuable if it is kept current. Regular maintenance includes:",[92,7976,7977,7983,7989,7995,8001],{},[95,7978,7979,7982],{},[52,7980,7981],{},"Periodic reviews"," — review the full register at least quarterly, with management review at least annually",[95,7984,7985,7988],{},[52,7986,7987],{},"Triggered updates"," — update the register when significant changes occur (new systems, new services, organizational changes, incidents)",[95,7990,7991,7994],{},[52,7992,7993],{},"New risk identification"," — continuously identify and add new risks as the threat landscape evolves",[95,7996,7997,8000],{},[52,7998,7999],{},"Treatment progress tracking"," — monitor and update the status of risk treatment activities",[95,8002,8003,8006],{},[52,8004,8005],{},"Residual risk reassessment"," — re-evaluate residual risk as controls are implemented or change",[44,8008,8010],{"id":8009},"what-are-common-risk-scoring-methodologies","What are common risk scoring methodologies?",[37,8012,8013],{},"How you score risks determines how actionable the register is. The most common approaches:",[37,8015,8016,8019],{},[52,8017,8018],{},"Qualitative (low\u002Fmedium\u002Fhigh)"," — Fast and intuitive, useful for getting started or communicating with non-technical stakeholders. The downside is limited precision; everything tends to collect in the middle.",[37,8021,8022,8025],{},[52,8023,8024],{},"Semi-quantitative (1–5 scales)"," — A 5×5 matrix with likelihood and impact each rated 1 through 5 produces a 1–25 risk score. This is the most widely used approach because it balances simplicity with discrimination.",[37,8027,8028,8031],{},[52,8029,8030],{},"Quantitative (dollar-based)"," — Approaches like FAIR (Factor Analysis of Information Risk) estimate Annual Loss Expectancy in dollars. This is the gold standard for board reporting but requires more mature data and analyst time.",[37,8033,8034,8035,8038],{},"Most compliance programs start with a 5×5 matrix, then introduce quantitative methods for top-tier risks. Whichever scale you choose, ",[52,8036,8037],{},"document the definitions"," — what does \"likelihood 4\" actually mean in your organization? Without clear definitions, different raters produce wildly different scores.",[44,8040,8042],{"id":8041},"how-do-compliance-frameworks-address-risk-register","How do compliance frameworks address risk register?",[37,8044,8045],{},"Different frameworks require or recommend risk registers, often with specific expectations:",[1954,8047,8048,8059],{},[1957,8049,8050],{},[1960,8051,8052,8054,8056],{},[1963,8053,6756],{},[1963,8055,4030],{},[1963,8057,8058],{},"Specific reference",[1970,8060,8061,8073,8085,8097,8109,8121],{},[1960,8062,8063,8067,8070],{},[1975,8064,8065],{},[52,8066,2728],{},[1975,8068,8069],{},"Documented risk assessment process with register as artifact",[1975,8071,8072],{},"Clause 6.1.2 and 8.2",[1960,8074,8075,8079,8082],{},[1975,8076,8077],{},[52,8078,3864],{},[1975,8080,8081],{},"Risk identification, assessment, and response",[1975,8083,8084],{},"CC3.1–CC3.4",[1960,8086,8087,8091,8094],{},[1975,8088,8089],{},[52,8090,155],{},[1975,8092,8093],{},"Risk assessment and risk management strategy",[1975,8095,8096],{},"ID.RA and GV.RM (new in 2.0)",[1960,8098,8099,8103,8106],{},[1975,8100,8101],{},[52,8102,3885],{},[1975,8104,8105],{},"Risk analysis for ePHI",[1975,8107,8108],{},"§164.308(a)(1)(ii)(A)",[1960,8110,8111,8115,8118],{},[1975,8112,8113],{},[52,8114,3899],{},[1975,8116,8117],{},"Targeted risk analyses for specific requirements",[1975,8119,8120],{},"PCI DSS v4.0 Req 12.3.1",[1960,8122,8123,8127,8130],{},[1975,8124,8125],{},[52,8126,504],{},[1975,8128,8129],{},"Risk management practices",[1975,8131,8132],{},"RA.L2-3.11.1 through 3.11.3",[37,8134,8135],{},"Auditors typically look for: documented scoring criteria, evidence of regular review cadence, treatment decisions tied to each risk, and linkage between risks and controls. A register without review dates, owner signatures, or treatment tracking will draw findings even if the risks themselves are well-identified.",[44,8137,8139],{"id":8138},"what-are-the-risk-treatment-options","What are the risk treatment options?",[37,8141,8142,8143,8147],{},"For each risk, pick one of four treatment strategies (often documented in a parallel ",[86,8144,8146],{"href":8145},"\u002Fglossary\u002Frisk-treatment-plan","risk treatment plan","):",[92,8149,8150,8156,8162,8168],{},[95,8151,8152,8155],{},[52,8153,8154],{},"Mitigate"," — implement controls to reduce likelihood or impact. Most common choice. Example: deploy MFA to reduce account takeover likelihood.",[95,8157,8158,8161],{},[52,8159,8160],{},"Accept"," — acknowledge the risk as within tolerance and proceed. Requires documented rationale and, for significant risks, executive sign-off.",[95,8163,8164,8167],{},[52,8165,8166],{},"Transfer"," — shift the risk to a third party via insurance, contract, or outsourcing. Cyber insurance is the canonical example.",[95,8169,8170,8173],{},[52,8171,8172],{},"Avoid"," — eliminate the activity causing the risk. Example: decide not to launch a feature in a high-risk jurisdiction.",[37,8175,8176],{},"Residual risk — the risk remaining after treatment — must be reassessed and either accepted or subjected to additional treatment. Chained mitigation (stacking controls) is a legitimate strategy for high-severity risks.",[44,8178,8180],{"id":8179},"how-do-you-connect-the-risk-register-to-operational-workflows","How do you connect the risk register to operational workflows?",[37,8182,8183],{},"A risk register that lives in isolation quickly goes stale. High-performing programs integrate it with:",[92,8185,8186,8195,8202,8208,8214],{},[95,8187,8188,8194],{},[52,8189,8190],{},[86,8191,8193],{"href":8192},"\u002Fglossary\u002Fvendor-risk-management","Vendor risk management"," — third-party risks from vendor assessments feed into the enterprise register",[95,8196,8197,8201],{},[52,8198,8199],{},[86,8200,4843],{"href":5850}," — post-incident reviews identify new risks or update likelihood scores for known ones",[95,8203,8204,8207],{},[52,8205,8206],{},"Change management"," — significant system or business changes trigger a register update before deployment",[95,8209,8210,8213],{},[52,8211,8212],{},"Policy reviews"," — annual policy reviews check whether controls still address the risks they were designed for",[95,8215,8216,8219],{},[52,8217,8218],{},"Board reporting"," — top-tier risks roll up into executive dashboards showing trends, treatment progress, and heat maps",[44,8221,8223],{"id":8222},"what-does-an-example-risk-register-entry-look-like","What does an example risk register entry look like?",[37,8225,8226],{},"A concrete example makes the structure tangible. Consider a risk identified during an ISO 27001 internal audit:",[1954,8228,8229,8239],{},[1957,8230,8231],{},[1960,8232,8233,8236],{},[1963,8234,8235],{},"Field",[1963,8237,8238],{},"Value",[1970,8240,8241,8248,8256,8264,8271,8278,8286,8294,8301,8308,8316,8323],{},[1960,8242,8243,8245],{},[1975,8244,7843],{},[1975,8246,8247],{},"R-042",[1960,8249,8250,8253],{},[1975,8251,8252],{},"Description",[1975,8254,8255],{},"Unencrypted customer PII in database backups stored in S3",[1960,8257,8258,8261],{},[1975,8259,8260],{},"Category",[1975,8262,8263],{},"Data protection \u002F technical",[1960,8265,8266,8268],{},[1975,8267,7861],{},[1975,8269,8270],{},"3 (possible — we have access logs but no automated detection)",[1960,8272,8273,8275],{},[1975,8274,7867],{},[1975,8276,8277],{},"5 (severe — regulatory exposure under GDPR and state privacy laws)",[1960,8279,8280,8283],{},[1975,8281,8282],{},"Inherent score",[1975,8284,8285],{},"15 (high)",[1960,8287,8288,8291],{},[1975,8289,8290],{},"Owner",[1975,8292,8293],{},"CISO",[1960,8295,8296,8299],{},[1975,8297,8298],{},"Treatment",[1975,8300,8154],{},[1960,8302,8303,8305],{},[1975,8304,7891],{},[1975,8306,8307],{},"Enable S3 server-side encryption with KMS; rotate existing backups; add Macie scan",[1960,8309,8310,8313],{},[1975,8311,8312],{},"Residual score",[1975,8314,8315],{},"4 (low — automated encryption + detection materially reduces both)",[1960,8317,8318,8320],{},[1975,8319,7903],{},[1975,8321,8322],{},"In treatment — 60% complete",[1960,8324,8325,8327],{},[1975,8326,7909],{},[1975,8328,8329],{},"2026-06-01 (quarterly cadence)",[37,8331,8332],{},"This level of detail turns the register into a practical management tool rather than a compliance artifact.",[44,8334,8336],{"id":8335},"what-are-common-pitfalls-with-a-risk-register","What are common pitfalls with a risk register?",[37,8338,8339],{},"Organizations often struggle with risk registers due to:",[92,8341,8342,8345,8348,8351,8354,8357,8364,8367],{},[95,8343,8344],{},"Making the register too complex or too simple",[95,8346,8347],{},"Failing to review and update regularly",[95,8349,8350],{},"Not assigning clear ownership or clear treatment deadlines",[95,8352,8353],{},"Rating all risks as \"high\" without meaningful differentiation",[95,8355,8356],{},"Treating the register as a compliance checkbox rather than a management tool",[95,8358,8359,8360,8363],{},"Disconnecting the register from ",[86,8361,8362],{"href":5850},"incident response"," and vendor management workflows",[95,8365,8366],{},"Keeping risks open indefinitely without closure criteria or residual risk acceptance",[95,8368,8369],{},"Not versioning the register, making it impossible to demonstrate historical decisions to auditors",[44,8371,8373],{"id":8372},"what-risk-register-tools-and-templates-are-available","What risk register tools and templates are available?",[37,8375,8376],{},"Organizations use a range of tools to maintain a register:",[92,8378,8379,8385,8391],{},[95,8380,8381,8384],{},[52,8382,8383],{},"Spreadsheets"," — acceptable for small teams or early-stage programs. The limitation is that spreadsheets do not track version history, send review reminders, or link risks to other artifacts cleanly.",[95,8386,8387,8390],{},[52,8388,8389],{},"GRC platforms"," — purpose-built tools (including episki) handle scoring, ownership, treatment workflows, and evidence links out of the box.",[95,8392,8393,8396],{},[52,8394,8395],{},"Issue trackers"," — some teams use Jira or Linear to track risks as tickets. This works for operational visibility but typically lacks the scoring and reporting structure auditors expect.",[37,8398,8399],{},"Whatever tool you choose, exportability matters: auditors frequently ask for point-in-time snapshots, and regulators may request historical registers during an investigation.",[44,8401,8403],{"id":8402},"how-does-episki-help-with-a-risk-register","How does episki help with a risk register?",[37,8405,8406,8407,313],{},"episki provides a built-in risk register with configurable likelihood and impact scales, automatic risk scoring, owner assignment, treatment tracking, and review scheduling. The platform links risks to controls and evidence, creating a complete chain from risk identification through treatment. Learn more on our ",[86,8408,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":8410},[8411],{"id":7825,"depth":437,"text":7826,"children":8412},[8413,8414,8415,8416,8417,8418,8419,8420,8421,8422,8423],{"id":7832,"depth":442,"text":7833},{"id":7913,"depth":442,"text":7914},{"id":7970,"depth":442,"text":7971},{"id":8009,"depth":442,"text":8010},{"id":8041,"depth":442,"text":8042},{"id":8138,"depth":442,"text":8139},{"id":8179,"depth":442,"text":8180},{"id":8222,"depth":442,"text":8223},{"id":8335,"depth":442,"text":8336},{"id":8372,"depth":442,"text":8373},{"id":8402,"depth":442,"text":8403},{},"\u002Fglossary\u002Frisk-register",[523,4258,2791,4257],[8428,4793,1742,3418],"risk-treatment-plan",{"title":8430,"description":8431},"What is a Risk Register? Definition & Compliance Guide","A risk register is a centralized document that records identified risks, their likelihood, impact, treatment, and ownership. Learn how to build and maintain one.","8.glossary\u002Frisk-register","NLvIZTF-yfLLX2ce3ayhQVoNPH15hEMUk7pCSPoO3Ro",{"id":8435,"title":8436,"body":8437,"description":436,"extension":467,"lastUpdated":925,"meta":8660,"navigation":505,"path":8661,"relatedFrameworks":8662,"relatedTerms":8663,"seo":8664,"slug":8667,"stem":8668,"term":8442,"__hash__":8669},"glossary\u002F8.glossary\u002Fsecurity-awareness-training.md","Security Awareness Training",{"type":29,"value":8438,"toc":8649},[8439,8443,8446,8450,8453,8470,8474,8477,8527,8531,8553,8557,8560,8592,8596,8599,8616,8620,8623,8640,8644],[32,8440,8442],{"id":8441},"what-is-security-awareness-training","What is Security Awareness Training?",[37,8444,8445],{},"Security awareness training is an educational program designed to teach employees about cybersecurity threats, security best practices, and their responsibilities for protecting organizational data and systems. Human error remains one of the leading causes of security incidents, making awareness training a critical control for reducing risk. Every major compliance framework requires or strongly recommends security awareness training.",[44,8447,8449],{"id":8448},"why-does-security-awareness-training-matter","Why does security awareness training matter?",[37,8451,8452],{},"Technology controls alone cannot prevent all security incidents. Employees interact with sensitive data, click links, open attachments, and make decisions that affect security every day. Effective training:",[92,8454,8455,8458,8461,8464,8467],{},[95,8456,8457],{},"Reduces the likelihood of successful phishing and social engineering attacks",[95,8459,8460],{},"Helps employees recognize and report suspicious activity",[95,8462,8463],{},"Builds a security-conscious culture throughout the organization",[95,8465,8466],{},"Meets compliance requirements across multiple frameworks",[95,8468,8469],{},"Reduces the frequency and impact of human-caused security incidents",[44,8471,8473],{"id":8472},"what-are-the-core-security-awareness-training-topics","What are the core security awareness training topics?",[37,8475,8476],{},"A comprehensive security awareness program typically covers:",[92,8478,8479,8485,8491,8497,8503,8509,8515,8521],{},[95,8480,8481,8484],{},[52,8482,8483],{},"Phishing and social engineering"," — how to identify and respond to phishing emails, phone-based pretexting, and other manipulation techniques",[95,8486,8487,8490],{},[52,8488,8489],{},"Password security"," — creating strong passwords, using password managers, and understanding multi-factor authentication",[95,8492,8493,8496],{},[52,8494,8495],{},"Data handling"," — proper classification, storage, transmission, and disposal of sensitive data",[95,8498,8499,8502],{},[52,8500,8501],{},"Physical security"," — securing workstations, preventing tailgating, and protecting physical access badges",[95,8504,8505,8508],{},[52,8506,8507],{},"Remote work security"," — securing home networks, using VPNs, and protecting devices outside the office",[95,8510,8511,8514],{},[52,8512,8513],{},"Incident reporting"," — how and when to report suspected security incidents",[95,8516,8517,8520],{},[52,8518,8519],{},"Acceptable use"," — organizational policies on technology use, internet access, and personal devices",[95,8522,8523,8526],{},[52,8524,8525],{},"Regulatory requirements"," — specific requirements based on the organization's compliance obligations (HIPAA for healthcare, PCI DSS for payment card handling)",[44,8528,8530],{"id":8529},"what-training-requirements-apply-by-framework","What training requirements apply by framework?",[92,8532,8533,8538,8543,8548],{},[95,8534,8535,8537],{},[52,8536,3864],{}," — CC1.4 requires that the organization demonstrates a commitment to attract, develop, and retain competent individuals, including security training",[95,8539,8540,8542],{},[52,8541,2728],{}," — control A.6.3 requires information security awareness, education, and training",[95,8544,8545,8547],{},[52,8546,3885],{}," — the Security Rule requires security awareness and training for all workforce members (45 CFR 164.308(a)(5))",[95,8549,8550,8552],{},[52,8551,3899],{}," — Requirement 12.6 requires security awareness training for all personnel upon hire and at least annually",[44,8554,8556],{"id":8555},"how-often-should-training-be-delivered-and-how","How often should training be delivered, and how?",[37,8558,8559],{},"Best practices for training delivery include:",[92,8561,8562,8568,8574,8580,8586],{},[95,8563,8564,8567],{},[52,8565,8566],{},"Upon hire"," — all new employees should complete security awareness training during onboarding",[95,8569,8570,8573],{},[52,8571,8572],{},"Annual refresher"," — all employees should complete refresher training at least annually",[95,8575,8576,8579],{},[52,8577,8578],{},"Role-specific training"," — employees in high-risk roles (developers, administrators, finance) should receive additional targeted training",[95,8581,8582,8585],{},[52,8583,8584],{},"Continuous reinforcement"," — supplement formal training with simulated phishing campaigns, security tips, and brief micro-learning modules throughout the year",[95,8587,8588,8591],{},[52,8589,8590],{},"Triggered training"," — require additional training when an employee fails a phishing simulation or is involved in a security incident",[44,8593,8595],{"id":8594},"how-do-you-measure-training-effectiveness","How do you measure training effectiveness?",[37,8597,8598],{},"Training effectiveness should be measured through:",[92,8600,8601,8604,8607,8610,8613],{},[95,8602,8603],{},"Phishing simulation click rates (tracked over time to show improvement)",[95,8605,8606],{},"Training completion rates",[95,8608,8609],{},"Security incident trends related to human factors",[95,8611,8612],{},"Employee knowledge assessments (quizzes or surveys)",[95,8614,8615],{},"Time to report suspicious activity",[44,8617,8619],{"id":8618},"what-training-evidence-do-auditors-look-for","What training evidence do auditors look for?",[37,8621,8622],{},"Auditors expect to see:",[92,8624,8625,8628,8631,8634,8637],{},[95,8626,8627],{},"Training policy documenting requirements and frequency",[95,8629,8630],{},"Records of training completion for all employees",[95,8632,8633],{},"Training content covering relevant topics",[95,8635,8636],{},"Phishing simulation results and trends",[95,8638,8639],{},"Evidence of new hire training",[44,8641,8643],{"id":8642},"how-does-episki-help-with-security-awareness-training","How does episki help with security awareness training?",[37,8645,8646,8647,313],{},"episki tracks security awareness training completion, sends reminders to employees and managers, and maintains training records as compliance evidence. The platform integrates with popular training providers and maps training requirements to framework controls. Learn more on our ",[86,8648,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":8650},[8651],{"id":8441,"depth":437,"text":8442,"children":8652},[8653,8654,8655,8656,8657,8658,8659],{"id":8448,"depth":442,"text":8449},{"id":8472,"depth":442,"text":8473},{"id":8529,"depth":442,"text":8530},{"id":8555,"depth":442,"text":8556},{"id":8594,"depth":442,"text":8595},{"id":8618,"depth":442,"text":8619},{"id":8642,"depth":442,"text":8643},{},"\u002Fglossary\u002Fsecurity-awareness-training",[523,4257,4258,4259,4260],[1413,4792,4510,5020],{"title":8665,"description":8666},"What is Security Awareness Training? Definition & Compliance Guide","Security awareness training educates employees about cybersecurity threats and best practices. Learn what to include and how it satisfies compliance requirements.","security-awareness-training","8.glossary\u002Fsecurity-awareness-training","xgD6bzRoOy6RZm_k9NAZRMfP5cKo0j-xLN3LeofSjwI",{"id":8671,"title":8672,"body":8673,"description":436,"extension":467,"lastUpdated":925,"meta":8841,"navigation":505,"path":8842,"relatedFrameworks":8843,"relatedTerms":8844,"seo":8846,"slug":8849,"stem":8850,"term":8678,"__hash__":8851},"glossary\u002F8.glossary\u002Fvulnerability-management.md","Vulnerability Management",{"type":29,"value":8674,"toc":8832},[8675,8679,8682,8686,8689,8726,8730,8733,8760,8764,8790,8794,8797,8823,8827],[32,8676,8678],{"id":8677},"what-is-vulnerability-management","What is Vulnerability Management?",[37,8680,8681],{},"Vulnerability management is the continuous process of identifying, classifying, prioritizing, and remediating security vulnerabilities in an organization's systems, software, and infrastructure. Unlike one-time assessments, vulnerability management is an ongoing program that adapts as new threats emerge and your environment changes.",[44,8683,8685],{"id":8684},"what-is-the-vulnerability-management-lifecycle","What is the vulnerability management lifecycle?",[37,8687,8688],{},"An effective program follows a repeating cycle:",[358,8690,8691,8697,8703,8709,8715,8721],{},[95,8692,8693,8696],{},[52,8694,8695],{},"Asset discovery"," — maintain an accurate inventory of all hardware, software, and cloud resources in scope",[95,8698,8699,8702],{},[52,8700,8701],{},"Vulnerability scanning"," — use automated tools to detect known vulnerabilities across your environment on a regular schedule",[95,8704,8705,8708],{},[52,8706,8707],{},"Prioritization"," — rank findings by severity (CVSS score), exploitability, asset criticality, and business context — not every \"critical\" CVE is critical to your organization",[95,8710,8711,8714],{},[52,8712,8713],{},"Remediation"," — apply patches, configuration changes, or compensating controls to address vulnerabilities within defined SLAs",[95,8716,8717,8720],{},[52,8718,8719],{},"Verification"," — rescan to confirm that remediation was effective and didn't introduce new issues",[95,8722,8723,8725],{},[52,8724,7699],{}," — track metrics like mean time to remediate (MTTR), vulnerability aging, and coverage rates",[44,8727,8729],{"id":8728},"how-do-compliance-frameworks-address-vulnerability-management","How do compliance frameworks address vulnerability management?",[37,8731,8732],{},"Most security frameworks require a formal vulnerability management program:",[92,8734,8735,8740,8745,8750,8755],{},[95,8736,8737,8739],{},[52,8738,3899],{}," — Requirement 6.3 requires patching critical vulnerabilities within defined timeframes; Requirement 11.3 requires internal and external vulnerability scanning",[95,8741,8742,8744],{},[52,8743,3864],{}," — CC7.1 covers detection of vulnerabilities and CC8.1 addresses change management for remediation",[95,8746,8747,8749],{},[52,8748,2728],{}," — A.8.8 (management of technical vulnerabilities) requires timely identification and remediation of vulnerabilities",[95,8751,8752,8754],{},[52,8753,155],{}," — ID.RA (risk assessment) and PR.IP (information protection) directly relate to vulnerability identification and remediation",[95,8756,8757,8759],{},[52,8758,504],{}," — RA.L2-3.11.2 requires remediation of vulnerabilities in accordance with risk assessments",[44,8761,8763],{"id":8762},"what-are-common-vulnerability-scanning-tools","What are common vulnerability scanning tools?",[92,8765,8766,8772,8778,8784],{},[95,8767,8768,8771],{},[52,8769,8770],{},"Infrastructure scanners"," — Nessus, Qualys, Rapid7 InsightVM for network and host-level vulnerabilities",[95,8773,8774,8777],{},[52,8775,8776],{},"Application scanners"," — OWASP ZAP, Burp Suite for web application vulnerabilities",[95,8779,8780,8783],{},[52,8781,8782],{},"Dependency scanners"," — Snyk, Dependabot, Trivy for software composition analysis (SCA)",[95,8785,8786,8789],{},[52,8787,8788],{},"Cloud security posture"," — AWS Inspector, Azure Defender, GCP Security Command Center for cloud misconfigurations",[44,8791,8793],{"id":8792},"what-are-sla-best-practices-for-vulnerability-management","What are SLA best practices for vulnerability management?",[37,8795,8796],{},"Define remediation timelines based on severity:",[92,8798,8799,8805,8811,8817],{},[95,8800,8801,8804],{},[52,8802,8803],{},"Critical"," — remediate within 24–72 hours",[95,8806,8807,8810],{},[52,8808,8809],{},"High"," — remediate within 7–14 days",[95,8812,8813,8816],{},[52,8814,8815],{},"Medium"," — remediate within 30 days",[95,8818,8819,8822],{},[52,8820,8821],{},"Low"," — remediate within 90 days or accept risk with documented justification",[44,8824,8826],{"id":8825},"how-does-episki-help-with-vulnerability-management","How does episki help with vulnerability management?",[37,8828,8829,8830,313],{},"episki tracks vulnerability findings, manages remediation workflows with due dates and ownership, and maps vulnerabilities to compliance framework requirements. The platform provides dashboards showing remediation progress and aging metrics for auditors. Learn more on our ",[86,8831,4239],{"href":4238},{"title":436,"searchDepth":437,"depth":437,"links":8833},[8834],{"id":8677,"depth":437,"text":8678,"children":8835},[8836,8837,8838,8839,8840],{"id":8684,"depth":442,"text":8685},{"id":8728,"depth":442,"text":8729},{"id":8762,"depth":442,"text":8763},{"id":8792,"depth":442,"text":8793},{"id":8825,"depth":442,"text":8826},{},"\u002Fglossary\u002Fvulnerability-management",[4257,4258,4260,2791,523],[5615,4793,4797,8845],"web-application-security",{"title":8847,"description":8848},"What is Vulnerability Management? Definition & Compliance Guide","Vulnerability management is the ongoing process of identifying, classifying, prioritizing, and remediating security vulnerabilities across your systems and applications.","vulnerability-management","8.glossary\u002Fvulnerability-management","uzdMPlyqCfawsSDUCyB5DBUfYbPo1BYxc5FJB7wJDgM",[8853,9135,9717,10212,10829,11337],{"id":4,"title":5,"advantages":8854,"body":8861,"checklist":9110,"cta":9112,"description":436,"extension":467,"faq":9113,"hero":9120,"lastUpdated":502,"meta":9124,"name":504,"navigation":505,"path":506,"resources":9125,"seo":9130,"slug":523,"stats":9131,"stem":534,"__hash__":535},[8855,8857,8859],{"title":8,"description":9,"bullets":8856},[11,12,13],{"title":15,"description":16,"bullets":8858},[18,19,20],{"title":22,"description":23,"bullets":8860},[25,26,27],{"type":29,"value":8862,"toc":9093},[8863,8865,8867,8869,8871,8875,8881,8887,8889,8893,8913,8915,8917,8923,8929,8931,8933,8945,8951,8953,8955,8957,8963,8967,8969,8977,8979,8981,8985,9003,9005,9019,9021,9025,9027,9031,9033,9037,9039,9041,9067,9069,9091],[32,8864,35],{"id":34},[37,8866,39],{},[37,8868,42],{},[44,8870,47],{"id":46},[37,8872,50,8873,55],{},[52,8874,54],{},[37,8876,58,8877,62,8879,66],{},[52,8878,61],{},[52,8880,65],{},[37,8882,69,8883,73,8885,77],{},[52,8884,72],{},[52,8886,76],{},[44,8888,81],{"id":80},[37,8890,84,8891,90],{},[86,8892,89],{"href":88},[92,8894,8895,8901,8907],{},[95,8896,8897,100,8899,104],{},[52,8898,99],{},[52,8900,103],{},[95,8902,8903,110,8905,114],{},[52,8904,109],{},[52,8906,113],{},[95,8908,8909,120,8911,124],{},[52,8910,119],{},[52,8912,123],{},[37,8914,127],{},[44,8916,131],{"id":130},[37,8918,134,8919,138,8921,143],{},[52,8920,137],{},[86,8922,142],{"href":141},[37,8924,146,8925,151,8927,156],{},[86,8926,150],{"href":149},[86,8928,155],{"href":154},[44,8930,160],{"id":159},[37,8932,163],{},[92,8934,8935,8937,8939,8941,8943],{},[95,8936,168],{},[95,8938,171],{},[95,8940,174],{},[95,8942,177],{},[95,8944,180],{},[37,8946,183,8947,188,8949,193],{},[86,8948,187],{"href":186},[86,8950,192],{"href":191},[37,8952,196],{},[44,8954,200],{"id":199},[37,8956,203],{},[37,8958,206,8959,210,8961,214],{},[52,8960,209],{},[52,8962,213],{},[37,8964,8965,221],{},[86,8966,220],{"href":219},[44,8968,225],{"id":224},[37,8970,228,8971,232,8973,236,8975,240],{},[52,8972,231],{},[52,8974,235],{},[52,8976,239],{},[37,8978,243],{},[44,8980,247],{"id":246},[37,8982,250,8983,255],{},[86,8984,254],{"href":253},[92,8986,8987,8991,8995,8999],{},[95,8988,8989,263],{},[52,8990,262],{},[95,8992,8993,269],{},[52,8994,268],{},[95,8996,8997,275],{},[52,8998,274],{},[95,9000,9001,281],{},[52,9002,280],{},[44,9004,285],{"id":284},[37,9006,288,9007,292,9009,236,9011,299,9013,303,9015,308,9017,313],{},[52,9008,291],{},[52,9010,295],{},[52,9012,298],{},[52,9014,302],{},[86,9016,307],{"href":306},[86,9018,312],{"href":311},[44,9020,317],{"id":316},[37,9022,320,9023,325],{},[86,9024,324],{"href":323},[44,9026,329],{"id":328},[37,9028,332,9029,337],{},[86,9030,336],{"href":335},[44,9032,341],{"id":340},[37,9034,344,9035,349],{},[86,9036,348],{"href":347},[44,9038,353],{"id":352},[37,9040,356],{},[358,9042,9043,9047,9051,9055,9059,9063],{},[95,9044,9045,365],{},[52,9046,364],{},[95,9048,9049,371],{},[52,9050,370],{},[95,9052,9053,377],{},[52,9054,376],{},[95,9056,9057,383],{},[52,9058,382],{},[95,9060,9061,389],{},[52,9062,388],{},[95,9064,9065,395],{},[52,9066,394],{},[44,9068,399],{"id":398},[92,9070,9071,9075,9079,9083,9087],{},[95,9072,9073,407],{},[52,9074,406],{},[95,9076,9077,413],{},[52,9078,412],{},[95,9080,9081,419],{},[52,9082,418],{},[95,9084,9085,425],{},[52,9086,424],{},[95,9088,9089,431],{},[52,9090,430],{},[37,9092,434],{},{"title":436,"searchDepth":437,"depth":437,"links":9094},[9095],{"id":34,"depth":437,"text":35,"children":9096},[9097,9098,9099,9100,9101,9102,9103,9104,9105,9106,9107,9108,9109],{"id":46,"depth":442,"text":47},{"id":80,"depth":442,"text":81},{"id":130,"depth":442,"text":131},{"id":159,"depth":442,"text":160},{"id":199,"depth":442,"text":200},{"id":224,"depth":442,"text":225},{"id":246,"depth":442,"text":247},{"id":284,"depth":442,"text":285},{"id":316,"depth":442,"text":317},{"id":328,"depth":442,"text":329},{"id":340,"depth":442,"text":341},{"id":352,"depth":442,"text":353},{"id":398,"depth":442,"text":399},{"title":456,"description":457,"items":9111},[459,460,461,462,463],{"title":465,"description":466},{"title":469,"items":9114},[9115,9116,9117,9118,9119],{"label":472,"content":473},{"label":475,"content":476},{"label":478,"content":479},{"label":481,"content":482},{"label":484,"content":485},{"headline":487,"title":488,"description":489,"links":9121},[9122,9123],{"label":492,"icon":493,"to":494},{"label":496,"icon":497,"color":498,"variant":499,"to":500,"target":501},{},{"headline":508,"title":508,"description":509,"items":9126},[9127,9128,9129],{"title":512,"description":513},{"title":515,"description":516},{"title":518,"description":519},{"title":521,"description":522},[9132,9133,9134],{"value":526,"description":527},{"value":529,"description":530},{"value":532,"description":533},{"id":9136,"title":9137,"advantages":9138,"body":9160,"checklist":9650,"cta":9659,"description":436,"extension":467,"faq":9662,"hero":9680,"lastUpdated":502,"meta":9688,"name":3885,"navigation":505,"path":3884,"resources":9689,"seo":9702,"slug":4259,"stats":9705,"stem":9715,"__hash__":9716},"frameworks\u002F5.frameworks\u002Fhipaa.md","Hipaa",[9139,9146,9153],{"title":9140,"description":9141,"bullets":9142},"Safeguards mapped to your stack","Every HIPAA standard comes with plain-language owners, SLAs, and tests.",[9143,9144,9145],"Assign compliance, engineering, and ops leads to each safeguard","Playbooks explain what “good” looks like for each requirement","Timeline view keeps renewals and reviews on schedule",{"title":9147,"description":9148,"bullets":9149},"PHI-aware evidence locker","Secure uploads, access controls, and audit trails keep regulators satisfied.",[9150,9151,9152],"Granular permissions for internal and external reviewers","Automated retention and deletion policies","Download tracking and access audit trails",{"title":9154,"description":9155,"bullets":9156},"Vendor & incident workflows","Track BAAs, vendor attestations, and incidents from discovery to closure.",[9157,9158,9159],"BAA repository tied to vendor risk levels","Incident response runbooks with reminders","Post-incident reports aligned to HIPAA timelines",{"type":29,"value":9161,"toc":9623},[9162,9166,9169,9181,9184,9188,9191,9234,9238,9241,9246,9250,9253,9257,9265,9285,9288,9292,9299,9307,9311,9314,9318,9321,9324,9337,9341,9344,9347,9351,9369,9373,9386,9390,9393,9400,9404,9407,9410,9417,9421,9428,9431,9435,9442,9445,9468,9472,9475,9478,9484,9488,9491,9517,9520,9523,9527,9530,9548,9551,9555,9561,9565,9568,9597,9605,9609,9612,9620],[32,9163,9165],{"id":9164},"what-is-hipaa","What is HIPAA?",[37,9167,9168],{},"HIPAA, the Health Insurance Portability and Accountability Act of 1996, is the cornerstone US federal law governing the privacy and security of patient health information. Signed into law by President Bill Clinton, the act was originally designed to improve the portability of health insurance coverage when workers changed jobs, combat fraud and waste in healthcare, and simplify the administration of health insurance through standardized electronic transactions. Over the decades since, HIPAA has evolved into the defining US regulation for how healthcare organizations and their partners handle sensitive patient data.",[37,9170,9171,9172,9176,9177,9180],{},"At its core, the law establishes national standards that protect sensitive patient information — known as ",[86,9173,9175],{"href":9174},"\u002Fglossary\u002Fphi","protected health information",", or PHI — from unauthorized use and disclosure. Any organization that creates, receives, maintains, or transmits PHI must comply, whether that organization is a hospital, a health plan, a billing clearinghouse, or a SaaS vendor providing services to healthcare customers. The ",[86,9178,9179],{"href":6915},"HIPAA glossary entry"," provides a concise definition, while this page walks through the full regulatory landscape so you understand how each HIPAA rule fits together.",[37,9182,9183],{},"Enforcement falls to the US Department of Health and Human Services (HHS) through its Office for Civil Rights (OCR). State attorneys general also have authority to bring enforcement actions under powers granted by the HITECH Act. The law applies across all 50 states and preempts weaker state privacy laws, though state laws that provide greater protection remain in force.",[32,9185,9187],{"id":9186},"a-brief-history-of-hipaa","A brief history of HIPAA",[37,9189,9190],{},"HIPAA was enacted in 1996, but its privacy and security requirements were not finalized overnight. The act directed HHS to develop implementing regulations, and the major rules were rolled out over more than a decade.",[92,9192,9193,9199,9205,9211,9222,9228],{},[95,9194,9195,9198],{},[52,9196,9197],{},"1996"," — Congress passes HIPAA, directing HHS to issue regulations on privacy, security, and electronic transactions.",[95,9200,9201,9204],{},[52,9202,9203],{},"2000"," — The HIPAA Privacy Rule is published; it takes full effect in 2003.",[95,9206,9207,9210],{},[52,9208,9209],{},"2003"," — The HIPAA Security Rule is finalized, with compliance required by 2005 for most entities.",[95,9212,9213,9216,9217,9221],{},[52,9214,9215],{},"2009"," — The Health Information Technology for Economic and Clinical Health Act (",[86,9218,9220],{"href":9219},"\u002Fframeworks\u002Fhipaa\u002Fhitech-and-omnibus","HITECH",") is signed into law as part of the American Recovery and Reinvestment Act, extending HIPAA obligations to business associates and introducing breach notification requirements.",[95,9223,9224,9227],{},[52,9225,9226],{},"2013"," — The HIPAA Omnibus Rule implements HITECH and further strengthens HIPAA enforcement, fines, and patient rights.",[95,9229,9230,9233],{},[52,9231,9232],{},"2024 and beyond"," — HHS continues to update HIPAA guidance, most recently around cybersecurity expectations, reproductive health privacy, and the proposed modernization of the HIPAA Security Rule to reflect modern threats.",[44,9235,9237],{"id":9236},"hitech-and-the-omnibus-rule","HITECH and the Omnibus Rule",[37,9239,9240],{},"The HITECH Act of 2009 was a watershed moment. Before HITECH, HIPAA obligations technically applied only to covered entities, and business associates were bound solely by contract. HITECH changed that by making business associates directly liable. It also introduced the federal Breach Notification Rule, increased civil monetary penalties, and funded the nationwide adoption of electronic health records — which dramatically expanded the volume of electronic PHI requiring protection.",[37,9242,9243,9244,313],{},"The 2013 Omnibus Rule then translated HITECH into binding regulation. It extended the Privacy and Security Rules to business associates and their subcontractors, tightened the definition of a breach, strengthened individual rights to access electronic health records, and aligned the law with the Genetic Information Nondiscrimination Act (GINA). For a deeper breakdown of what changed, read ",[86,9245,9237],{"href":9219},[32,9247,9249],{"id":9248},"who-hipaa-applies-to","Who HIPAA applies to",[37,9251,9252],{},"HIPAA applies to two broad categories of organizations: covered entities and business associates. Understanding which category your organization falls into is the first and most important step in any HIPAA compliance program.",[44,9254,9256],{"id":9255},"covered-entities","Covered entities",[37,9258,9259,9260,9264],{},"A ",[86,9261,9263],{"href":9262},"\u002Fglossary\u002Fcovered-entity","covered entity"," is any of the following:",[92,9266,9267,9273,9279],{},[95,9268,9269,9272],{},[52,9270,9271],{},"Health plans"," — health insurance companies, HMOs, employer-sponsored group health plans, government programs like Medicare and Medicaid, and long-term care insurers.",[95,9274,9275,9278],{},[52,9276,9277],{},"Healthcare providers"," — hospitals, clinics, physician practices, dentists, pharmacies, psychologists, and any other provider that transmits health information electronically for billing or eligibility purposes.",[95,9280,9281,9284],{},[52,9282,9283],{},"Healthcare clearinghouses"," — entities that process nonstandard health information into standard formats (or vice versa), such as billing services and repricing companies.",[37,9286,9287],{},"If your organization directly delivers healthcare or finances it, you are almost certainly a covered entity.",[44,9289,9291],{"id":9290},"business-associates","Business associates",[37,9293,9259,9294,9298],{},[86,9295,9297],{"href":9296},"\u002Fglossary\u002Fbusiness-associate","business associate"," is any person or organization that performs a function or activity on behalf of a covered entity that involves the use or disclosure of PHI. Typical business associates include cloud hosting providers, billing vendors, EHR vendors, IT service providers, analytics firms, legal counsel, accounting firms, transcription services, and SaaS platforms that process PHI on behalf of covered entities.",[37,9300,9301,9302,9306],{},"Most modern SaaS companies serving healthcare customers are business associates. If your product ingests, stores, processes, or transmits PHI for a covered entity, HIPAA applies to you directly — regardless of whether you consider yourself a \"healthcare company.\" Subcontractors of business associates are themselves business associates and are bound by the same obligations. Signing a ",[86,9303,9305],{"href":9304},"\u002Fglossary\u002Fbaa","business associate agreement"," with every upstream and downstream partner that touches PHI is non-negotiable.",[44,9308,9310],{"id":9309},"who-is-not-covered-by-hipaa","Who is not covered by HIPAA?",[37,9312,9313],{},"Not every organization that handles health information is subject to the law. Consumer wellness apps, fitness trackers, direct-to-consumer genetic testing services, employers (in their role as employers), life insurers, and schools generally fall outside its reach unless they act on behalf of a covered entity. That said, many of these organizations still face FTC oversight, state privacy laws, and customer expectations that mirror HIPAA protections.",[32,9315,9317],{"id":9316},"the-hipaa-privacy-rule","The HIPAA Privacy Rule",[37,9319,9320],{},"The HIPAA Privacy Rule sets national standards for the protection of PHI in all forms — electronic, paper, and oral. It establishes when PHI may be used and disclosed, defines patient rights over their own health data, and imposes the minimum necessary standard on most disclosures. The Privacy Rule applies to covered entities directly and to business associates through their BAAs.",[37,9322,9323],{},"Key Privacy Rule concepts include the Notice of Privacy Practices, patient access rights (including the right to an electronic copy of an electronic health record within 30 days), the right to request amendments and accounting of disclosures, the minimum necessary standard, permitted uses for treatment, payment, and operations, and the authorization requirements for marketing and sale of PHI.",[37,9325,9326,9327,9331,9332,9336],{},"For a comprehensive walkthrough of the HIPAA Privacy Rule, permitted disclosures, and patient rights, read the dedicated ",[86,9328,9330],{"href":9329},"\u002Fframeworks\u002Fhipaa\u002Fprivacy-rule","HIPAA Privacy Rule"," guide. For more on the narrowly tailored access principle that governs day-to-day PHI handling, see the ",[86,9333,9335],{"href":9334},"\u002Fframeworks\u002Fhipaa\u002Fminimum-necessary-rule","minimum necessary rule"," page.",[32,9338,9340],{"id":9339},"the-hipaa-security-rule","The HIPAA Security Rule",[37,9342,9343],{},"The HIPAA Security Rule establishes the national floor for protecting electronic PHI (ePHI). While the Privacy Rule covers every form of PHI, the Security Rule is scoped to electronic data — which, in 2026, is effectively every record of clinical or financial relevance inside a modern healthcare organization.",[37,9345,9346],{},"The Security Rule organizes its requirements into three categories of safeguards. Every covered entity and business associate must implement each category based on a documented HIPAA risk analysis.",[44,9348,9350],{"id":9349},"administrative-safeguards","Administrative safeguards",[37,9352,9353,9354,9358,9359,9363,9364,9368],{},"Administrative safeguards are the policies, procedures, and organizational measures that govern your HIPAA program. They include security management processes, a designated security official, ",[86,9355,9357],{"href":9356},"\u002Fframeworks\u002Fhipaa\u002Fworkforce-training","workforce training",", a ",[86,9360,9362],{"href":9361},"\u002Fframeworks\u002Fhipaa\u002Fsanctions-policy","sanctions policy"," for workforce violations, access management, ",[86,9365,9367],{"href":9366},"\u002Fframeworks\u002Fhipaa\u002Fcontingency-planning","contingency planning",", periodic evaluations, and BAAs with every downstream partner. These typically consume the most effort because they touch every corner of the business.",[44,9370,9372],{"id":9371},"physical-safeguards","Physical safeguards",[37,9374,9375,9376,9380,9381,9385],{},"Physical safeguards protect the facilities, workstations, devices, and media that house ePHI. This category covers ",[86,9377,9379],{"href":9378},"\u002Fframeworks\u002Fhipaa\u002Ffacility-access-controls","facility access controls",", ",[86,9382,9384],{"href":9383},"\u002Fframeworks\u002Fhipaa\u002Fworkstation-and-device-controls","workstation and device controls",", and media disposal. For cloud-first SaaS companies, physical safeguards increasingly translate into inherited controls from hyperscale cloud providers, but every regulated organization still needs defensible answers for the laptops, offices, and portable media its workforce uses.",[44,9387,9389],{"id":9388},"technical-safeguards","Technical safeguards",[37,9391,9392],{},"Technical safeguards are the technology controls that protect ePHI and govern access to it. They include unique user identification, automatic logoff, encryption and decryption of ePHI at rest and in transit, audit controls that log system activity, integrity controls that prevent improper alteration, and person or entity authentication.",[37,9394,9395,9396,9399],{},"For a deep dive into the complete Security Rule standards, required versus addressable implementation specifications, and how to pass an OCR audit of your ePHI safeguards, read the ",[86,9397,9398],{"href":3889},"HIPAA Security Rule"," guide.",[32,9401,9403],{"id":9402},"the-hipaa-breach-notification-rule","The HIPAA Breach Notification Rule",[37,9405,9406],{},"The Breach Notification Rule, added by HITECH and finalized in the Omnibus Rule, requires covered entities and business associates to notify affected individuals, HHS, and in some cases the media when unsecured PHI is breached. A breach is presumed whenever PHI is used or disclosed in a way that is not permitted under the Privacy Rule, unless the organization can demonstrate through a four-factor risk assessment that there is a low probability the PHI has been compromised.",[37,9408,9409],{},"Notifications must be made without unreasonable delay and in no case later than 60 calendar days after discovery. Business associates must notify their covered entity clients, who in turn notify affected individuals. Breaches involving 500 or more individuals must be reported to HHS within 60 days and listed on the public OCR \"Wall of Shame,\" while smaller breaches may be reported in an annual log.",[37,9411,9412,9413,9399],{},"For full details on timelines, content requirements, and documentation expectations, see the ",[86,9414,9416],{"href":9415},"\u002Fframeworks\u002Fhipaa\u002Fbreach-notification","HIPAA Breach Notification Rule",[32,9418,9420],{"id":9419},"business-associate-agreements","Business associate agreements",[37,9422,9423,9424,9427],{},"No PHI should ever leave a covered entity — or a business associate — without a properly executed BAA in place. A ",[86,9425,9305],{"href":9426},"\u002Fframeworks\u002Fhipaa\u002Fbusiness-associate-agreements"," is a legally binding contract that defines permitted uses and disclosures of PHI, requires implementation of appropriate safeguards, obligates breach notification, mandates BAA flow-down to subcontractors, and establishes termination rights when a business associate violates the agreement.",[37,9429,9430],{},"In practice, BAA management is one of the most common HIPAA failure modes for growing SaaS companies. Deals close, engineering ships, and PHI starts flowing before legal has countersigned the BAA — creating exposure for both sides. A disciplined BAA intake process, a BAA repository with renewal reminders, and clear ownership of vendor risk are table stakes for any serious compliance program.",[32,9432,9434],{"id":9433},"hipaa-compliance-checklist","HIPAA compliance checklist",[37,9436,9437,9438,9441],{},"Translating the regulatory language into day-to-day operations is where most programs struggle. The ",[86,9439,9434],{"href":9440},"\u002Fframeworks\u002Fhipaa\u002Fcompliance-checklist"," walks through every major obligation — from assigning a security official through finalizing your Notice of Privacy Practices — as a sequenced program of work.",[37,9443,9444],{},"At a high level, a complete HIPAA program includes:",[92,9446,9447,9450,9453,9456,9459,9462,9465],{},[95,9448,9449],{},"A current risk analysis and documented risk management plan.",[95,9451,9452],{},"Written policies and procedures covering Privacy, Security, and Breach Notification obligations.",[95,9454,9455],{},"A signed BAA with every vendor, subcontractor, and customer that exchanges PHI.",[95,9457,9458],{},"Workforce training at hire and at least annually thereafter, with documented completion.",[95,9460,9461],{},"Access control, audit logging, encryption, and contingency planning for every system that touches ePHI.",[95,9463,9464],{},"An incident response runbook aligned to the Breach Notification Rule.",[95,9466,9467],{},"Documentation retained for at least six years from creation or last effective date, whichever is later.",[32,9469,9471],{"id":9470},"hipaa-risk-analysis","HIPAA risk analysis",[37,9473,9474],{},"Every HIPAA Security Rule program begins with a risk analysis. Under 45 CFR §164.308(a)(1)(ii)(A), covered entities and business associates must conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. HHS has repeatedly stated that a missing or superficial risk analysis is among the most common findings in OCR enforcement actions.",[37,9476,9477],{},"A defensible risk analysis inventories every system that creates, receives, maintains, or transmits ePHI, identifies threats and vulnerabilities affecting each system, measures the likelihood and impact of each risk, and feeds directly into the Security Management Process that prioritizes mitigation. Most mature programs align their methodology to NIST Special Publication 800-30, which OCR cites favorably.",[37,9479,9480,9481,9399],{},"For a full breakdown of methodology, documentation requirements, and common pitfalls, read the ",[86,9482,9471],{"href":9483},"\u002Fframeworks\u002Fhipaa\u002Frisk-analysis",[32,9485,9487],{"id":9486},"penalties-and-enforcement","Penalties and enforcement",[37,9489,9490],{},"Enforcement is administered by OCR, with parallel criminal enforcement authority held by the Department of Justice and civil enforcement authority held by state attorneys general. HIPAA penalties are tiered by culpability.",[92,9492,9493,9499,9505,9511],{},[95,9494,9495,9498],{},[52,9496,9497],{},"Tier 1 — Unknowing violation"," — $100 to $50,000 per violation; annual cap $25,000 for identical violations.",[95,9500,9501,9504],{},[52,9502,9503],{},"Tier 2 — Reasonable cause"," — $1,000 to $50,000 per violation; annual cap $100,000.",[95,9506,9507,9510],{},[52,9508,9509],{},"Tier 3 — Willful neglect, corrected"," — $10,000 to $50,000 per violation; annual cap $250,000.",[95,9512,9513,9516],{},[52,9514,9515],{},"Tier 4 — Willful neglect, uncorrected"," — $50,000 per violation; annual cap $1.5 million per violation category.",[37,9518,9519],{},"Penalty amounts are adjusted annually for inflation. Criminal penalties can reach $250,000 and 10 years of imprisonment for offenses involving intent to sell, transfer, or use PHI for commercial advantage, personal gain, or malicious harm.",[37,9521,9522],{},"OCR enforcement tends to cluster around predictable themes: missing or inadequate risk analyses, lost unencrypted devices, failure to terminate workforce access, insufficient BAAs, delayed breach notifications, and refusal to provide patient access to records. Organizations that can demonstrate a mature, well-documented program — with evidence of ongoing risk analysis, training, and monitoring — consistently receive more favorable resolutions.",[32,9524,9526],{"id":9525},"hipaa-vs-hitech-vs-hitrust","HIPAA vs HITECH vs HITRUST",[37,9528,9529],{},"These three acronyms sit close together in healthcare conversations and are often conflated. They are related but distinct.",[92,9531,9532,9537,9542],{},[95,9533,9534,9536],{},[52,9535,3885],{}," is the underlying federal law and its implementing regulations (Privacy, Security, Breach Notification, and Enforcement Rules). HIPAA defines the legal obligations.",[95,9538,9539,9541],{},[52,9540,9220],{}," is a 2009 federal law that strengthened HIPAA — extending it to business associates, introducing breach notification, increasing penalties, and funding EHR adoption. HITECH is part of HIPAA's regulatory stack, not a separate framework.",[95,9543,9544,9547],{},[52,9545,9546],{},"HITRUST"," is a private-sector certification maintained by the HITRUST Alliance. The HITRUST CSF is a control framework that maps HIPAA, NIST, ISO 27001, PCI DSS, and other standards into a single certifiable set of controls. HITRUST is a common way to demonstrate HIPAA compliance to sophisticated healthcare customers, but HITRUST certification is not itself required by HIPAA.",[37,9549,9550],{},"A healthcare SaaS company might pursue HITRUST CSF certification as a commercial asset while its underlying legal obligation remains HIPAA compliance under HITECH-amended rules.",[44,9552,9554],{"id":9553},"hipaa-and-soc-2","HIPAA and SOC 2",[37,9556,9557,9558,9560],{},"Many SaaS companies pursue ",[86,9559,3864],{"href":3863}," alongside HIPAA. The two frameworks complement each other: SOC 2 evaluates security, availability, confidentiality, processing integrity, and privacy trust services criteria, while HIPAA is a statutory requirement for handling PHI. A well-designed control environment can satisfy both with substantial overlap.",[32,9562,9564],{"id":9563},"getting-hipaa-compliant","Getting HIPAA compliant",[37,9566,9567],{},"The most successful HIPAA programs treat compliance as a continuous operating rhythm rather than a once-a-year scramble. A typical rollout for a SaaS company serving healthcare customers looks like this.",[358,9569,9570,9573,9576,9579,9582,9585,9588,9591,9594],{},[95,9571,9572],{},"Confirm your status as a covered entity, business associate, or both, and inventory the PHI you handle today.",[95,9574,9575],{},"Appoint a security official and a privacy official (the same person may hold both roles at small companies).",[95,9577,9578],{},"Conduct a risk analysis scoped to every system that creates, receives, maintains, or transmits ePHI.",[95,9580,9581],{},"Implement the administrative, physical, and technical safeguards required by the Security Rule, informed by your risk analysis.",[95,9583,9584],{},"Draft and publish policies and procedures covering Privacy, Security, and Breach Notification obligations.",[95,9586,9587],{},"Execute BAAs with every vendor that touches PHI, and require a signed BAA before onboarding any new customer that qualifies as a covered entity.",[95,9589,9590],{},"Deliver workforce training at hire and annually thereafter, and document completion.",[95,9592,9593],{},"Stand up an incident response runbook aligned to the Breach Notification Rule.",[95,9595,9596],{},"Operate the program: review access quarterly, test contingency plans at least annually, refresh your risk analysis whenever material change occurs, and retain documentation for at least six years.",[37,9598,9599,9600,9604],{},"For companies operating in the broader ",[86,9601,9603],{"href":9602},"\u002Findustry\u002Fhealthcare","healthcare industry",", HIPAA is rarely the only regulation in scope. State privacy laws, the 21st Century Cures Act, FDA software-as-a-medical-device requirements, and payor-specific security reviews often run in parallel — which is why most compliance programs are built into a broader GRC operating model.",[32,9606,9608],{"id":9607},"how-episki-helps-with-hipaa-compliance","How episki helps with HIPAA compliance",[37,9610,9611],{},"episki is the HIPAA compliance platform for healthtech teams that need to ship fast without losing control of PHI. We map Privacy, Security, and Breach Notification obligations directly to your systems, automate evidence collection for every safeguard, manage BAAs across your vendor ecosystem, and keep risk analyses current as your stack evolves.",[37,9613,9614,9615,9619],{},"Our platform was designed by practitioners who have led HIPAA programs at healthcare organizations and audited them as consultants. The result is a workspace that makes it obvious what is done, what is due, and what is drifting — so you can spend less time reconstructing evidence the week before a customer audit and more time building product. Read the ",[86,9616,9618],{"href":9617},"\u002Fnow\u002Fhipaa-compliance-healthtech","HIPAA for healthtech"," playbook for a closer look at how modern SaaS companies operate HIPAA at startup speed.",[37,9621,9622],{},"Ready to tighten your HIPAA program? Start a free trial or book a demo from the top of this page.",{"title":436,"searchDepth":437,"depth":437,"links":9624},[9625,9626,9629,9634,9635,9640,9641,9642,9643,9644,9645,9648,9649],{"id":9164,"depth":437,"text":9165},{"id":9186,"depth":437,"text":9187,"children":9627},[9628],{"id":9236,"depth":442,"text":9237},{"id":9248,"depth":437,"text":9249,"children":9630},[9631,9632,9633],{"id":9255,"depth":442,"text":9256},{"id":9290,"depth":442,"text":9291},{"id":9309,"depth":442,"text":9310},{"id":9316,"depth":437,"text":9317},{"id":9339,"depth":437,"text":9340,"children":9636},[9637,9638,9639],{"id":9349,"depth":442,"text":9350},{"id":9371,"depth":442,"text":9372},{"id":9388,"depth":442,"text":9389},{"id":9402,"depth":437,"text":9403},{"id":9419,"depth":437,"text":9420},{"id":9433,"depth":437,"text":9434},{"id":9470,"depth":437,"text":9471},{"id":9486,"depth":437,"text":9487},{"id":9525,"depth":437,"text":9526,"children":9646},[9647],{"id":9553,"depth":442,"text":9554},{"id":9563,"depth":437,"text":9564},{"id":9607,"depth":437,"text":9608},{"title":9651,"description":9652,"items":9653},"HIPAA launch kit","Guided steps keep privacy, security, and ops in sync from day one.",[9654,9655,9656,9657,9658],"Safeguard library with ownership matrix","Evidence tracking for access logs and configs","BAA tracker with renewal reminders","Incident and breach response templates","Stakeholder portal with PHI redaction controls",{"title":9660,"description":9661},"Launch HIPAA monitoring in minutes","Kick off the free trial and invite stakeholders before your next diligence call.",{"title":9663,"items":9664},"HIPAA compliance frequently asked questions",[9665,9668,9671,9674,9677],{"label":9666,"content":9667},"Who needs to comply with HIPAA?","HIPAA applies to covered entities (health plans, healthcare providers, clearinghouses) and business associates — any vendor or subcontractor that creates, receives, maintains, or transmits protected health information (PHI). SaaS companies serving healthcare customers almost always qualify as business associates.",{"label":9669,"content":9670},"What is a Business Associate Agreement (BAA)?","A BAA is a legally required contract between a covered entity and a business associate that establishes permitted uses and disclosures of PHI, requires appropriate safeguards, and outlines breach notification responsibilities. No PHI should be shared with a vendor before a BAA is signed.",{"label":9672,"content":9673},"What are the penalties for HIPAA violations?","HIPAA penalties range from $100 to $50,000 per violation depending on the level of negligence, with annual maximums up to $1.5 million per violation category. Criminal penalties can include fines up to $250,000 and imprisonment. The HHS Office for Civil Rights enforces compliance.",{"label":9675,"content":9676},"Does HIPAA apply to SaaS companies?","Yes. Any SaaS company that handles, stores, or transmits PHI on behalf of a healthcare organization is considered a business associate under HIPAA and must comply with the Security Rule, Privacy Rule, and Breach Notification Rule.",{"label":9678,"content":9679},"What are the three HIPAA safeguard categories?","HIPAA requires administrative safeguards (policies, training, risk assessments), physical safeguards (facility access, workstation security), and technical safeguards (access controls, encryption, audit logging) to protect electronic PHI.",{"headline":9681,"title":9682,"description":9683,"links":9684},"HIPAA-ready cloud teams","Stay HIPAA compliant while shipping product weekly","episki maps administrative, physical, and technical safeguards to your systems and keeps PHI protections verifiable.",[9685,9687],{"label":9686,"icon":493,"to":494},"Start HIPAA trial",{"label":496,"icon":497,"color":498,"variant":499,"to":500,"target":501},{},{"headline":9690,"title":9690,"description":9691,"items":9692},"HIPAA enablement","Keep leadership, customers, and partners aligned.",[9693,9696,9699],{"title":9694,"description":9695},"Board-ready posture report","Shows maturity score, risk trends, and upcoming audits.",{"title":9697,"description":9698},"Customer FAQ pack","Answers the most common HIPAA diligence questions.",{"title":9700,"description":9701},"Ops automation guide","Explains how to plug security tasks into existing tools.",{"title":9703,"description":9704},"HIPAA Compliance Management Software","Map HIPAA safeguards, track PHI evidence, and manage BAAs in one secure workspace. Get audit-ready in 30 days with episki's free trial.",[9706,9709,9712],{"value":9707,"description":9708},"30-day rollout","Average time to production monitoring across safeguards.",{"value":9710,"description":9711},"PHI-safe sharing","Role-based portals keep sensitive documents organized and protected.",{"value":9713,"description":9714},"24\u002F7 alerts","Continuous monitoring for access, logging, and vendor risks.","5.frameworks\u002Fhipaa","9IldK-wXldOkZs8WFGmDWXYF8To1wETqwKkhsGGUW04",{"id":9718,"title":9719,"advantages":9720,"body":9742,"checklist":10145,"cta":10156,"description":436,"extension":467,"faq":10159,"hero":10177,"lastUpdated":502,"meta":10185,"name":2728,"navigation":505,"path":2727,"resources":10186,"seo":10199,"slug":4258,"stats":10202,"stem":10210,"__hash__":10211},"frameworks\u002F5.frameworks\u002Fiso27001.md","Iso27001",[9721,9728,9735],{"title":9722,"description":9723,"bullets":9724},"Statement of Applicability in minutes","Generate and maintain your SoA directly from your control graph with justification notes for every inclusion and exclusion.",[9725,9726,9727],"Auto-populate applicability status from existing controls","Link each control to risk treatment decisions","Export auditor-ready SoA documents on demand",{"title":9729,"description":9730,"bullets":9731},"Risk-driven control management","Connect your risk register to Annex A controls so treatment plans and evidence stay aligned as threats evolve.",[9732,9733,9734],"Risk assessment templates following ISO 27005 guidance","Heat maps show residual risk by domain","Treatment plans tie directly to control tasks and owners",{"title":9736,"description":9737,"bullets":9738},"Surveillance audit confidence","Keep your ISMS current between certification cycles with continuous monitoring and internal audit workflows.",[9739,9740,9741],"Automated evidence refresh and expiration alerts","Internal audit scheduling with finding tracking","Management review templates with trend data",{"type":29,"value":9743,"toc":10127},[9744,9748,9759,9762,9765,9768,9772,9775,9778,9781,9785,9788,9801,9805,9808,9815,9818,9822,9829,9832,9840,9844,9852,9855,9863,9867,9870,9914,9922,9930,9934,9937,9940,9947,9951,9954,9957,9969,9973,9976,9984,9988,9991,9998,10002,10005,10031,10038,10042,10045,10053,10057,10060,10068,10072,10075,10096,10102,10106,10109,10121,10124],[32,9745,9747],{"id":9746},"what-is-iso-27001","What is ISO 27001?",[37,9749,9750,9753,9754,9758],{},[86,9751,2728],{"href":9752},"\u002Fglossary\u002Fiso27001"," is the world's most widely adopted international standard for information security management. Formally titled ISO\u002FIEC 27001, it defines the requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System, or ",[86,9755,9757],{"href":9756},"\u002Fglossary\u002Fisms","ISMS",". Organizations that align with ISO 27001 commit to a risk-based, process-driven approach to protecting the confidentiality, integrity, and availability of the information they hold on behalf of customers, employees, and business partners.",[37,9760,9761],{},"The standard is published jointly by two bodies. The International Organization for Standardization (ISO), headquartered in Geneva, develops consensus-based standards across nearly every industry. The International Electrotechnical Commission (IEC) is its counterpart for electrotechnical and information technology standards. Together, their joint technical committee ISO\u002FIEC JTC 1\u002FSC 27 maintains the ISO 27001 family, which includes supporting documents such as ISO 27002 (implementation guidance) and ISO 27005 (risk management guidance).",[37,9763,9764],{},"ISO 27001 was first released in 2005, revised in 2013, and most recently updated in October 2022. The 2022 revision is now the only version against which new ISO 27001 certifications are issued. Any discussion of ISO 27001 today should default to this edition, which reorganized the control set and introduced eleven new controls addressing modern risks like threat intelligence, data masking, and secure coding.",[37,9766,9767],{},"At the heart of ISO 27001 is the concept of an ISMS. An ISMS is not a product you can buy or a checklist you can run through once. It is the living combination of policies, processes, people, and technology that your organization uses to identify information security risks, decide how to treat them, implement controls, measure effectiveness, and continually improve. ISO 27001 provides the blueprint. Your ISMS is the thing you build from that blueprint.",[32,9769,9771],{"id":9770},"why-iso-27001-matters","Why ISO 27001 matters",[37,9773,9774],{},"ISO 27001 is recognized in more than 160 countries and frequently shows up as a procurement requirement for enterprise technology contracts, financial services partnerships, public sector work, and any organization selling into European or APAC markets. Unlike self-attested programs, ISO 27001 certification is issued by an independent accredited certification body, which gives customers and regulators external assurance that your security practices are real and not marketing.",[37,9776,9777],{},"Beyond procurement, ISO 27001 brings discipline. Many organizations treat security as a reactive function that only activates after an incident or failed audit. The ISO 27001 approach forces proactive risk identification, documented decisions, and measurable effectiveness. Even teams that never pursue certification often adopt the ISO 27001 framework as an internal operating model because it is mature, well-documented, and maps cleanly to other standards.",[37,9779,9780],{},"ISO 27001 also signals organizational maturity to investors. Due diligence for Series B and later funding rounds almost always includes a security review. Holding an ISO 27001 certificate short-circuits much of that review and accelerates close.",[32,9782,9784],{"id":9783},"the-iso-27001-certification-process","The ISO 27001 certification process",[37,9786,9787],{},"ISO 27001 certification follows a standardized two-stage audit model used worldwide. A Stage 1 audit reviews your ISMS documentation and readiness. A Stage 2 audit evaluates whether your ISMS is actually implemented and effective in practice. If there are no major nonconformities, the certification body recommends certification and a three-year certificate is issued. Annual surveillance audits follow, with full recertification every three years.",[37,9789,9790,9791,9795,9796,9800],{},"For a deep walkthrough of every phase of the journey, including timelines, auditor expectations, and common pitfalls, see the ",[86,9792,9794],{"href":9793},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification process guide",". If you are still evaluating whether to pursue ISO 27001 at all, the ",[86,9797,9799],{"href":9798},"\u002Fnow\u002Fiso27001-certification-guide","ISO 27001 certification guide"," covers the business case and sequencing decisions.",[32,9802,9804],{"id":9803},"iso-270012022-what-changed","ISO 27001:2022 — What changed",[37,9806,9807],{},"The 2022 revision is the current version of the standard. Two changes matter most for teams implementing ISO 27001 today.",[37,9809,9810,9811,9814],{},"First, the control set was restructured. The 2013 edition had 114 controls across 14 domains. ISO 27001:2022 consolidates these into ",[52,9812,9813],{},"93 controls across four themes",": organizational (37 controls), people (8 controls), physical (14 controls), and technological (34 controls). Eleven entirely new controls were introduced, including threat intelligence, information security for cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering, and secure coding.",[37,9816,9817],{},"Second, the clause-level requirements in sections 4 through 10 received targeted updates around planning, leadership commitment, and operational control. The Plan-Do-Check-Act structure remains, but the language is tighter and more aligned with other ISO management system standards such as ISO 9001 and ISO 14001. Organizations holding ISO 27001:2013 certificates were given a transition window, and most have now migrated. New certifications are assessed exclusively against ISO 27001:2022.",[32,9819,9821],{"id":9820},"annex-a-controls","Annex A controls",[37,9823,9824,9825,9828],{},"Annex A of ISO 27001 is the reference control set. The ",[86,9826,9827],{"href":3875},"93 Annex A controls"," are organized under the four themes described above and represent the universe of possible safeguards your ISMS might apply. Every control must be evaluated for applicability and either implemented or formally excluded with justification.",[37,9830,9831],{},"Organizational controls cover governance, policy, third-party management, incident response, and business continuity. People controls address screening, training, responsibilities, and remote working. Physical controls protect buildings, equipment, and storage media. Technological controls handle access control, cryptography, logging, vulnerability management, secure development, and cloud security.",[37,9833,9834,9835,9839],{},"For a full breakdown of every theme, example controls in each, and how to prioritize implementation, see the ",[86,9836,9838],{"href":9837},"\u002Fframeworks\u002Fiso27001\u002Fannex-a-controls","ISO 27001 Annex A controls reference",". ISO 27002:2022 provides detailed implementation guidance for each control and is invaluable as a companion reference, though it is not mandatory to follow prescriptively.",[32,9841,9843],{"id":9842},"statement-of-applicability-soa","Statement of Applicability (SoA)",[37,9845,9846,9847,9851],{},"The ",[86,9848,9850],{"href":9849},"\u002Fglossary\u002Fstatement-of-applicability","Statement of Applicability"," is arguably the single most important document in your ISO 27001 program. The SoA lists every Annex A control, records whether it is applicable to your ISMS, explains why, and summarizes how the control is implemented. It is the document auditors will open first, and it is the document customers may ask to see.",[37,9853,9854],{},"A well-built SoA ties directly to your risk assessment output. Controls are marked applicable because they treat identified risks, satisfy legal or contractual requirements, or reflect business decisions. Controls marked not applicable require a short but credible justification. Auditors routinely sample SoA entries during Stage 2 and ask for corresponding evidence.",[37,9856,9857,9858,9862],{},"See the dedicated guide on the ",[86,9859,9861],{"href":9860},"\u002Fframeworks\u002Fiso27001\u002Fstatement-of-applicability","ISO 27001 Statement of Applicability"," for format examples, justification patterns, and common SoA mistakes.",[32,9864,9866],{"id":9865},"building-your-isms","Building your ISMS",[37,9868,9869],{},"Implementing ISO 27001 is primarily an exercise in building a functioning ISMS. The standard walks through this in clauses 4 through 10:",[92,9871,9872,9878,9884,9890,9896,9902,9908],{},[95,9873,9874,9877],{},[52,9875,9876],{},"Clause 4 — Context of the organization."," Understand internal and external issues, interested parties, and define the ISMS scope.",[95,9879,9880,9883],{},[52,9881,9882],{},"Clause 5 — Leadership."," Top management must demonstrate commitment, approve the information security policy, and assign roles.",[95,9885,9886,9889],{},[52,9887,9888],{},"Clause 6 — Planning."," Identify risks and opportunities, set information security objectives, and plan how to achieve them.",[95,9891,9892,9895],{},[52,9893,9894],{},"Clause 7 — Support."," Provide resources, competence, awareness, communication, and documented information.",[95,9897,9898,9901],{},[52,9899,9900],{},"Clause 8 — Operation."," Execute the risk assessment and risk treatment process and operate the ISMS on an ongoing basis.",[95,9903,9904,9907],{},[52,9905,9906],{},"Clause 9 — Performance evaluation."," Monitor, measure, analyze, evaluate, conduct internal audits, and hold management reviews.",[95,9909,9910,9913],{},[52,9911,9912],{},"Clause 10 — Improvement."," Handle nonconformities and drive continual improvement.",[37,9915,9916,9917,9921],{},"Each clause has mandatory documented information and mandatory activities. The ",[86,9918,9920],{"href":9919},"\u002Fframeworks\u002Fiso27001\u002Fisms-implementation","ISO 27001 ISMS implementation guide"," breaks down exactly what to produce at each stage.",[37,9923,9924,9925,9929],{},"Scope definition deserves special attention. A scope that is too narrow can fail to satisfy customers. A scope that is too broad inflates audit cost and implementation effort. The ",[86,9926,9928],{"href":9927},"\u002Fframeworks\u002Fiso27001\u002Fisms-scope","ISMS scope"," guide walks through how to draw the right boundaries for your business.",[32,9931,9933],{"id":9932},"iso-27001-risk-assessment","ISO 27001 risk assessment",[37,9935,9936],{},"Risk assessment is the engine that drives control selection in ISO 27001. The standard requires a documented, repeatable methodology. Most organizations use a qualitative or semi-quantitative approach that evaluates likelihood and impact across confidentiality, integrity, and availability. ISO 27005 provides detailed guidance but is not mandatory.",[37,9938,9939],{},"Outputs of the risk assessment feed directly into the risk treatment plan, which in turn feeds the Statement of Applicability. This chain is why ISO 27001 auditors spend significant time tracing from a risk to a treatment decision to a control to evidence of operation. Break this chain and you create nonconformities.",[37,9941,9942,9943,313],{},"For methodology, risk register structure, treatment options, and residual risk handling, see the ",[86,9944,9946],{"href":9945},"\u002Fframeworks\u002Fiso27001\u002Frisk-assessment","ISO 27001 risk assessment guide",[32,9948,9950],{"id":9949},"internal-audits-and-management-review","Internal audits and management review",[37,9952,9953],{},"Two activities inside Clause 9 are frequent failure points for first-time ISO 27001 certifiers. Clause 9.2 requires internal audits of the ISMS at planned intervals. Clause 9.3 requires a formal management review with defined inputs and outputs. Both must be complete before your Stage 2 audit.",[37,9955,9956],{},"Internal audits must cover every clause of ISO 27001 and every applicable Annex A control across your audit cycle. Auditors must be objective and impartial, which typically means the person who built a control cannot audit it. Findings must be documented, communicated, and tracked to closure.",[37,9958,9959,9960,9964,9965,313],{},"Management reviews force leadership engagement. Inputs include audit results, risk changes, nonconformities, and stakeholder feedback. Outputs include decisions on resources, improvement opportunities, and changes to the ISMS. Detailed coverage lives in the ",[86,9961,9963],{"href":9962},"\u002Fframeworks\u002Fiso27001\u002Finternal-audit","internal audit guide"," and the ",[86,9966,9968],{"href":9967},"\u002Fframeworks\u002Fiso27001\u002Fmanagement-review","management review guide",[32,9970,9972],{"id":9971},"nonconformities-and-corrective-action","Nonconformities and corrective action",[37,9974,9975],{},"When something in your ISMS does not meet ISO 27001 requirements, your own policies, or customer obligations, that is a nonconformity. Clauses 10.1 and 10.2 require you to react, contain the consequences, perform root cause analysis, implement corrective action, and verify effectiveness.",[37,9977,9978,9979,9983],{},"Mature organizations treat nonconformities as valuable signals rather than failures. The ",[86,9980,9982],{"href":9981},"\u002Fframeworks\u002Fiso27001\u002Fnonconformity-and-corrective-action","nonconformity and corrective action"," guide walks through the full CAPA workflow auditors expect to see.",[32,9985,9987],{"id":9986},"continual-improvement","Continual improvement",[37,9989,9990],{},"Clause 10.3 requires continual improvement of the suitability, adequacy, and effectiveness of the ISMS. This is not about constantly changing controls. It is about demonstrating measurable progress over time through metrics, KPIs, trend analysis, and lessons learned.",[37,9992,9993,9994,313],{},"Learn how to set ISMS metrics that auditors respect and leadership actually uses in the ",[86,9995,9997],{"href":9996},"\u002Fframeworks\u002Fiso27001\u002Fcontinual-improvement","continual improvement guide",[32,9999,10001],{"id":10000},"cost-and-timeline","Cost and timeline",[37,10003,10004],{},"ISO 27001 certification costs vary by scope, organization size, and maturity. A realistic budget range for a first-time certification at a small to mid-sized technology company looks like this:",[92,10006,10007,10013,10019,10025],{},[95,10008,10009,10012],{},[52,10010,10011],{},"Internal effort."," Six to twelve months of fractional time from an ISMS owner plus contributions from engineering, HR, legal, and IT. Equivalent fully loaded cost of $50,000 to $200,000.",[95,10014,10015,10018],{},[52,10016,10017],{},"External consulting (optional)."," Gap analysis and implementation support from a consultancy typically runs $20,000 to $100,000 depending on scope.",[95,10020,10021,10024],{},[52,10022,10023],{},"Certification body fees."," Stage 1 and Stage 2 audits combined usually cost $15,000 to $40,000. Annual surveillance audits run $8,000 to $20,000. Recertification in year three runs similar to the initial audit.",[95,10026,10027,10030],{},[52,10028,10029],{},"Platform and tooling."," GRC platforms like episki typically replace $30,000 or more in spreadsheet-driven consulting labor annually.",[37,10032,10033,10034,10037],{},"Total first-year ISO 27001 program cost for a 50 to 200 person company commonly lands between $60,000 and $150,000 all-in. Timeline from kickoff to certificate in hand is typically nine to fifteen months. See the ",[86,10035,10036],{"href":9793},"cost and timeline discussion in the certification process guide"," for more detail.",[32,10039,10041],{"id":10040},"choosing-a-certification-body","Choosing a certification body",[37,10043,10044],{},"Only an accredited certification body can issue a recognized ISO 27001 certificate. Accreditation is granted by national bodies such as UKAS in the United Kingdom, ANAB in the United States, and JAS-ANZ in Australia and New Zealand, all operating under the International Accreditation Forum (IAF). A certificate from a non-accredited body has little value with enterprise customers.",[37,10046,10047,10048,10052],{},"Selection criteria include accreditation scope, industry experience, auditor availability, geographic coverage, and cost transparency. The ",[86,10049,10051],{"href":10050},"\u002Fframeworks\u002Fiso27001\u002Fcertification-body-selection","certification body selection guide"," walks through the full evaluation.",[32,10054,10056],{"id":10055},"surveillance-audits-and-recertification","Surveillance audits and recertification",[37,10058,10059],{},"Once certified, your ISO 27001 certificate is valid for three years. Certification bodies conduct a lighter annual surveillance audit in years one and two to confirm the ISMS is still operating effectively. A full recertification audit occurs in year three. Nonconformities identified during surveillance can put your certificate at risk if not resolved within the specified timeframe.",[37,10061,10062,10063,10067],{},"See the ",[86,10064,10066],{"href":10065},"\u002Fframeworks\u002Fiso27001\u002Fsurveillance-audits","surveillance audits guide"," for preparation checklists and what auditors typically sample during year-one and year-two visits.",[32,10069,10071],{"id":10070},"iso-27001-vs-soc-2-vs-nist-csf","ISO 27001 vs SOC 2 vs NIST CSF",[37,10073,10074],{},"Customers and leadership teams frequently ask how ISO 27001 compares to other frameworks. The short version:",[92,10076,10077,10085],{},[95,10078,10079,10084],{},[52,10080,10081,10082,313],{},"ISO 27001 vs ",[86,10083,3864],{"href":3863}," ISO 27001 is an international certification of an ISMS. SOC 2 is a US-centric attestation of controls aligned with the AICPA Trust Services Criteria. SOC 2 produces a detailed report; ISO 27001 produces a certificate. SOC 2 is faster to complete and often preferred by US buyers. ISO 27001 is stronger for European customers and regulated industries. Many organizations run both, mapping controls once in a tool like episki.",[95,10086,10087,10090,10091,10095],{},[52,10088,10089],{},"ISO 27001 vs NIST CSF."," NIST CSF is a voluntary US framework structured around five functions: Identify, Protect, Detect, Respond, and Recover. It is not a certification. Organizations often use NIST CSF as a maturity assessment tool and ISO 27001 as the formal certification. The two map cleanly at the control level. See ",[86,10092,10094],{"href":10093},"\u002Fframeworks\u002Fnistcsf\u002Fmapping-to-other-frameworks","NIST CSF mapping to other frameworks"," for a side-by-side comparison.",[37,10097,10098,10099,10101],{},"If you are weighing which framework to pursue first, the ",[86,10100,9799],{"href":9798}," covers framework sequencing for growing companies.",[32,10103,10105],{"id":10104},"getting-certified-with-episki","Getting certified with episki",[37,10107,10108],{},"Most teams discover that ISO 27001 certification is less about security expertise and more about sustained, organized execution across months of risk assessments, control implementation, evidence collection, and documentation. Spreadsheet-based ISO 27001 programs tend to collapse under their own weight, especially when the certification cycle extends across surveillance audits and the 2022 transition creates additional documentation churn.",[37,10110,10111,10112,236,10116,10120],{},"episki was built to collapse that effort. The platform ships with the full 93-control Annex A library pre-mapped, automatic Statement of Applicability generation, a risk register tied to ISO 27005 treatment options, internal audit workflows, management review templates, and continuous evidence collection. Customers regularly compare episki against more established vendors; see ",[86,10113,10115],{"href":10114},"\u002Fcompare\u002Fvanta","episki vs Vanta",[86,10117,10119],{"href":10118},"\u002Fcompare\u002Fdrata","episki vs Drata"," for honest side-by-side views.",[37,10122,10123],{},"Teams using episki typically cut ISO 27001 preparation time by 60 percent compared to manual approaches and arrive at Stage 2 with a clean, auditor-ready evidence pack. Whether you are starting from zero or migrating an existing ISO 27001:2013 program to the 2022 standard, the platform scales with your scope.",[37,10125,10126],{},"Start a free trial, import your controls, and run your first ISO 27001 gap analysis in under an hour.",{"title":436,"searchDepth":437,"depth":437,"links":10128},[10129,10130,10131,10132,10133,10134,10135,10136,10137,10138,10139,10140,10141,10142,10143,10144],{"id":9746,"depth":437,"text":9747},{"id":9770,"depth":437,"text":9771},{"id":9783,"depth":437,"text":9784},{"id":9803,"depth":437,"text":9804},{"id":9820,"depth":437,"text":9821},{"id":9842,"depth":437,"text":9843},{"id":9865,"depth":437,"text":9866},{"id":9932,"depth":437,"text":9933},{"id":9949,"depth":437,"text":9950},{"id":9971,"depth":437,"text":9972},{"id":9986,"depth":437,"text":9987},{"id":10000,"depth":437,"text":10001},{"id":10040,"depth":437,"text":10041},{"id":10055,"depth":437,"text":10056},{"id":10070,"depth":437,"text":10071},{"id":10104,"depth":437,"text":10105},{"title":10146,"description":10147,"items":10148},"ISO 27001 certification checklist inside episki","Everything you need to scope, implement, and certify your ISMS is preloaded in your free trial.",[10149,10150,10151,10152,10153,10154,10155],"ISMS scope definition and context of the organization templates","Full Annex A control library with implementation guidance","Risk assessment and treatment plan workflows","Statement of Applicability generator","Internal audit programme with finding management","Management review agenda and output templates","Corrective action tracking with root cause analysis",{"title":10157,"description":10158},"Start your ISO 27001 journey today","Import your controls, define your ISMS scope, and generate your first Statement of Applicability in under an hour.",{"title":10160,"items":10161},"ISO 27001 frequently asked questions",[10162,10165,10168,10171,10174],{"label":10163,"content":10164},"How long does ISO 27001 certification take?","Most organizations achieve certification in 6-12 months depending on scope and existing maturity. The process includes a Stage 1 documentation review and a Stage 2 implementation audit. episki reduces preparation time by up to 60% with pre-mapped controls and automated evidence.",{"label":10166,"content":10167},"What is the difference between ISO 27001 and SOC 2?","ISO 27001 is an international certification standard focused on building a complete information security management system (ISMS). SOC 2 is a US-based attestation that evaluates specific Trust Services Criteria. Many companies pursue both, and episki lets you map controls once and reuse them across frameworks.",{"label":10169,"content":10170},"What is an ISMS?","An Information Security Management System (ISMS) is the set of policies, procedures, controls, and processes an organization uses to manage information security risk. ISO 27001 provides the framework for establishing, implementing, maintaining, and continually improving an ISMS.",{"label":10172,"content":10173},"How much does ISO 27001 certification cost?","Certification costs vary by organization size and scope but typically range from $30,000 to $80,000 including auditor fees, with ongoing surveillance audit costs annually. episki's flat-rate pricing keeps the platform cost predictable at $500\u002Fmonth.",{"label":10175,"content":10176},"How often are ISO 27001 surveillance audits?","After initial certification, surveillance audits occur annually to confirm your ISMS remains effective. A full recertification audit is required every three years. episki's continuous monitoring keeps evidence current between audits.",{"headline":10178,"title":10179,"description":10180,"links":10181},"ISO 27001 certification on your timeline","Build and maintain your ISMS without drowning in spreadsheets","episki maps Annex A controls, tracks your Statement of Applicability, and keeps risk treatment plans linked to real evidence so certification audits run smoothly.",[10182,10184],{"label":10183,"icon":493,"to":494},"Start ISO 27001 trial",{"label":496,"icon":497,"color":498,"variant":499,"to":500,"target":501},{},{"headline":10187,"title":10187,"description":10188,"items":10189},"ISO 27001 certification resources","Give leadership, auditors, and customers visibility into your ISMS maturity.",[10190,10193,10196],{"title":10191,"description":10192},"ISMS maturity dashboard","Visual progress across all Annex A domains with gap analysis and trending.",{"title":10194,"description":10195},"Auditor collaboration portal","Scoped access for certification bodies with evidence requests and Q&A threads.",{"title":10197,"description":10198},"Customer trust pack","Shareable ISO 27001 certification summary with scope details and control highlights.",{"title":10200,"description":10201},"ISO 27001 Compliance Platform","Build and certify your ISMS faster with episki. Annex A control mapping, SoA generation, and risk treatment plans in one workspace. Free 14-day trial.",[10203,10205,10208],{"value":9827,"description":10204},"Pre-mapped to your control graph with owners, evidence, and review cadences.",{"value":10206,"description":10207},"60% less prep","Average reduction in Stage 2 audit preparation time with episki's automation.",{"value":4742,"description":10209},"Surveillance audits stay painless with always-current evidence and risk registers.","5.frameworks\u002Fiso27001","aThn2G4vv-MUlfe5mhRJFQHtMgpdfJi3-UMVou77OZs",{"id":10213,"title":10214,"advantages":10215,"body":10237,"checklist":10762,"cta":10771,"description":436,"extension":467,"faq":10774,"hero":10791,"lastUpdated":502,"meta":10800,"name":155,"navigation":505,"path":154,"resources":10801,"seo":10814,"slug":2791,"stats":10817,"stem":10827,"__hash__":10828},"frameworks\u002F5.frameworks\u002Fnistcsf.md","Nistcsf",[10216,10223,10230],{"title":10217,"description":10218,"bullets":10219},"Tailored CSF roadmap","Start with opinionated baseline controls, then layer your own.",[10220,10221,10222],"Gap analysis highlights missing outcomes","Auto-generated improvement initiatives","Budget impact estimates for leadership",{"title":10224,"description":10225,"bullets":10226},"Continuous monitoring and AI ops","Stream alerts, detections, and incidents into CSF context.",[10227,10228,10229],"Connect SIEM, EDR, and cloud posture tools","AI summarizes incidents for exec updates","Workflows escalate unreviewed alerts",{"title":10231,"description":10232,"bullets":10233},"Board and customer alignment","Share progress externally with confidence.",[10234,10235,10236],"Customizable scorecards for customers or partners","Trend lines show quarter-over-quarter improvements","Trust room access with expiring links",{"type":29,"value":10238,"toc":10740},[10239,10243,10250,10253,10257,10264,10267,10271,10274,10284,10288,10291,10294,10333,10339,10343,10346,10349,10353,10362,10366,10375,10379,10388,10392,10401,10405,10414,10418,10427,10430,10434,10441,10467,10473,10477,10483,10486,10500,10503,10514,10518,10528,10545,10552,10556,10564,10570,10581,10585,10588,10635,10638,10642,10645,10677,10680,10683,10687,10690,10734,10737],[32,10240,10242],{"id":10241},"what-is-nist-csf","What is NIST CSF?",[37,10244,10245,10246,10249],{},"The NIST Cybersecurity Framework (NIST CSF) is a voluntary, outcome-based set of cybersecurity guidelines published by the ",[86,10247,10248],{"href":141},"National Institute of Standards and Technology",". The NIST Cybersecurity Framework gives organizations a shared vocabulary and a prioritized structure for managing cybersecurity risk, measuring program maturity, and communicating security posture to executives, boards, regulators, customers, and insurers.",[37,10251,10252],{},"NIST CSF is not a certification, a control catalog, or a compliance standard. It is a framework — a model that organizes cybersecurity activities into functions, categories, and subcategories so that any organization can describe its current cybersecurity posture, describe its target cybersecurity posture, identify and prioritize opportunities for improvement, assess progress, and communicate cybersecurity risk in a consistent way. Because NIST CSF is technology- and sector-neutral, it has become one of the most widely adopted cybersecurity frameworks in the world, used by Fortune 500 companies, federal contractors, critical infrastructure operators, state and local governments, startups, nonprofits, and multinational enterprises.",[44,10254,10256],{"id":10255},"nist-origin-and-executive-order-13636","NIST origin and Executive Order 13636",[37,10258,10259,10260,10263],{},"The NIST Cybersecurity Framework was created in response to a growing wave of attacks against United States critical infrastructure. In February 2013, President Barack Obama signed ",[52,10261,10262],{},"Executive Order 13636 — Improving Critical Infrastructure Cybersecurity",", which directed NIST to work with industry, academia, and other government agencies to develop a voluntary cybersecurity framework for critical infrastructure operators. The executive order explicitly called for a flexible, repeatable, performance-based, and cost-effective approach that could scale from small municipal utilities to the largest financial institutions.",[37,10265,10266],{},"NIST published version 1.0 of the NIST Cybersecurity Framework in February 2014 after a year of public workshops, industry comment periods, and collaboration with more than three thousand individuals and organizations. The first version of NIST CSF introduced the five core functions — Identify, Protect, Detect, Respond, and Recover — along with the concept of framework profiles and implementation tiers. Even though NIST CSF was designed for critical infrastructure, organizations in every sector quickly adopted it because it filled a gap that prescriptive standards did not: a business-friendly model for talking about cybersecurity risk.",[44,10268,10270],{"id":10269},"the-evolution-of-nist-csf","The evolution of NIST CSF",[37,10272,10273],{},"In April 2018, NIST released NIST CSF version 1.1. This incremental update clarified existing guidance, added a new Supply Chain Risk Management category (ID.SC), improved the self-assessment language, and added authentication and identity proofing subcategories. NIST CSF 1.1 contained 108 subcategories grouped under 23 categories across the five functions, and it remained the dominant version of the NIST Cybersecurity Framework for six years.",[37,10275,10276,10277,10280,10281,10283],{},"In February 2024, NIST published ",[52,10278,10279],{},"NIST CSF 2.0"," — the first major revision of the NIST Cybersecurity Framework. NIST CSF 2.0 expanded the scope of the framework beyond critical infrastructure, added a brand-new sixth function called ",[52,10282,2672],{},", reorganized several categories, and introduced a richer set of implementation resources including quick-start guides, informative references, and community profiles.",[32,10285,10287],{"id":10286},"nist-csf-20-changes","NIST CSF 2.0 changes",[37,10289,10290],{},"The jump from NIST CSF 1.1 to NIST CSF 2.0 is the most significant update the NIST Cybersecurity Framework has ever received. The changes are not cosmetic — they reshape how organizations are expected to structure and govern their cybersecurity programs.",[37,10292,10293],{},"Highlights of NIST CSF 2.0:",[92,10295,10296,10302,10308,10314,10327],{},[95,10297,10298,10301],{},[52,10299,10300],{},"A sixth function — Govern (GV)"," — elevates cybersecurity governance from a sub-category under Identify to a standalone top-level function covering organizational context, risk management strategy, roles and responsibilities, policy, oversight, and cybersecurity supply chain risk management.",[95,10303,10304,10307],{},[52,10305,10306],{},"Explicit scope expansion"," — NIST CSF 2.0 applies to organizations of any size, sector, or maturity level, not just critical infrastructure. Small-business quick-start guides, community profiles, and sector-specific profiles make the NIST Cybersecurity Framework accessible to organizations that previously found NIST CSF 1.1 too enterprise-centric.",[95,10309,10310,10313],{},[52,10311,10312],{},"Stronger supply chain focus"," — GV.SC expands the NIST CSF treatment of third-party risk, supplier due diligence, and software supply chain security, reflecting the lessons of SolarWinds, Kaseya, Log4j, and MOVEit.",[95,10315,10316,10319,10320,10323,10324,10326],{},[52,10317,10318],{},"Improved implementation guidance"," — NIST CSF 2.0 ships with a companion CSF Reference Tool, searchable informative references mapping NIST CSF subcategories to ",[86,10321,10322],{"href":141},"NIST SP 800-53",", ISO 27001, CIS Controls, ",[86,10325,3864],{"href":3863},", and more.",[95,10328,10329,10332],{},[52,10330,10331],{},"Refreshed implementation tiers"," — the four-tier maturity model (Partial, Risk-Informed, Repeatable, Adaptive) now explicitly incorporates governance and supply chain considerations.",[37,10334,10335,10336,9399],{},"For a deep dive into every structural and categorical change between NIST CSF 1.1 and NIST CSF 2.0, see our ",[86,10337,10287],{"href":10338},"\u002Fframeworks\u002Fnistcsf\u002Fv2-changes",[32,10340,10342],{"id":10341},"the-six-core-functions-of-nist-csf-20","The six core functions of NIST CSF 2.0",[37,10344,10345],{},"The NIST Cybersecurity Framework organizes cybersecurity activity into a small number of top-level functions. NIST CSF 1.1 defined five functions; NIST CSF 2.0 defines six. Each function represents a category of outcomes that a mature cybersecurity program must deliver, and each function decomposes into categories and subcategories that describe the outcomes in progressively more specific terms.",[37,10347,10348],{},"The six NIST CSF 2.0 functions are:",[44,10350,10352],{"id":10351},"govern-gv","Govern (GV)",[37,10354,9846,10355,10357,10358,313],{},[52,10356,2672],{}," function — new in NIST CSF 2.0 — establishes, communicates, and monitors the organization's cybersecurity risk management strategy, expectations, and policy. Govern is the leadership and accountability layer of NIST CSF. It sits above the other five functions and informs everything the organization does to identify, protect, detect, respond, and recover. Deep dive: ",[86,10359,10361],{"href":10360},"\u002Fframeworks\u002Fnistcsf\u002Fgovern-function","NIST CSF Govern function",[44,10363,10365],{"id":10364},"identify-id","Identify (ID)",[37,10367,9846,10368,10370,10371,313],{},[52,10369,2680],{}," function develops an organizational understanding of cybersecurity risk to systems, people, assets, data, and capabilities. Identify is where you inventory what you have, understand the business context in which it operates, and decide what matters most. Without Identify, the rest of the NIST Cybersecurity Framework has nothing to act on. Deep dive: ",[86,10372,10374],{"href":10373},"\u002Fframeworks\u002Fnistcsf\u002Fidentify-function","NIST CSF Identify function",[44,10376,10378],{"id":10377},"protect-pr","Protect (PR)",[37,10380,9846,10381,10383,10384,313],{},[52,10382,2688],{}," function implements safeguards to ensure delivery of critical services and limit or contain the impact of cybersecurity events. Protect encompasses identity and access management, awareness and training, data security, information protection processes, maintenance, and protective technology. Deep dive: ",[86,10385,10387],{"href":10386},"\u002Fframeworks\u002Fnistcsf\u002Fprotect-function","NIST CSF Protect function",[44,10389,10391],{"id":10390},"detect-de","Detect (DE)",[37,10393,9846,10394,10396,10397,313],{},[52,10395,2696],{}," function develops and implements appropriate activities to identify the occurrence of a cybersecurity event in a timely manner. Detect covers continuous monitoring, anomaly analysis, and detection processes — the telemetry, alerting, and threat-hunting capabilities that surface attacks as they happen. Deep dive: ",[86,10398,10400],{"href":10399},"\u002Fframeworks\u002Fnistcsf\u002Fdetect-function","NIST CSF Detect function",[44,10402,10404],{"id":10403},"respond-rs","Respond (RS)",[37,10406,9846,10407,10409,10410,313],{},[52,10408,2704],{}," function contains activities to take action regarding a detected cybersecurity incident. Respond covers incident response planning, communications, analysis, containment, eradication, and lessons-learned improvements. A strong Respond capability is what separates a contained incident from a front-page breach. Deep dive: ",[86,10411,10413],{"href":10412},"\u002Fframeworks\u002Fnistcsf\u002Frespond-function","NIST CSF Respond function",[44,10415,10417],{"id":10416},"recover-rc","Recover (RC)",[37,10419,9846,10420,10422,10423,313],{},[52,10421,2712],{}," function contains activities to maintain plans for resilience and to restore any capabilities or services that were impaired due to a cybersecurity incident. Recover covers recovery planning, improvements, and communications. Recover is how organizations return to normal operations while capturing lessons learned to strengthen the program. Deep dive: ",[86,10424,10426],{"href":10425},"\u002Fframeworks\u002Fnistcsf\u002Frecover-function","NIST CSF Recover function",[37,10428,10429],{},"Together, the six NIST CSF functions describe the complete cybersecurity lifecycle. Mature organizations operate all six functions simultaneously and continuously, not in a linear sequence.",[32,10431,10433],{"id":10432},"nist-csf-implementation-tiers","NIST CSF implementation tiers",[37,10435,10436,10437,10440],{},"NIST CSF uses ",[52,10438,10439],{},"implementation tiers"," to describe the degree to which an organization's cybersecurity risk management practices exhibit the characteristics defined in the NIST Cybersecurity Framework. The four tiers are not a maturity scale in the traditional sense — NIST is careful to say that Tier 4 is not required for every organization. Instead, implementation tiers help organizations choose an appropriate level of rigor given their risk tolerance, mission, regulatory obligations, threat environment, and resources.",[92,10442,10443,10449,10455,10461],{},[95,10444,10445,10448],{},[52,10446,10447],{},"Tier 1 — Partial",": Cybersecurity risk management is ad hoc and reactive. Policies are informal, risk awareness is limited, and supply chain considerations are rarely formalized.",[95,10450,10451,10454],{},[52,10452,10453],{},"Tier 2 — Risk-Informed",": Risk management practices are approved by management but may not be established organization-wide. Cybersecurity activities consider organizational risk objectives.",[95,10456,10457,10460],{},[52,10458,10459],{},"Tier 3 — Repeatable",": Formal policies exist and are applied consistently. The organization has the people, processes, and tooling to operate the NIST Cybersecurity Framework repeatably.",[95,10462,10463,10466],{},[52,10464,10465],{},"Tier 4 — Adaptive",": The organization adapts its cybersecurity practices based on lessons learned, threat intelligence, and changes in the business environment. Cybersecurity risk management is part of the organizational culture.",[37,10468,10469,10470,9399],{},"For a complete walkthrough of each tier, including how to select a target tier and move between tiers, see our ",[86,10471,10433],{"href":10472},"\u002Fframeworks\u002Fnistcsf\u002Fimplementation-tiers",[32,10474,10476],{"id":10475},"nist-csf-framework-profiles","NIST CSF framework profiles",[37,10478,9259,10479,10482],{},[52,10480,10481],{},"framework profile"," is the unique alignment of NIST CSF functions, categories, and subcategories with the organization's business requirements, risk tolerance, and resources. Profiles are the tool that turns the NIST Cybersecurity Framework from a generic model into a specific plan for a specific organization.",[37,10484,10485],{},"NIST CSF supports two kinds of profiles:",[92,10487,10488,10494],{},[95,10489,9259,10490,10493],{},[52,10491,10492],{},"Current Profile"," describes the cybersecurity outcomes the organization is achieving today.",[95,10495,9259,10496,10499],{},[52,10497,10498],{},"Target Profile"," describes the cybersecurity outcomes the organization wants to achieve.",[37,10501,10502],{},"The gap between the Current Profile and the Target Profile becomes a prioritized roadmap: which NIST CSF subcategories need investment, in what order, and at what cost. Community profiles published by NIST (for small business, healthcare, financial services, manufacturing, and others) give organizations a head start by providing pre-built Target Profiles tailored to specific sectors.",[37,10504,10505,10506,10510,10511,313],{},"For a complete framework profiles walkthrough — including how to build your first profile, how to use community profiles, and how to link profiles to your ",[86,10507,10509],{"href":10508},"\u002Fglossary\u002Fcontrol-framework","control framework"," — see ",[86,10512,10476],{"href":10513},"\u002Fframeworks\u002Fnistcsf\u002Fframework-profiles",[32,10515,10517],{"id":10516},"nist-csf-categories-and-subcategories","NIST CSF categories and subcategories",[37,10519,10520,10521,236,10524,10527],{},"Below the function layer, NIST CSF decomposes cybersecurity activity into ",[52,10522,10523],{},"categories",[52,10525,10526],{},"subcategories",". Categories group related outcomes within a function (for example, Asset Management, Access Control, Continuous Monitoring), and subcategories express specific outcome statements that a mature program should achieve.",[92,10529,10530,10540],{},[95,10531,10532,10535,10536,10539],{},[52,10533,10534],{},"NIST CSF 1.1"," defined 23 categories and ",[52,10537,10538],{},"108 subcategories"," across the five original functions.",[95,10541,10542,10544],{},[52,10543,10279],{}," reorganized the catalog around six functions. The total number of subcategories in NIST CSF 2.0 was restructured (and slightly reduced after consolidation) to roughly 106, grouped under 22 categories, with Govern contributing six new categories of its own.",[37,10546,10547,10548,10551],{},"Every NIST CSF subcategory is written as an outcome — for example, \"PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization.\" NIST intentionally avoids prescribing specific technologies, controls, or implementation details. Instead, NIST CSF provides ",[52,10549,10550],{},"informative references"," that map each subcategory to specific controls in NIST SP 800-53, ISO 27001 Annex A, CIS Critical Security Controls, COBIT, and other authoritative sources. This outcome-first design is what makes NIST CSF work across industries, company sizes, and technology stacks.",[32,10553,10555],{"id":10554},"mapping-nist-csf-to-other-frameworks","Mapping NIST CSF to other frameworks",[37,10557,10558,10559,9380,10561,10563],{},"One of the most valuable properties of the NIST Cybersecurity Framework is its ability to act as a unifying layer across multiple compliance regimes. Organizations that need to satisfy ",[86,10560,3864],{"href":3863},[86,10562,2728],{"href":2727},", HIPAA, PCI DSS, GDPR, FedRAMP, CMMC, and NIST SP 800-171 at the same time can use NIST CSF as the \"Rosetta Stone\" that maps each requirement to a common set of outcomes.",[37,10565,10566,10567,10569],{},"For federal contractors in particular, NIST CSF acts as the governance umbrella above NIST SP 800-171 and ",[86,10568,504],{"href":149},", both of which are derived from the NIST family of publications. A NIST CSF Target Profile that references NIST SP 800-53 informative references can be reused — with minor adjustments — as an ISO 27001 Statement of Applicability, a SOC 2 Trust Services Criteria mapping, and a HIPAA Security Rule crosswalk.",[37,10571,10572,10573,10575,10576,10580],{},"For a detailed crosswalk between NIST CSF and the major compliance frameworks — including worked examples of how a single NIST CSF subcategory maps to multiple standards — see ",[86,10574,10555],{"href":10093},". If you are actively building that mapping into a live compliance program, our ",[86,10577,10579],{"href":10578},"\u002Fnow\u002Fnist-csf-mapping-compliance","NIST CSF mapping compliance"," guide walks through the operational mechanics.",[32,10582,10584],{"id":10583},"who-uses-nist-csf","Who uses NIST CSF?",[37,10586,10587],{},"The NIST Cybersecurity Framework started as a voluntary framework for United States critical infrastructure. A decade later, NIST CSF is used by:",[92,10589,10590,10596,10605,10611,10617,10623,10629],{},[95,10591,10592,10595],{},[52,10593,10594],{},"Critical infrastructure operators"," — energy, water, transportation, communications, healthcare, and financial services organizations that fall under the 16 critical infrastructure sectors originally targeted by Executive Order 13636.",[95,10597,10598,10601,10602,313],{},[52,10599,10600],{},"Federal agencies and federal contractors"," — Executive Order 13800 required federal agencies to use NIST CSF to manage cybersecurity risk. Agencies and their contractors routinely use NIST CSF alongside ",[86,10603,10604],{"href":149},"NIST SP 800-171 and the CMMC program",[95,10606,10607,10610],{},[52,10608,10609],{},"State, local, tribal, and territorial (SLTT) governments"," — many states have adopted NIST CSF as the baseline cybersecurity model for agencies and municipal systems.",[95,10612,10613,10616],{},[52,10614,10615],{},"Large enterprises"," — Fortune 500 companies use NIST CSF to communicate cybersecurity risk to boards, investors, insurers, and regulators.",[95,10618,10619,10622],{},[52,10620,10621],{},"Small and mid-sized businesses (SMBs)"," — especially after NIST CSF 2.0, which ships with SMB-specific quick-start guides and community profiles.",[95,10624,10625,10628],{},[52,10626,10627],{},"Non-US organizations"," — NIST CSF is widely used outside the United States as a practical cybersecurity model that complements ISO 27001 and other international standards.",[95,10630,10631,10634],{},[52,10632,10633],{},"Insurers and investors"," — cyber insurance carriers and private-equity diligence teams increasingly ask portfolio companies to report maturity against NIST CSF as evidence of disciplined cybersecurity risk management.",[37,10636,10637],{},"The common thread is that NIST CSF works for any organization that needs to manage cybersecurity risk and communicate that risk to non-technical stakeholders. That is essentially every organization.",[32,10639,10641],{"id":10640},"nist-csf-vs-nist-sp-800-53-vs-nist-sp-800-171","NIST CSF vs NIST SP 800-53 vs NIST SP 800-171",[37,10643,10644],{},"NIST publishes dozens of cybersecurity documents, and three of them — NIST CSF, NIST SP 800-53, and NIST SP 800-171 — are often confused. Here is how they differ and how they fit together.",[92,10646,10647,10657,10667],{},[95,10648,10649,10652,10653,10656],{},[52,10650,10651],{},"NIST CSF (Cybersecurity Framework)"," is an ",[52,10654,10655],{},"outcome-based framework",". It defines what cybersecurity outcomes to achieve (the subcategories) but does not tell you exactly how to achieve them. NIST CSF is voluntary, technology-neutral, and applies to any organization.",[95,10658,10659,10662,10663,10666],{},[52,10660,10661],{},"NIST SP 800-53 (Security and Privacy Controls for Information Systems and Organizations)"," is a comprehensive ",[52,10664,10665],{},"control catalog",". SP 800-53 contains more than one thousand security and privacy controls organized into families such as Access Control (AC), Audit and Accountability (AU), and System and Communications Protection (SC). NIST SP 800-53 is mandatory for US federal information systems under FISMA and the Risk Management Framework (RMF).",[95,10668,10669,10672,10673,10676],{},[52,10670,10671],{},"NIST SP 800-171 (Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations)"," is a ",[52,10674,10675],{},"derived subset"," of NIST SP 800-53 focused on protecting Controlled Unclassified Information (CUI) in nonfederal systems. SP 800-171 is mandatory for any organization that handles CUI on behalf of the federal government and forms the basis for CMMC.",[37,10678,10679],{},"The relationship between the three is straightforward: NIST CSF describes the outcomes, NIST SP 800-53 and NIST SP 800-171 describe the controls that deliver those outcomes, and the NIST CSF informative references tell you which 800-53 and 800-171 controls satisfy each NIST CSF subcategory. Organizations use NIST CSF to frame the strategy and use NIST SP 800-53 or NIST SP 800-171 to implement the controls.",[37,10681,10682],{},"Federal contractors that handle CUI will typically use all three: NIST CSF for executive communication and maturity scoring, NIST SP 800-171 as the binding control baseline, and NIST SP 800-53 as the deeper reference catalog.",[32,10684,10686],{"id":10685},"getting-started-with-nist-csf","Getting started with NIST CSF",[37,10688,10689],{},"Implementing the NIST Cybersecurity Framework does not require a multi-year consulting engagement. A typical first NIST CSF implementation follows a repeatable pattern:",[358,10691,10692,10698,10704,10710,10716,10722,10728],{},[95,10693,10694,10697],{},[52,10695,10696],{},"Scope and prioritize"," — decide which parts of the organization are in scope for this iteration of NIST CSF. Startups often scope the entire company. Enterprises may scope a business unit, a product line, or a critical system.",[95,10699,10700,10703],{},[52,10701,10702],{},"Build a Current Profile"," — score the organization's current performance against each NIST CSF subcategory. Be honest. Many organizations discover that half of their NIST CSF subcategories are informal or partially implemented.",[95,10705,10706,10709],{},[52,10707,10708],{},"Build a Target Profile"," — decide what level of NIST CSF maturity the organization needs. Community profiles and sector profiles published by NIST are excellent starting points.",[95,10711,10712,10715],{},[52,10713,10714],{},"Perform a gap analysis"," — the delta between Current and Target is your NIST CSF roadmap. Prioritize by business impact, risk, and cost.",[95,10717,10718,10721],{},[52,10719,10720],{},"Select implementation tiers"," — match each part of the program to an appropriate tier. Not every subcategory needs to be Tier 4.",[95,10723,10724,10727],{},[52,10725,10726],{},"Execute and measure"," — track initiatives, re-score the NIST CSF profile quarterly, and report progress to leadership.",[95,10729,10730,10733],{},[52,10731,10732],{},"Map to other frameworks"," — reuse the NIST CSF profile as the source of truth for SOC 2, ISO 27001, HIPAA, and CMMC evidence.",[37,10735,10736],{},"episki was built for exactly this workflow. episki turns NIST CSF into a live scorecard: you import or build a Current Profile, choose a Target Profile, and episki generates the initiatives, tasks, and evidence collection needed to close the gap — all mapped to your other frameworks automatically. If you are starting from scratch or migrating from NIST CSF 1.1 to NIST CSF 2.0, episki can help you skip the spreadsheet phase entirely.",[37,10738,10739],{},"Ready to operationalize the NIST Cybersecurity Framework? Start a trial, import your controls, and share a NIST CSF scorecard with leadership the same day.",{"title":436,"searchDepth":437,"depth":437,"links":10741},[10742,10746,10747,10755,10756,10757,10758,10759,10760,10761],{"id":10241,"depth":437,"text":10242,"children":10743},[10744,10745],{"id":10255,"depth":442,"text":10256},{"id":10269,"depth":442,"text":10270},{"id":10286,"depth":437,"text":10287},{"id":10341,"depth":437,"text":10342,"children":10748},[10749,10750,10751,10752,10753,10754],{"id":10351,"depth":442,"text":10352},{"id":10364,"depth":442,"text":10365},{"id":10377,"depth":442,"text":10378},{"id":10390,"depth":442,"text":10391},{"id":10403,"depth":442,"text":10404},{"id":10416,"depth":442,"text":10417},{"id":10432,"depth":437,"text":10433},{"id":10475,"depth":437,"text":10476},{"id":10516,"depth":437,"text":10517},{"id":10554,"depth":437,"text":10555},{"id":10583,"depth":437,"text":10584},{"id":10640,"depth":437,"text":10641},{"id":10685,"depth":437,"text":10686},{"title":10763,"description":10764,"items":10765},"NIST CSF launch guide","Use episki’s free trial to benchmark, prioritize, and communicate fast.",[10766,10767,10768,10769,10770],"Baseline maturity assessment","Control library mapped to CSF categories","Initiative tracker with due dates and owners","Risk register tied to CSF outcomes","Executive report template",{"title":10772,"description":10773},"See your NIST CSF score in episki","Start the trial, import controls, and share a scorecard the same day.",{"title":10775,"items":10776},"NIST CSF frequently asked questions",[10777,10779,10782,10785,10788],{"label":10242,"content":10778},"The NIST Cybersecurity Framework (CSF) is a voluntary framework published by the National Institute of Standards and Technology that helps organizations manage and reduce cybersecurity risk. It provides a common language for understanding, managing, and expressing cybersecurity risk through five core functions.",{"label":10780,"content":10781},"What is the difference between NIST CSF and ISO 27001?","NIST CSF is a voluntary, outcome-focused maturity framework that helps organizations assess and improve their cybersecurity posture. ISO 27001 is a certifiable standard requiring a formal ISMS. Many organizations use NIST CSF as an internal maturity model alongside ISO 27001 certification for external assurance.",{"label":10783,"content":10784},"Is NIST CSF mandatory?","NIST CSF is voluntary for most private-sector organizations but is mandatory for US federal agencies under Executive Order 13800. Many industries and regulators reference it as a best-practice baseline, and customers increasingly expect suppliers to demonstrate alignment.",{"label":10786,"content":10787},"What are the NIST CSF implementation tiers?","The four tiers describe the maturity of an organization's cybersecurity risk management. Tier 1 (Partial) is ad hoc and reactive. Tier 2 (Risk-Informed) has some risk awareness. Tier 3 (Repeatable) has formal policies. Tier 4 (Adaptive) continuously improves based on lessons learned and threat intelligence.",{"label":10789,"content":10790},"How does NIST CSF relate to other compliance frameworks?","NIST CSF maps to many standards including SOC 2, ISO 27001, HIPAA, and PCI DSS. Organizations use it as a unifying layer to identify control gaps and overlaps across multiple compliance requirements, reducing duplicate work when pursuing multiple frameworks.",{"headline":10792,"title":10793,"description":10794,"links":10795},"Measure security maturity","Operationalize NIST CSF across Identify, Protect, Detect, Respond, and Recover","episki translates CSF categories into action plans with real-time scoring and executive reporting.",[10796,10798],{"label":10797,"icon":493,"to":494},"Start NIST CSF trial",{"label":496,"icon":10799,"color":498,"variant":499,"to":500,"target":501},"i-lucide-presentation",{},{"headline":10802,"title":10802,"description":10803,"items":10804},"NIST CSF toolset","Everything you need to show measurable progress.",[10805,10808,10811],{"title":10806,"description":10807},"Quarterly business review pack","Slides with KPIs, upcoming initiatives, and resource needs.",{"title":10809,"description":10810},"Customer assurance brief","Explains how NIST CSF maps to their requirements.",{"title":10812,"description":10813},"Automation cookbook","Step-by-step instructions for connecting your tooling.",{"title":10815,"description":10816},"NIST CSF Framework Software","Operationalize NIST CSF with live maturity scoring, risk registers, and executive dashboards. Benchmark and improve your cybersecurity posture with episki.",[10818,10821,10824],{"value":10819,"description":10820},"Live maturity score","Automated scoring by category, tier, and business unit.",{"value":10822,"description":10823},"Unified risk register","Link risks to CSF categories with AI-prioritized remediation.",{"value":10825,"description":10826},"Executive-ready","Dashboards turn security work into business milestones.","5.frameworks\u002Fnistcsf","Doz-LVyeK9ESsWNopGw7Kjfzq0igBKQBgD_u17qdUwk",{"id":10830,"title":10831,"advantages":10832,"body":10854,"checklist":11269,"cta":11278,"description":436,"extension":467,"faq":11281,"hero":11299,"lastUpdated":502,"meta":11308,"name":3899,"navigation":505,"path":3898,"resources":11309,"seo":11322,"slug":4260,"stats":11325,"stem":11335,"__hash__":11336},"frameworks\u002F5.frameworks\u002Fpci.md","Pci",[10833,10840,10847],{"title":10834,"description":10835,"bullets":10836},"Cardholder data mapped","Visualize systems, networks, and data flows tied to each DSS requirement.",[10837,10838,10839],"Track segmentation documentation and approvals","Connect SIEM and log tools for retention evidence","Link vulnerability scans and pen tests to controls",{"title":10841,"description":10842,"bullets":10843},"Task orchestration for engineering","Send prioritized remediation tasks to Jira or Linear with context.",[10844,10845,10846],"Auto-created tickets with required evidence","SLA tracking ensures high-risk remediations close on time","Change management logs sync back automatically",{"title":10848,"description":10849,"bullets":10850},"QSA-ready collaboration","Centralize requests, walkthroughs, and findings with secure file sharing.",[10851,10852,10853],"QSA comments resolve next to each control","Expiring links for sensitive diagrams","Exportable ROC narrative drafts",{"type":29,"value":10855,"toc":11256},[10856,10860,10866,10869,10872,10876,10884,10970,10973,10977,10984,10988,11001,11005,11013,11066,11078,11082,11093,11096,11099,11103,11120,11124,11127,11164,11172,11176,11179,11183,11196,11200,11203,11253],[32,10857,10859],{"id":10858},"what-is-pci-dss","What is PCI DSS?",[37,10861,10862,10863,10865],{},"The Payment Card Industry Data Security Standard -- universally known as ",[86,10864,3899],{"href":6907}," -- is the global baseline for protecting payment card data. Any organization that stores, processes, or transmits cardholder data is expected to meet PCI DSS, from a mom-and-pop e-commerce store to a Fortune 500 retailer and every payment processor in between. PCI DSS exists because card data is one of the most monetizable targets on the internet, and a single breach can expose millions of account numbers, trigger steep fines, and end businesses. PCI DSS translates decades of hard-won lessons into a prescriptive framework that security, engineering, and finance teams can operationalize.",[37,10867,10868],{},"PCI DSS is maintained by the Payment Card Industry Security Standards Council (PCI SSC), an independent standards body founded in 2006 by the five major payment brands: Visa, Mastercard, American Express, Discover, and JCB. The PCI SSC writes and publishes the standard, accredits assessors and scanning vendors, and runs supporting programs such as PA-DSS (now replaced by the PCI Secure Software Standard) and P2PE. While the PCI SSC owns the standard itself, it does not enforce PCI DSS. Enforcement is delegated to the card brands, which in turn push obligations down through acquiring banks and payment processors to merchants and service providers. In practice, your acquirer is the entity that tells you which PCI DSS validation path you owe and what happens if you fail it.",[37,10870,10871],{},"PCI DSS emerged from a patchwork of brand-specific programs in the early 2000s, including Visa's Cardholder Information Security Program (CISP) and Mastercard's Site Data Protection (SDP). PCI DSS v1.0 launched in December 2004. PCI DSS v2.0 arrived in 2010, v3.0 in 2013, v3.1 in 2015, v3.2 in 2016, v3.2.1 in 2018, and the long-anticipated PCI DSS v4.0 in March 2022, followed by v4.0.1 clarifications in June 2024. Organizations have until March 31, 2025 to fully meet the new \"future-dated\" PCI DSS v4.0 requirements. Each revision tightens controls around emerging threats: phishing-resistant authentication, e-commerce script tampering, automated log review, and customized approaches for mature security programs.",[32,10873,10875],{"id":10874},"the-12-pci-dss-requirements","The 12 PCI DSS requirements",[37,10877,10878,10879,10883],{},"PCI DSS organizes technical and operational controls across twelve core requirements grouped into six objectives. The full set of PCI DSS requirements is detailed on the ",[86,10880,10882],{"href":10881},"\u002Fframeworks\u002Fpci\u002Frequirements","PCI DSS requirements page","; at a glance they are:",[358,10885,10886,10896,10902,10916,10922,10928,10934,10940,10946,10952,10958,10964],{},[95,10887,10888,10891,10892,313],{},[52,10889,10890],{},"Install and maintain network security controls"," -- firewalls and equivalent controls around the ",[86,10893,10895],{"href":10894},"\u002Fglossary\u002Fcardholder-data-environment","cardholder data environment",[95,10897,10898,10901],{},[52,10899,10900],{},"Apply secure configurations to all system components"," -- hardening standards, default credential elimination, and secure build baselines.",[95,10903,10904,10907,10908,10911,10912,10915],{},[52,10905,10906],{},"Protect stored account data"," -- encryption, truncation, hashing, or ",[86,10909,5485],{"href":10910},"\u002Fglossary\u002Ftokenization"," of the ",[86,10913,10914],{"href":6316},"PAN"," and prohibition on storing sensitive authentication data.",[95,10917,10918,10921],{},[52,10919,10920],{},"Protect cardholder data with strong cryptography during transmission"," over open, public networks.",[95,10923,10924,10927],{},[52,10925,10926],{},"Protect all systems and networks from malicious software"," -- anti-malware on in-scope systems and defenses against script-based threats.",[95,10929,10930,10933],{},[52,10931,10932],{},"Develop and maintain secure systems and software"," -- secure SDLC, patching, and vulnerability management for in-scope systems.",[95,10935,10936,10939],{},[52,10937,10938],{},"Restrict access to system components and cardholder data by business need to know"," -- least-privilege role design.",[95,10941,10942,10945],{},[52,10943,10944],{},"Identify users and authenticate access to system components"," -- unique IDs, strong authentication, and phishing-resistant MFA.",[95,10947,10948,10951],{},[52,10949,10950],{},"Restrict physical access to cardholder data"," -- physical security for facilities, media, and devices.",[95,10953,10954,10957],{},[52,10955,10956],{},"Log and monitor all access to system components and cardholder data"," -- centralized logging, daily review, and tamper protection.",[95,10959,10960,10963],{},[52,10961,10962],{},"Test security of systems and networks regularly"," -- ASV scans, internal scans, pen tests, and segmentation validation.",[95,10965,10966,10969],{},[52,10967,10968],{},"Support information security with organizational policies and programs"," -- governance, awareness, incident response, and third-party oversight.",[37,10971,10972],{},"Each PCI DSS requirement is broken into numbered sub-requirements with explicit testing procedures that an assessor follows line by line. The \"defined approach\" dictates specific controls; PCI DSS v4.0 also introduces a \"customized approach\" where mature organizations can meet a requirement's objective through alternative controls, documented in a controls matrix and targeted risk analysis.",[32,10974,10976],{"id":10975},"pci-dss-v40-changes","PCI DSS v4.0 changes",[37,10978,10979,10980,313],{},"PCI DSS v4.0 is the largest revision in more than a decade. Its headline shifts include a customized-approach validation path, mandatory multi-factor authentication for all access into the CDE, expanded requirements to detect and respond to e-commerce script tampering, targeted risk analyses replacing prescriptive frequencies, and stronger expectations for continuous security rather than point-in-time compliance. Several of the most material v4.0 controls became mandatory on March 31, 2025 after a two-year grace period. The full changelog, new testing procedures, and a migration checklist are covered in the ",[86,10981,10983],{"href":10982},"\u002Fframeworks\u002Fpci\u002Fv4-changes","PCI DSS v4.0 changes guide",[32,10985,10987],{"id":10986},"merchant-compliance-levels-1-4","Merchant compliance levels 1-4",[37,10989,10990,10991,10995,10996,11000],{},"Every merchant is assigned to one of four PCI DSS compliance levels based on annual card transaction volume across all channels. PCI DSS Level 1 covers merchants processing more than 6 million transactions per year and requires a formal Report on Compliance (ROC) signed by a ",[86,10992,10994],{"href":10993},"\u002Fglossary\u002Fqsa","QSA",". Level 2 covers 1-6 million transactions. Level 3 covers 20,000 to 1 million e-commerce transactions. Level 4 covers everything below those thresholds. Service providers have their own two-level structure. Your acquiring bank can also assign you a higher PCI DSS level at its discretion -- particularly after a breach. The ",[86,10997,10999],{"href":10998},"\u002Fframeworks\u002Fpci\u002Fcompliance-levels","PCI DSS compliance levels page"," breaks down every threshold by card brand and the validation path each level owes.",[32,11002,11004],{"id":11003},"self-assessment-questionnaires-saqs","Self-Assessment Questionnaires (SAQs)",[37,11006,11007,11008,11012],{},"Merchants and service providers that are not required to complete a full PCI DSS Report on Compliance validate using a ",[86,11009,11011],{"href":11010},"\u002Fglossary\u002Fsaq","Self-Assessment Questionnaire",", or SAQ. The PCI SSC publishes nine SAQ types, each tailored to a specific acceptance channel and technology profile:",[92,11014,11015,11021,11027,11033,11039,11045,11051,11057],{},[95,11016,11017,11020],{},[52,11018,11019],{},"SAQ A"," -- card-not-present merchants that fully outsource all cardholder data functions.",[95,11022,11023,11026],{},[52,11024,11025],{},"SAQ A-EP"," -- e-commerce merchants that partially outsource payment processing but host pages that could affect payment page security.",[95,11028,11029,11032],{},[52,11030,11031],{},"SAQ B"," -- merchants using only imprint machines or standalone dial-out terminals.",[95,11034,11035,11038],{},[52,11036,11037],{},"SAQ B-IP"," -- merchants using only standalone IP-connected POI devices.",[95,11040,11041,11044],{},[52,11042,11043],{},"SAQ C-VT"," -- merchants entering transactions into a virtual payment terminal.",[95,11046,11047,11050],{},[52,11048,11049],{},"SAQ C"," -- merchants with payment application systems connected to the internet.",[95,11052,11053,11056],{},[52,11054,11055],{},"SAQ P2PE"," -- merchants using PCI-listed point-to-point encryption solutions.",[95,11058,11059,236,11062,11065],{},[52,11060,11061],{},"SAQ D for Merchants",[52,11063,11064],{},"SAQ D for Service Providers"," -- the catch-all SAQs for entities that store cardholder data or do not qualify for a simpler SAQ.",[37,11067,11068,11069,9964,11073,11077],{},"Eligibility is narrow and precise. Picking the wrong SAQ is one of the most common PCI DSS mistakes -- and one that an acquiring bank or breach investigation can expose instantly. The ",[86,11070,11072],{"href":11071},"\u002Fframeworks\u002Fpci\u002Fself-assessment-questionnaire","SAQ reference",[86,11074,11076],{"href":11075},"\u002Fframeworks\u002Fpci\u002Fsaq-types-explained","SAQ types explained"," page walk through each SAQ's eligibility, question count, and typical pitfalls.",[32,11079,11081],{"id":11080},"cardholder-data-environment-cde-and-scoping","Cardholder data environment (CDE) and scoping",[37,11083,11084,11085,11087,11088,11092],{},"Every PCI DSS program begins with scoping. The ",[86,11086,10895],{"href":10894},", or CDE, is the set of people, processes, and technologies that store, process, or transmit cardholder data or sensitive authentication data, plus any system component that is connected to or could impact the security of those components. Determining what is in ",[86,11089,11091],{"href":11090},"\u002Fglossary\u002Fpci-scope","PCI scope"," is the single highest-leverage activity in a PCI DSS program -- it drives how many controls apply, how much evidence you collect, and how much your QSA engagement costs.",[37,11094,11095],{},"PCI DSS scoping has three categories: CDE systems that directly handle card data; connected-to systems that can route traffic to the CDE, authenticate CDE users, or otherwise interact with CDE components; and security-impacting systems that could affect CDE security even without direct connectivity (think SIEM, patch management, or anti-malware consoles). All three categories are in scope for PCI DSS.",[37,11097,11098],{},"Document your CDE with an annotated network diagram and a data-flow diagram for every payment channel. PCI DSS v4.0 makes these diagrams a requirement, not a nice-to-have, and your assessor will test them during every assessment.",[32,11100,11102],{"id":11101},"scope-reduction-strategies","Scope reduction strategies",[37,11104,11105,11106,11110,11111,11115,11116,11119],{},"Because PCI DSS obligations scale with the CDE, shrinking the CDE is the fastest way to cut PCI DSS cost and risk. Effective ",[86,11107,11109],{"href":11108},"\u002Fframeworks\u002Fpci\u002Fscope-reduction","PCI DSS scope reduction"," typically combines four levers: strong ",[86,11112,11114],{"href":11113},"\u002Fframeworks\u002Fpci\u002Fnetwork-segmentation","network segmentation"," that isolates the CDE onto dedicated VLANs with tightly controlled firewall rules; ",[86,11117,5485],{"href":11118},"\u002Fframeworks\u002Fpci\u002Ftokenization-vs-encryption"," that replaces stored PANs with non-sensitive surrogates; PCI-listed point-to-point encryption (P2PE) that removes in-store networks from PCI scope; and outsourcing card capture to a validated service provider so your systems never touch real card data. Layered correctly, these strategies can reduce a PCI DSS assessment from hundreds of in-scope systems to a handful.",[32,11121,11123],{"id":11122},"key-pci-dss-roles-qsas-asvs-and-isas","Key PCI DSS roles: QSAs, ASVs, and ISAs",[37,11125,11126],{},"Three accredited roles support every PCI DSS program:",[92,11128,11129,11143,11158],{},[95,11130,11131,11137,11138,11142],{},[52,11132,11133,11134,1083],{},"Qualified Security Assessors (",[86,11135,11136],{"href":10993},"QSAs"," -- individuals and firms certified by the PCI SSC to perform on-site PCI DSS assessments, produce the ROC, and sign the Attestation of Compliance. Selecting the right QSA shapes your PCI DSS experience for years; the ",[86,11139,11141],{"href":11140},"\u002Fframeworks\u002Fpci\u002Fqsa-selection","QSA selection guide"," covers how to evaluate firms, cost drivers, and red flags.",[95,11144,11145,11152,11153,11157],{},[52,11146,11147,11148,1083],{},"Approved Scanning Vendors (",[86,11149,11151],{"href":11150},"\u002Fglossary\u002Fasv","ASVs"," -- PCI SSC-approved firms that run the quarterly external vulnerability scans required by PCI DSS Requirement 11.3.2. The ",[86,11154,11156],{"href":11155},"\u002Fframeworks\u002Fpci\u002Fasv-program","ASV program guide"," covers vendor selection, scanning cadence, passing thresholds, and remediation workflows.",[95,11159,11160,11163],{},[52,11161,11162],{},"Internal Security Assessors (ISAs)"," -- employees who have completed PCI SSC training and can complete certain internal PCI DSS assessments or support a QSA engagement. ISAs are a cost-effective way to build PCI DSS capability inside large programs.",[37,11165,11166,11167,11171],{},"Penetration testing (Requirement 11.4) sits alongside ASV scanning and is a frequent source of PCI DSS findings. The ",[86,11168,11170],{"href":11169},"\u002Fframeworks\u002Fpci\u002Fpenetration-testing","PCI DSS penetration testing guide"," covers internal vs external scope, segmentation testing, and frequency.",[32,11173,11175],{"id":11174},"penalties-for-non-compliance","Penalties for non-compliance",[37,11177,11178],{},"PCI DSS is not law, but non-compliance carries material financial consequences. Acquirers can levy fines of $5,000 to $100,000 per month for PCI DSS violations, pass fines down to merchants, raise transaction fees, or revoke payment processing privileges outright. After a confirmed breach of card data, a merchant typically faces a forensic PFI investigation, card brand fines, assessments for fraud losses, reissuance costs for compromised cards, and mandatory Level 1 PCI DSS validation going forward. Regulators and state attorneys general may also get involved, and the organization almost always faces litigation. In short, PCI DSS fines are rarely the largest line item -- the true cost of a breach is reputational damage, customer churn, and the fully loaded cost of breach response.",[32,11180,11182],{"id":11181},"pci-dss-vs-other-frameworks","PCI DSS vs other frameworks",[37,11184,11185,11186,11190,11191,11195],{},"PCI DSS is narrower and more prescriptive than most security frameworks. ISO 27001 is a management-system standard focused on the process of running an ISMS; it tells you how to manage risk but does not specify controls the way PCI DSS does. SOC 2 is an attestation framework where you define your own controls against the Trust Services Criteria; PCI DSS prescribes them. HIPAA and HITECH cover protected health information, not cardholder data. NIST CSF and NIST SP 800-53 offer control catalogues and risk management guidance that many organizations map into their PCI DSS program, especially under the v4.0 customized approach. PCI DSS is also one of the few frameworks with ongoing external validation -- ASV scans every quarter, penetration tests at least annually, and a full assessment every year. For businesses in the ",[86,11187,11189],{"href":11188},"\u002Findustry\u002Ffinance","finance industry"," or running ",[86,11192,11194],{"href":11193},"\u002Findustry\u002Fecommerce","e-commerce"," platforms, PCI DSS almost always becomes the binding constraint that the rest of the security program organizes around.",[32,11197,11199],{"id":11198},"getting-pci-compliant","Getting PCI compliant",[37,11201,11202],{},"A typical path to PCI DSS compliance looks like this:",[358,11204,11205,11211,11217,11223,11229,11235,11241,11247],{},[95,11206,11207,11210],{},[52,11208,11209],{},"Define scope"," -- inventory every place card data lives, moves, or could move. Produce annotated network and data-flow diagrams.",[95,11212,11213,11216],{},[52,11214,11215],{},"Reduce scope"," -- apply segmentation, tokenization, P2PE, and outsourcing to shrink the CDE before assessment.",[95,11218,11219,11222],{},[52,11220,11221],{},"Select your validation path"," -- confirm your PCI DSS level with your acquirer and determine whether you owe a ROC or an SAQ.",[95,11224,11225,11228],{},[52,11226,11227],{},"Gap assess"," -- map your current controls to every applicable PCI DSS requirement and prioritize remediation.",[95,11230,11231,11234],{},[52,11232,11233],{},"Remediate and document"," -- close gaps, write the policies and procedures PCI DSS expects, and stand up the logging, monitoring, scanning, and testing programs.",[95,11236,11237,11240],{},[52,11238,11239],{},"Engage your QSA or ASV"," -- commission the ASV scans, book the penetration test, and (for Level 1) schedule your QSA engagement early enough to allow remediation cycles.",[95,11242,11243,11246],{},[52,11244,11245],{},"Validate and attest"," -- produce the ROC or SAQ plus Attestation of Compliance, and submit to your acquirer on the required cadence.",[95,11248,11249,11252],{},[52,11250,11251],{},"Operate continuously"," -- PCI DSS v4.0 expects continuous monitoring, targeted risk analyses, and evidence that controls stay effective between assessments.",[37,11254,11255],{},"episki automates the bulk of the evidence collection, control testing, and QSA collaboration work so your PCI DSS program is audit-ready year-round instead of scrambling at the end of each cycle. If you are starting a new PCI DSS program or rebuilding an existing one, episki can shorten your path from scoping through Report on Compliance.",{"title":436,"searchDepth":437,"depth":437,"links":11257},[11258,11259,11260,11261,11262,11263,11264,11265,11266,11267,11268],{"id":10858,"depth":437,"text":10859},{"id":10874,"depth":437,"text":10875},{"id":10975,"depth":437,"text":10976},{"id":10986,"depth":437,"text":10987},{"id":11003,"depth":437,"text":11004},{"id":11080,"depth":437,"text":11081},{"id":11101,"depth":437,"text":11102},{"id":11122,"depth":437,"text":11123},{"id":11174,"depth":437,"text":11175},{"id":11181,"depth":437,"text":11182},{"id":11198,"depth":437,"text":11199},{"title":11270,"description":11271,"items":11272},"PCI DSS playbook","Follow structured milestones from scoping through ROC submission.",[11273,11274,11275,11276,11277],"Automated scope confirmation questionnaires","Connector-backed logging and monitoring checks","Quarterly vulnerability and penetration testing tracker","Change-management evidence capture","ROC narrative template and artifact index",{"title":11279,"description":11280},"Keep PCI DSS audit-ready around the clock","Spin up your trial, sync evidence, and invite your QSA in a single day.",{"title":11282,"items":11283},"PCI DSS frequently asked questions",[11284,11287,11290,11293,11296],{"label":11285,"content":11286},"What are the PCI DSS compliance levels?","PCI DSS has four merchant levels based on annual transaction volume. Level 1 (over 6 million transactions) requires a formal Report on Compliance by a QSA. Levels 2-4 may self-assess using the appropriate Self-Assessment Questionnaire (SAQ). Service providers have two levels with different validation requirements.",{"label":11288,"content":11289},"What changed in PCI DSS 4.0?","PCI DSS 4.0 introduced a customized validation approach allowing organizations to meet objectives with alternative controls, expanded multi-factor authentication requirements, strengthened e-commerce and phishing protections, and added emphasis on continuous security rather than point-in-time compliance.",{"label":11291,"content":11292},"Who needs PCI DSS compliance?","Any organization that stores, processes, or transmits cardholder data must comply with PCI DSS. This includes merchants, payment processors, acquirers, issuers, and service providers. The scope is determined by your cardholder data environment (CDE).",{"label":11294,"content":11295},"How often is a PCI DSS assessment required?","PCI DSS assessments are required annually. Level 1 merchants and service providers must complete a formal assessment by a Qualified Security Assessor (QSA). Additionally, quarterly network vulnerability scans by an Approved Scanning Vendor (ASV) are required.",{"label":11297,"content":11298},"What is a cardholder data environment (CDE)?","The CDE includes all people, processes, and technologies that store, process, or transmit cardholder data or sensitive authentication data, plus any systems connected to those components. Accurate CDE scoping is the foundation of an efficient PCI DSS assessment.",{"headline":11300,"title":11301,"description":11302,"links":11303},"PCI controls that stay current","Keep PCI DSS requirements passing even as your CDE evolves","episki maps DSS requirements, automates testing, and keeps QSAs collaborating in one secure workspace.",[11304,11306],{"label":11305,"icon":493,"to":494},"Start PCI trial",{"label":496,"icon":11307,"color":498,"variant":499,"to":500,"target":501},"i-lucide-calendar",{},{"headline":11310,"title":11310,"description":11311,"items":11312},"PCI enablement kit","Give leadership, ops, and QSAs a single source of truth.",[11313,11316,11319],{"title":11314,"description":11315},"CDE architecture report","Share sanitized diagrams and segmentation notes with prospects.",{"title":11317,"description":11318},"Risk and remediation digest","Weekly summary of open items, owners, and due dates.",{"title":11320,"description":11321},"Assessor workspace","Prebuilt template keeps every requirement, artifact, and note aligned.",{"title":11323,"description":11324},"PCI DSS Compliance Tool","Automate PCI DSS evidence collection, manage QSA collaboration, and keep cardholder data controls current. Start your free 14-day trial with episki.",[11326,11329,11332],{"value":11327,"description":11328},"90% automation","Evidence coverage across access, logging, segmentation, and monitoring.",{"value":11330,"description":11331},"QSA portal","Scoped access keeps your assessor in sync without endless spreadsheets.",{"value":11333,"description":11334},"Weekly drift checks","Automated alerts highlight misconfigurations before audits.","5.frameworks\u002Fpci","wxvQHRYeBHEsDrDF1QZg43Nio6AvwX3DWW21RftBG2c",{"id":11338,"title":11339,"advantages":11340,"body":11362,"checklist":11869,"cta":11878,"description":436,"extension":467,"faq":11881,"hero":11898,"lastUpdated":502,"meta":11906,"name":11907,"navigation":505,"path":3863,"resources":11908,"seo":11920,"slug":4257,"stats":11923,"stem":11933,"__hash__":11934},"frameworks\u002F5.frameworks\u002Fsoc2.md","Soc2",[11341,11348,11355],{"title":11342,"description":11343,"bullets":11344},"Mapped once, reused forever","Applies Trust Service Criteria to your existing controls and keeps overlaps synced.",[11345,11346,11347],"Control graph highlights reuse across security, availability, and confidentiality","AI suggests narratives and testing procedures","Version history shows every update for auditors",{"title":11349,"description":11350,"bullets":11351},"Evidence organized by control","Upload and track screenshots, configs, and exports in a structured evidence locker.",[11352,11353,11354],"Organized screenshots, configs, and test exports","Alerting when evidence expires or SLAs slip","Immutable locker with reviewer threads",{"title":11356,"description":11357,"bullets":11358},"Auditor collaboration hub","Invite your auditor with scoped access and keep Q&A right next to each control.",[11359,11360,11361],"Bulk requests & fulfillment tracking","Redacted file sharing with access controls","One-click SOC 2 summaries for customers",{"type":29,"value":11363,"toc":11851},[11364,11368,11371,11379,11387,11393,11397,11400,11406,11412,11427,11431,11436,11440,11443,11447,11455,11459,11462,11466,11474,11478,11485,11489,11492,11495,11512,11520,11524,11531,11573,11576,11580,11583,11586,11624,11632,11636,11639,11695,11698,11702,11705,11712,11719,11726,11738,11746,11750,11758,11790,11793,11797,11800,11803,11841],[32,11365,11367],{"id":11366},"what-is-soc-2","What is SOC 2?",[37,11369,11370],{},"SOC 2 (System and Organization Controls 2) is an auditing standard developed by the American Institute of Certified Public Accountants (AICPA) that evaluates how a service organization manages customer data. A SOC 2 report is the de facto security credential for modern SaaS companies — enterprise buyers request it before signing, procurement teams rely on it during vendor reviews, and auditors consult it when assessing outsourced systems. Unlike a prescriptive standard, SOC 2 is principle-based. It does not tell you which tools to deploy; it tells you which outcomes you must demonstrate and leaves the implementation details to you.",[37,11372,11373,11374,11378],{},"SOC 2 evolved from SAS 70, an older attestation framework used primarily for financial reporting systems. As technology service providers increased their role in handling sensitive data, the AICPA introduced the SOC reporting suite. SOC 1 continued to address controls relevant to financial reporting. SOC 2 and SOC 3 shifted attention to information security, availability, and related commitments. Today, SOC 2 is issued under the AICPA's AT-C 105 and AT-C 205 attestation standards, following the ",[86,11375,11377],{"href":11376},"\u002Fglossary\u002Fssae-18","SSAE 18"," framework.",[37,11380,11381,11382,11386],{},"A SOC 2 engagement produces an opinion letter from a licensed CPA firm. That letter is the report buyers ask for. It documents the system under audit, the ",[86,11383,11385],{"href":11384},"\u002Fframeworks\u002Fsoc2\u002Ftrust-services-criteria","Trust Services Criteria"," selected, the controls in place, the testing the auditor performed, and any exceptions noted. A clean SOC 2 opinion signals to the market that a third party examined your controls and found them suitable — or in the case of Type II, found them operating effectively across a defined window.",[37,11388,11389,11390,11392],{},"SOC 2 is built on five ",[52,11391,11385],{},": security, availability, processing integrity, confidentiality, and privacy. Security is mandatory. The other four are optional and chosen based on your service commitments and customer expectations. Most first-time SOC 2 audits cover security alone or security plus one or two additional criteria. Scope expansion happens later, as the program matures.",[32,11394,11396],{"id":11395},"soc-2-type-i-vs-type-ii","SOC 2 Type I vs Type II",[37,11398,11399],{},"Every SOC 2 engagement is either Type I or Type II, and the difference matters.",[37,11401,9259,11402,11405],{},[52,11403,11404],{},"SOC 2 Type I"," report evaluates whether controls are suitably designed and implemented as of a single date. Think of it as a design review. The auditor confirms your policies exist, your technical controls are configured, and your processes are in place. Type I is the fastest path to a SOC 2 report and is useful when a deal is on the line, but it does not prove your controls work day after day.",[37,11407,9259,11408,11411],{},[52,11409,11410],{},"SOC 2 Type II"," report evaluates whether controls operated effectively across an observation period, typically three to twelve months. The auditor samples evidence from throughout the period — access reviews, change approvals, incident tickets, monitoring alerts — to confirm that controls were not just designed but consistently executed. Most enterprise buyers require a Type II, and many will not accept a Type I at all.",[37,11413,11414,11415,11419,11420,236,11424,313],{},"For a full comparison including cost benchmarks, observation period tradeoffs, and decision frameworks, see ",[86,11416,11418],{"href":11417},"\u002Fframeworks\u002Fsoc2\u002Ftype-1-vs-type-2","SOC 2 Type 1 vs Type 2",". Related glossary terms: ",[86,11421,11423],{"href":11422},"\u002Fglossary\u002Fsoc2-type-2","SOC 2 Type 2",[86,11425,11385],{"href":11426},"\u002Fglossary\u002Ftrust-services-criteria",[32,11428,11430],{"id":11429},"the-five-trust-services-criteria","The five Trust Services Criteria",[37,11432,9846,11433,11435],{},[86,11434,11385],{"href":11384}," define the principles your controls must satisfy. Each criterion addresses a different aspect of how a service organization protects and manages customer data.",[44,11437,11439],{"id":11438},"security-common-criteria-required","Security (Common Criteria) — required",[37,11441,11442],{},"The security criterion, also called the Common Criteria, is required for every SOC 2 engagement. It evaluates whether the system is protected against unauthorized access — both logical and physical. The Common Criteria are organized into nine categories (CC1 through CC9) that map to the COSO internal control framework and cover governance, communication, risk assessment, monitoring, access control, system operations, change management, and vendor risk. Every SOC 2 report includes testing against these categories.",[44,11444,11446],{"id":11445},"availability","Availability",[37,11448,11449,11450,11454],{},"The availability criterion applies when an organization commits to specific uptime levels or recovery capabilities. It covers environmental protections, capacity planning, disaster recovery, and incident management for availability-impacting events. If your product has published SLAs or customers rely on continuous uptime, include availability. Read the ",[86,11451,11453],{"href":11452},"\u002Fframeworks\u002Fsoc2\u002Favailability-criteria","availability criteria deep dive"," for common controls and implementation patterns.",[44,11456,11458],{"id":11457},"processing-integrity","Processing integrity",[37,11460,11461],{},"Processing integrity focuses on whether the system processes data completely, validly, accurately, timely, and with proper authorization. This criterion is relevant for platforms that perform calculations, process financial transactions, or transform customer data. It is less common in first-time SOC 2 audits but important for fintech, billing platforms, and data pipelines that customers rely on for operational decisions.",[44,11463,11465],{"id":11464},"confidentiality","Confidentiality",[37,11467,11468,11469,11473],{},"The confidentiality criterion addresses information designated as confidential — distinct from personal information. It covers data classification, access restrictions, encryption, and secure disposal of confidential data. If you handle intellectual property, business plans, or other sensitive non-personal information on behalf of clients, include confidentiality. See the ",[86,11470,11472],{"href":11471},"\u002Fframeworks\u002Fsoc2\u002Fconfidentiality-criteria","confidentiality criteria deep dive"," for details.",[44,11475,11477],{"id":11476},"privacy","Privacy",[37,11479,11480,11481,313],{},"The privacy criterion applies to personal information — data that can identify an individual. It evaluates whether your data practices match your stated privacy commitments across notice, choice, collection, use, retention, disclosure, security, and accuracy. Privacy aligns closely with regulations like GDPR and CCPA and is the most demanding criterion in terms of control coverage. For a full walkthrough, see the ",[86,11482,11484],{"href":11483},"\u002Fframeworks\u002Fsoc2\u002Fprivacy-criteria","privacy criteria deep dive",[32,11486,11488],{"id":11487},"who-needs-soc-2-compliance","Who needs SOC 2 compliance?",[37,11490,11491],{},"SOC 2 is not legally mandated, but the market treats it as a cost of doing business. Any SaaS company, cloud service provider, managed service provider, or data processor that handles customer data is a likely SOC 2 candidate. If your customers are businesses and their security teams will scrutinize your controls before signing, SOC 2 is almost certainly on your roadmap.",[37,11493,11494],{},"Companies typically pursue SOC 2 when one or more of the following is true:",[92,11496,11497,11500,11503,11506,11509],{},[95,11498,11499],{},"Enterprise prospects are asking for a report during procurement or vendor reviews.",[95,11501,11502],{},"Sales cycles are slowing because buyers are blocking deals on security questionnaires.",[95,11504,11505],{},"Existing customers are requesting a current SOC 2 report during annual reviews.",[95,11507,11508],{},"Investors or partners are asking about the company's security posture.",[95,11510,11511],{},"The business is entering regulated verticals like financial services, healthcare, or government.",[37,11513,11514,11515,11519],{},"Industries that almost always require SOC 2 from their vendors include financial services, healthcare, legal technology, HR technology, martech that handles PII, and any B2B SaaS selling into enterprise accounts. For SaaS companies specifically, SOC 2 has become table stakes — see ",[86,11516,11518],{"href":11517},"\u002Fnow\u002Fsoc2-for-saas","SOC 2 for SaaS"," for a deeper discussion.",[32,11521,11523],{"id":11522},"the-soc-2-audit-process-overview","The SOC 2 audit process overview",[37,11525,9846,11526,11530],{},[86,11527,11529],{"href":11528},"\u002Fframeworks\u002Fsoc2\u002Faudit-process","SOC 2 audit process"," follows a predictable sequence. Understanding each phase prevents surprises and helps you set realistic timelines with your team and auditor.",[358,11532,11533,11549,11555,11561,11567],{},[95,11534,11535,11538,11539,11543,11544,11548],{},[52,11536,11537],{},"Scoping and readiness assessment."," Define what systems and Trust Services Criteria are in scope, then perform a ",[86,11540,11542],{"href":11541},"\u002Fframeworks\u002Fsoc2\u002Freadiness-assessment","readiness assessment"," to compare current controls against ",[86,11545,11547],{"href":11546},"\u002Fframeworks\u002Fsoc2\u002Frequirements","SOC 2 requirements",". The output is a prioritized remediation plan.",[95,11550,11551,11554],{},[52,11552,11553],{},"Remediation."," Close the gaps identified during readiness. Common items include formalizing policies, enabling MFA everywhere, centralizing logging, documenting vendor risk processes, and running tabletop exercises.",[95,11556,11557,11560],{},[52,11558,11559],{},"Auditor selection."," SOC 2 audits must be performed by a CPA firm licensed to issue SOC reports. Request proposals from two to four firms, compare scope and pricing, and check references from similar companies.",[95,11562,11563,11566],{},[52,11564,11565],{},"Audit fieldwork."," For Type I, the auditor validates control design at a point in time. For Type II, the auditor samples evidence from across the observation period and tests operating effectiveness.",[95,11568,11569,11572],{},[52,11570,11571],{},"Report delivery and ongoing operation."," Once the report is issued, plan the next observation period so you maintain continuous coverage with no bridge gaps that buyers might question.",[37,11574,11575],{},"Most organizations complete their first Type I in three to six months and their first Type II in six to eighteen months, depending on starting maturity and observation period length.",[32,11577,11579],{"id":11578},"what-does-soc-2-cost","What does SOC 2 cost?",[37,11581,11582],{},"SOC 2 cost varies widely based on scope, starting maturity, and whether you pursue Type I, Type II, or both. Auditor fees are the largest line item, but they are not the only cost. You should budget for readiness consulting, compliance tooling, internal staff time, remediation work, and penetration testing.",[37,11584,11585],{},"Typical benchmarks for a first-time SOC 2 engagement:",[92,11587,11588,11594,11600,11606,11612,11618],{},[95,11589,11590,11593],{},[52,11591,11592],{},"Type I auditor fees",": $15,000 to $40,000",[95,11595,11596,11599],{},[52,11597,11598],{},"Type II auditor fees",": $25,000 to $80,000",[95,11601,11602,11605],{},[52,11603,11604],{},"Readiness consulting"," (optional): $10,000 to $40,000",[95,11607,11608,11611],{},[52,11609,11610],{},"Compliance platform",": $6,000 to $60,000 annually depending on vendor",[95,11613,11614,11617],{},[52,11615,11616],{},"Penetration testing",": $8,000 to $30,000 per test",[95,11619,11620,11623],{},[52,11621,11622],{},"Internal staff time",": 200 to 600 hours across the first cycle",[37,11625,11626,11627,11631],{},"Total first-year cost for most growth-stage SaaS companies lands between $40,000 and $200,000. See the full ",[86,11628,11630],{"href":11629},"\u002Fframeworks\u002Fsoc2\u002Fcost","SOC 2 cost breakdown"," for detailed ranges and cost-reduction strategies.",[32,11633,11635],{"id":11634},"common-soc-2-challenges","Common SOC 2 challenges",[37,11637,11638],{},"SOC 2 programs rarely fail because the audit is unfair. They fail because organizations underestimate the operational discipline required. The challenges show up in predictable places.",[92,11640,11641,11647,11653,11659,11665,11676,11686],{},[95,11642,11643,11646],{},[52,11644,11645],{},"Scope creep."," Teams add new systems mid-audit or expand Trust Services Criteria without revisiting the control set. Every addition extends timelines and evidence requirements.",[95,11648,11649,11652],{},[52,11650,11651],{},"Evidence gaps."," Screenshots expire. Configurations change. Ownership drifts between quarters. By the time the auditor asks, the evidence trail is broken.",[95,11654,11655,11658],{},[52,11656,11657],{},"Cross-team coordination."," SOC 2 touches engineering, IT, HR, legal, and finance. Without a single source of truth for control status, teams duplicate work or miss handoffs.",[95,11660,11661,11664],{},[52,11662,11663],{},"Policy drift."," Policies written for the audit do not match how the team actually operates. Auditors detect this quickly during interviews and walkthroughs.",[95,11666,11667,11670,11671,11675],{},[52,11668,11669],{},"Vendor oversight."," Third-party vendors handle critical data but are rarely monitored with the same rigor as internal systems. See ",[86,11672,11674],{"href":11673},"\u002Fframeworks\u002Fsoc2\u002Fvendor-management","vendor management"," for how to close this gap.",[95,11677,11678,11681,11682,11685],{},[52,11679,11680],{},"Change management."," Production changes bypass approval workflows, leaving no audit trail. ",[86,11683,8206],{"href":11684},"\u002Fframeworks\u002Fsoc2\u002Fchange-management"," is a frequent source of Type II exceptions.",[95,11687,11688,11691,11692,313],{},[52,11689,11690],{},"Incident response immaturity."," Teams have an incident response plan but have never tested it. Auditors look for evidence of real incidents handled end to end. See ",[86,11693,8362],{"href":11694},"\u002Fframeworks\u002Fsoc2\u002Fincident-response",[37,11696,11697],{},"A structured approach — mapping controls, evidence, and owners from day one — removes most of these friction points before they become audit findings.",[32,11699,11701],{"id":11700},"how-soc-2-compares-to-other-frameworks","How SOC 2 compares to other frameworks",[37,11703,11704],{},"SOC 2 is not the only security framework buyers may request. Understanding how SOC 2 relates to other standards helps you plan a cohesive compliance strategy rather than running parallel audits with overlapping work.",[37,11706,11707,11711],{},[52,11708,11709],{},[86,11710,2728],{"href":2727}," is an international certification focused on information security management systems. Unlike SOC 2, which produces an auditor's opinion letter, ISO 27001 results in a certificate issued by an accredited registrar. ISO 27001 is prescriptive about building an ISMS but the control set in Annex A overlaps heavily with the SOC 2 Common Criteria. Many mature companies pursue both and reuse evidence across them. ISO 27001 tends to be preferred by European and international buyers; SOC 2 is the North American standard.",[37,11713,11714,11718],{},[52,11715,11716],{},[86,11717,3885],{"href":3884}," is a US healthcare law that mandates specific safeguards for protected health information. HIPAA is a regulatory requirement rather than a voluntary attestation — there is no HIPAA certificate, but business associates and covered entities must comply. SOC 2 controls address many HIPAA administrative and technical safeguards, and a SOC 2 Type II report is often used as evidence of HIPAA compliance in vendor due diligence.",[37,11720,11721,11725],{},[52,11722,11723],{},[86,11724,3899],{"href":3898}," is the payment card industry's prescriptive standard for any organization that stores, processes, or transmits cardholder data. Unlike SOC 2, PCI DSS specifies exact controls down to firewall rules and encryption key rotation cadences. SOC 2 and PCI DSS share concepts like encryption, access control, and monitoring, but PCI DSS scope is narrower (cardholder data environment) and the requirements are more specific. Companies that process payments typically need both.",[37,11727,11728,9380,11731,11734,11735,11737],{},[52,11729,11730],{},"NIST Cybersecurity Framework",[52,11732,11733],{},"FedRAMP",", and ",[52,11736,504],{}," address additional specialized audiences — federal contractors, defense industrial base, and government-adjacent systems. These are out of scope for most commercial SaaS but worth mapping if your buyer base includes public sector.",[37,11739,11740,11741,11745],{},"If you are comparing SOC 2 tooling options, our ",[86,11742,11744],{"href":11743},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata comparison"," covers the leading compliance automation platforms.",[32,11747,11749],{"id":11748},"soc-2-readiness-checklist","SOC 2 readiness checklist",[37,11751,11752,11753,11757],{},"A readiness checklist keeps your team focused during the months before the audit begins. The ",[86,11754,11756],{"href":11755},"\u002Fframeworks\u002Fsoc2\u002Fchecklist","full SOC 2 checklist"," covers every category, but at a high level expect to address:",[92,11759,11760,11763,11766,11769,11772,11775,11778,11781,11784,11787],{},[95,11761,11762],{},"Governance and policies (information security policy, acceptable use, code of conduct)",[95,11764,11765],{},"Access control (SSO, MFA, role-based access, quarterly access reviews)",[95,11767,11768],{},"Change management (code review, deployment approvals, production change logs)",[95,11770,11771],{},"Vendor risk management (inventory, assessments, monitoring)",[95,11773,11774],{},"Incident response (documented plan, tested at least annually)",[95,11776,11777],{},"Business continuity and disaster recovery (plan with defined RPO\u002FRTO, tested)",[95,11779,11780],{},"Logging and monitoring (centralized logs, alerting, incident tickets)",[95,11782,11783],{},"Security awareness training (annual minimum, tracked completion)",[95,11785,11786],{},"HR controls (background checks, onboarding, offboarding, confidentiality agreements)",[95,11788,11789],{},"Risk assessment (annual risk review, risk register, treatment plans)",[37,11791,11792],{},"Most companies find that the readiness phase surfaces gaps they did not know existed. That is the point — better to discover them before the auditor arrives.",[32,11794,11796],{"id":11795},"getting-started-with-soc-2","Getting started with SOC 2",[37,11798,11799],{},"The best time to start a SOC 2 program is before the first buyer demands it. The second best time is now.",[37,11801,11802],{},"A reasonable starting sequence:",[358,11804,11805,11811,11817,11823,11829,11835],{},[95,11806,11807,11810],{},[52,11808,11809],{},"Pick your Trust Services Criteria."," Security is required. Add others only if you have customer commitments that map to them.",[95,11812,11813,11816],{},[52,11814,11815],{},"Decide Type I vs Type II."," If you need a report fast for a specific deal, start with Type I. If you have time and buyer pressure is general, skip straight to Type II.",[95,11818,11819,11822],{},[52,11820,11821],{},"Run a readiness assessment."," Either internally or with a consultant. The goal is a prioritized remediation list, not a polished report.",[95,11824,11825,11828],{},[52,11826,11827],{},"Remediate in priority order."," Address policy gaps, access control weaknesses, and logging first — these are the most common sources of findings.",[95,11830,11831,11834],{},[52,11832,11833],{},"Select an auditor."," Get proposals from two to four CPA firms. Check references from similar companies. Book early — good auditors are scheduled quarters in advance.",[95,11836,11837,11840],{},[52,11838,11839],{},"Operate, collect, and iterate."," Run your controls, collect evidence continuously, and prepare for fieldwork. Do not treat the audit as a one-time event.",[37,11842,11843,11844,731,11847,11850],{},"episki was built for exactly this journey. The platform maps your controls to Trust Services Criteria, automates evidence collection, tracks ownership across teams, and gives your auditor structured access when fieldwork begins. ",[86,11845,903],{"href":494,"rel":11846},[902],[86,11848,11849],{"href":500},"book a demo"," to see how SOC 2 looks with the scramble removed.",{"title":436,"searchDepth":437,"depth":437,"links":11852},[11853,11854,11855,11862,11863,11864,11865,11866,11867,11868],{"id":11366,"depth":437,"text":11367},{"id":11395,"depth":437,"text":11396},{"id":11429,"depth":437,"text":11430,"children":11856},[11857,11858,11859,11860,11861],{"id":11438,"depth":442,"text":11439},{"id":11445,"depth":442,"text":11446},{"id":11457,"depth":442,"text":11458},{"id":11464,"depth":442,"text":11465},{"id":11476,"depth":442,"text":11477},{"id":11487,"depth":437,"text":11488},{"id":11522,"depth":437,"text":11523},{"id":11578,"depth":437,"text":11579},{"id":11634,"depth":437,"text":11635},{"id":11700,"depth":437,"text":11701},{"id":11748,"depth":437,"text":11749},{"id":11795,"depth":437,"text":11796},{"title":11870,"description":11871,"items":11872},"SOC 2 readiness checklist inside episki","Everything is preloaded in your free trial so you can start assigning ownership and collecting proof immediately.",[11873,11874,11875,11876,11877],"Trust Service Criteria library with mapped controls","Policy templates and AI drafting assistant","Evidence library with structured ownership and review cadences","Emulated auditor workspace with sample requests","Customer-facing compliance portal template",{"title":11879,"description":11880},"Launch your SOC 2 workspace today","Import your controls, connect evidence, and invite your auditor in under an hour.",{"title":11882,"items":11883},"SOC 2 frequently asked questions",[11884,11887,11890,11893,11895],{"label":11885,"content":11886},"How long does a SOC 2 audit take?","A SOC 2 Type I audit typically takes 4-8 weeks of preparation plus the audit itself. Type II requires a 3-12 month observation period followed by the assessment. episki's automation can cut preparation time by up to 45 days.",{"label":11888,"content":11889},"What is the difference between SOC 2 Type I and Type II?","SOC 2 Type I evaluates whether controls are suitably designed at a single point in time. Type II tests whether those controls operated effectively over a sustained period, usually 3-12 months. Most enterprise buyers require a Type II report.",{"label":11891,"content":11892},"How much does SOC 2 compliance cost?","Total costs typically range from $20,000 to $100,000+ depending on scope, readiness, and auditor fees. episki covers the platform side at a flat $500\u002Fmonth with no per-seat charges, significantly reducing the software portion of that budget.",{"label":11488,"content":11894},"Any SaaS company, cloud service provider, or data processor handling customer data is a likely candidate. Enterprise buyers in financial services, healthcare, and technology frequently require a current SOC 2 report before signing contracts.",{"label":11896,"content":11897},"What are the SOC 2 Trust Services Criteria?","The five Trust Services Criteria are security (required), availability, processing integrity, confidentiality, and privacy. Security is mandatory for every SOC 2 audit; the other four are optional and selected based on the services you provide.",{"headline":11899,"title":11900,"description":11901,"links":11902},"SOC 2 without the scramble","Ship SOC 2 audits without slowing product velocity","episki maps Trust Service Criteria, automates evidence, and keeps auditors in sync so your team can focus on building.",[11903,11905],{"label":11904,"icon":493,"to":494},"Start SOC 2 trial",{"label":496,"icon":497,"color":498,"variant":499,"to":500,"target":501},{},"SOC 2 Type I\u002FII",{"headline":11909,"title":11909,"description":11910,"items":11911},"SOC 2 acceleration resources","Give execs and customers visibility into progress at every stage.",[11912,11914,11917],{"title":512,"description":11913},"Summaries translate control work into risk reduction and deals unlocked.",{"title":11915,"description":11916},"Sales enablement kit","SOC 2 FAQ answers and trust collateral ready for GTM teams.",{"title":11918,"description":11919},"Audit retro template","Capture what worked, track remediations, and prep the next period.",{"title":11921,"description":11922},"SOC 2 Compliance Software","Get SOC 2 Type I and Type II audit-ready faster with episki's automated controls, evidence tracking, and auditor collaboration. Start your free 14-day trial.",[11924,11927,11930],{"value":11925,"description":11926},"45 days faster","Average time saved reaching Type II readiness with episki’s automation.",{"value":11928,"description":11929},"120+ controls","Pre-mapped control narratives with owners, evidence, and review cadences.",{"value":11931,"description":11932},"100% coverage","Auditor portal with control health dashboards and SOC 2 exports.","5.frameworks\u002Fsoc2","bJbRF5XSL9ALksj1QWkHTg9lO2E2kfmot3QsCAz1naE",1778494662429]