[{"data":1,"prerenderedAt":13423},["ShallowReactive",2],{"\u002Fframeworks\u002Fnistcsf":3,"framework-hub-topics-nistcsf":665,"related-glossary-nistcsf":4392,"related-frameworks-nistcsf":10371},{"id":4,"title":5,"advantages":6,"body":28,"checklist":585,"cta":594,"description":561,"extension":597,"faq":598,"hero":615,"lastUpdated":631,"meta":632,"name":633,"navigation":634,"path":635,"resources":636,"seo":649,"slug":652,"stats":653,"stem":663,"__hash__":664},"frameworks\u002F5.frameworks\u002Fnistcsf.md","Nistcsf",[7,14,21],{"title":8,"description":9,"bullets":10},"Tailored CSF roadmap","Start with opinionated baseline controls, then layer your own.",[11,12,13],"Gap analysis highlights missing outcomes","Auto-generated improvement initiatives","Budget impact estimates for leadership",{"title":15,"description":16,"bullets":17},"Continuous monitoring and AI ops","Stream alerts, detections, and incidents into CSF context.",[18,19,20],"Connect SIEM, EDR, and cloud posture tools","AI summarizes incidents for exec updates","Workflows escalate unreviewed alerts",{"title":22,"description":23,"bullets":24},"Board and customer alignment","Share progress externally with confidence.",[25,26,27],"Customizable scorecards for customers or partners","Trend lines show quarter-over-quarter improvements","Trust room access with expiring links",{"type":29,"value":30,"toc":560},"minimark",[31,36,46,49,54,62,65,69,72,83,87,90,93,136,143,147,150,153,157,168,172,182,186,196,200,210,214,224,228,238,241,245,252,278,284,288,295,298,312,315,326,330,341,358,365,369,380,388,400,404,407,454,457,461,464,496,499,502,506,509,554,557],[32,33,35],"h2",{"id":34},"what-is-nist-csf","What is NIST CSF?",[37,38,39,40,45],"p",{},"The NIST Cybersecurity Framework (NIST CSF) is a voluntary, outcome-based set of cybersecurity guidelines published by the ",[41,42,44],"a",{"href":43},"\u002Fglossary\u002Fnist","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,47,48],{},"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.",[50,51,53],"h3",{"id":52},"nist-origin-and-executive-order-13636","NIST origin and Executive Order 13636",[37,55,56,57,61],{},"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 ",[58,59,60],"strong",{},"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,63,64],{},"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.",[50,66,68],{"id":67},"the-evolution-of-nist-csf","The evolution of NIST CSF",[37,70,71],{},"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,73,74,75,78,79,82],{},"In February 2024, NIST published ",[58,76,77],{},"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 ",[58,80,81],{},"Govern",", reorganized several categories, and introduced a richer set of implementation resources including quick-start guides, informative references, and community profiles.",[32,84,86],{"id":85},"nist-csf-20-changes","NIST CSF 2.0 changes",[37,88,89],{},"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,91,92],{},"Highlights of NIST CSF 2.0:",[94,95,96,103,109,115,130],"ul",{},[97,98,99,102],"li",{},[58,100,101],{},"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.",[97,104,105,108],{},[58,106,107],{},"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.",[97,110,111,114],{},[58,112,113],{},"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.",[97,116,117,120,121,124,125,129],{},[58,118,119],{},"Improved implementation guidance"," — NIST CSF 2.0 ships with a companion CSF Reference Tool, searchable informative references mapping NIST CSF subcategories to ",[41,122,123],{"href":43},"NIST SP 800-53",", ISO 27001, CIS Controls, ",[41,126,128],{"href":127},"\u002Fframeworks\u002Fsoc2","SOC 2",", and more.",[97,131,132,135],{},[58,133,134],{},"Refreshed implementation tiers"," — the four-tier maturity model (Partial, Risk-Informed, Repeatable, Adaptive) now explicitly incorporates governance and supply chain considerations.",[37,137,138,139,142],{},"For a deep dive into every structural and categorical change between NIST CSF 1.1 and NIST CSF 2.0, see our ",[41,140,86],{"href":141},"\u002Fframeworks\u002Fnistcsf\u002Fv2-changes"," guide.",[32,144,146],{"id":145},"the-six-core-functions-of-nist-csf-20","The six core functions of NIST CSF 2.0",[37,148,149],{},"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,151,152],{},"The six NIST CSF 2.0 functions are:",[50,154,156],{"id":155},"govern-gv","Govern (GV)",[37,158,159,160,162,163,167],{},"The ",[58,161,81],{}," 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: ",[41,164,166],{"href":165},"\u002Fframeworks\u002Fnistcsf\u002Fgovern-function","NIST CSF Govern function",".",[50,169,171],{"id":170},"identify-id","Identify (ID)",[37,173,159,174,177,178,167],{},[58,175,176],{},"Identify"," 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: ",[41,179,181],{"href":180},"\u002Fframeworks\u002Fnistcsf\u002Fidentify-function","NIST CSF Identify function",[50,183,185],{"id":184},"protect-pr","Protect (PR)",[37,187,159,188,191,192,167],{},[58,189,190],{},"Protect"," 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: ",[41,193,195],{"href":194},"\u002Fframeworks\u002Fnistcsf\u002Fprotect-function","NIST CSF Protect function",[50,197,199],{"id":198},"detect-de","Detect (DE)",[37,201,159,202,205,206,167],{},[58,203,204],{},"Detect"," 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: ",[41,207,209],{"href":208},"\u002Fframeworks\u002Fnistcsf\u002Fdetect-function","NIST CSF Detect function",[50,211,213],{"id":212},"respond-rs","Respond (RS)",[37,215,159,216,219,220,167],{},[58,217,218],{},"Respond"," 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: ",[41,221,223],{"href":222},"\u002Fframeworks\u002Fnistcsf\u002Frespond-function","NIST CSF Respond function",[50,225,227],{"id":226},"recover-rc","Recover (RC)",[37,229,159,230,233,234,167],{},[58,231,232],{},"Recover"," 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: ",[41,235,237],{"href":236},"\u002Fframeworks\u002Fnistcsf\u002Frecover-function","NIST CSF Recover function",[37,239,240],{},"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,242,244],{"id":243},"nist-csf-implementation-tiers","NIST CSF implementation tiers",[37,246,247,248,251],{},"NIST CSF uses ",[58,249,250],{},"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.",[94,253,254,260,266,272],{},[97,255,256,259],{},[58,257,258],{},"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.",[97,261,262,265],{},[58,263,264],{},"Tier 2 — Risk-Informed",": Risk management practices are approved by management but may not be established organization-wide. Cybersecurity activities consider organizational risk objectives.",[97,267,268,271],{},[58,269,270],{},"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.",[97,273,274,277],{},[58,275,276],{},"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,279,280,281,142],{},"For a complete walkthrough of each tier, including how to select a target tier and move between tiers, see our ",[41,282,244],{"href":283},"\u002Fframeworks\u002Fnistcsf\u002Fimplementation-tiers",[32,285,287],{"id":286},"nist-csf-framework-profiles","NIST CSF framework profiles",[37,289,290,291,294],{},"A ",[58,292,293],{},"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,296,297],{},"NIST CSF supports two kinds of profiles:",[94,299,300,306],{},[97,301,290,302,305],{},[58,303,304],{},"Current Profile"," describes the cybersecurity outcomes the organization is achieving today.",[97,307,290,308,311],{},[58,309,310],{},"Target Profile"," describes the cybersecurity outcomes the organization wants to achieve.",[37,313,314],{},"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,316,317,318,322,323,167],{},"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 ",[41,319,321],{"href":320},"\u002Fglossary\u002Fcontrol-framework","control framework"," — see ",[41,324,287],{"href":325},"\u002Fframeworks\u002Fnistcsf\u002Fframework-profiles",[32,327,329],{"id":328},"nist-csf-categories-and-subcategories","NIST CSF categories and subcategories",[37,331,332,333,336,337,340],{},"Below the function layer, NIST CSF decomposes cybersecurity activity into ",[58,334,335],{},"categories"," and ",[58,338,339],{},"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.",[94,342,343,353],{},[97,344,345,348,349,352],{},[58,346,347],{},"NIST CSF 1.1"," defined 23 categories and ",[58,350,351],{},"108 subcategories"," across the five original functions.",[97,354,355,357],{},[58,356,77],{}," 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,359,360,361,364],{},"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 ",[58,362,363],{},"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,366,368],{"id":367},"mapping-nist-csf-to-other-frameworks","Mapping NIST CSF to other frameworks",[37,370,371,372,374,375,379],{},"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 ",[41,373,128],{"href":127},", ",[41,376,378],{"href":377},"\u002Fframeworks\u002Fiso27001","ISO 27001",", 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,381,382,383,387],{},"For federal contractors in particular, NIST CSF acts as the governance umbrella above NIST SP 800-171 and ",[41,384,386],{"href":385},"\u002Fframeworks\u002Fcmmc\u002Fnist-800-171-mapping","CMMC",", 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,389,390,391,394,395,399],{},"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 ",[41,392,368],{"href":393},"\u002Fframeworks\u002Fnistcsf\u002Fmapping-to-other-frameworks",". If you are actively building that mapping into a live compliance program, our ",[41,396,398],{"href":397},"\u002Fnow\u002Fnist-csf-mapping-compliance","NIST CSF mapping compliance"," guide walks through the operational mechanics.",[32,401,403],{"id":402},"who-uses-nist-csf","Who uses NIST CSF?",[37,405,406],{},"The NIST Cybersecurity Framework started as a voluntary framework for United States critical infrastructure. A decade later, NIST CSF is used by:",[94,408,409,415,424,430,436,442,448],{},[97,410,411,414],{},[58,412,413],{},"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.",[97,416,417,420,421,167],{},[58,418,419],{},"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 ",[41,422,423],{"href":385},"NIST SP 800-171 and the CMMC program",[97,425,426,429],{},[58,427,428],{},"State, local, tribal, and territorial (SLTT) governments"," — many states have adopted NIST CSF as the baseline cybersecurity model for agencies and municipal systems.",[97,431,432,435],{},[58,433,434],{},"Large enterprises"," — Fortune 500 companies use NIST CSF to communicate cybersecurity risk to boards, investors, insurers, and regulators.",[97,437,438,441],{},[58,439,440],{},"Small and mid-sized businesses (SMBs)"," — especially after NIST CSF 2.0, which ships with SMB-specific quick-start guides and community profiles.",[97,443,444,447],{},[58,445,446],{},"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.",[97,449,450,453],{},[58,451,452],{},"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,455,456],{},"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,458,460],{"id":459},"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,462,463],{},"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.",[94,465,466,476,486],{},[97,467,468,471,472,475],{},[58,469,470],{},"NIST CSF (Cybersecurity Framework)"," is an ",[58,473,474],{},"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.",[97,477,478,481,482,485],{},[58,479,480],{},"NIST SP 800-53 (Security and Privacy Controls for Information Systems and Organizations)"," is a comprehensive ",[58,483,484],{},"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).",[97,487,488,491,492,495],{},[58,489,490],{},"NIST SP 800-171 (Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations)"," is a ",[58,493,494],{},"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,497,498],{},"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,500,501],{},"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,503,505],{"id":504},"getting-started-with-nist-csf","Getting started with NIST CSF",[37,507,508],{},"Implementing the NIST Cybersecurity Framework does not require a multi-year consulting engagement. A typical first NIST CSF implementation follows a repeatable pattern:",[510,511,512,518,524,530,536,542,548],"ol",{},[97,513,514,517],{},[58,515,516],{},"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.",[97,519,520,523],{},[58,521,522],{},"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.",[97,525,526,529],{},[58,527,528],{},"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.",[97,531,532,535],{},[58,533,534],{},"Perform a gap analysis"," — the delta between Current and Target is your NIST CSF roadmap. Prioritize by business impact, risk, and cost.",[97,537,538,541],{},[58,539,540],{},"Select implementation tiers"," — match each part of the program to an appropriate tier. Not every subcategory needs to be Tier 4.",[97,543,544,547],{},[58,545,546],{},"Execute and measure"," — track initiatives, re-score the NIST CSF profile quarterly, and report progress to leadership.",[97,549,550,553],{},[58,551,552],{},"Map to other frameworks"," — reuse the NIST CSF profile as the source of truth for SOC 2, ISO 27001, HIPAA, and CMMC evidence.",[37,555,556],{},"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,558,559],{},"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":561,"searchDepth":562,"depth":562,"links":563},"",2,[564,569,570,578,579,580,581,582,583,584],{"id":34,"depth":562,"text":35,"children":565},[566,568],{"id":52,"depth":567,"text":53},3,{"id":67,"depth":567,"text":68},{"id":85,"depth":562,"text":86},{"id":145,"depth":562,"text":146,"children":571},[572,573,574,575,576,577],{"id":155,"depth":567,"text":156},{"id":170,"depth":567,"text":171},{"id":184,"depth":567,"text":185},{"id":198,"depth":567,"text":199},{"id":212,"depth":567,"text":213},{"id":226,"depth":567,"text":227},{"id":243,"depth":562,"text":244},{"id":286,"depth":562,"text":287},{"id":328,"depth":562,"text":329},{"id":367,"depth":562,"text":368},{"id":402,"depth":562,"text":403},{"id":459,"depth":562,"text":460},{"id":504,"depth":562,"text":505},{"title":586,"description":587,"items":588},"NIST CSF launch guide","Use episki’s free trial to benchmark, prioritize, and communicate fast.",[589,590,591,592,593],"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":595,"description":596},"See your NIST CSF score in episki","Start the trial, import controls, and share a scorecard the same day.","md",{"title":599,"items":600},"NIST CSF frequently asked questions",[601,603,606,609,612],{"label":35,"content":602},"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":604,"content":605},"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":607,"content":608},"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":610,"content":611},"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":613,"content":614},"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":616,"title":617,"description":618,"links":619},"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.",[620,624],{"label":621,"icon":622,"to":623},"Start NIST CSF trial","i-lucide-rocket","https:\u002F\u002Fepiski.app\u002Fauth\u002Fregister",{"label":625,"icon":626,"color":627,"variant":628,"to":629,"target":630},"Book a demo","i-lucide-presentation","neutral","subtle","\u002Fdemo","_blank","2026-04-27",{},"NIST CSF",true,"\u002Fframeworks\u002Fnistcsf",{"headline":637,"title":637,"description":638,"items":639},"NIST CSF toolset","Everything you need to show measurable progress.",[640,643,646],{"title":641,"description":642},"Quarterly business review pack","Slides with KPIs, upcoming initiatives, and resource needs.",{"title":644,"description":645},"Customer assurance brief","Explains how NIST CSF maps to their requirements.",{"title":647,"description":648},"Automation cookbook","Step-by-step instructions for connecting your tooling.",{"title":650,"description":651},"NIST CSF Framework Software","Operationalize NIST CSF with live maturity scoring, risk registers, and executive dashboards. Benchmark and improve your cybersecurity posture with episki.","nistcsf",[654,657,660],{"value":655,"description":656},"Live maturity score","Automated scoring by category, tier, and business unit.",{"value":658,"description":659},"Unified risk register","Link risks to CSF categories with AI-prioritized remediation.",{"value":661,"description":662},"Executive-ready","Dashboards turn security work into business milestones.","5.frameworks\u002Fnistcsf","Doz-LVyeK9ESsWNopGw7Kjfzq0igBKQBgD_u17qdUwk",[666,968,1263,1722,2037,2331,2734,3187,3478,3756,4031],{"id":667,"title":668,"body":669,"description":937,"extension":597,"faq":938,"frameworkSlug":652,"lastUpdated":952,"meta":953,"navigation":634,"path":208,"relatedTerms":954,"relatedTopics":958,"seo":963,"stem":966,"__hash__":967},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fdetect-function.md","NIST CSF Detect Function",{"type":29,"value":670,"toc":926},[671,675,681,684,687,691,694,739,742,746,749,752,772,776,779,782,796,800,803,847,851,854,892,896,899,902,906,914],[32,672,674],{"id":673},"what-is-the-nist-csf-detect-function","What is the NIST CSF Detect function?",[37,676,159,677,680],{},[58,678,679],{},"Detect (DE) function"," develops and implements activities to identify the occurrence of a cybersecurity event in a timely manner. Detect is where the cybersecurity program proves it can see what is actually happening. No preventive control is perfect, and the gap between compromise and detection — dwell time — is one of the most decisive variables in the final impact of an attack. An adversary detected within hours is an incident; an adversary detected after six months is a breach.",[37,682,683],{},"Detect sits between Protect (the preventive function) and Respond (the reactive function). Telemetry from the platforms, identities, data stores, and networks protected in the Protect function flows into Detect, where continuous monitoring and event analysis turn raw signals into actionable alerts. Those alerts become the inputs to Respond.",[37,685,686],{},"Detect is also the function most likely to be measured badly. A detection program that produces thousands of alerts that nobody reads is not detecting anything; it is generating noise. Mature NIST CSF Detect programs are judged by mean time to detect (MTTD), true-positive rate, and coverage against relevant threat scenarios — not by alert volume.",[32,688,690],{"id":689},"how-detect-changed-in-nist-csf-20","How Detect changed in NIST CSF 2.0",[37,692,693],{},"NIST CSF 1.1 split the Detect function into three categories: Anomalies and Events (DE.AE), Security Continuous Monitoring (DE.CM), and Detection Processes (DE.DP). NIST CSF 2.0 consolidated these into two:",[695,696,697,713],"table",{},[698,699,700],"thead",{},[701,702,703,707,710],"tr",{},[704,705,706],"th",{},"Category",[704,708,709],{},"ID",[704,711,712],{},"Focus",[714,715,716,728],"tbody",{},[701,717,718,722,725],{},[719,720,721],"td",{},"Continuous Monitoring",[719,723,724],{},"DE.CM",[719,726,727],{},"Monitoring of networks, physical environments, personnel activity, and third parties",[701,729,730,733,736],{},[719,731,732],{},"Adverse Event Analysis",[719,734,735],{},"DE.AE",[719,737,738],{},"Analysis of anomalies, correlation across sources, and characterization of events",[37,740,741],{},"The old Detection Processes category (DE.DP) was partially folded into DE.AE and partially moved into the Govern function's oversight and improvement outcomes. The net effect is a cleaner distinction: DE.CM is the telemetry layer, DE.AE is the analysis layer, and governance of the detection program itself is handled through Govern.",[50,743,745],{"id":744},"continuous-monitoring-decm","Continuous Monitoring (DE.CM)",[37,747,748],{},"DE.CM covers the collection of telemetry and the continuous monitoring of the environment for cybersecurity-relevant signals. This includes monitoring of networks, endpoints, cloud services, applications, identities, physical environments, personnel activity, and third-party connections. DE.CM outcomes are usually measured in coverage: what percentage of the environment is visible, which assets or tiers of assets are blind spots, and whether critical logs are being retained for long enough to support Respond and Recover.",[37,750,751],{},"A healthy DE.CM program integrates logs from:",[94,753,754,757,760,763,766,769],{},[97,755,756],{},"Endpoints — EDR agents across workstations, servers, and mobile devices.",[97,758,759],{},"Identity providers — authentication logs, privileged access, federation, and token issuance events.",[97,761,762],{},"Cloud providers — control-plane audit logs, data-plane access logs, and configuration change logs.",[97,764,765],{},"Network — flow data, DNS logs, and network detection and response (NDR) sensors on segments where they are warranted.",[97,767,768],{},"Applications — application-layer logs for critical business systems.",[97,770,771],{},"Third parties — logs from managed service providers, SaaS vendors, and partners with privileged access.",[50,773,775],{"id":774},"adverse-event-analysis-deae","Adverse Event Analysis (DE.AE)",[37,777,778],{},"DE.AE takes the raw signals collected by DE.CM and turns them into characterized events. Analysts triage anomalies, correlate across sources, determine the scope and potential impact, and decide whether an event warrants escalation to the Respond function. DE.AE is where the real expertise lives. Signatures catch known-bad behavior; DE.AE analysis catches the variants, the novel techniques, and the low-and-slow activity that evades pure-signature detection.",[37,780,781],{},"Mature DE.AE practices include:",[94,783,784,787,790,793],{},[97,785,786],{},"Threat-informed detection engineering — mapping detection coverage to a threat model such as MITRE ATT&CK.",[97,788,789],{},"Purple-team exercises that test whether detections actually fire against realistic attack scenarios.",[97,791,792],{},"Documented triage runbooks that produce consistent decisions regardless of which analyst is on shift.",[97,794,795],{},"Feedback loops from Respond back to DE.AE — every incident becomes an opportunity to improve future detection.",[32,797,799],{"id":798},"implementation-guidance","Implementation guidance",[37,801,802],{},"A pragmatic sequence for standing up the Detect function:",[510,804,805,811,817,823,829,835,841],{},[97,806,807,810],{},[58,808,809],{},"Decide what must be detected."," Start from the prioritized risk register in the Identify function. Pick the top threat scenarios that matter most to the business — ransomware on critical systems, credential theft of privileged identities, exfiltration of regulated data — and design detection coverage to meet them.",[97,812,813,816],{},[58,814,815],{},"Centralize logs."," Choose a SIEM, a log analytics platform, or a managed detection service. What matters is that logs from endpoints, identities, and cloud control planes are collected, retained for a defined period, and searchable.",[97,818,819,822],{},[58,820,821],{},"Start with high-fidelity detections."," Identity-centric detections (impossible travel, MFA bypass, new admin creation, token theft indicators) and EDR-based detections tend to produce the highest signal-to-noise ratios. Expand from there.",[97,824,825,828],{},[58,826,827],{},"Write and test runbooks."," Every detection should have a runbook that tells an analyst how to triage it. Runbooks should be living documents updated after every incident.",[97,830,831,834],{},[58,832,833],{},"Tune continuously."," Alert fatigue kills detection programs. Measure false-positive rates and either tune, suppress, or remove noisy detections.",[97,836,837,840],{},[58,838,839],{},"Measure coverage against a framework."," Use MITRE ATT&CK or a similar model to track detection coverage over time. Coverage gaps become initiatives in the NIST CSF roadmap.",[97,842,843,846],{},[58,844,845],{},"Feed improvements back to Govern and Identify."," Detection findings often change the risk picture; that information belongs in the risk register and in leadership reporting.",[32,848,850],{"id":849},"common-challenges","Common challenges",[37,852,853],{},"Detect programs commonly hit these walls:",[94,855,856,862,868,874,880,886],{},[97,857,858,861],{},[58,859,860],{},"Tooling without tuning."," A SIEM deployed and left on defaults produces a flood of low-value alerts. Investment in detection engineering is non-negotiable.",[97,863,864,867],{},[58,865,866],{},"Coverage illusions."," Dashboards that count log sources ingested rather than relevant telemetry collected can create a false sense of coverage. Measure coverage against real threat scenarios, not against log volume.",[97,869,870,873],{},[58,871,872],{},"Logs that cannot be searched quickly."," Detection value evaporates if analysts cannot query logs in seconds. Storage architecture and retention policies matter as much as collection.",[97,875,876,879],{},[58,877,878],{},"Alert fatigue."," Analysts triaging hundreds of alerts per shift will miss the important ones. Suppress noise aggressively and treat alert volume as a defect metric, not a success metric.",[97,881,882,885],{},[58,883,884],{},"No purple-teaming."," Detections that have never been tested against realistic attack simulations often fail silently when a real attack occurs. Regular purple-team exercises validate that the detections actually work.",[97,887,888,891],{},[58,889,890],{},"Unclear escalation criteria."," Analysts need a clear rule for when an adverse event becomes an incident and handoff to the Respond function begins. Ambiguity here costs minutes that matter.",[32,893,895],{"id":894},"measuring-detect-outcomes","Measuring Detect outcomes",[37,897,898],{},"Mean time to detect (MTTD) is the headline metric for the NIST CSF Detect function, but MTTD alone can be misleading. A Detect program with excellent MTTD for commodity malware but no visibility into identity-based attacks is not actually strong. Mature Detect programs report a small portfolio of metrics: MTTD by scenario class, true-positive rate per detection, alert-to-escalation time, coverage of the MITRE ATT&CK tactics most relevant to the threat model, and percentage of incidents first detected by internal telemetry rather than by a third party or an affected customer. That last metric — internal-first detection rate — is often the most honest measure of Detect maturity.",[37,900,901],{},"Detect also benefits from ongoing threat intelligence integration. Intelligence about current adversary behavior, sector-specific threats, and software supply chain compromises should flow into the detection engineering backlog and update existing detections. Without this feedback loop, DE.CM coverage and DE.AE analytics slowly drift behind what attackers are actually doing.",[32,903,905],{"id":904},"how-episki-helps","How episki helps",[37,907,908,909,374,911,913],{},"episki connects directly to your identity provider, EDR, cloud accounts, and SIEM to measure DE.CM coverage and DE.AE performance as living metrics. Coverage gaps against the risk scenarios that matter most to the business become tracked initiatives with owners and due dates. Detection engineering improvements captured in one place are automatically reflected in the NIST CSF profile and in the corresponding ",[41,910,128],{"href":127},[41,912,378],{"href":377},", HIPAA, and PCI DSS controls. Leadership sees mean time to detect trending down quarter over quarter; practitioners see the concrete work that made it happen.",[37,915,916,917,922,923,167],{},"Ready to turn the NIST CSF Detect function into live, measurable operations? ",[41,918,921],{"href":623,"rel":919},[920],"nofollow","Start a trial"," or ",[41,924,925],{"href":629},"book a demo",{"title":561,"searchDepth":562,"depth":562,"links":927},[928,929,933,934,935,936],{"id":673,"depth":562,"text":674},{"id":689,"depth":562,"text":690,"children":930},[931,932],{"id":744,"depth":567,"text":745},{"id":774,"depth":567,"text":775},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":894,"depth":562,"text":895},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF Detect function — continuous monitoring, adverse event analysis, and detection processes that surface attacks in time to respond.",{"items":939},[940,943,946,949],{"label":941,"content":942},"What is the Detect function in NIST CSF?","The Detect function develops and implements activities to identify the occurrence of a cybersecurity event in a timely manner. Detect covers continuous monitoring, anomaly and event analysis, and the detection processes that turn telemetry into actionable alerts. Strong Detect shrinks dwell time — the gap between when an attacker gets in and when the organization notices.",{"label":944,"content":945},"How did the Detect function change in NIST CSF 2.0?","NIST CSF 2.0 consolidated the original three Detect categories (Anomalies and Events, Security Continuous Monitoring, Detection Processes) into two: Continuous Monitoring (DE.CM) and Adverse Event Analysis (DE.AE). The outcomes previously captured in Detection Processes were folded into DE.AE and the Govern function's oversight category.",{"label":947,"content":948},"What should Detect actually produce?","Detect should produce high-fidelity alerts that reach a human or automated responder within minutes and that clearly describe what happened, on which asset, affecting which data, with enough context to begin response. The measure of a healthy Detect program is mean time to detect (MTTD) and the ratio of true-positive to false-positive alerts.",{"label":950,"content":951},"Do small organizations need a SIEM to satisfy Detect?","Not necessarily. The NIST Cybersecurity Framework is outcome-based — Detect requires that cybersecurity events are identified in a timely manner, not that a specific tool is deployed. Small organizations can often meet early Detect maturity with cloud-native logging, endpoint detection and response (EDR), identity provider logs, and managed detection and response (MDR) services.","2026-04-16",{},[955,956,957],"continuous-monitoring","audit-trail","siem",[959,960,961,962],"protect-function","respond-function","govern-function","framework-profiles",{"title":964,"description":965},"NIST CSF Detect Function (DE): Categories, Subcategories, and Implementation","The NIST CSF Detect function finds cybersecurity events in time to act. Learn DE.CM and DE.AE, build continuous monitoring coverage, and tune detections for real outcomes.","5.frameworks\u002Fnistcsf\u002Fdetect-function","H0LVEtvNGPwmDYOsIoTCZVbzfCvU92sFePdfpUQ3bGw",{"id":969,"title":970,"body":971,"description":1249,"extension":597,"faq":1250,"frameworkSlug":652,"lastUpdated":952,"meta":1251,"navigation":634,"path":1252,"relatedTerms":1253,"relatedTopics":1255,"seo":1258,"stem":1261,"__hash__":1262},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Ffive-functions.md","NIST CSF Five Functions",{"type":29,"value":972,"toc":1225},[973,977,980,983,989,991,994,998,1004,1010,1016,1022,1028,1034,1038,1041,1043,1046,1049,1055,1061,1067,1073,1079,1085,1088,1091,1093,1096,1099,1105,1111,1117,1120,1123,1125,1128,1131,1137,1143,1149,1155,1161,1164,1167,1169,1172,1175,1181,1187,1193,1196,1199,1203,1206],[32,974,976],{"id":975},"the-core-of-the-nist-cybersecurity-framework","The core of the NIST Cybersecurity Framework",[37,978,979],{},"The NIST Cybersecurity Framework (CSF) organizes cybersecurity activities into five core functions: Identify, Protect, Detect, Respond, and Recover. These functions provide a high-level, strategic view of an organization's cybersecurity risk management lifecycle. They are not meant to be followed sequentially but rather operate concurrently and continuously as part of a mature security program.",[37,981,982],{},"The five functions apply to organizations of all sizes and across all industries. They serve as a common language for communicating cybersecurity posture to executives, boards, regulators, and technical teams. Each function breaks down into categories and subcategories that provide progressively more specific guidance.",[37,984,985,986,988],{},"Note that NIST CSF 2.0 introduced a sixth function, Govern, which is covered in the ",[41,987,86],{"href":141}," topic.",[32,990,171],{"id":170},[37,992,993],{},"The Identify function develops an organizational understanding of how to manage cybersecurity risk to systems, people, assets, data, and capabilities. Before you can protect anything, you must know what you have and what risks you face.",[50,995,997],{"id":996},"key-categories","Key categories",[37,999,1000,1003],{},[58,1001,1002],{},"Asset management (ID.AM)"," - Inventory and manage all physical devices, software platforms, data flows, and external information systems. You cannot protect assets you do not know exist. This includes hardware inventories, software bills of materials, data classification schemes, and mapping of information flows between systems.",[37,1005,1006,1009],{},[58,1007,1008],{},"Business environment (ID.BE)"," - Understand the organization's mission, objectives, stakeholders, and supply chain. Cybersecurity priorities should align with business goals and risk tolerance. This category ensures that security investments support the most critical business functions.",[37,1011,1012,1015],{},[58,1013,1014],{},"Governance (ID.GV)"," - Establish and maintain cybersecurity policies, roles, responsibilities, and coordination between internal and external stakeholders. Governance provides the management framework that directs all other cybersecurity activities.",[37,1017,1018,1021],{},[58,1019,1020],{},"Risk assessment (ID.RA)"," - Identify, analyze, and prioritize cybersecurity risks. This includes threat intelligence, vulnerability identification, likelihood and impact analysis, and risk determination. Risk assessments inform where to allocate resources for the greatest security benefit.",[37,1023,1024,1027],{},[58,1025,1026],{},"Risk management strategy (ID.RM)"," - Define risk tolerance and establish processes for managing risk on an ongoing basis. This includes policies for accepting, mitigating, transferring, or avoiding identified risks.",[37,1029,1030,1033],{},[58,1031,1032],{},"Supply chain risk management (ID.SC)"," - Identify, assess, and manage risks associated with third-party service providers, vendors, and supply chain partners. This category has grown in importance as organizations increasingly depend on external services and software.",[50,1035,1037],{"id":1036},"practical-application","Practical application",[37,1039,1040],{},"The Identify function should produce a comprehensive picture of your organization's cybersecurity posture. This includes a current asset inventory, a risk register prioritized by business impact, documented governance structures, and an understanding of your supply chain dependencies. This foundation enables informed decisions across all other functions.",[32,1042,185],{"id":184},[37,1044,1045],{},"The Protect function implements safeguards to ensure delivery of critical services and limit the impact of potential cybersecurity events. This is where preventive controls are designed and deployed.",[50,1047,997],{"id":1048},"key-categories-1",[37,1050,1051,1054],{},[58,1052,1053],{},"Identity management, authentication, and access control (PR.AC)"," - Manage credentials, implement multi-factor authentication, enforce least privilege, and control access to physical and logical assets. Access control is consistently one of the most critical protective measures across all compliance frameworks.",[37,1056,1057,1060],{},[58,1058,1059],{},"Awareness and training (PR.AT)"," - Ensure that personnel at all levels receive cybersecurity awareness training appropriate to their roles. Privileged users, executives, and third-party stakeholders each need tailored training programs.",[37,1062,1063,1066],{},[58,1064,1065],{},"Data security (PR.DS)"," - Protect data at rest and in transit through encryption, integrity checking, and data loss prevention mechanisms. This category covers the entire data lifecycle from creation through disposal.",[37,1068,1069,1072],{},[58,1070,1071],{},"Information protection processes and procedures (PR.IP)"," - Maintain and use security policies, baselines, and procedures that protect information and systems. This includes configuration management, change control, backup procedures, and incident response planning.",[37,1074,1075,1078],{},[58,1076,1077],{},"Maintenance (PR.MA)"," - Perform and log maintenance on organizational assets in a controlled manner. Remote maintenance must be approved, logged, and conducted using secure channels.",[37,1080,1081,1084],{},[58,1082,1083],{},"Protective technology (PR.PT)"," - Deploy technical security solutions including firewalls, intrusion prevention systems, endpoint protection, and security monitoring tools. Audit logs must be maintained and protected, and communications and control networks must be secured.",[50,1086,1037],{"id":1087},"practical-application-1",[37,1089,1090],{},"The Protect function translates risk assessments from the Identify function into concrete security controls. Effective protection requires layered defenses that address people (training), process (policies and procedures), and technology (security tools). No single control is sufficient -- defense in depth is the guiding principle.",[32,1092,199],{"id":198},[37,1094,1095],{},"The Detect function defines activities to identify the occurrence of a cybersecurity event in a timely manner. The speed of detection directly impacts the severity of a security incident.",[50,1097,997],{"id":1098},"key-categories-2",[37,1100,1101,1104],{},[58,1102,1103],{},"Anomalies and events (DE.AE)"," - Establish baselines of normal activity and detect deviations that may indicate malicious behavior. This includes analyzing event data from multiple sources, correlating events to identify patterns, and determining the impact of detected anomalies.",[37,1106,1107,1110],{},[58,1108,1109],{},"Security continuous monitoring (DE.CM)"," - Monitor information systems and assets at regular intervals to detect cybersecurity events and verify the effectiveness of protective measures. This encompasses network monitoring, physical environment monitoring, personnel activity monitoring, malicious code detection, unauthorized mobile code detection, and external service provider activity monitoring.",[37,1112,1113,1116],{},[58,1114,1115],{},"Detection processes (DE.DP)"," - Maintain and test detection processes and procedures to ensure awareness of anomalous events. Detection roles and responsibilities must be defined, detection activities must comply with applicable requirements, detection processes must be tested, and event detection information must be communicated to appropriate parties.",[50,1118,1037],{"id":1119},"practical-application-2",[37,1121,1122],{},"The Detect function relies heavily on technology solutions such as SIEM platforms, intrusion detection systems, endpoint detection and response (EDR) tools, and network traffic analysis. However, technology alone is insufficient. Organizations must define what constitutes normal activity, establish alert thresholds, create response playbooks for different detection scenarios, and regularly test their detection capabilities through exercises like red team engagements and tabletop exercises.",[32,1124,213],{"id":212},[37,1126,1127],{},"The Respond function defines activities to take action regarding a detected cybersecurity incident. A well-prepared response capability limits the damage of an incident and supports faster recovery.",[50,1129,997],{"id":1130},"key-categories-3",[37,1132,1133,1136],{},[58,1134,1135],{},"Response planning (RS.RP)"," - Develop and maintain incident response plans that are executed during and after an incident. Plans should be documented, assign roles and responsibilities, and be tested regularly through exercises.",[37,1138,1139,1142],{},[58,1140,1141],{},"Communications (RS.CO)"," - Coordinate response activities with internal and external stakeholders. This includes notifying affected parties, coordinating with law enforcement when appropriate, sharing information with ISACs and other intelligence sharing organizations, and managing public relations.",[37,1144,1145,1148],{},[58,1146,1147],{},"Analysis (RS.AN)"," - Investigate detected incidents to understand their scope, determine impact, and support forensic analysis. Notifications from detection systems must be investigated, the impact of the incident must be understood, and forensic evidence must be collected and preserved.",[37,1150,1151,1154],{},[58,1152,1153],{},"Mitigation (RS.MI)"," - Contain the incident to prevent expansion and mitigate its effects. This includes isolating affected systems, implementing temporary countermeasures, and addressing newly identified vulnerabilities.",[37,1156,1157,1160],{},[58,1158,1159],{},"Improvements (RS.IM)"," - Incorporate lessons learned from detection and response activities into future response plans and strategies. Post-incident reviews should identify what worked, what did not, and what changes are needed.",[50,1162,1037],{"id":1163},"practical-application-3",[37,1165,1166],{},"Effective incident response requires preparation long before an incident occurs. Organizations should maintain documented response plans, conduct tabletop exercises at least annually, establish communication templates for different incident types, maintain relationships with law enforcement and forensic firms, and test recovery procedures. The Respond function works hand-in-hand with the Detect function -- detection without response capability provides limited value.",[32,1168,227],{"id":226},[37,1170,1171],{},"The Recover function develops and implements activities to maintain plans for resilience and restore any capabilities or services that were impaired due to a cybersecurity incident.",[50,1173,997],{"id":1174},"key-categories-4",[37,1176,1177,1180],{},[58,1178,1179],{},"Recovery planning (RC.RP)"," - Develop and maintain recovery plans that are executed during and after an incident. Plans should address the restoration of systems, data, and operations to normal levels within defined recovery time objectives.",[37,1182,1183,1186],{},[58,1184,1185],{},"Improvements (RC.IM)"," - Incorporate lessons learned from recovery activities into updated recovery strategies. This creates a feedback loop that strengthens resilience over time.",[37,1188,1189,1192],{},[58,1190,1191],{},"Communications (RC.CO)"," - Manage public relations, repair reputational damage, and communicate recovery activities to internal and external stakeholders. Coordinated communication during recovery maintains trust with customers, partners, and regulators.",[50,1194,1037],{"id":1195},"practical-application-4",[37,1197,1198],{},"Recovery planning encompasses business continuity planning, disaster recovery procedures, data backup strategies, and communications planning. Organizations should define recovery time objectives (RTOs) and recovery point objectives (RPOs) for all critical systems, test backup restoration regularly, and maintain alternate processing capabilities for mission-critical services.",[32,1200,1202],{"id":1201},"how-the-five-functions-work-together","How the five functions work together",[37,1204,1205],{},"The five functions are not a linear sequence but a continuous cycle. Risk identification informs protective controls, protective controls support detection capabilities, detection triggers response, response enables recovery, and recovery feeds back into improved identification and protection.",[37,1207,1208,1209,1211,1212,1215,1216,1219,1220,1224],{},"Organizations using the NIST CSF should assess their maturity across all five functions using ",[41,1210,250],{"href":283}," and build ",[41,1213,1214],{"href":325},"framework profiles"," that capture their current and target states. The five functions also ",[41,1217,1218],{"href":393},"map to other frameworks"," like SOC 2, ISO 27001, and ",[41,1221,1223],{"href":1222},"\u002Fframeworks\u002Fpci","PCI DSS",", making them a useful organizing structure for organizations managing multiple compliance requirements.",{"title":561,"searchDepth":562,"depth":562,"links":1226},[1227,1228,1232,1236,1240,1244,1248],{"id":975,"depth":562,"text":976},{"id":170,"depth":562,"text":171,"children":1229},[1230,1231],{"id":996,"depth":567,"text":997},{"id":1036,"depth":567,"text":1037},{"id":184,"depth":562,"text":185,"children":1233},[1234,1235],{"id":1048,"depth":567,"text":997},{"id":1087,"depth":567,"text":1037},{"id":198,"depth":562,"text":199,"children":1237},[1238,1239],{"id":1098,"depth":567,"text":997},{"id":1119,"depth":567,"text":1037},{"id":212,"depth":562,"text":213,"children":1241},[1242,1243],{"id":1130,"depth":567,"text":997},{"id":1163,"depth":567,"text":1037},{"id":226,"depth":562,"text":227,"children":1245},[1246,1247],{"id":1174,"depth":567,"text":997},{"id":1195,"depth":567,"text":1037},{"id":1201,"depth":562,"text":1202},"A detailed exploration of the five core functions of the NIST Cybersecurity Framework -- Identify, Protect, Detect, Respond, and Recover.",null,{},"\u002Fframeworks\u002Fnistcsf\u002Ffive-functions",[1254],"grc",[1256,962,1257],"implementation-tiers","v2-changes",{"title":1259,"description":1260},"NIST CSF Five Functions - Identify, Protect, Detect, Respond, Recover","Understand the five core NIST CSF functions that organize cybersecurity activities. Learn what each function covers and how they work together.","5.frameworks\u002Fnistcsf\u002Ffive-functions","UKMCkvYY8EuaXD7Ye2itJwTIEwrWdBaTphfOZvfHqb4",{"id":1264,"title":1265,"body":1266,"description":1698,"extension":597,"faq":1699,"frameworkSlug":652,"lastUpdated":952,"meta":1712,"navigation":634,"path":325,"relatedTerms":1713,"relatedTopics":1714,"seo":1717,"stem":1720,"__hash__":1721},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fframework-profiles.md","NIST CSF Framework Profiles",{"type":29,"value":1267,"toc":1672},[1268,1272,1275,1278,1292,1295,1299,1302,1306,1309,1312,1326,1330,1333,1359,1362,1366,1369,1373,1376,1443,1446,1450,1453,1457,1463,1473,1479,1485,1491,1495,1498,1501,1505,1508,1512,1515,1541,1545,1548,1568,1572,1575,1579,1582,1586,1589,1593,1600,1604,1607,1611,1614,1618,1624,1627,1630,1634,1637,1669],[32,1269,1271],{"id":1270},"what-is-a-nist-csf-framework-profile","What is a NIST CSF framework profile?",[37,1273,1274],{},"A framework profile is a customized alignment of the NIST Cybersecurity Framework's functions, categories, and subcategories with your organization's specific business requirements, risk tolerance, and available resources. Profiles provide a mechanism for organizations to tailor the NIST CSF to their unique circumstances rather than treating the framework as a one-size-fits-all checklist.",[37,1276,1277],{},"The NIST CSF defines two types of profiles:",[94,1279,1280,1286],{},[97,1281,1282,1285],{},[58,1283,1284],{},"Current profile"," - Describes the cybersecurity outcomes your organization is currently achieving",[97,1287,1288,1291],{},[58,1289,1290],{},"Target profile"," - Describes the cybersecurity outcomes your organization wants to achieve",[37,1293,1294],{},"The gap between these two profiles drives your prioritization, investment, and improvement roadmap. This makes profiles one of the most practical and actionable components of the NIST CSF.",[32,1296,1298],{"id":1297},"building-a-current-profile","Building a current profile",[37,1300,1301],{},"A current profile captures an honest assessment of where your cybersecurity program stands today. It requires input from across the organization, not just the security team.",[50,1303,1305],{"id":1304},"step-1-select-relevant-subcategories","Step 1 - Select relevant subcategories",[37,1307,1308],{},"The NIST CSF contains 108 subcategories across the five core functions (Identify, Protect, Detect, Respond, Recover). Not all subcategories are equally relevant to every organization. Start by reviewing each subcategory and determining whether it applies to your business context.",[37,1310,1311],{},"Consider:",[94,1313,1314,1317,1320,1323],{},[97,1315,1316],{},"Your industry and regulatory requirements (healthcare organizations will prioritize different subcategories than financial services firms)",[97,1318,1319],{},"Your technology environment (cloud-native organizations face different risks than those with primarily on-premises infrastructure)",[97,1321,1322],{},"Your threat landscape (organizations handling sensitive data face different threats than those primarily concerned with availability)",[97,1324,1325],{},"Your supply chain complexity",[50,1327,1329],{"id":1328},"step-2-assess-current-state-for-each-subcategory","Step 2 - Assess current state for each subcategory",[37,1331,1332],{},"For each relevant subcategory, assess your current implementation level. Many organizations use a simple rating scale:",[94,1334,1335,1341,1347,1353],{},[97,1336,1337,1340],{},[58,1338,1339],{},"Not implemented"," - No activity or controls are in place for this subcategory",[97,1342,1343,1346],{},[58,1344,1345],{},"Partially implemented"," - Some controls exist but are inconsistent, undocumented, or incomplete",[97,1348,1349,1352],{},[58,1350,1351],{},"Largely implemented"," - Controls are in place and documented but may have gaps or are not regularly reviewed",[97,1354,1355,1358],{},[58,1356,1357],{},"Fully implemented"," - Controls are documented, consistently applied, regularly tested, and subject to continuous improvement",[37,1360,1361],{},"Document the evidence supporting each assessment. This evidence will be valuable for gap analysis and for demonstrating progress over time.",[50,1363,1365],{"id":1364},"step-3-document-findings","Step 3 - Document findings",[37,1367,1368],{},"Compile the assessment into a structured document or tool that maps each subcategory to its current state, supporting evidence, and any known gaps. The current profile should be reviewed and endorsed by senior leadership to ensure organizational alignment.",[50,1370,1372],{"id":1371},"example-assessment","Example assessment",[37,1374,1375],{},"For the Identify function, Asset Management category:",[695,1377,1378,1391],{},[698,1379,1380],{},[701,1381,1382,1385,1388],{},[704,1383,1384],{},"Subcategory",[704,1386,1387],{},"Description",[704,1389,1390],{},"Current state",[714,1392,1393,1403,1413,1423,1433],{},[701,1394,1395,1398,1401],{},[719,1396,1397],{},"ID.AM-1",[719,1399,1400],{},"Physical devices and systems are inventoried",[719,1402,1351],{},[701,1404,1405,1408,1411],{},[719,1406,1407],{},"ID.AM-2",[719,1409,1410],{},"Software platforms and applications are inventoried",[719,1412,1345],{},[701,1414,1415,1418,1421],{},[719,1416,1417],{},"ID.AM-3",[719,1419,1420],{},"Organizational communication and data flows are mapped",[719,1422,1339],{},[701,1424,1425,1428,1431],{},[719,1426,1427],{},"ID.AM-4",[719,1429,1430],{},"External information systems are catalogued",[719,1432,1345],{},[701,1434,1435,1438,1441],{},[719,1436,1437],{},"ID.AM-5",[719,1439,1440],{},"Resources are prioritized based on classification and business value",[719,1442,1345],{},[37,1444,1445],{},"This granular view reveals specific areas needing attention rather than painting the entire function with a single broad assessment.",[32,1447,1449],{"id":1448},"building-a-target-profile","Building a target profile",[37,1451,1452],{},"The target profile defines where your organization needs to be. It should be driven by business objectives, regulatory requirements, and risk tolerance rather than by the aspiration to achieve the highest possible maturity in every subcategory.",[50,1454,1456],{"id":1455},"inputs-for-target-profile-development","Inputs for target profile development",[37,1458,1459,1462],{},[58,1460,1461],{},"Business objectives"," - What are the organization's strategic priorities? A company planning rapid growth in e-commerce will have different cybersecurity priorities than one focused on operational efficiency in manufacturing.",[37,1464,1465,1468,1469,1472],{},[58,1466,1467],{},"Regulatory requirements"," - What compliance frameworks must you meet? If you need ",[41,1470,1471],{"href":1222},"PCI DSS compliance",", your target profile should ensure that subcategories relevant to PCI DSS requirements are rated at full implementation. If you operate in healthcare, HIPAA requirements will shape your targets.",[37,1474,1475,1478],{},[58,1476,1477],{},"Risk tolerance"," - How much cybersecurity risk is the organization willing to accept? This is a business decision, not a technical one. Risk-averse organizations (financial institutions, defense contractors) will set higher targets than organizations with lower risk profiles.",[37,1480,1481,1484],{},[58,1482,1483],{},"Resource constraints"," - What budget, personnel, and technology resources are available? Target profiles must be realistic. Setting targets that far exceed available resources creates an unachievable plan that will be ignored.",[37,1486,1487,1490],{},[58,1488,1489],{},"Threat intelligence"," - What threats are most relevant to your industry and organization? Prioritize subcategories that address the threats most likely to materialize and cause the greatest impact.",[50,1492,1494],{"id":1493},"setting-target-levels","Setting target levels",[37,1496,1497],{},"For each relevant subcategory, define the desired implementation level. Not every subcategory needs to reach \"fully implemented.\" Some subcategories may appropriately remain at \"partially implemented\" if the risk is low and the cost of full implementation is high.",[37,1499,1500],{},"Target profiles should include timelines. A three-year target profile might set interim milestones at six months, one year, and two years, allowing the organization to track progress and adjust priorities as conditions change.",[32,1502,1504],{"id":1503},"conducting-gap-analysis","Conducting gap analysis",[37,1506,1507],{},"The gap between your current profile and target profile is your cybersecurity improvement roadmap. Effective gap analysis translates abstract assessments into actionable work.",[50,1509,1511],{"id":1510},"prioritizing-gaps","Prioritizing gaps",[37,1513,1514],{},"Not all gaps are equal. Prioritize based on:",[510,1516,1517,1523,1529,1535],{},[97,1518,1519,1522],{},[58,1520,1521],{},"Risk impact"," - Gaps in subcategories that address your most significant risks should receive the highest priority. A gap in incident response planning for an organization that has already experienced a breach is more urgent than a gap in physical security awareness training.",[97,1524,1525,1528],{},[58,1526,1527],{},"Regulatory urgency"," - Gaps that create compliance violations carry immediate consequences. If you are pursuing SOC 2 and your current profile shows gaps in monitoring and logging subcategories, those gaps need prompt attention.",[97,1530,1531,1534],{},[58,1532,1533],{},"Implementation effort"," - Some gaps can be closed quickly with modest investment (enabling MFA, updating policies), while others require significant time and resources (deploying a SIEM, building a security operations center). Quick wins build momentum and demonstrate progress.",[97,1536,1537,1540],{},[58,1538,1539],{},"Dependency chains"," - Some improvements depend on others. You cannot implement effective monitoring (Detect function) without first having an accurate asset inventory (Identify function). Map dependencies and sequence your improvements accordingly.",[50,1542,1544],{"id":1543},"creating-an-action-plan","Creating an action plan",[37,1546,1547],{},"For each prioritized gap, document:",[94,1549,1550,1553,1556,1559,1562,1565],{},[97,1551,1552],{},"The specific subcategory and the gap between current and target states",[97,1554,1555],{},"The actions required to close the gap (technical implementations, process changes, training programs)",[97,1557,1558],{},"The resources required (budget, personnel, tools)",[97,1560,1561],{},"The responsible owner",[97,1563,1564],{},"The target completion date",[97,1566,1567],{},"How success will be measured",[50,1569,1571],{"id":1570},"tracking-progress","Tracking progress",[37,1573,1574],{},"Gap analysis is not a one-time activity. Reassess your current profile at regular intervals (quarterly or semi-annually) to track progress, identify new gaps introduced by changes in your environment, and adjust priorities based on evolving threats and business needs.",[32,1576,1578],{"id":1577},"customizing-profiles-for-your-organization","Customizing profiles for your organization",[37,1580,1581],{},"The NIST CSF is deliberately flexible, and profiles are the primary mechanism for customization. Several strategies can help you build profiles that are practical and valuable.",[50,1583,1585],{"id":1584},"industry-specific-profiles","Industry-specific profiles",[37,1587,1588],{},"The NIST CSF encourages the creation of sector-specific profiles that reflect the unique risks and requirements of particular industries. Several sector-specific profiles already exist, including profiles for manufacturing, maritime, and energy sectors. These can serve as starting points for your organization's profile development.",[50,1590,1592],{"id":1591},"regulatory-mapping","Regulatory mapping",[37,1594,1595,1596,1599],{},"Map your profile subcategories to your specific regulatory requirements. If you must comply with multiple frameworks, your target profile should incorporate the most stringent requirement for each subcategory. The ",[41,1597,1598],{"href":393},"mapping to other frameworks"," topic covers how NIST CSF aligns with SOC 2, ISO 27001, HIPAA, and PCI DSS.",[50,1601,1603],{"id":1602},"organizational-context","Organizational context",[37,1605,1606],{},"Customize profiles based on your organizational structure. Large enterprises may create multiple profiles for different business units, each reflecting the unit's specific risk environment and regulatory requirements. A retail division handling payment data will have a different profile than a corporate shared services division.",[50,1608,1610],{"id":1609},"stakeholder-communication","Stakeholder communication",[37,1612,1613],{},"Profiles are powerful communication tools. Executive-level summaries should highlight the overall gap position and the business risk associated with the most critical gaps. Technical teams need detailed subcategory-level assessments and action plans. Board reporting should focus on trends over time and the alignment between cybersecurity investments and risk reduction.",[32,1615,1617],{"id":1616},"profiles-and-implementation-tiers","Profiles and implementation tiers",[37,1619,1620,1621,1623],{},"Framework profiles and ",[41,1622,250],{"href":283}," work together but serve different purposes. Tiers describe how your organization approaches cybersecurity risk management (from ad hoc to adaptive), while profiles describe what cybersecurity outcomes you achieve.",[37,1625,1626],{},"An organization at Tier 2 (Risk Informed) might have a current profile that shows strong implementation in some subcategories and weak implementation in others. The tier reflects the overall maturity of the risk management process, while the profile provides the granular detail about specific capabilities.",[37,1628,1629],{},"Your target tier and target profile should be aligned. If you are progressing from Tier 2 to Tier 3, your target profile should reflect the systematic, policy-driven approach to cybersecurity that characterizes Tier 3 organizations. Conversely, if your target profile calls for advanced capabilities in detection and response, you likely need to be operating at Tier 3 or higher to sustain those capabilities.",[32,1631,1633],{"id":1632},"maintaining-profiles-over-time","Maintaining profiles over time",[37,1635,1636],{},"Profiles are living documents that should evolve with your organization. Review and update profiles when:",[94,1638,1639,1645,1651,1657,1663],{},[97,1640,1641,1644],{},[58,1642,1643],{},"Significant business changes occur"," - mergers, acquisitions, new product lines, or market entry",[97,1646,1647,1650],{},[58,1648,1649],{},"The threat landscape shifts"," - new attack techniques, emerging vulnerabilities, or intelligence indicating heightened risk",[97,1652,1653,1656],{},[58,1654,1655],{},"Regulatory requirements change"," - new laws, updated standards, or audit findings",[97,1658,1659,1662],{},[58,1660,1661],{},"Technology changes"," - cloud migration, new platforms, or decommissioning of legacy systems",[97,1664,1665,1668],{},[58,1666,1667],{},"After security incidents"," - lessons learned should feed directly into updated current and target profiles",[37,1670,1671],{},"By treating profiles as dynamic tools rather than static documents, organizations can maintain an accurate view of their cybersecurity posture and ensure that improvement efforts remain aligned with current business needs and risks.",{"title":561,"searchDepth":562,"depth":562,"links":1673},[1674,1675,1681,1685,1690,1696,1697],{"id":1270,"depth":562,"text":1271},{"id":1297,"depth":562,"text":1298,"children":1676},[1677,1678,1679,1680],{"id":1304,"depth":567,"text":1305},{"id":1328,"depth":567,"text":1329},{"id":1364,"depth":567,"text":1365},{"id":1371,"depth":567,"text":1372},{"id":1448,"depth":562,"text":1449,"children":1682},[1683,1684],{"id":1455,"depth":567,"text":1456},{"id":1493,"depth":567,"text":1494},{"id":1503,"depth":562,"text":1504,"children":1686},[1687,1688,1689],{"id":1510,"depth":567,"text":1511},{"id":1543,"depth":567,"text":1544},{"id":1570,"depth":567,"text":1571},{"id":1577,"depth":562,"text":1578,"children":1691},[1692,1693,1694,1695],{"id":1584,"depth":567,"text":1585},{"id":1591,"depth":567,"text":1592},{"id":1602,"depth":567,"text":1603},{"id":1609,"depth":567,"text":1610},{"id":1616,"depth":562,"text":1617},{"id":1632,"depth":562,"text":1633},"How to use NIST CSF framework profiles to assess your current cybersecurity posture, define target states, perform gap analysis, and customize the framework.",{"items":1700},[1701,1703,1706,1709],{"label":1271,"content":1702},"A framework profile is a customized alignment of the NIST CSF's functions, categories, and subcategories with your organization's specific business requirements and risk tolerance. The CSF defines two profile types: a current profile (where you are now) and a target profile (where you want to be). The gap between them drives your improvement roadmap.",{"label":1704,"content":1705},"How do I build a current profile?","Start by selecting the NIST CSF subcategories relevant to your organization, then assess each one using a maturity scale (not implemented, partially implemented, largely implemented, fully implemented). Document the evidence supporting each assessment and have senior leadership review and endorse the results.",{"label":1707,"content":1708},"What is the difference between profiles and implementation tiers?","Profiles describe what cybersecurity outcomes you achieve at a granular subcategory level. Implementation tiers describe how your organization approaches cybersecurity risk management overall (from ad hoc to adaptive). An organization at Tier 2 might still have some subcategories at full implementation — profiles give that detail.",{"label":1710,"content":1711},"How often should I update NIST CSF profiles?","Reassess your current profile quarterly or semi-annually. Additionally, update profiles when significant business changes occur (mergers, new product lines), the threat landscape shifts, regulatory requirements change, technology changes (cloud migration), or after security incidents.",{},[1254],[1715,1256,1716],"five-functions","mapping-to-other-frameworks",{"title":1718,"description":1719},"NIST CSF Framework Profiles: Build Current & Target State Gap Analysis","Step-by-step guide to building NIST CSF framework profiles — assess your current cybersecurity posture, define target states, and prioritize improvements.","5.frameworks\u002Fnistcsf\u002Fframework-profiles","k8BTWrVwkOqcQOqIEgaK29gs9zbopmkOpc3SleT9Lu4",{"id":1723,"title":1724,"body":1725,"description":2011,"extension":597,"faq":2012,"frameworkSlug":652,"lastUpdated":952,"meta":2026,"navigation":634,"path":165,"relatedTerms":2027,"relatedTopics":2030,"seo":2032,"stem":2035,"__hash__":2036},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fgovern-function.md","NIST CSF Govern Function",{"type":29,"value":1726,"toc":1996},[1727,1731,1737,1740,1743,1746,1750,1753,1767,1770,1774,1777,1857,1861,1864,1868,1871,1875,1878,1882,1885,1889,1892,1896,1899,1901,1904,1942,1945,1947,1950,1982,1984,1987],[32,1728,1730],{"id":1729},"what-is-the-nist-csf-govern-function","What is the NIST CSF Govern function?",[37,1732,159,1733,1736],{},[58,1734,1735],{},"Govern (GV) function"," is the newest and arguably most consequential addition to NIST CSF 2.0. It represents a fundamental shift in how NIST wants organizations to think about cybersecurity: not as a technical program owned by IT, but as an enterprise risk discipline owned by the executive team and the board.",[37,1738,1739],{},"In NIST CSF 1.1, governance was a single category — ID.GV — tucked inside the Identify function alongside Asset Management, Business Environment, and Risk Assessment. In practice, that placement caused the problem NIST was trying to solve. Organizations treated governance as a box to check during an initial Identify exercise, then drifted into the Protect and Detect functions where the \"real\" cybersecurity work seemed to happen. Policies got stale, roles and responsibilities were vague, supply chain risk was handled reactively, and leadership had no structured way to set cybersecurity priorities or hold the program accountable.",[37,1741,1742],{},"NIST CSF 2.0 fixes that by pulling governance out of Identify and making it a top-level function that sits above the original five. Govern now frames every other function. It asks: what is the organization's mission? Who are our stakeholders? What is our risk appetite? Who is accountable for cybersecurity outcomes? What policies govern our behavior? How do we oversee our own cybersecurity performance? How do we manage cybersecurity risk in our supply chain?",[37,1744,1745],{},"Govern is where cybersecurity strategy is made. Identify, Protect, Detect, Respond, and Recover are where that strategy is executed.",[32,1747,1749],{"id":1748},"why-nist-added-the-govern-function","Why NIST added the Govern function",[37,1751,1752],{},"NIST spent more than a year gathering feedback from thousands of stakeholders before publishing NIST CSF 2.0. The feedback about governance was strikingly consistent:",[94,1754,1755,1758,1761,1764],{},[97,1756,1757],{},"Executives did not know how to translate cybersecurity risk into business decisions.",[97,1759,1760],{},"Boards were under growing regulatory pressure (SEC cybersecurity disclosure rules, state-level privacy laws, DORA in the EU) to demonstrate cybersecurity oversight, but the original NIST CSF gave them little to oversee.",[97,1762,1763],{},"Supply chain attacks — SolarWinds, Kaseya, Log4j, MOVEit — exposed the limits of treating third-party risk as a subcategory of Identify.",[97,1765,1766],{},"Mature organizations told NIST that their real differentiator was not a specific tool or control; it was the governance fabric that made every other control stick.",[37,1768,1769],{},"By elevating governance, NIST acknowledged that cybersecurity programs fail at the top, not at the bottom. The Govern function gives leadership an explicit mandate and gives practitioners a structured way to request the executive engagement that mature programs require.",[32,1771,1773],{"id":1772},"the-six-categories-of-the-govern-function","The six categories of the Govern function",[37,1775,1776],{},"The Govern function contains six categories. Each category has several subcategories expressed as outcome statements. Below is a concise map.",[695,1778,1779,1789],{},[698,1780,1781],{},[701,1782,1783,1785,1787],{},[704,1784,706],{},[704,1786,709],{},[704,1788,712],{},[714,1790,1791,1802,1813,1824,1835,1846],{},[701,1792,1793,1796,1799],{},[719,1794,1795],{},"Organizational Context",[719,1797,1798],{},"GV.OC",[719,1800,1801],{},"Mission, stakeholders, legal and regulatory requirements, critical dependencies",[701,1803,1804,1807,1810],{},[719,1805,1806],{},"Risk Management Strategy",[719,1808,1809],{},"GV.RM",[719,1811,1812],{},"Risk appetite, risk tolerance, risk assumptions, and cybersecurity strategy",[701,1814,1815,1818,1821],{},[719,1816,1817],{},"Roles, Responsibilities, and Authorities",[719,1819,1820],{},"GV.RR",[719,1822,1823],{},"Defined cybersecurity roles, accountability, resources, and performance",[701,1825,1826,1829,1832],{},[719,1827,1828],{},"Policy",[719,1830,1831],{},"GV.PO",[719,1833,1834],{},"Cybersecurity policies, standards, and procedures that guide the program",[701,1836,1837,1840,1843],{},[719,1838,1839],{},"Oversight",[719,1841,1842],{},"GV.OV",[719,1844,1845],{},"Monitoring and adjusting the strategy based on performance data",[701,1847,1848,1851,1854],{},[719,1849,1850],{},"Cybersecurity Supply Chain Risk Management",[719,1852,1853],{},"GV.SC",[719,1855,1856],{},"Third-party, supplier, and software supply chain cybersecurity risk",[50,1858,1860],{"id":1859},"organizational-context-gvoc","Organizational Context (GV.OC)",[37,1862,1863],{},"GV.OC sets the frame for everything else. It requires the organization to understand its own mission, stakeholders, objectives, legal and regulatory obligations, and the critical dependencies that must be protected. An e-commerce company, a hospital network, and a defense contractor will have radically different organizational contexts, and therefore radically different cybersecurity priorities. Without a documented GV.OC, cybersecurity decisions devolve into generic best-practice lists disconnected from business reality.",[50,1865,1867],{"id":1866},"risk-management-strategy-gvrm","Risk Management Strategy (GV.RM)",[37,1869,1870],{},"GV.RM moves risk management strategy from its former home in the Identify function (ID.RM) to the Govern function. The shift is symbolic and operational: risk appetite, risk tolerance, and the overall cybersecurity risk strategy are governance decisions, not operational ones. GV.RM requires leadership to articulate how much cybersecurity risk the organization is willing to accept, how that risk aligns with business objectives, and how risk decisions will be documented.",[50,1872,1874],{"id":1873},"roles-responsibilities-and-authorities-gvrr","Roles, Responsibilities, and Authorities (GV.RR)",[37,1876,1877],{},"GV.RR formalizes the organizational structure of cybersecurity accountability. It requires clear assignment of cybersecurity roles — CISO, security engineers, IT operations, HR, legal, internal audit — and defines the authority each role has to make decisions, commit resources, and enforce policy. GV.RR also covers cybersecurity performance management: how the organization reviews cybersecurity talent, rewards strong performance, and addresses gaps.",[50,1879,1881],{"id":1880},"policy-gvpo","Policy (GV.PO)",[37,1883,1884],{},"GV.PO governs the cybersecurity policy library itself. Policies must be established, communicated, enforced, and periodically updated. GV.PO asks whether the organization's cybersecurity policies are current, whether employees actually read and follow them, and whether policy exceptions are logged and reviewed. A dusty policy PDF nobody has read since onboarding fails GV.PO even if it technically exists.",[50,1886,1888],{"id":1887},"oversight-gvov","Oversight (GV.OV)",[37,1890,1891],{},"GV.OV creates the feedback loop between operational cybersecurity activity and executive decision-making. It requires that the results of cybersecurity activities — incidents, audit findings, risk assessments, control performance — feed back into the risk management strategy and are used to adjust priorities, investments, and policies. Without GV.OV, Govern becomes a one-time documentation exercise instead of a living management system.",[50,1893,1895],{"id":1894},"cybersecurity-supply-chain-risk-management-gvsc","Cybersecurity Supply Chain Risk Management (GV.SC)",[37,1897,1898],{},"GV.SC is where NIST CSF 2.0 confronts the modern reality that most organizations' biggest cybersecurity exposures are not in their own infrastructure but in their suppliers, software vendors, managed service providers, and open-source dependencies. GV.SC covers supplier due diligence, contractual cybersecurity requirements, ongoing monitoring of supplier cybersecurity posture, and contingency plans for supplier disruption. GV.SC is one of the largest category expansions in NIST CSF 2.0.",[32,1900,799],{"id":798},[37,1902,1903],{},"A pragmatic path to implementing the Govern function looks like this:",[510,1905,1906,1912,1918,1924,1930,1936],{},[97,1907,1908,1911],{},[58,1909,1910],{},"Draft a one-page organizational context statement."," Capture mission, critical services, key stakeholders, and top regulatory obligations. This becomes the seed document for GV.OC.",[97,1913,1914,1917],{},[58,1915,1916],{},"Have leadership sign off on a risk appetite statement."," Two or three sentences that describe how much cybersecurity risk the organization is willing to take, expressed in business terms. This anchors GV.RM.",[97,1919,1920,1923],{},[58,1921,1922],{},"Publish a cybersecurity RACI."," Who is responsible, accountable, consulted, and informed for each major cybersecurity activity? This anchors GV.RR.",[97,1925,1926,1929],{},[58,1927,1928],{},"Take inventory of policies."," List every cybersecurity-related policy, its owner, its last review date, and its next review date. Retire policies that are redundant. This anchors GV.PO.",[97,1931,1932,1935],{},[58,1933,1934],{},"Establish a recurring oversight cadence."," Monthly or quarterly, leadership reviews cybersecurity metrics, incidents, risks, and initiative progress. This anchors GV.OV.",[97,1937,1938,1941],{},[58,1939,1940],{},"Build a third-party risk program."," Start with a vendor inventory, tier vendors by criticality, and implement due diligence for the top tier. This anchors GV.SC.",[37,1943,1944],{},"Govern does not require a massive investment up front. It requires a small amount of leadership discipline applied consistently over time.",[32,1946,850],{"id":849},[37,1948,1949],{},"The Govern function is simple in concept and difficult in practice. Organizations running into trouble with Govern typically hit one or more of the following walls:",[94,1951,1952,1958,1964,1970,1976],{},[97,1953,1954,1957],{},[58,1955,1956],{},"Executive disengagement."," Govern demands executive attention. If the CEO or board treats cybersecurity as an IT problem, Govern will stall. The fix is structural — schedule standing cybersecurity reviews, tie executive incentives to cybersecurity outcomes, and brief the board with the language of business risk.",[97,1959,1960,1963],{},[58,1961,1962],{},"Policy sprawl."," Many organizations have dozens of overlapping policies nobody reads. GV.PO fails when policies are written for auditors rather than employees. Consolidate, simplify, and translate into the everyday language employees use.",[97,1965,1966,1969],{},[58,1967,1968],{},"Supplier opacity."," GV.SC requires visibility into suppliers you may not fully control. Start with the critical few, get contractual rights to audit and monitor, and add more suppliers over time.",[97,1971,1972,1975],{},[58,1973,1974],{},"Siloed risk programs."," Govern often duplicates work already happening in enterprise risk management, internal audit, or legal. Integrate rather than re-create. GV.RM should draw from the enterprise risk register, not a parallel one.",[97,1977,1978,1981],{},[58,1979,1980],{},"Metrics without meaning."," GV.OV only works if the metrics tell leadership something decision-relevant. Replace vanity metrics (patches installed, tickets closed) with outcome metrics (time to detect, time to recover, risk-adjusted loss).",[32,1983,905],{"id":904},[37,1985,1986],{},"episki was built to operate the Govern function as a living system rather than a static binder. Organizational context, risk appetite, roles and responsibilities, policies, oversight cadence, and supplier risk are first-class objects in episki, linked to the underlying NIST CSF subcategories and to every other framework the organization cares about. Policy reviews, supplier re-assessments, and oversight meetings become scheduled workflows with owners, due dates, and audit-ready evidence. Leadership sees a real-time Govern scorecard; practitioners see the concrete initiatives that roll up to it.",[37,1988,1989,1990,922,1993,1995],{},"Ready to operationalize the NIST CSF Govern function without the binder? ",[41,1991,921],{"href":623,"rel":1992},[920],[41,1994,925],{"href":629}," and share a Govern function scorecard with your leadership team the same day.",{"title":561,"searchDepth":562,"depth":562,"links":1997},[1998,1999,2000,2008,2009,2010],{"id":1729,"depth":562,"text":1730},{"id":1748,"depth":562,"text":1749},{"id":1772,"depth":562,"text":1773,"children":2001},[2002,2003,2004,2005,2006,2007],{"id":1859,"depth":567,"text":1860},{"id":1866,"depth":567,"text":1867},{"id":1873,"depth":567,"text":1874},{"id":1880,"depth":567,"text":1881},{"id":1887,"depth":567,"text":1888},{"id":1894,"depth":567,"text":1895},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF 2.0 Govern function — its six categories (OC, RM, RR, PO, OV, SC), why NIST added it, and how to implement it.",{"items":2013},[2014,2017,2020,2023],{"label":2015,"content":2016},"Why did NIST add the Govern function in CSF 2.0?","NIST added the Govern function because organizations using CSF 1.1 consistently under-invested in governance. Governance was a single category (ID.GV) buried inside Identify, and it rarely got leadership attention. Elevating Govern to a top-level function forces cybersecurity governance onto the executive agenda and acknowledges that sustained cybersecurity outcomes depend on leadership, policy, and risk management strategy.",{"label":2018,"content":2019},"What are the six categories of the Govern function?","The six Govern categories are Organizational Context (GV.OC), Risk Management Strategy (GV.RM), Roles, Responsibilities, and Authorities (GV.RR), Policy (GV.PO), Oversight (GV.OV), and Cybersecurity Supply Chain Risk Management (GV.SC).",{"label":2021,"content":2022},"Who is accountable for the Govern function?","The Govern function is owned by senior leadership — typically the CEO, board, CISO, or an executive risk committee. While operational teams contribute evidence and execute policies, accountability for cybersecurity governance cannot be delegated below the executive layer. Boards and audit committees increasingly review Govern function performance as part of their cybersecurity oversight duties.",{"label":2024,"content":2025},"How does Govern relate to the other NIST CSF functions?","Govern sits above the other five functions. Organizational context, risk appetite, policies, and oversight set in Govern flow downward into how Identify, Protect, Detect, Respond, and Recover are operated. Data from those operational functions flows back up into Govern to adjust strategy and investment.",{},[1254,2028,2029],"control-framework","risk-management",[1257,2031,962,1716],"identify-function",{"title":2033,"description":2034},"NIST CSF Govern Function (GV): Categories, Subcategories, and Implementation","The NIST CSF 2.0 Govern function elevates cybersecurity governance to a top-level function. Learn GV.OC, GV.RM, GV.RR, GV.PO, GV.OV, and GV.SC and how to implement each.","5.frameworks\u002Fnistcsf\u002Fgovern-function","rpfpeWzPMC-Gls_kIMpb4CyjbI5fyc9Ak8yX-MzqXac",{"id":2038,"title":2039,"body":2040,"description":2307,"extension":597,"faq":2308,"frameworkSlug":652,"lastUpdated":952,"meta":2322,"navigation":634,"path":180,"relatedTerms":2323,"relatedTopics":2325,"seo":2326,"stem":2329,"__hash__":2330},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fidentify-function.md","NIST CSF Identify Function",{"type":29,"value":2041,"toc":2295},[2042,2046,2052,2055,2058,2062,2065,2084,2087,2091,2138,2144,2148,2151,2154,2179,2183,2186,2189,2193,2196,2198,2201,2239,2241,2244,2276,2278,2286],[32,2043,2045],{"id":2044},"what-is-the-nist-csf-identify-function","What is the NIST CSF Identify function?",[37,2047,159,2048,2051],{},[58,2049,2050],{},"Identify (ID) function"," is where a NIST CSF program begins. Its purpose is to develop an organizational understanding of cybersecurity risk to systems, people, assets, data, and capabilities. Identify is not glamorous — no dashboards full of blocked attacks, no incident response war rooms — but it is the function that determines whether every other function has something coherent to act on.",[37,2053,2054],{},"You cannot protect an asset you do not know you own. You cannot detect anomalies in a data flow you have never mapped. You cannot respond to an incident without knowing which systems are critical. You cannot recover what you have not inventoried. Identify is the groundwork that makes the Protect, Detect, Respond, and Recover functions possible, and it is the input that feeds the Govern function's risk management strategy.",[37,2056,2057],{},"Identify is also the function most often shortchanged. Teams rush into Protect because controls feel tangible, and they discover months later that their scope was wrong, their risk register was stale, and their supply chain exposure was invisible. Mature organizations invest heavily and continuously in Identify.",[32,2059,2061],{"id":2060},"how-identify-changed-in-nist-csf-20","How Identify changed in NIST CSF 2.0",[37,2063,2064],{},"NIST CSF 2.0 restructured the Identify function. Two of the original Identify categories moved to the new Govern function:",[94,2066,2067,2072,2078],{},[97,2068,2069,2071],{},[58,2070,1014],{}," was elevated to the Govern function and split into GV.OC, GV.RR, GV.PO, and GV.OV.",[97,2073,2074,2077],{},[58,2075,2076],{},"Risk Management Strategy (ID.RM)"," became GV.RM.",[97,2079,2080,2083],{},[58,2081,2082],{},"Supply Chain Risk Management (ID.SC)"," moved to GV.SC.",[37,2085,2086],{},"What remains in Identify is tightly focused on knowing what you have and what is at risk: Asset Management, Risk Assessment, and Improvement. The Business Environment outcomes from CSF 1.1 were folded into GV.OC but continue to inform Identify activities. The result is a leaner, more operationally focused Identify function that pairs cleanly with the strategic Govern function above it.",[32,2088,2090],{"id":2089},"the-categories-of-the-identify-function","The categories of the Identify function",[695,2092,2093,2103],{},[698,2094,2095],{},[701,2096,2097,2099,2101],{},[704,2098,706],{},[704,2100,709],{},[704,2102,712],{},[714,2104,2105,2116,2127],{},[701,2106,2107,2110,2113],{},[719,2108,2109],{},"Asset Management",[719,2111,2112],{},"ID.AM",[719,2114,2115],{},"Inventory of hardware, software, systems, data, and external dependencies",[701,2117,2118,2121,2124],{},[719,2119,2120],{},"Risk Assessment",[719,2122,2123],{},"ID.RA",[719,2125,2126],{},"Identification, analysis, and prioritization of cybersecurity risks",[701,2128,2129,2132,2135],{},[719,2130,2131],{},"Improvement",[719,2133,2134],{},"ID.IM",[719,2136,2137],{},"Lessons learned from assessments, tests, and incidents feed program improvements",[37,2139,2140],{},[2141,2142,2143],"em",{},"In NIST CSF 1.1 the Identify function also included Business Environment (ID.BE), Governance (ID.GV), Risk Management Strategy (ID.RM), and Supply Chain Risk Management (ID.SC). Those outcomes now live in the Govern function in NIST CSF 2.0.",[50,2145,2147],{"id":2146},"asset-management-idam","Asset Management (ID.AM)",[37,2149,2150],{},"ID.AM is the most foundational category in the entire NIST Cybersecurity Framework. It requires the organization to identify and manage all of the assets that enable it to achieve its business purposes, consistent with their relative importance to business objectives and the organization's risk strategy. Assets include physical devices, operating systems and applications, data, personnel, and external systems the organization depends on.",[37,2152,2153],{},"Practical ID.AM outcomes include:",[94,2155,2156,2159,2162,2170,2173,2176],{},[97,2157,2158],{},"A current inventory of hardware and physical devices.",[97,2160,2161],{},"A current inventory of software platforms and applications, including open-source components and SaaS subscriptions.",[97,2163,2164,2165,2169],{},"An inventory of data classified by sensitivity and regulatory obligation, linked to the systems that store and process it. (See our ",[41,2166,2168],{"href":2167},"\u002Fglossary\u002Fdata-classification","data classification"," primer.)",[97,2171,2172],{},"A map of communication and data flows — which systems talk to which, over which protocols, across which trust boundaries.",[97,2174,2175],{},"An inventory of external information systems the organization depends on, including suppliers, SaaS vendors, and managed services.",[97,2177,2178],{},"Prioritization of assets by criticality so that Protect, Detect, Respond, and Recover can focus on what matters most.",[50,2180,2182],{"id":2181},"risk-assessment-idra","Risk Assessment (ID.RA)",[37,2184,2185],{},"ID.RA is where the organization systematically identifies, analyzes, and prioritizes cybersecurity risks. ID.RA covers threat intelligence collection and analysis, vulnerability identification, likelihood and impact analysis, and risk determination. A mature ID.RA program produces a prioritized risk register that feeds directly into the Govern function's risk management strategy (GV.RM) and drives investment decisions across the other functions.",[37,2187,2188],{},"ID.RA is not a one-time activity. Threats evolve, the business changes, and new vulnerabilities are disclosed daily. Risk assessments should be refreshed on a regular cadence and triggered by significant events — major system changes, acquisitions, new product launches, or significant incidents.",[50,2190,2192],{"id":2191},"improvement-idim","Improvement (ID.IM)",[37,2194,2195],{},"ID.IM is new in NIST CSF 2.0. It captures the outcomes associated with continuous improvement of the cybersecurity program based on assessments, tests, exercises, incidents, and audits. ID.IM asks whether the organization systematically captures lessons learned and translates them into updated policies, controls, and practices. Without ID.IM, the NIST Cybersecurity Framework stops evolving with the organization.",[32,2197,799],{"id":798},[37,2199,2200],{},"A pragmatic sequence for building out the Identify function:",[510,2202,2203,2209,2215,2221,2227,2233],{},[97,2204,2205,2208],{},[58,2206,2207],{},"Pick an authoritative asset system of record."," Choose one tool (a CMDB, an endpoint management platform, or a cloud asset inventory) as the source of truth. Integrate data from other tools into it rather than maintaining parallel inventories.",[97,2210,2211,2214],{},[58,2212,2213],{},"Classify data."," Map every sensitive data type to the systems that store and process it. Link data classification to regulatory obligations (HIPAA, PCI DSS, GDPR, CUI) captured in the Govern function.",[97,2216,2217,2220],{},[58,2218,2219],{},"Draw a data flow diagram."," Even a rough diagram beats no diagram. Iterate it over time.",[97,2222,2223,2226],{},[58,2224,2225],{},"Build a prioritized risk register."," Begin with qualitative scoring (high \u002F medium \u002F low) and mature toward quantitative methods over time. Use the risk register as the single place where business, compliance, and engineering risks live.",[97,2228,2229,2232],{},[58,2230,2231],{},"Schedule formal risk assessments."," Pick a cadence (quarterly for dynamic environments, annually for stable ones) and stick to it. Trigger ad-hoc assessments after major changes.",[97,2234,2235,2238],{},[58,2236,2237],{},"Close the improvement loop."," After every audit, tabletop exercise, penetration test, or incident, capture lessons learned in ID.IM and feed them back into policy and control updates.",[32,2240,850],{"id":849},[37,2242,2243],{},"Identify fails for a handful of recurring reasons:",[94,2245,2246,2252,2258,2264,2270],{},[97,2247,2248,2251],{},[58,2249,2250],{},"Shadow IT and shadow SaaS."," Employees adopt tools the security team never sees. ID.AM erodes continuously unless the organization has a discovery and procurement process that catches new SaaS and cloud accounts early.",[97,2253,2254,2257],{},[58,2255,2256],{},"Inventory without criticality."," A 50,000-row CMDB is useless if every asset has the same priority. ID.AM must include criticality scoring that drives where Protect and Detect resources are applied.",[97,2259,2260,2263],{},[58,2261,2262],{},"Risk register as a spreadsheet graveyard."," Registers maintained in static spreadsheets drift out of date within weeks. Treat the risk register as a living artifact with owners, due dates, and review cadences.",[97,2265,2266,2269],{},[58,2267,2268],{},"Disconnected data classification."," Data classification schemes that nobody uses are common. Tie classification to access control, encryption, and DLP decisions so that the classification actually changes behavior.",[97,2271,2272,2275],{},[58,2273,2274],{},"Identify as a one-off project."," Many organizations treat Identify as a project to finish rather than a continuous capability. NIST CSF 2.0's ID.IM category is a deliberate counterweight.",[32,2277,905],{"id":904},[37,2279,2280,2281,374,2283,2285],{},"episki turns the Identify function into an always-on capability. Asset inventories, data classifications, data flow maps, and risk registers are maintained in one place, linked to the NIST CSF subcategories they satisfy and to the corresponding outcomes in ",[41,2282,128],{"href":127},[41,2284,378],{"href":377},", HIPAA, PCI DSS, and CMMC. Integrations pull hardware, software, and cloud asset data directly from the tools that already know. Risk assessments, improvement actions, and lessons-learned loops become tracked workflows rather than documents in a shared drive.",[37,2287,2288,2289,922,2292,2294],{},"Ready to make the NIST CSF Identify function live? ",[41,2290,921],{"href":623,"rel":2291},[920],[41,2293,925],{"href":629}," and stand up a working NIST CSF Identify profile in days, not quarters.",{"title":561,"searchDepth":562,"depth":562,"links":2296},[2297,2298,2299,2304,2305,2306],{"id":2044,"depth":562,"text":2045},{"id":2060,"depth":562,"text":2061},{"id":2089,"depth":562,"text":2090,"children":2300},[2301,2302,2303],{"id":2146,"depth":567,"text":2147},{"id":2181,"depth":567,"text":2182},{"id":2191,"depth":567,"text":2192},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF Identify function — asset management, business environment, governance, risk assessment, risk management strategy, and supply chain risk.",{"items":2309},[2310,2313,2316,2319],{"label":2311,"content":2312},"What is the Identify function in NIST CSF?","The Identify function develops an organizational understanding of cybersecurity risk to systems, people, assets, data, and capabilities. Identify is the foundation of a NIST CSF program — you cannot protect, detect, respond to, or recover from threats to assets you do not know you own, and you cannot prioritize risk you have not assessed.",{"label":2314,"content":2315},"How did the Identify function change in NIST CSF 2.0?","NIST CSF 2.0 moved two categories out of Identify and into the new Govern function: Governance (ID.GV) became GV.OC, GV.RR, GV.PO, and GV.OV, and Risk Management Strategy (ID.RM) became GV.RM. Supply Chain Risk Management also moved from ID.SC to GV.SC. Identify retains Asset Management, Business Environment, Risk Assessment, and Improvement outcomes focused on knowing what you own and what is at risk.",{"label":2317,"content":2318},"What is the most important Identify category?","Asset Management (ID.AM) is the foundational Identify category. Without a comprehensive inventory of hardware, software, data, and external systems, every other NIST CSF function operates on guesswork. Most breaches can be traced back to an unknown asset, an unknown account, or an unknown data flow.",{"label":2320,"content":2321},"How often should I update Identify function outputs?","Asset inventories, risk assessments, and data flow maps should be updated continuously for dynamic environments and at minimum annually for stable ones. Mature organizations use automated discovery tooling to keep inventories fresh in near real time and refresh formal risk assessments quarterly or after significant changes.",{},[1254,2028,2324,2029],"data-classification",[961,959,1257,962],{"title":2327,"description":2328},"NIST CSF Identify Function (ID): Categories, Subcategories, and Implementation","The NIST CSF Identify function builds the foundation of a cybersecurity program. Learn ID.AM, ID.BE, ID.GV, ID.RA, ID.RM, and ID.SC and how to implement each.","5.frameworks\u002Fnistcsf\u002Fidentify-function","hpUV2VVMm8PbAJ9dV6sCneNvTf5SCEQquJFvHLRIh4U",{"id":2332,"title":2333,"body":2334,"description":2725,"extension":597,"faq":1250,"frameworkSlug":652,"lastUpdated":952,"meta":2726,"navigation":634,"path":283,"relatedTerms":2727,"relatedTopics":2728,"seo":2729,"stem":2732,"__hash__":2733},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fimplementation-tiers.md","NIST CSF Implementation Tiers",{"type":29,"value":2335,"toc":2705},[2336,2340,2343,2346,2349,2353,2357,2360,2366,2372,2378,2383,2400,2404,2407,2412,2417,2422,2427,2444,2448,2451,2456,2461,2466,2471,2491,2495,2498,2503,2508,2513,2518,2538,2542,2549,2553,2556,2570,2574,2577,2591,2595,2598,2612,2616,2622,2626,2629,2633,2650,2654,2674,2678,2698],[32,2337,2339],{"id":2338},"what-are-nist-csf-implementation-tiers","What are NIST CSF implementation tiers?",[37,2341,2342],{},"The NIST Cybersecurity Framework (CSF) uses four implementation tiers to describe the degree to which an organization's cybersecurity risk management practices exhibit the characteristics defined in the framework. The tiers range from Partial (Tier 1) to Adaptive (Tier 4) and provide context for how an organization views cybersecurity risk and the processes in place to manage that risk.",[37,2344,2345],{},"Implementation tiers are not maturity levels in the traditional sense. The NIST CSF explicitly states that tiers do not represent maturity, and organizations are not expected to progress to Tier 4 in all areas. Instead, tiers help organizations understand their current approach to cybersecurity risk management and determine whether that approach is appropriate given their threat environment, business requirements, and risk tolerance.",[37,2347,2348],{},"That said, most organizations use the tiers as a practical benchmark for measuring progress and setting improvement goals.",[32,2350,2352],{"id":2351},"the-four-implementation-tiers","The four implementation tiers",[50,2354,2356],{"id":2355},"tier-1-partial","Tier 1 - Partial",[37,2358,2359],{},"At Tier 1, cybersecurity risk management is ad hoc and reactive. The organization has limited awareness of cybersecurity risk and manages it on a case-by-case basis without established processes.",[37,2361,2362,2365],{},[58,2363,2364],{},"Risk management process:"," There is no formalized risk management process. Cybersecurity activities are performed irregularly and in response to specific events rather than proactively. Risk decisions are made without a systematic approach to identifying, assessing, and prioritizing risks.",[37,2367,2368,2371],{},[58,2369,2370],{},"Integrated risk management program:"," Cybersecurity is not integrated into organizational risk management. There is limited awareness at the management level of cybersecurity risks, and cybersecurity activities are not coordinated across the organization. Different departments may implement security controls independently without a unified strategy.",[37,2373,2374,2377],{},[58,2375,2376],{},"External participation:"," The organization does not understand its role in the broader ecosystem. There is little or no collaboration with external entities regarding cybersecurity threats, and the organization does not share or receive threat intelligence.",[37,2379,2380],{},[58,2381,2382],{},"Characteristics of Tier 1 organizations:",[94,2384,2385,2388,2391,2394,2397],{},[97,2386,2387],{},"No documented cybersecurity policies or only outdated ones",[97,2389,2390],{},"Incident response is improvised rather than planned",[97,2392,2393],{},"Asset inventories are incomplete or nonexistent",[97,2395,2396],{},"Security investments are reactive, driven by incidents or audit findings",[97,2398,2399],{},"Little to no awareness of supply chain cybersecurity risks",[50,2401,2403],{"id":2402},"tier-2-risk-informed","Tier 2 - Risk informed",[37,2405,2406],{},"At Tier 2, the organization is aware of cybersecurity risks and has begun to formalize its risk management practices, but implementation is inconsistent and may not extend across the entire organization.",[37,2408,2409,2411],{},[58,2410,2364],{}," Risk management practices are approved by management but may not be established as organization-wide policy. Risk awareness exists, but the processes for identifying and managing risk are not consistently applied. Some risk assessments have been conducted, but they may not be comprehensive or regularly updated.",[37,2413,2414,2416],{},[58,2415,2370],{}," There is some awareness of cybersecurity risk at the organizational level, but it may not be formally communicated or consistently integrated into enterprise-wide risk management. Some coordination exists between departments, but cybersecurity considerations may not factor into all business decisions.",[37,2418,2419,2421],{},[58,2420,2376],{}," The organization understands its role in the broader ecosystem but has not formalized its external engagement. Some informal information sharing may occur, but there is no structured participation in threat intelligence communities or supply chain risk management programs.",[37,2423,2424],{},[58,2425,2426],{},"Characteristics of Tier 2 organizations:",[94,2428,2429,2432,2435,2438,2441],{},[97,2430,2431],{},"Some documented cybersecurity policies exist but are not uniformly enforced",[97,2433,2434],{},"Risk assessments have been performed but may be outdated or incomplete",[97,2436,2437],{},"Incident response plans exist on paper but have not been regularly tested",[97,2439,2440],{},"Security awareness training is conducted but may be infrequent",[97,2442,2443],{},"Some vendor risk assessment processes are in place",[50,2445,2447],{"id":2446},"tier-3-repeatable","Tier 3 - Repeatable",[37,2449,2450],{},"At Tier 3, the organization has formalized its cybersecurity risk management practices into policies that are consistently applied across the organization. Risk management is integrated into organizational processes and regularly updated.",[37,2452,2453,2455],{},[58,2454,2364],{}," Risk management practices are formally approved, documented, and expressed as policy. Policies and procedures are regularly reviewed and updated based on changes to the threat landscape, technology, and business requirements. Risk assessments are conducted regularly and inform cybersecurity priorities and resource allocation.",[37,2457,2458,2460],{},[58,2459,2370],{}," Cybersecurity risk management is integrated into organizational risk management practices. Senior leadership considers cybersecurity risk alongside other business risks. There is organization-wide awareness of cybersecurity policies, and personnel at all levels understand their cybersecurity responsibilities.",[37,2462,2463,2465],{},[58,2464,2376],{}," The organization actively participates in external cybersecurity communities. It receives and acts on threat intelligence from industry groups, government agencies, and information sharing organizations. Supply chain risk management practices are formalized, and the organization understands and manages the cybersecurity risks associated with its third-party relationships.",[37,2467,2468],{},[58,2469,2470],{},"Characteristics of Tier 3 organizations:",[94,2472,2473,2476,2479,2482,2485,2488],{},[97,2474,2475],{},"Comprehensive, documented cybersecurity policies consistently enforced",[97,2477,2478],{},"Regular risk assessments that inform budgeting and prioritization",[97,2480,2481],{},"Tested incident response plans with defined roles and playbooks",[97,2483,2484],{},"Continuous security monitoring with SIEM and alerting capabilities",[97,2486,2487],{},"Formal vendor risk management programs",[97,2489,2490],{},"Regular reporting of cybersecurity posture to executive leadership",[50,2492,2494],{"id":2493},"tier-4-adaptive","Tier 4 - Adaptive",[37,2496,2497],{},"At Tier 4, the organization adapts its cybersecurity practices based on lessons learned and predictive indicators. Cybersecurity risk management is a core part of organizational culture and decision-making.",[37,2499,2500,2502],{},[58,2501,2364],{}," The organization continuously adapts its cybersecurity practices based on real-time threat intelligence, lessons learned from incidents, and predictive analytics. Risk management is dynamic and responds to changes in the threat environment proactively rather than reactively. Technologies and processes are continuously evaluated and improved.",[37,2504,2505,2507],{},[58,2506,2370],{}," Cybersecurity risk management is fully integrated into organizational culture. There is a clear understanding of risk tolerance, and cybersecurity considerations are embedded in all business decisions, from strategic planning to daily operations. Budget allocation reflects a risk-informed approach with flexibility to address emerging threats.",[37,2509,2510,2512],{},[58,2511,2376],{}," The organization actively contributes to the broader cybersecurity ecosystem. It shares threat intelligence, participates in industry working groups, and collaborates with partners and peers to improve collective security. Supply chain risk management is advanced, with continuous monitoring of third-party security postures.",[37,2514,2515],{},[58,2516,2517],{},"Characteristics of Tier 4 organizations:",[94,2519,2520,2523,2526,2529,2532,2535],{},[97,2521,2522],{},"Cybersecurity practices evolve based on threat intelligence and lessons learned",[97,2524,2525],{},"Automated, continuous monitoring with advanced analytics and anomaly detection",[97,2527,2528],{},"Mature incident response with regular exercises including tabletop and red team operations",[97,2530,2531],{},"Cybersecurity metrics tracked and reported to the board regularly",[97,2533,2534],{},"Active participation in ISACs and information sharing communities",[97,2536,2537],{},"Predictive capabilities that anticipate emerging threats",[32,2539,2541],{"id":2540},"assessing-your-current-tier","Assessing your current tier",[37,2543,2544,2545,2548],{},"Assessing your implementation tier requires honest evaluation across three dimensions for each of the ",[41,2546,2547],{"href":1252},"five core functions",":",[50,2550,2552],{"id":2551},"step-1-evaluate-risk-management-processes","Step 1 - Evaluate risk management processes",[37,2554,2555],{},"Examine whether your cybersecurity risk management processes are documented, approved by leadership, consistently applied, and regularly updated. Consider the following questions:",[94,2557,2558,2561,2564,2567],{},[97,2559,2560],{},"Do you have a formal risk management framework?",[97,2562,2563],{},"Are risk assessments conducted regularly and used to inform security decisions?",[97,2565,2566],{},"Is there a defined risk tolerance that guides control selection?",[97,2568,2569],{},"Are risk management processes reviewed and updated when the threat landscape changes?",[50,2571,2573],{"id":2572},"step-2-assess-integration-with-organizational-risk-management","Step 2 - Assess integration with organizational risk management",[37,2575,2576],{},"Determine how deeply cybersecurity is embedded in overall business risk management:",[94,2578,2579,2582,2585,2588],{},[97,2580,2581],{},"Does executive leadership receive regular cybersecurity risk briefings?",[97,2583,2584],{},"Are cybersecurity considerations factored into business decisions such as new product launches, acquisitions, and vendor selections?",[97,2586,2587],{},"Is cybersecurity funding aligned with identified risks?",[97,2589,2590],{},"Do all departments understand their cybersecurity responsibilities?",[50,2592,2594],{"id":2593},"step-3-evaluate-external-participation","Step 3 - Evaluate external participation",[37,2596,2597],{},"Assess your engagement with the broader cybersecurity community:",[94,2599,2600,2603,2606,2609],{},[97,2601,2602],{},"Do you receive threat intelligence from industry groups or government sources?",[97,2604,2605],{},"Do you share threat information with peers?",[97,2607,2608],{},"Is supply chain cybersecurity risk formally managed?",[97,2610,2611],{},"Do you participate in sector-specific cybersecurity initiatives?",[50,2613,2615],{"id":2614},"step-4-build-a-tier-assessment-matrix","Step 4 - Build a tier assessment matrix",[37,2617,2618,2619,2621],{},"For each core function (Identify, Protect, Detect, Respond, Recover), rate your organization across the three dimensions. You may be at different tiers for different functions, which is normal. Use this matrix to build a ",[41,2620,293],{"href":325}," that captures your current state and defines your target state.",[32,2623,2625],{"id":2624},"progressing-to-higher-tiers","Progressing to higher tiers",[37,2627,2628],{},"Tier progression should be driven by business need and risk tolerance, not by a desire to achieve the highest possible tier. For many organizations, Tier 3 represents an appropriate target that balances security maturity with resource investment.",[50,2630,2632],{"id":2631},"moving-from-tier-1-to-tier-2","Moving from Tier 1 to Tier 2",[94,2634,2635,2638,2641,2644,2647],{},[97,2636,2637],{},"Document your current cybersecurity policies, even if they are informal",[97,2639,2640],{},"Conduct an initial risk assessment to identify the most critical gaps",[97,2642,2643],{},"Establish basic asset management practices",[97,2645,2646],{},"Create an incident response plan, even a simple one",[97,2648,2649],{},"Begin security awareness training for all employees",[50,2651,2653],{"id":2652},"moving-from-tier-2-to-tier-3","Moving from Tier 2 to Tier 3",[94,2655,2656,2659,2662,2665,2668,2671],{},[97,2657,2658],{},"Formalize policies into organization-wide standards",[97,2660,2661],{},"Implement continuous security monitoring (SIEM, EDR, vulnerability scanning)",[97,2663,2664],{},"Integrate cybersecurity risk into enterprise risk management",[97,2666,2667],{},"Establish a formal vendor risk management program",[97,2669,2670],{},"Conduct regular tabletop exercises for incident response",[97,2672,2673],{},"Report cybersecurity metrics to executive leadership",[50,2675,2677],{"id":2676},"moving-from-tier-3-to-tier-4","Moving from Tier 3 to Tier 4",[94,2679,2680,2683,2686,2689,2692,2695],{},[97,2681,2682],{},"Implement advanced threat detection with behavioral analytics",[97,2684,2685],{},"Develop predictive capabilities based on threat intelligence",[97,2687,2688],{},"Conduct red team exercises and adversary emulation",[97,2690,2691],{},"Actively contribute to information sharing communities",[97,2693,2694],{},"Continuously optimize security controls based on performance metrics",[97,2696,2697],{},"Embed cybersecurity decision-making into all business processes",[37,2699,2700,2701,2704],{},"The NIST CSF implementation tiers provide a useful vocabulary for communicating cybersecurity maturity internally and externally. They also ",[41,2702,2703],{"href":393},"map effectively to other frameworks",", helping organizations that must meet multiple compliance requirements understand how maturity investments in one area benefit their overall posture.",{"title":561,"searchDepth":562,"depth":562,"links":2706},[2707,2708,2714,2720],{"id":2338,"depth":562,"text":2339},{"id":2351,"depth":562,"text":2352,"children":2709},[2710,2711,2712,2713],{"id":2355,"depth":567,"text":2356},{"id":2402,"depth":567,"text":2403},{"id":2446,"depth":567,"text":2447},{"id":2493,"depth":567,"text":2494},{"id":2540,"depth":562,"text":2541,"children":2715},[2716,2717,2718,2719],{"id":2551,"depth":567,"text":2552},{"id":2572,"depth":567,"text":2573},{"id":2593,"depth":567,"text":2594},{"id":2614,"depth":567,"text":2615},{"id":2624,"depth":562,"text":2625,"children":2721},[2722,2723,2724],{"id":2631,"depth":567,"text":2632},{"id":2652,"depth":567,"text":2653},{"id":2676,"depth":567,"text":2677},"A guide to the four NIST CSF implementation tiers, how to assess your current tier, and strategies for progressing to higher tiers.",{},[1254],[1715,962,1716],{"title":2730,"description":2731},"NIST CSF Implementation Tiers - Tier 1 to 4 Assessment Guide","Learn the four NIST CSF implementation tiers from Partial to Adaptive. Assess your current cybersecurity maturity and plan your progression path.","5.frameworks\u002Fnistcsf\u002Fimplementation-tiers","_VG0Ohos-g1KhmjjwxcVs_9ndSoy55Ql4zzl54FuTis",{"id":2735,"title":2736,"body":2737,"description":3174,"extension":597,"faq":1250,"frameworkSlug":652,"lastUpdated":952,"meta":3175,"navigation":634,"path":393,"relatedTerms":3176,"relatedTopics":3181,"seo":3182,"stem":3185,"__hash__":3186},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fmapping-to-other-frameworks.md","Mapping NIST CSF to Other Frameworks",{"type":29,"value":2738,"toc":3148},[2739,2743,2746,2752,2756,2759,2763,2768,2779,2784,2795,2800,2808,2813,2821,2826,2831,2835,2841,2845,2848,2851,2856,2867,2872,2883,2888,2896,2901,2909,2914,2919,2922,2925,2929,2932,2935,2940,2951,2956,2967,2972,2977,2982,2990,2995,3000,3003,3006,3010,3019,3022,3027,3038,3043,3054,3059,3067,3072,3077,3082,3087,3090,3096,3100,3103,3107,3110,3114,3117,3121,3124,3128,3135,3139,3145],[32,2740,2742],{"id":2741},"why-framework-mapping-matters","Why framework mapping matters",[37,2744,2745],{},"Most organizations do not operate under a single compliance framework. A healthcare company processing payments may need to comply with HIPAA, PCI DSS, and SOC 2 simultaneously. A financial services firm may face ISO 27001 certification requirements alongside SOC 2 and PCI DSS. Without a structured approach to managing overlapping requirements, organizations end up duplicating effort, maintaining separate evidence repositories, and fatiguing both their security teams and their auditors.",[37,2747,2748,2749,2751],{},"The NIST Cybersecurity Framework serves as an effective common denominator for multi-framework compliance. Its broad scope, voluntary nature, and risk-based approach make it a natural organizing structure. By mapping other frameworks to the NIST CSF's ",[41,2750,2547],{"href":1252}," and their categories, organizations can implement controls once and demonstrate compliance across multiple standards.",[32,2753,2755],{"id":2754},"nist-csf-to-soc-2","NIST CSF to SOC 2",[37,2757,2758],{},"SOC 2 is built around five Trust Services Criteria (TSC): Security, Availability, Processing Integrity, Confidentiality, and Privacy. The Security criterion (also known as the Common Criteria) is required for all SOC 2 reports, while the other four are optional based on the services provided.",[50,2760,2762],{"id":2761},"key-mappings","Key mappings",[37,2764,2765],{},[58,2766,2767],{},"Identify function to SOC 2:",[94,2769,2770,2773,2776],{},[97,2771,2772],{},"Asset management (ID.AM) maps to CC6.1 (logical and physical access controls) and CC6.6 (boundary protection)",[97,2774,2775],{},"Risk assessment (ID.RA) maps to CC3.1 through CC3.4 (risk assessment criteria)",[97,2777,2778],{},"Governance (ID.GV) maps to CC1.1 through CC1.5 (control environment)",[37,2780,2781],{},[58,2782,2783],{},"Protect function to SOC 2:",[94,2785,2786,2789,2792],{},[97,2787,2788],{},"Access control (PR.AC) maps directly to CC6.1 through CC6.8 (logical and physical access)",[97,2790,2791],{},"Data security (PR.DS) maps to CC6.1 (encryption), CC6.7 (data transmission), and C1.1-C1.2 (Confidentiality criteria)",[97,2793,2794],{},"Awareness and training (PR.AT) maps to CC1.4 (competence and accountability)",[37,2796,2797],{},[58,2798,2799],{},"Detect function to SOC 2:",[94,2801,2802,2805],{},[97,2803,2804],{},"Security continuous monitoring (DE.CM) maps to CC7.1 through CC7.3 (system monitoring and incident detection)",[97,2806,2807],{},"Anomalies and events (DE.AE) maps to CC7.2 (monitoring for anomalies)",[37,2809,2810],{},[58,2811,2812],{},"Respond function to SOC 2:",[94,2814,2815,2818],{},[97,2816,2817],{},"Response planning and mitigation (RS.RP, RS.MI) map to CC7.3 through CC7.5 (incident response and recovery)",[97,2819,2820],{},"Communications (RS.CO) maps to CC2.2 and CC2.3 (internal and external communications)",[37,2822,2823],{},[58,2824,2825],{},"Recover function to SOC 2:",[94,2827,2828],{},[97,2829,2830],{},"Recovery planning (RC.RP) maps to CC7.5 (recovery activities) and A1.2-A1.3 (Availability criteria)",[50,2832,2834],{"id":2833},"practical-considerations","Practical considerations",[37,2836,2837,2838,2840],{},"SOC 2 is principles-based rather than prescriptive, giving organizations flexibility in how they meet each criterion. Organizations that have built their ",[41,2839,1214],{"href":325}," around the NIST CSF can map their existing controls directly to SOC 2 criteria with minimal additional effort. The main gap is typically in the Privacy and Processing Integrity criteria, which have limited direct mapping to NIST CSF subcategories.",[32,2842,2844],{"id":2843},"nist-csf-to-iso-27001","NIST CSF to ISO 27001",[37,2846,2847],{},"ISO 27001 is an international standard for information security management systems (ISMS). It requires organizations to establish, implement, maintain, and continually improve an ISMS. The standard includes 93 controls organized across four themes in the 2022 revision (organizational, people, physical, and technological).",[50,2849,2762],{"id":2850},"key-mappings-1",[37,2852,2853],{},[58,2854,2855],{},"Identify function to ISO 27001:",[94,2857,2858,2861,2864],{},[97,2859,2860],{},"Asset management (ID.AM) maps to A.5 (Information security policies) and A.8 (Asset management controls in ISO 27001:2022)",[97,2862,2863],{},"Risk assessment (ID.RA) maps directly to clauses 6.1.2 and 8.2 (risk assessment process), which is the core of ISO 27001",[97,2865,2866],{},"Governance (ID.GV) maps to clauses 5.1 through 5.3 (leadership and commitment)",[37,2868,2869],{},[58,2870,2871],{},"Protect function to ISO 27001:",[94,2873,2874,2877,2880],{},[97,2875,2876],{},"Access control (PR.AC) maps to A.8.2 through A.8.5 (access control theme)",[97,2878,2879],{},"Data security (PR.DS) maps to A.8.10 through A.8.12 (data protection controls)",[97,2881,2882],{},"Awareness and training (PR.AT) maps to A.6.3 (information security awareness and training)",[37,2884,2885],{},[58,2886,2887],{},"Detect function to ISO 27001:",[94,2889,2890,2893],{},[97,2891,2892],{},"Security continuous monitoring (DE.CM) maps to A.8.15 (logging) and A.8.16 (monitoring activities)",[97,2894,2895],{},"Detection processes (DE.DP) maps to clause 9.1 (monitoring, measurement, analysis, and evaluation)",[37,2897,2898],{},[58,2899,2900],{},"Respond function to ISO 27001:",[94,2902,2903,2906],{},[97,2904,2905],{},"Response planning (RS.RP) maps to A.5.24 through A.5.28 (incident management)",[97,2907,2908],{},"Analysis (RS.AN) maps to A.5.27 (learning from information security incidents)",[37,2910,2911],{},[58,2912,2913],{},"Recover function to ISO 27001:",[94,2915,2916],{},[97,2917,2918],{},"Recovery planning (RC.RP) maps to A.5.29 and A.5.30 (ICT readiness for business continuity)",[50,2920,2834],{"id":2921},"practical-considerations-1",[37,2923,2924],{},"ISO 27001 and the NIST CSF share strong conceptual alignment. Both emphasize risk-based approaches, continuous improvement, and management engagement. Organizations pursuing ISO 27001 certification that already have NIST CSF profiles will find that much of the groundwork for the ISMS has already been completed. The primary additional effort for ISO 27001 involves establishing the formal management system structure (clauses 4 through 10) and conducting the required management reviews and internal audits.",[32,2926,2928],{"id":2927},"nist-csf-to-hipaa","NIST CSF to HIPAA",[37,2930,2931],{},"HIPAA's Security Rule establishes requirements for protecting electronic protected health information (ePHI). It is organized into Administrative, Physical, and Technical Safeguards.",[50,2933,2762],{"id":2934},"key-mappings-2",[37,2936,2937],{},[58,2938,2939],{},"Identify function to HIPAA:",[94,2941,2942,2945,2948],{},[97,2943,2944],{},"Risk assessment (ID.RA) maps directly to the HIPAA Security Rule requirement for risk analysis (45 CFR 164.308(a)(1)(ii)(A))",[97,2946,2947],{},"Asset management (ID.AM) maps to device and media controls (45 CFR 164.310(d))",[97,2949,2950],{},"Governance (ID.GV) maps to assigned security responsibility (45 CFR 164.308(a)(2))",[37,2952,2953],{},[58,2954,2955],{},"Protect function to HIPAA:",[94,2957,2958,2961,2964],{},[97,2959,2960],{},"Access control (PR.AC) maps to access controls (45 CFR 164.312(a)) and facility access controls (45 CFR 164.310(a))",[97,2962,2963],{},"Awareness and training (PR.AT) maps to security awareness and training (45 CFR 164.308(a)(5))",[97,2965,2966],{},"Data security (PR.DS) maps to transmission security (45 CFR 164.312(e)) and integrity controls (45 CFR 164.312(c))",[37,2968,2969],{},[58,2970,2971],{},"Detect function to HIPAA:",[94,2973,2974],{},[97,2975,2976],{},"Security continuous monitoring (DE.CM) maps to audit controls (45 CFR 164.312(b)) and information system activity review (45 CFR 164.308(a)(1)(ii)(D))",[37,2978,2979],{},[58,2980,2981],{},"Respond function to HIPAA:",[94,2983,2984,2987],{},[97,2985,2986],{},"Response planning (RS.RP) maps to security incident procedures (45 CFR 164.308(a)(6))",[97,2988,2989],{},"Communications (RS.CO) maps to breach notification requirements (45 CFR 164.400-414)",[37,2991,2992],{},[58,2993,2994],{},"Recover function to HIPAA:",[94,2996,2997],{},[97,2998,2999],{},"Recovery planning (RC.RP) maps to contingency plan (45 CFR 164.308(a)(7)) including data backup, disaster recovery, and emergency mode operations",[50,3001,2834],{"id":3002},"practical-considerations-2",[37,3004,3005],{},"HIPAA is less prescriptive than PCI DSS or ISO 27001, using terms like \"reasonable and appropriate\" to describe required safeguards. This flexibility means organizations must use their risk analysis to determine the specificity of controls, which aligns well with the NIST CSF's risk-based approach. HHS has published a crosswalk between the HIPAA Security Rule and the NIST CSF that provides detailed subcategory-level mappings.",[32,3007,3009],{"id":3008},"nist-csf-to-pci-dss","NIST CSF to PCI DSS",[37,3011,3012,3014,3015,167],{},[41,3013,1223],{"href":1222}," is the most prescriptive of the frameworks discussed here, with specific technical requirements and testing procedures for each of its ",[41,3016,3018],{"href":3017},"\u002Fframeworks\u002Fpci\u002Frequirements","12 requirements",[50,3020,2762],{"id":3021},"key-mappings-3",[37,3023,3024],{},[58,3025,3026],{},"Identify function to PCI DSS:",[94,3028,3029,3032,3035],{},[97,3030,3031],{},"Asset management (ID.AM) maps to Requirement 2 (system inventory and configuration management) and Requirement 12 (information security policy)",[97,3033,3034],{},"Risk assessment (ID.RA) maps to Requirement 12.3 (risk assessment)",[97,3036,3037],{},"Supply chain risk management (ID.SC) maps to Requirement 12.8 (third-party service provider management)",[37,3039,3040],{},[58,3041,3042],{},"Protect function to PCI DSS:",[94,3044,3045,3048,3051],{},[97,3046,3047],{},"Access control (PR.AC) maps to Requirements 7, 8, and 9 (access control, authentication, physical security)",[97,3049,3050],{},"Data security (PR.DS) maps to Requirements 3 and 4 (stored data protection and transmission encryption)",[97,3052,3053],{},"Protective technology (PR.PT) maps to Requirements 1 and 5 (network security controls and anti-malware)",[37,3055,3056],{},[58,3057,3058],{},"Detect function to PCI DSS:",[94,3060,3061,3064],{},[97,3062,3063],{},"Security continuous monitoring (DE.CM) maps to Requirement 10 (logging and monitoring) and Requirement 11 (vulnerability scanning and IDS\u002FIPS)",[97,3065,3066],{},"Anomalies and events (DE.AE) maps to Requirement 10.4 (audit log review)",[37,3068,3069],{},[58,3070,3071],{},"Respond function to PCI DSS:",[94,3073,3074],{},[97,3075,3076],{},"Response planning (RS.RP) maps to Requirement 12.10 (incident response plan)",[37,3078,3079],{},[58,3080,3081],{},"Recover function to PCI DSS:",[94,3083,3084],{},[97,3085,3086],{},"Recovery planning (RC.RP) maps to Requirement 12.10.2 (recovery procedures within the incident response plan)",[50,3088,2834],{"id":3089},"practical-considerations-3",[37,3091,3092,3093,3095],{},"PCI DSS controls are more specific than NIST CSF subcategories, meaning a single PCI DSS requirement may address multiple NIST CSF subcategories or vice versa. Organizations that use the NIST CSF as their primary framework will need to supplement their profiles with PCI DSS-specific technical controls. However, the NIST CSF provides the risk management and governance structure that supports a sustainable ",[41,3094,1471],{"href":1222}," program.",[32,3097,3099],{"id":3098},"building-a-unified-control-framework","Building a unified control framework",[37,3101,3102],{},"To operationalize framework mapping effectively:",[50,3104,3106],{"id":3105},"create-a-control-matrix","Create a control matrix",[37,3108,3109],{},"Build a master control matrix that lists each control once and maps it to every applicable framework requirement. This eliminates duplicate controls and ensures that evidence collected for one audit can be reused for others.",[50,3111,3113],{"id":3112},"centralize-evidence-collection","Centralize evidence collection",[37,3115,3116],{},"Implement a single repository for compliance evidence. When you collect evidence for a NIST CSF subcategory, tag it with the corresponding SOC 2 criteria, ISO 27001 controls, HIPAA safeguards, and PCI DSS requirements. This dramatically reduces evidence collection effort during audit season.",[50,3118,3120],{"id":3119},"harmonize-assessment-schedules","Harmonize assessment schedules",[37,3122,3123],{},"Align your internal assessments and external audits to minimize disruption. If your SOC 2 audit occurs in Q1 and your PCI DSS assessment in Q3, schedule internal control testing to feed both assessments rather than running separate testing cycles.",[50,3125,3127],{"id":3126},"use-nist-csf-as-the-organizing-layer","Use NIST CSF as the organizing layer",[37,3129,3130,3131,3134],{},"The NIST CSF's ",[41,3132,3133],{"href":1252},"five functions"," provide an intuitive organizing structure that stakeholders across the business can understand. Technical teams work at the subcategory level, mapping specific controls to framework requirements. Executives receive reporting at the function level, understanding the organization's posture across Identify, Protect, Detect, Respond, and Recover. This layered communication approach works because the NIST CSF was designed for exactly this purpose.",[50,3136,3138],{"id":3137},"leverage-implementation-tiers-for-maturity-tracking","Leverage implementation tiers for maturity tracking",[37,3140,3141,3142,3144],{},"Use ",[41,3143,244],{"href":283}," to track maturity across all mapped frameworks. As you progress from Tier 2 to Tier 3, the systematic policy-driven approach benefits every framework simultaneously. This is more efficient than tracking maturity separately for each compliance requirement.",[37,3146,3147],{},"Framework mapping is not a one-time project. As frameworks are updated (NIST CSF 2.0, PCI DSS v4.0, ISO 27001:2022), mappings must be refreshed to reflect new requirements and structural changes. Maintaining current mappings ensures that your unified control framework remains accurate and continues to reduce compliance overhead.",{"title":561,"searchDepth":562,"depth":562,"links":3149},[3150,3151,3155,3159,3163,3167],{"id":2741,"depth":562,"text":2742},{"id":2754,"depth":562,"text":2755,"children":3152},[3153,3154],{"id":2761,"depth":567,"text":2762},{"id":2833,"depth":567,"text":2834},{"id":2843,"depth":562,"text":2844,"children":3156},[3157,3158],{"id":2850,"depth":567,"text":2762},{"id":2921,"depth":567,"text":2834},{"id":2927,"depth":562,"text":2928,"children":3160},[3161,3162],{"id":2934,"depth":567,"text":2762},{"id":3002,"depth":567,"text":2834},{"id":3008,"depth":562,"text":3009,"children":3164},[3165,3166],{"id":3021,"depth":567,"text":2762},{"id":3089,"depth":567,"text":2834},{"id":3098,"depth":562,"text":3099,"children":3168},[3169,3170,3171,3172,3173],{"id":3105,"depth":567,"text":3106},{"id":3112,"depth":567,"text":3113},{"id":3119,"depth":567,"text":3120},{"id":3126,"depth":567,"text":3127},{"id":3137,"depth":567,"text":3138},"How the NIST Cybersecurity Framework maps to SOC 2, ISO 27001, HIPAA, and PCI DSS, enabling efficient multi-framework compliance.",{},[1254,3177,3178,3179,3180],"soc2","iso27001","hipaa","pci-dss",[1715,962,1256],{"title":3183,"description":3184},"Mapping NIST CSF to SOC 2, ISO 27001, HIPAA, and PCI DSS","Learn how NIST CSF maps to SOC 2, ISO 27001, HIPAA, and PCI DSS. Reduce audit fatigue with unified controls across multiple compliance frameworks.","5.frameworks\u002Fnistcsf\u002Fmapping-to-other-frameworks","PyHbyZtZIxNF1Nlz-mfVBFbQQE0BWZaGSpteiuaRN8o",{"id":3188,"title":3189,"body":3190,"description":3450,"extension":597,"faq":3451,"frameworkSlug":652,"lastUpdated":952,"meta":3465,"navigation":634,"path":194,"relatedTerms":3466,"relatedTopics":3471,"seo":3473,"stem":3476,"__hash__":3477},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fprotect-function.md","NIST CSF Protect Function",{"type":29,"value":3191,"toc":3436},[3192,3196,3202,3205,3209,3212,3215,3284,3288,3291,3294,3298,3301,3305,3308,3312,3315,3319,3322,3324,3327,3365,3367,3370,3408,3412,3415,3418,3420,3428],[32,3193,3195],{"id":3194},"what-is-the-nist-csf-protect-function","What is the NIST CSF Protect function?",[37,3197,159,3198,3201],{},[58,3199,3200],{},"Protect (PR) function"," implements the safeguards that ensure delivery of critical services and that limit or contain the impact of cybersecurity events. If Identify is the map and Govern is the strategy, Protect is where the majority of day-to-day cybersecurity engineering work happens. Firewalls, identity providers, endpoint agents, encryption, access reviews, secure configuration baselines, awareness training — almost every tangible cybersecurity control lives somewhere inside Protect.",[37,3203,3204],{},"Protect is also the function most at risk of becoming a tool-buying exercise. Organizations that skip straight from \"we need to do cybersecurity\" to \"let's buy an EDR\" typically end up with a large tool stack and thin outcomes. The discipline of the NIST Cybersecurity Framework is that every Protect control should map back to an outcome described in an Identify-driven risk assessment and a Govern-driven risk strategy. Protect earns its place not by the number of tools deployed but by the reduction in residual risk it delivers.",[32,3206,3208],{"id":3207},"how-protect-changed-in-nist-csf-20","How Protect changed in NIST CSF 2.0",[37,3210,3211],{},"NIST CSF 2.0 streamlined the Protect function. NIST CSF 1.1 contained six Protect categories: Identity Management, Authentication, and Access Control (PR.AC), Awareness and Training (PR.AT), Data Security (PR.DS), Information Protection Processes and Procedures (PR.IP), Maintenance (PR.MA), and Protective Technology (PR.PT). Several of these overlapped, and practitioners often had trouble deciding where specific controls belonged.",[37,3213,3214],{},"NIST CSF 2.0 reorganized Protect into five cleaner categories:",[695,3216,3217,3227],{},[698,3218,3219],{},[701,3220,3221,3223,3225],{},[704,3222,706],{},[704,3224,709],{},[704,3226,712],{},[714,3228,3229,3240,3251,3262,3273],{},[701,3230,3231,3234,3237],{},[719,3232,3233],{},"Identity Management, Authentication, and Access Control",[719,3235,3236],{},"PR.AA",[719,3238,3239],{},"Identity lifecycle, authentication, authorization, and least privilege",[701,3241,3242,3245,3248],{},[719,3243,3244],{},"Awareness and Training",[719,3246,3247],{},"PR.AT",[719,3249,3250],{},"Security-relevant awareness and role-based training",[701,3252,3253,3256,3259],{},[719,3254,3255],{},"Data Security",[719,3257,3258],{},"PR.DS",[719,3260,3261],{},"Confidentiality, integrity, and availability of data at rest, in transit, and in use",[701,3263,3264,3267,3270],{},[719,3265,3266],{},"Platform Security",[719,3268,3269],{},"PR.PS",[719,3271,3272],{},"Hardening, configuration, patching, and secure software supply chain of platforms",[701,3274,3275,3278,3281],{},[719,3276,3277],{},"Technology Infrastructure Resilience",[719,3279,3280],{},"PR.IR",[719,3282,3283],{},"Network, environmental, and infrastructure resilience against disruption",[50,3285,3287],{"id":3286},"identity-management-authentication-and-access-control-praa","Identity Management, Authentication, and Access Control (PR.AA)",[37,3289,3290],{},"PR.AA is where most of the security world's attention belongs. It covers the entire identity lifecycle — provisioning, authentication, authorization, re-certification, and deprovisioning — for users, services, and devices. Key PR.AA outcomes include multi-factor authentication on all remote and privileged access, least-privilege access controls, privileged access management with just-in-time elevation, access reviews at a defined cadence, and robust deprovisioning when employees leave.",[37,3292,3293],{},"Well-executed PR.AA is the single most impactful thing most organizations can do. Nearly every major breach of the last five years involved identity — credential theft, session hijacking, OAuth abuse, MFA fatigue, or a dormant account that should have been disabled.",[50,3295,3297],{"id":3296},"awareness-and-training-prat","Awareness and Training (PR.AT)",[37,3299,3300],{},"PR.AT covers cybersecurity awareness for all personnel and role-specific training for those with elevated responsibilities. General-purpose phishing awareness is table stakes; role-based training for developers, administrators, finance staff, and executives is where PR.AT delivers disproportionate value. Mature programs also train the board and senior leadership, because many of the Govern function's oversight obligations depend on leadership being literate in cybersecurity risk.",[50,3302,3304],{"id":3303},"data-security-prds","Data Security (PR.DS)",[37,3306,3307],{},"PR.DS protects the confidentiality, integrity, and availability of data across its lifecycle. It covers encryption at rest and in transit, key management, data loss prevention, integrity monitoring, data minimization, and secure data disposal. PR.DS outcomes should track the data classifications established in the Identify function — the most sensitive data warrants the strongest controls.",[50,3309,3311],{"id":3310},"platform-security-prps","Platform Security (PR.PS)",[37,3313,3314],{},"PR.PS consolidates several NIST CSF 1.1 categories into a unified focus on the platforms that run the organization's software: servers, endpoints, mobile devices, containers, cloud services, and the software supply chain. PR.PS covers secure configuration baselines, hardening, patching and vulnerability remediation, change management, and the integrity of the software supply chain from build through deployment.",[50,3316,3318],{"id":3317},"technology-infrastructure-resilience-prir","Technology Infrastructure Resilience (PR.IR)",[37,3320,3321],{},"PR.IR covers the resilience of the underlying infrastructure — networks, environmental controls, and the physical and virtual facilities that host the organization's systems. Network segmentation, redundancy, fail-over architectures, and environmental protections (power, cooling, physical access) all live here. PR.IR partially overlaps with the Recover function but focuses on the preventive side: building infrastructure that resists disruption in the first place.",[32,3323,799],{"id":798},[37,3325,3326],{},"A pragmatic sequence for standing up the Protect function:",[510,3328,3329,3335,3341,3347,3353,3359],{},[97,3330,3331,3334],{},[58,3332,3333],{},"Lock down identity first."," Enforce MFA everywhere it is possible, implement SSO, tier administrative accounts, and commit to quarterly access reviews. These PR.AA basics eliminate the majority of common attack paths.",[97,3336,3337,3340],{},[58,3338,3339],{},"Encrypt by default."," Encryption at rest for storage, TLS for data in transit, and managed key rotation. Tie key management to the Identify function's data classification so that the most sensitive data receives the strongest protection.",[97,3342,3343,3346],{},[58,3344,3345],{},"Establish configuration baselines."," Pick a standard (CIS Benchmarks, DISA STIGs, or a cloud provider's security baseline) and measure drift continuously.",[97,3348,3349,3352],{},[58,3350,3351],{},"Automate patching and vulnerability management."," The goal is not zero vulnerabilities; it is a short mean-time-to-remediate for the vulnerabilities that matter most.",[97,3354,3355,3358],{},[58,3356,3357],{},"Build a real awareness program."," Phishing simulations, role-based training, and annual certification. Metrics that matter: phishing click rate over time, training completion, reported suspicious emails.",[97,3360,3361,3364],{},[58,3362,3363],{},"Segment the network."," Flat networks are where ransomware thrives. Basic segmentation between workstations, servers, and operational technology dramatically reduces blast radius.",[32,3366,850],{"id":849},[37,3368,3369],{},"Protect programs commonly hit these walls:",[94,3371,3372,3378,3384,3390,3396,3402],{},[97,3373,3374,3377],{},[58,3375,3376],{},"Tool sprawl without outcome improvement."," Buying more tools does not automatically improve Protect maturity. Every tool should map to a specific NIST CSF subcategory and a measurable outcome.",[97,3379,3380,3383],{},[58,3381,3382],{},"MFA exceptions that swallow the benefit."," \"Emergency\" accounts, service accounts, and legacy applications without MFA undo most of the value of PR.AA. Track and retire these exceptions aggressively.",[97,3385,3386,3389],{},[58,3387,3388],{},"Stale access rights."," Access reviews that are performed but not acted on (access is never actually revoked) are a common audit finding. Build tooling that makes revocation the default.",[97,3391,3392,3395],{},[58,3393,3394],{},"Configuration drift."," Baselines that are set once and never re-measured drift within weeks. Continuous configuration monitoring is table stakes in modern Protect programs.",[97,3397,3398,3401],{},[58,3399,3400],{},"Training that nobody respects."," Hour-long cringe-worthy training videos fail both the compliance and the behavior-change test. Short, relevant, role-based training beats annual endurance tests.",[97,3403,3404,3407],{},[58,3405,3406],{},"Unclear ownership."," Protect controls commonly span IT, security, platform engineering, and product teams. Without clear ownership (set in the Govern function's GV.RR), controls fall through the cracks.",[32,3409,3411],{"id":3410},"measuring-protect-outcomes","Measuring Protect outcomes",[37,3413,3414],{},"The Protect function is the NIST CSF function with the widest gap between compliance reporting and real security outcomes. Compliance-first Protect programs optimize for \"controls in place.\" Outcome-first Protect programs optimize for metrics that reflect actual risk reduction: MFA coverage as a percentage of authentications, mean time to patch critical vulnerabilities, percentage of privileged access granted just in time rather than standing, phishing reporting rate, encryption coverage of sensitive data, and baseline compliance drift over time. These metrics should be reported to the Govern function's oversight process so leadership can tell whether Protect investments are actually moving the dial.",[37,3416,3417],{},"Mature NIST CSF Protect programs also test their safeguards continuously. Red-team exercises, penetration tests, breach-and-attack-simulation tooling, and purple-team collaboration all validate that Protect controls behave as expected under adversary conditions. Controls that look strong on paper and fail under realistic pressure are a common failure mode that only testing exposes.",[32,3419,905],{"id":904},[37,3421,3422,3423,374,3425,3427],{},"episki maps every Protect subcategory to concrete controls, evidence collection, and the owning team — then keeps that mapping live through integrations with your identity provider, endpoint management tooling, vulnerability scanners, and cloud providers. MFA coverage, access review completion, patch SLAs, and baseline drift all become real-time metrics on an executive dashboard. Controls that satisfy the NIST CSF Protect function are automatically mapped to the corresponding ",[41,3424,128],{"href":127},[41,3426,378],{"href":377},", HIPAA, PCI DSS, and CMMC requirements, so the same evidence satisfies multiple frameworks.",[37,3429,3430,3431,922,3434,167],{},"Ready to operate the NIST CSF Protect function instead of just documenting it? ",[41,3432,921],{"href":623,"rel":3433},[920],[41,3435,925],{"href":629},{"title":561,"searchDepth":562,"depth":562,"links":3437},[3438,3439,3446,3447,3448,3449],{"id":3194,"depth":562,"text":3195},{"id":3207,"depth":562,"text":3208,"children":3440},[3441,3442,3443,3444,3445],{"id":3286,"depth":567,"text":3287},{"id":3296,"depth":567,"text":3297},{"id":3303,"depth":567,"text":3304},{"id":3310,"depth":567,"text":3311},{"id":3317,"depth":567,"text":3318},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":3410,"depth":562,"text":3411},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF Protect function — identity and access, awareness and training, data security, platform security, and technology infrastructure resilience.",{"items":3452},[3453,3456,3459,3462],{"label":3454,"content":3455},"What is the Protect function in NIST CSF?","The Protect function implements safeguards to ensure delivery of critical services and to limit or contain the impact of cybersecurity events. Protect is where most preventive controls live — identity and access management, encryption, endpoint hardening, secure configuration, awareness training, and infrastructure resilience.",{"label":3457,"content":3458},"How did the Protect function change in NIST CSF 2.0?","NIST CSF 2.0 restructured Protect into five categories: Identity Management, Authentication, and Access Control (PR.AA), Awareness and Training (PR.AT), Data Security (PR.DS), Platform Security (PR.PS), and Technology Infrastructure Resilience (PR.IR). Several CSF 1.1 categories were consolidated — Information Protection Processes and Procedures (PR.IP) and Maintenance (PR.MA) were merged into PR.PS and PR.IR.",{"label":3460,"content":3461},"What is the most impactful Protect category?","Identity Management, Authentication, and Access Control (PR.AA) is typically the highest-leverage Protect category. The majority of modern breaches involve compromised identities — phished credentials, reused passwords, missing MFA, or over-privileged accounts. Strong PR.AA dramatically reduces the blast radius of a successful attack.",{"label":3463,"content":3464},"Do I need every Protect subcategory at the same maturity level?","No. NIST CSF expects organizations to set different target maturity levels for different subcategories based on risk. A healthcare provider may need Tier 4 maturity for PR.DS (Data Security) while Tier 2 is adequate for Platform Security. The target profile built in the Govern function drives these choices.",{},[3467,3468,3469,3470],"access-control","encryption","key-management","mfa",[2031,3472,961,962],"detect-function",{"title":3474,"description":3475},"NIST CSF Protect Function (PR): Categories, Subcategories, and Implementation","The NIST CSF Protect function deploys safeguards that limit the impact of cybersecurity events. Learn PR.AA, PR.AT, PR.DS, PR.PS, and PR.IR and how to implement each.","5.frameworks\u002Fnistcsf\u002Fprotect-function","KilPtQqSJw7OZ3o0xYRS0vV3Xra-lLpndZBovaGVeHg",{"id":3479,"title":3480,"body":3481,"description":3730,"extension":597,"faq":3731,"frameworkSlug":652,"lastUpdated":952,"meta":3745,"navigation":634,"path":236,"relatedTerms":3746,"relatedTopics":3750,"seo":3751,"stem":3754,"__hash__":3755},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Frecover-function.md","NIST CSF Recover Function",{"type":29,"value":3482,"toc":3719},[3483,3487,3493,3496,3499,3503,3506,3542,3545,3549,3552,3555,3587,3591,3594,3596,3599,3642,3644,3647,3691,3695,3698,3701,3703,3711],[32,3484,3486],{"id":3485},"what-is-the-nist-csf-recover-function","What is the NIST CSF Recover function?",[37,3488,159,3489,3492],{},[58,3490,3491],{},"Recover (RC) function"," is the final function in the NIST Cybersecurity Framework lifecycle. Its purpose is to maintain plans for resilience and to restore any capabilities or services that were impaired by a cybersecurity incident. Recover picks up where Respond ends — once the attacker has been contained and eradicated, Recover is responsible for getting the business back to normal operation, rebuilding trust with customers and regulators, and capturing lessons that strengthen the rest of the NIST CSF program.",[37,3494,3495],{},"Recover is the function most often conflated with business continuity and disaster recovery (BC\u002FDR), and for good reason: the two disciplines share tooling, plans, and testing practices. But Recover is specifically the cybersecurity slice of BC\u002FDR. Recovering from a hurricane, a power outage, or a cloud provider failure is traditional BC\u002FDR territory. Recovering from ransomware, destructive malware, data integrity compromise, or a supplier cyber incident adds cybersecurity-specific concerns — forensic preservation, supply-chain verification, credential rotation, and regulatory follow-through — that generic BC\u002FDR plans rarely cover in depth.",[37,3497,3498],{},"Mature organizations treat Recover as the end of an incident lifecycle and the beginning of a program improvement cycle. Every recovery reveals gaps — controls that failed, backups that were incomplete, runbooks that were wrong — and those gaps feed the Identify function's Improvement category and the Govern function's oversight loop.",[32,3500,3502],{"id":3501},"how-recover-changed-in-nist-csf-20","How Recover changed in NIST CSF 2.0",[37,3504,3505],{},"NIST CSF 1.1 contained three Recover categories: Recovery Planning (RC.RP), Improvements (RC.IM), and Communications (RC.CO). NIST CSF 2.0 streamlined Recover into two:",[695,3507,3508,3518],{},[698,3509,3510],{},[701,3511,3512,3514,3516],{},[704,3513,706],{},[704,3515,709],{},[704,3517,712],{},[714,3519,3520,3531],{},[701,3521,3522,3525,3528],{},[719,3523,3524],{},"Incident Recovery Plan Execution",[719,3526,3527],{},"RC.RP",[719,3529,3530],{},"Executing recovery plans to restore services, systems, and data",[701,3532,3533,3536,3539],{},[719,3534,3535],{},"Incident Recovery Communication",[719,3537,3538],{},"RC.CO",[719,3540,3541],{},"Internal and external communications during and after recovery",[37,3543,3544],{},"The Improvements category (RC.IM) was moved to the Identify function as part of the new Improvement category (ID.IM), and recovery planning itself (the development and maintenance of recovery plans) is now governed through the Govern function's policy and oversight categories. The remaining Recover function is tightly focused on execution and communication during the recovery phase.",[50,3546,3548],{"id":3547},"incident-recovery-plan-execution-rcrp","Incident Recovery Plan Execution (RC.RP)",[37,3550,3551],{},"RC.RP covers the actual execution of the organization's incident recovery plans: restoring systems and data from known-good sources, verifying the integrity of restored systems, re-issuing credentials, re-establishing network connectivity, and returning services to production in a controlled sequence. RC.RP outcomes include tested recovery procedures, defined recovery priorities based on business criticality, and clear handoff protocols from the Respond function.",[37,3553,3554],{},"Key RC.RP considerations:",[94,3556,3557,3563,3569,3575,3581],{},[97,3558,3559,3562],{},[58,3560,3561],{},"Backup integrity and immutability."," Backups that were encrypted by ransomware are not backups. Immutable, air-gapped, or offline backups are core to modern RC.RP.",[97,3564,3565,3568],{},[58,3566,3567],{},"Known-good restoration sources."," Rebuilding from potentially compromised golden images reintroduces the same compromise. RC.RP requires verified clean sources.",[97,3570,3571,3574],{},[58,3572,3573],{},"Forensic preservation before restoration."," Restoring systems without first preserving forensic evidence destroys information that may be needed later.",[97,3576,3577,3580],{},[58,3578,3579],{},"Staged restoration."," Critical business services come back first, in an order that accounts for dependencies between systems.",[97,3582,3583,3586],{},[58,3584,3585],{},"Credential and secret rotation."," Any credential that could have been exposed during the incident must be rotated before services return to production.",[50,3588,3590],{"id":3589},"incident-recovery-communication-rcco","Incident Recovery Communication (RC.CO)",[37,3592,3593],{},"RC.CO covers the communications specific to the recovery phase: status updates to customers, partners, regulators, and employees during restoration; public updates if the incident was disclosed; and post-recovery communications that close out the incident. RC.CO continues the communication discipline established in the Respond function's RS.CO category but shifts focus from incident acknowledgment to restoration progress and final resolution.",[32,3595,799],{"id":798},[37,3597,3598],{},"A pragmatic sequence for standing up the Recover function:",[510,3600,3601,3607,3613,3619,3625,3631,3637],{},[97,3602,3603,3606],{},[58,3604,3605],{},"Align with the business."," Work with business stakeholders to document Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) for each critical business service. These anchor every other Recover decision.",[97,3608,3609,3612],{},[58,3610,3611],{},"Map technical recovery capabilities to business services."," Each critical business service should have a documented recovery runbook that maps systems, data, dependencies, and responsible teams.",[97,3614,3615,3618],{},[58,3616,3617],{},"Harden backups."," Immutable backups, air-gapped copies, and regularly tested restore procedures are the foundation of modern cybersecurity recovery.",[97,3620,3621,3624],{},[58,3622,3623],{},"Test recoveries."," A backup that has never been restored is not a backup. Schedule regular restore tests and include full end-to-end business service recovery in annual exercises.",[97,3626,3627,3630],{},[58,3628,3629],{},"Pre-stage clean images."," Maintain verified clean golden images of critical systems outside of the production environment so that recovery is not dependent on the compromised environment.",[97,3632,3633,3636],{},[58,3634,3635],{},"Rehearse communications."," Include RC.CO communication drills in tabletop exercises so that customer updates, regulator updates, and employee communications during a recovery are not improvised.",[97,3638,3639,3641],{},[58,3640,2237],{}," Every real recovery and every exercise produces lessons learned that feed ID.IM and update policies and controls across the NIST CSF program.",[32,3643,850],{"id":849},[37,3645,3646],{},"Recover programs commonly hit these walls:",[94,3648,3649,3655,3661,3667,3673,3679,3685],{},[97,3650,3651,3654],{},[58,3652,3653],{},"Untested backups."," Organizations discover during a real incident that their backups are incomplete, corrupted, stored in a compromised location, or cannot be restored within the RTO.",[97,3656,3657,3660],{},[58,3658,3659],{},"Ransomware on backups."," Attackers deliberately target backup infrastructure. Backups without immutability or offline copies fail exactly when they are needed.",[97,3662,3663,3666],{},[58,3664,3665],{},"RTO and RPO assumptions that don't match reality."," RTO and RPO numbers written in a BC\u002FDR plan often have no relationship to what is actually achievable. Testing surfaces the gap.",[97,3668,3669,3672],{},[58,3670,3671],{},"Forgotten dependencies."," Systems restored without their dependencies (identity providers, DNS, secrets management, logging) restart in a broken state. Dependency mapping is a core Recover discipline.",[97,3674,3675,3678],{},[58,3676,3677],{},"Reintroducing compromise."," Rebuilding from potentially compromised images or failing to rotate credentials allows the attacker to return the moment services come back online.",[97,3680,3681,3684],{},[58,3682,3683],{},"Recovery without communication."," Customers who do not hear from you during a recovery assume the worst. Silence is a choice and usually the wrong one.",[97,3686,3687,3690],{},[58,3688,3689],{},"No lessons-learned process."," Organizations that close out incidents without a structured review lose the single biggest benefit of having had the incident.",[32,3692,3694],{"id":3693},"measuring-recover-outcomes","Measuring Recover outcomes",[37,3696,3697],{},"The primary Recover metrics are the two that most directly reflect business impact: Recovery Time Objective (RTO) and Recovery Point Objective (RPO), expressed for each critical business service and compared against the actual RTO and RPO achieved in exercises and real recoveries. Mature programs add supporting metrics: backup coverage of critical systems, backup restoration test success rate, percentage of recoveries completed within the stated RTO, time to first customer communication during a recovery, and the percentage of recoveries that produced a documented lessons-learned review. Outcomes are only credible when the underlying restoration procedures have been tested against realistic cybersecurity scenarios — not just generic infrastructure-loss scenarios.",[37,3699,3700],{},"Ransomware-specific recovery readiness deserves its own review cadence. Can the organization restore a full critical service from immutable or offline backups without touching the compromised environment? Are golden images verified, stored outside the blast radius, and recent enough to matter? Are credential rotation runbooks tested at scale? These questions have become table-stakes for any serious NIST CSF Recover function and should be reviewed explicitly by the Govern function's oversight process.",[32,3702,905],{"id":904},[37,3704,3705,3706,374,3708,3710],{},"episki maps every Recover subcategory to the plans, playbooks, backup systems, and test schedules that actually deliver the outcome. Recovery plans are structured data with linked dependencies, owners, and test history — not static documents in a shared drive. RTO and RPO targets are measurable and tracked against real recovery tests. Post-recovery lessons learned automatically flow into the NIST CSF improvement category (ID.IM) and into the Protect, Detect, Respond, and Govern functions so that every recovery makes the program stronger. Evidence of recovery tests, plan reviews, and improvements maps automatically to the corresponding requirements in ",[41,3707,128],{"href":127},[41,3709,378],{"href":377},", HIPAA, PCI DSS, and CMMC.",[37,3712,3713,3714,922,3717,167],{},"Ready to know — not hope — that the NIST CSF Recover function will work when it has to? ",[41,3715,921],{"href":623,"rel":3716},[920],[41,3718,925],{"href":629},{"title":561,"searchDepth":562,"depth":562,"links":3720},[3721,3722,3726,3727,3728,3729],{"id":3485,"depth":562,"text":3486},{"id":3501,"depth":562,"text":3502,"children":3723},[3724,3725],{"id":3547,"depth":567,"text":3548},{"id":3589,"depth":567,"text":3590},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":3693,"depth":562,"text":3694},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF Recover function — recovery planning, recovery execution, improvements, and communications after a cybersecurity incident.",{"items":3732},[3733,3736,3739,3742],{"label":3734,"content":3735},"What is the Recover function in NIST CSF?","The Recover function maintains plans for resilience and restores any capabilities or services that were impaired due to a cybersecurity incident. Recover covers recovery planning, recovery execution, improvements based on lessons learned, and the internal and external communications associated with restoration.",{"label":3737,"content":3738},"How did the Recover function change in NIST CSF 2.0?","NIST CSF 2.0 consolidated Recover into two categories: Incident Recovery Plan Execution (RC.RP) and Incident Recovery Communication (RC.CO). The Improvements category from CSF 1.1 was moved into the Identify function's new Improvement category (ID.IM). Recovery planning itself is now governed through the Govern function.",{"label":3740,"content":3741},"How does Recover relate to business continuity and disaster recovery?","Recover is the cybersecurity-specific subset of the broader business continuity and disaster recovery (BC\u002FDR) discipline. Cybersecurity recovery plans should be aligned with the organization's BC\u002FDR strategy but explicitly account for cybersecurity scenarios such as ransomware, destructive malware, data integrity loss, and supplier cyber incidents that disrupt service.",{"label":3743,"content":3744},"What are the key metrics for the Recover function?","The two most important Recover metrics are Recovery Time Objective (RTO) — how quickly a service must be restored — and Recovery Point Objective (RPO) — how much data loss is tolerable. Mature programs also track the actual RTO and RPO achieved during tests and real incidents, plus the completeness and integrity of restored systems and data.",{},[3747,3748,3749],"business-continuity","disaster-recovery","incident-response",[960,959,961,962],{"title":3752,"description":3753},"NIST CSF Recover Function (RC): Categories, Subcategories, and Implementation","The NIST CSF Recover function restores services after an incident. Learn RC.RP and RC.CO, tie recovery to BCP\u002FDR, and close the loop into program improvements.","5.frameworks\u002Fnistcsf\u002Frecover-function","LfZOXA9eGQ7MBHLqHQzNv74AF_pZu_47n_Ib639_pMQ",{"id":3757,"title":3758,"body":3759,"description":4006,"extension":597,"faq":4007,"frameworkSlug":652,"lastUpdated":952,"meta":4021,"navigation":634,"path":222,"relatedTerms":4022,"relatedTopics":4024,"seo":4026,"stem":4029,"__hash__":4030},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Frespond-function.md","NIST CSF Respond Function",{"type":29,"value":3760,"toc":3993},[3761,3765,3771,3774,3777,3781,3784,3842,3845,3849,3852,3856,3859,3863,3866,3870,3873,3875,3878,3922,3924,3927,3965,3969,3972,3975,3977,3985],[32,3762,3764],{"id":3763},"what-is-the-nist-csf-respond-function","What is the NIST CSF Respond function?",[37,3766,159,3767,3770],{},[58,3768,3769],{},"Respond (RS) function"," contains the activities an organization performs once a cybersecurity incident has been detected. Respond is the function that gets stress-tested under the worst conditions: at 3 a.m., with incomplete information, under regulatory pressure, while the attacker is still in the environment. The quality of an organization's Respond function is often invisible until the moment it is desperately needed.",[37,3772,3773],{},"Respond in the NIST Cybersecurity Framework is deliberately broader than what many organizations call \"incident response.\" It includes not only the technical work of containment, eradication, and analysis, but also the governance work of coordinating legal, communications, human resources, insurance, law enforcement, and regulators. A technically excellent containment performed without legal oversight, without regulator notification, or without customer communication can still produce a catastrophic outcome.",[37,3775,3776],{},"Respond is where the Govern function's policies and the Identify function's asset and risk data get their most important test. An incident response team fights better with a current asset inventory, clear ownership, a defined risk-tolerance decision authority, and pre-approved communication templates. Every shortcut taken during Identify, Govern, and Protect shows up during Respond.",[32,3778,3780],{"id":3779},"how-respond-changed-in-nist-csf-20","How Respond changed in NIST CSF 2.0",[37,3782,3783],{},"NIST CSF 1.1 organized Respond into five categories: Response Planning (RS.RP), Communications (RS.CO), Analysis (RS.AN), Mitigation (RS.MI), and Improvements (RS.IM). NIST CSF 2.0 restructured this into four:",[695,3785,3786,3796],{},[698,3787,3788],{},[701,3789,3790,3792,3794],{},[704,3791,706],{},[704,3793,709],{},[704,3795,712],{},[714,3797,3798,3809,3820,3831],{},[701,3799,3800,3803,3806],{},[719,3801,3802],{},"Incident Management",[719,3804,3805],{},"RS.MA",[719,3807,3808],{},"Executing the incident response plan, triage, categorization, escalation",[701,3810,3811,3814,3817],{},[719,3812,3813],{},"Incident Analysis",[719,3815,3816],{},"RS.AN",[719,3818,3819],{},"Investigating scope, root cause, impact, and preserving evidence",[701,3821,3822,3825,3828],{},[719,3823,3824],{},"Incident Response Reporting and Communication",[719,3826,3827],{},"RS.CO",[719,3829,3830],{},"Internal, external, regulatory, and law enforcement communications",[701,3832,3833,3836,3839],{},[719,3834,3835],{},"Incident Mitigation",[719,3837,3838],{},"RS.MI",[719,3840,3841],{},"Containment, eradication, and prevention of further expansion",[37,3843,3844],{},"The Improvements category from CSF 1.1 was folded into the Identify function's new Improvement category (ID.IM) and into the Govern function. Response Planning is now largely owned by the Govern function (policy, plans, playbooks) with execution governed by RS.MA.",[50,3846,3848],{"id":3847},"incident-management-rsma","Incident Management (RS.MA)",[37,3850,3851],{},"RS.MA covers the execution of the incident response plan itself — how incidents are declared, triaged, categorized by severity, escalated to the appropriate authorities, and managed through a defined lifecycle. RS.MA also covers the coordination of roles across IT, security, legal, human resources, communications, executives, and external partners. A well-run RS.MA process produces a consistent experience regardless of which incident commander is on duty.",[50,3853,3855],{"id":3854},"incident-analysis-rsan","Incident Analysis (RS.AN)",[37,3857,3858],{},"RS.AN is the investigative arm of the Respond function. It covers forensic analysis of affected systems, scope determination, root cause analysis, evidence preservation, and correlation with external threat intelligence. RS.AN outputs feed both RS.MI (so mitigations are targeted correctly) and the post-incident lessons-learned loop that drives ID.IM.",[50,3860,3862],{"id":3861},"incident-response-reporting-and-communication-rsco","Incident Response Reporting and Communication (RS.CO)",[37,3864,3865],{},"RS.CO covers every communication associated with an incident: internal updates to leadership and employees, external updates to customers and partners, regulatory notifications (breach notification laws, SEC disclosure, sector-specific rules), law enforcement coordination, insurance claim notifications, and public-relations statements. RS.CO is where many incidents turn from manageable into publicly damaging. Pre-drafted templates, decision authorities, and rehearsed communication protocols are non-negotiable.",[50,3867,3869],{"id":3868},"incident-mitigation-rsmi","Incident Mitigation (RS.MI)",[37,3871,3872],{},"RS.MI is the containment and eradication arm: isolating affected systems, revoking compromised credentials, blocking malicious network traffic, removing persistence, patching exploited vulnerabilities, and ensuring the attacker cannot regain access. RS.MI hands off to the Recover function once eradication is complete and restoration begins.",[32,3874,799],{"id":798},[37,3876,3877],{},"A pragmatic sequence for operating the Respond function:",[510,3879,3880,3886,3892,3898,3904,3910,3916],{},[97,3881,3882,3885],{},[58,3883,3884],{},"Write a usable incident response plan."," A ten-page plan that assigns roles, lists escalation contacts, documents severity criteria, and references playbooks for common scenarios beats a hundred-page compliance artifact.",[97,3887,3888,3891],{},[58,3889,3890],{},"Name an incident commander role."," One person (with backups) runs each incident. Ambiguity in command costs time.",[97,3893,3894,3897],{},[58,3895,3896],{},"Pre-draft communication templates."," Customer notifications, internal all-hands announcements, regulator notifications, and board briefings should be drafted, reviewed by legal and communications, and stored with the incident response plan.",[97,3899,3900,3903],{},[58,3901,3902],{},"Rehearse."," Tabletop exercises at least annually, ideally quarterly, with realistic scenarios drawn from current threat intelligence. Include legal, communications, and executives in the exercises.",[97,3905,3906,3909],{},[58,3907,3908],{},"Establish external relationships before you need them."," Digital forensics and incident response (DFIR) retainer, cyber insurance carrier contacts, outside counsel, law enforcement liaisons — all identified and contracted in advance.",[97,3911,3912,3915],{},[58,3913,3914],{},"Integrate with Detect."," Clear escalation criteria from DE.AE into RS.MA so analysts know exactly when an adverse event becomes a declared incident.",[97,3917,3918,3921],{},[58,3919,3920],{},"Close the loop."," Every incident produces a post-incident review that feeds improvements into ID.IM, Govern, and the Protect and Detect backlogs.",[32,3923,850],{"id":849},[37,3925,3926],{},"Respond programs commonly hit these walls:",[94,3928,3929,3935,3941,3947,3953,3959],{},[97,3930,3931,3934],{},[58,3932,3933],{},"Plans that exist on paper but not in practice."," An incident response plan that has not been rehearsed in the last twelve months is a liability.",[97,3936,3937,3940],{},[58,3938,3939],{},"Ambiguous decision authority."," During an incident there is no time to debate who can authorize taking systems offline, issuing a customer notification, or engaging law enforcement. Decision authorities must be documented in advance.",[97,3942,3943,3946],{},[58,3944,3945],{},"Regulatory notification misses."," Breach notification laws and sector-specific rules (HIPAA, PCI DSS, GDPR, state privacy laws, SEC cybersecurity disclosure, DORA) have tight clocks. Tracking regulator obligations per data type per jurisdiction is a core Respond capability that belongs in the Govern function's organizational context.",[97,3948,3949,3952],{},[58,3950,3951],{},"Evidence handling mistakes."," Rebooting a compromised system, deleting logs, or operating from a memory image without preservation practices destroys forensic evidence that may be needed for civil, criminal, insurance, or regulatory purposes.",[97,3954,3955,3958],{},[58,3956,3957],{},"Communication silence."," Delayed or inconsistent communication during an incident erodes trust with customers, regulators, and employees. Pre-approved templates and a defined communication cadence are essential.",[97,3960,3961,3964],{},[58,3962,3963],{},"No integration with Recover."," Respond and Recover are separate NIST CSF functions but they share time and people. A handoff protocol between the two is easy to overlook.",[32,3966,3968],{"id":3967},"measuring-respond-outcomes","Measuring Respond outcomes",[37,3970,3971],{},"Respond metrics focus on speed, consistency, and completeness. The headline metrics are mean time to contain (MTTC) — how quickly an active incident is contained after detection — and mean time to eradicate (MTTE) — how quickly the attacker is fully removed from the environment. Beyond the time metrics, mature programs also track the percentage of incidents managed fully within the documented playbook, the time to first external communication for publicly disclosable incidents, on-time rate for regulatory notifications, and the proportion of incidents that produced a documented lessons-learned review. Those last two metrics tie Respond directly to Govern's oversight expectations and to ID.IM.",[37,3973,3974],{},"Tabletop exercise cadence and realism are themselves measurable. Organizations that run two or more cross-functional tabletops per year, involve executives and legal counsel, and introduce curveballs drawn from current threat intelligence consistently outperform organizations that treat tabletops as an annual compliance check. Exercise outputs — gaps identified, playbook updates, new contact information — belong in the same improvement loop that captures lessons from real incidents.",[32,3976,905],{"id":904},[37,3978,3979,3980,374,3982,3984],{},"episki operationalizes the Respond function end to end: incident response plans, playbooks, tabletop exercise schedules, contact directories, communication templates, and regulatory notification trackers live as structured data rather than scattered documents. Incidents are declared, tracked, and triaged in a workflow that captures RS.MA, RS.AN, RS.CO, and RS.MI evidence automatically, producing audit-ready artifacts for ",[41,3981,128],{"href":127},[41,3983,378],{"href":377},", HIPAA, and PCI DSS reviewers. Post-incident reviews feed improvements directly into the Protect, Detect, Govern, and Identify functions so that every incident makes the next one less likely.",[37,3986,3987,3988,922,3991,167],{},"Ready to prove the NIST CSF Respond function before the next incident does? ",[41,3989,921],{"href":623,"rel":3990},[920],[41,3992,925],{"href":629},{"title":561,"searchDepth":562,"depth":562,"links":3994},[3995,3996,4002,4003,4004,4005],{"id":3763,"depth":562,"text":3764},{"id":3779,"depth":562,"text":3780,"children":3997},[3998,3999,4000,4001],{"id":3847,"depth":567,"text":3848},{"id":3854,"depth":567,"text":3855},{"id":3861,"depth":567,"text":3862},{"id":3868,"depth":567,"text":3869},{"id":798,"depth":562,"text":799},{"id":849,"depth":562,"text":850},{"id":3967,"depth":562,"text":3968},{"id":904,"depth":562,"text":905},"A complete guide to the NIST CSF Respond function — incident management, analysis, mitigation, reporting, and communications during a cybersecurity event.",{"items":4008},[4009,4012,4015,4018],{"label":4010,"content":4011},"What is the Respond function in NIST CSF?","The Respond function contains the activities an organization takes once a cybersecurity incident has been detected. Respond covers incident management, analysis, mitigation, reporting, and both internal and external communications. Its purpose is to contain the impact of an incident, preserve evidence, meet regulatory notification obligations, and set up the Recover function to restore operations.",{"label":4013,"content":4014},"How did the Respond function change in NIST CSF 2.0?","NIST CSF 2.0 restructured Respond around four categories: Incident Management (RS.MA), Incident Analysis (RS.AN), Incident Response Reporting and Communication (RS.CO), and Incident Mitigation (RS.MI). The Improvements category from CSF 1.1 was consolidated into Identify's new Improvement category (ID.IM) and the Govern function.",{"label":4016,"content":4017},"What is the difference between Respond and Recover?","Respond focuses on the active phase of the incident: containment, eradication, analysis, and communication. Recover focuses on restoring normal operations, implementing long-term improvements, and communicating recovery progress. Many Recover activities begin during Respond — the two functions overlap in time but have distinct outcomes.",{"label":4019,"content":4020},"Do small organizations need a formal incident response plan?","Yes. Regardless of size, organizations need a written incident response plan that names roles, escalation paths, internal and external communication templates, and legal and regulatory notification obligations. The plan does not need to be long — a tight ten-page plan that the team has actually rehearsed beats a hundred-page plan nobody has read.",{},[3749,4023],"breach-notification",[3472,4025,961,962],"recover-function",{"title":4027,"description":4028},"NIST CSF Respond Function (RS): Categories, Subcategories, and Implementation","The NIST CSF Respond function governs how organizations act during a cybersecurity incident. Learn RS.MA, RS.AN, RS.MI, RS.CO, and the incident response lifecycle.","5.frameworks\u002Fnistcsf\u002Frespond-function","iGo6rHe-stXsvTuW9NkdVB69k3g4Caa0hnoAAeZPC4Y",{"id":4032,"title":4033,"body":4034,"description":4369,"extension":597,"faq":4370,"frameworkSlug":652,"lastUpdated":952,"meta":4384,"navigation":634,"path":141,"relatedTerms":4385,"relatedTopics":4386,"seo":4387,"stem":4390,"__hash__":4391},"frameworkTopics\u002F5.frameworks\u002Fnistcsf\u002Fv2-changes.md","NIST CSF 2.0 Changes",{"type":29,"value":4035,"toc":4348},[4036,4040,4043,4046,4050,4053,4057,4060,4064,4067,4073,4079,4085,4090,4095,4101,4105,4111,4115,4118,4121,4132,4135,4139,4142,4146,4152,4158,4178,4184,4188,4191,4194,4197,4201,4204,4207,4211,4214,4235,4241,4245,4248,4262,4265,4269,4275,4278,4282,4285,4288,4308,4312,4315,4321,4327,4333,4339,4345],[32,4037,4039],{"id":4038},"the-evolution-to-nist-csf-20","The evolution to NIST CSF 2.0",[37,4041,4042],{},"The National Institute of Standards and Technology (NIST) published the Cybersecurity Framework 2.0 in February 2024, marking the first major revision since the framework's original release in 2014 and its minor update to version 1.1 in 2018. CSF 2.0 reflects a decade of real-world usage, stakeholder feedback, and lessons learned from the evolving cybersecurity landscape.",[37,4044,4045],{},"The update was driven by several factors: the need to address governance gaps that organizations encountered when implementing the original framework, the expanding scope of cybersecurity risk beyond critical infrastructure, the growing importance of supply chain security, and the desire to improve the framework's usability for organizations of all sizes and maturity levels.",[32,4047,4049],{"id":4048},"the-new-govern-function","The new Govern function",[37,4051,4052],{},"The most significant structural change in NIST CSF 2.0 is the addition of a sixth core function: Govern (GV). This function elevates cybersecurity governance from a subcategory within the Identify function to a standalone function that underpins all five original functions.",[50,4054,4056],{"id":4055},"why-governance-was-elevated","Why governance was elevated",[37,4058,4059],{},"In NIST CSF 1.1, governance was addressed through the Identify function's Governance category (ID.GV). In practice, organizations often treated governance as a secondary concern, focusing on technical controls in the Protect and Detect functions while neglecting the management structures needed to sustain those controls. CSF 2.0 addresses this by making governance an explicit, top-level function that informs and directs all other cybersecurity activities.",[50,4061,4063],{"id":4062},"govern-function-categories","Govern function categories",[37,4065,4066],{},"The Govern function includes the following categories:",[37,4068,4069,4072],{},[58,4070,4071],{},"Organizational context (GV.OC)"," - Understand the organizational mission, stakeholder expectations, and legal and regulatory requirements that influence cybersecurity risk management. This category ensures that cybersecurity strategy aligns with business objectives.",[37,4074,4075,4078],{},[58,4076,4077],{},"Risk management strategy (GV.RM)"," - Establish and communicate the organization's cybersecurity risk management priorities, constraints, risk tolerance, and appetite. This was previously under the Identify function but is now positioned as a governance responsibility, reinforcing that risk management strategy is a leadership decision.",[37,4080,4081,4084],{},[58,4082,4083],{},"Roles, responsibilities, and authorities (GV.RR)"," - Define and communicate cybersecurity roles, responsibilities, and authorities across the organization. This includes ensuring that cybersecurity responsibilities are assigned at appropriate levels and that personnel have the authority and resources to fulfill their roles.",[37,4086,4087,4089],{},[58,4088,1881],{}," - Establish, communicate, and enforce cybersecurity policies that are informed by the organizational context and risk management strategy. Policies should be reviewed and updated regularly to remain current with evolving threats and business changes.",[37,4091,4092,4094],{},[58,4093,1888],{}," - Use results from cybersecurity risk management activities to inform and adjust the organization's strategy. This creates a feedback loop where operational cybersecurity data informs governance decisions, which in turn shape operational priorities.",[37,4096,4097,4100],{},[58,4098,4099],{},"Cybersecurity supply chain risk management (GV.SC)"," - Identify, establish, manage, monitor, and improve supply chain cybersecurity risk management processes. This category was significantly expanded from its position in CSF 1.1 and is discussed in detail below.",[50,4102,4104],{"id":4103},"impact-on-existing-programs","Impact on existing programs",[37,4106,4107,4108,4110],{},"Organizations that built their cybersecurity programs around the original five functions will need to restructure their ",[41,4109,1214],{"href":325}," to incorporate the Govern function. In many cases, the activities described in the Govern function are already being performed but may not be formally documented or consistently applied. The elevation to a standalone function provides an opportunity to formalize and strengthen governance practices.",[32,4112,4114],{"id":4113},"expanded-scope-beyond-critical-infrastructure","Expanded scope beyond critical infrastructure",[37,4116,4117],{},"NIST CSF 1.0 was originally developed under Executive Order 13636 with a primary focus on critical infrastructure sectors (energy, healthcare, financial services, etc.). While it was always available for any organization to use, its framing and examples were oriented toward critical infrastructure.",[37,4119,4120],{},"NIST CSF 2.0 explicitly broadens the framework's intended audience to all organizations, regardless of size, sector, or cybersecurity maturity. This change is reflected in several ways:",[94,4122,4123,4126,4129],{},[97,4124,4125],{},"The framework's title dropped \"for Improving Critical Infrastructure Cybersecurity\" in favor of broader applicability",[97,4127,4128],{},"Examples and guidance address the needs of small and medium-sized organizations alongside large enterprises",[97,4130,4131],{},"Implementation guidance recognizes that organizations at different maturity levels need different levels of prescriptiveness",[37,4133,4134],{},"This expanded scope also makes NIST CSF 2.0 more relevant internationally, as organizations outside the United States increasingly adopt the framework as a voluntary standard for cybersecurity risk management.",[32,4136,4138],{"id":4137},"enhanced-supply-chain-risk-management","Enhanced supply chain risk management",[37,4140,4141],{},"Supply chain cybersecurity risk management received significantly more attention in CSF 2.0 compared to its predecessor. The new Govern function includes a dedicated category (GV.SC) with multiple subcategories addressing supply chain risk.",[50,4143,4145],{"id":4144},"key-supply-chain-changes","Key supply chain changes",[37,4147,4148,4151],{},[58,4149,4150],{},"Dedicated governance category"," - Supply chain risk management is now a governance responsibility with explicit leadership oversight, rather than a technical concern buried within the Identify function.",[37,4153,4154,4157],{},[58,4155,4156],{},"Expanded subcategories"," - CSF 2.0 includes specific subcategories for:",[94,4159,4160,4163,4166,4169,4172,4175],{},[97,4161,4162],{},"Establishing supply chain risk management strategy and policies",[97,4164,4165],{},"Integrating supply chain risk into enterprise risk management",[97,4167,4168],{},"Conducting due diligence on suppliers and third-party partners",[97,4170,4171],{},"Monitoring supplier cybersecurity practices throughout the relationship lifecycle",[97,4173,4174],{},"Planning for supply chain disruptions and compromises",[97,4176,4177],{},"Including cybersecurity requirements in contracts and agreements",[37,4179,4180,4183],{},[58,4181,4182],{},"Supply chain risk in all functions"," - Beyond the Govern function, supply chain considerations are woven into the other five functions. For example, the Identify function addresses identifying and prioritizing suppliers, the Protect function covers securing supply chain interactions, and the Respond function addresses responding to supply chain incidents.",[50,4185,4187],{"id":4186},"why-supply-chain-focus-increased","Why supply chain focus increased",[37,4189,4190],{},"Several high-profile supply chain attacks (SolarWinds, Kaseya, Log4j) demonstrated that third-party risk is one of the most significant cybersecurity challenges facing organizations. CSF 2.0 reflects the reality that an organization's cybersecurity posture is only as strong as its weakest supply chain link.",[32,4192,119],{"id":4193},"improved-implementation-guidance",[37,4195,4196],{},"NIST CSF 2.0 introduces significant improvements to help organizations put the framework into practice.",[50,4198,4200],{"id":4199},"implementation-examples","Implementation examples",[37,4202,4203],{},"CSF 2.0 provides implementation examples for each subcategory, offering concrete actions that organizations can take. These examples are not prescriptive requirements but rather illustrative guidance that helps organizations, particularly smaller ones, understand what each subcategory looks like in practice.",[37,4205,4206],{},"For example, under the Protect function's data security category, implementation examples might include encrypting data at rest using AES-256, implementing data loss prevention tools, or classifying data based on sensitivity levels. These examples make the framework more accessible to organizations that lack dedicated compliance teams.",[50,4208,4210],{"id":4209},"informative-references","Informative references",[37,4212,4213],{},"NIST CSF 2.0 maintains and expands its catalog of informative references that map the framework to other standards, guidelines, and best practices. These references include mappings to:",[94,4215,4216,4219,4222,4225,4228,4232],{},[97,4217,4218],{},"NIST SP 800-53 (Security and Privacy Controls)",[97,4220,4221],{},"ISO 27001 and ISO 27002",[97,4223,4224],{},"COBIT",[97,4226,4227],{},"CIS Controls",[97,4229,4230],{},[41,4231,1223],{"href":1222},[97,4233,4234],{},"HIPAA Security Rule",[37,4236,4237,4238,4240],{},"The informative references are now maintained as a separate, regularly updated resource rather than being embedded in the framework document. This allows mappings to be updated as referenced standards evolve without requiring a new version of the CSF itself. See the ",[41,4239,1598],{"href":393}," topic for practical guidance on using these mappings.",[50,4242,4244],{"id":4243},"quick-start-guides","Quick start guides",[37,4246,4247],{},"NIST published companion quick start guides alongside CSF 2.0 to help specific audiences get started:",[94,4249,4250,4253,4256,4259],{},[97,4251,4252],{},"A guide for small businesses that simplifies the framework into actionable steps",[97,4254,4255],{},"A guide for enterprise risk managers that connects CSF 2.0 to enterprise risk management",[97,4257,4258],{},"A guide for creating and using organizational profiles",[97,4260,4261],{},"A guide for supply chain risk management",[37,4263,4264],{},"These guides lower the barrier to adoption for organizations that found the original framework document dense or difficult to operationalize.",[32,4266,4268],{"id":4267},"updated-tiers-and-profiles","Updated tiers and profiles",[37,4270,4271,4272,4274],{},"While the ",[41,4273,250],{"href":283}," (Partial, Risk Informed, Repeatable, Adaptive) remain conceptually the same in CSF 2.0, they have been updated to incorporate the Govern function. Organizations now assess their tier across six functions rather than five, with governance maturity playing a significant role in the overall tier assessment.",[37,4276,4277],{},"Framework profiles in CSF 2.0 also incorporate the Govern function and benefit from improved guidance on how to create, compare, and communicate profiles. The concept of community profiles -- profiles developed by a sector, industry group, or other community to address shared cybersecurity concerns -- is more prominent in CSF 2.0. Community profiles can serve as starting points that individual organizations customize to their specific needs.",[32,4279,4281],{"id":4280},"continuous-improvement-emphasis","Continuous improvement emphasis",[37,4283,4284],{},"CSF 2.0 strengthens the emphasis on continuous improvement throughout the framework. The Govern function's Oversight category (GV.OV) creates an explicit feedback loop between operational cybersecurity activities and governance decisions. This reinforces that cybersecurity is not a project with a defined end state but an ongoing program that must adapt to changing threats, technologies, and business conditions.",[37,4286,4287],{},"The framework now more clearly articulates the cycle of:",[510,4289,4290,4293,4296,4299,4302,4305],{},[97,4291,4292],{},"Understanding your current posture (current profile)",[97,4294,4295],{},"Defining your target posture (target profile)",[97,4297,4298],{},"Identifying and prioritizing gaps",[97,4300,4301],{},"Implementing improvements",[97,4303,4304],{},"Measuring results",[97,4306,4307],{},"Adjusting strategy based on outcomes (feeding back into governance)",[32,4309,4311],{"id":4310},"transitioning-from-csf-11-to-20","Transitioning from CSF 1.1 to 2.0",[37,4313,4314],{},"Organizations currently using NIST CSF 1.1 should plan a structured transition to CSF 2.0:",[37,4316,4317,4320],{},[58,4318,4319],{},"Assess governance maturity"," - Evaluate your existing governance practices against the new Govern function. Many organizations will find that they are already performing some governance activities but need to formalize and document them.",[37,4322,4323,4326],{},[58,4324,4325],{},"Update framework profiles"," - Rebuild your current and target profiles to incorporate the Govern function's categories and subcategories. This is also an opportunity to refresh your assessments of the original five functions.",[37,4328,4329,4332],{},[58,4330,4331],{},"Expand supply chain coverage"," - Review and strengthen your supply chain risk management practices against the expanded GV.SC subcategories. This may require new processes for vendor assessment, contract requirements, and ongoing monitoring.",[37,4334,4335,4338],{},[58,4336,4337],{},"Leverage new resources"," - Take advantage of the implementation examples, quick start guides, and updated informative references to fill gaps and improve your program.",[37,4340,4341,4344],{},[58,4342,4343],{},"Update training and communication"," - Ensure that stakeholders across the organization understand the changes in CSF 2.0, particularly the elevated importance of governance and supply chain risk management. Executive leadership should understand how the Govern function affects their responsibilities.",[37,4346,4347],{},"NIST CSF 2.0 represents a maturation of the framework that reflects how cybersecurity risk management has evolved over the past decade. Organizations that embrace the updated structure, particularly the Govern function and enhanced supply chain coverage, will be better positioned to manage cybersecurity risk in an increasingly complex threat environment.",{"title":561,"searchDepth":562,"depth":562,"links":4349},[4350,4351,4356,4357,4361,4366,4367,4368],{"id":4038,"depth":562,"text":4039},{"id":4048,"depth":562,"text":4049,"children":4352},[4353,4354,4355],{"id":4055,"depth":567,"text":4056},{"id":4062,"depth":567,"text":4063},{"id":4103,"depth":567,"text":4104},{"id":4113,"depth":562,"text":4114},{"id":4137,"depth":562,"text":4138,"children":4358},[4359,4360],{"id":4144,"depth":567,"text":4145},{"id":4186,"depth":567,"text":4187},{"id":4193,"depth":562,"text":119,"children":4362},[4363,4364,4365],{"id":4199,"depth":567,"text":4200},{"id":4209,"depth":567,"text":4210},{"id":4243,"depth":567,"text":4244},{"id":4267,"depth":562,"text":4268},{"id":4280,"depth":562,"text":4281},{"id":4310,"depth":562,"text":4311},"An overview of the key changes in NIST Cybersecurity Framework 2.0, including the new Govern function, expanded scope, and supply chain focus.",{"items":4371},[4372,4375,4378,4381],{"label":4373,"content":4374},"What is the biggest change in NIST CSF 2.0?","The addition of a sixth core function called Govern (GV). This elevates cybersecurity governance from a subcategory within the Identify function to a standalone function that underpins all other cybersecurity activities, emphasizing leadership accountability and risk management strategy.",{"label":4376,"content":4377},"Does NIST CSF 2.0 only apply to critical infrastructure?","No. NIST CSF 2.0 explicitly broadens its scope to all organizations regardless of size, sector, or maturity level. The original framework was primarily focused on critical infrastructure, but 2.0 dropped that limitation and includes guidance for small and medium-sized businesses.",{"label":4379,"content":4380},"Do I need to migrate from CSF 1.1 to 2.0?","While NIST CSF is voluntary, organizations currently using 1.1 should plan a structured transition. Start by assessing your governance maturity against the new Govern function, rebuild your framework profiles to incorporate the sixth function, and expand your supply chain risk coverage.",{"label":4382,"content":4383},"How does NIST CSF 2.0 address supply chain risk?","CSF 2.0 significantly expands supply chain coverage with a dedicated governance category (GV.SC) covering supplier due diligence, contract requirements, ongoing monitoring, and disruption planning. This was driven by high-profile supply chain attacks like SolarWinds and Log4j.",{},[1254],[1715,1256,962],{"title":4388,"description":4389},"NIST CSF 2.0 vs 1.1: What Changed & What It Means for Your Program","NIST CSF 2.0 adds the Govern function, expands scope beyond critical infrastructure, and strengthens supply chain requirements. Full breakdown with migration steps.","5.frameworks\u002Fnistcsf\u002Fv2-changes","k_8CNxbL7zc7Obs5nIBNJlxu8dIPSzib8H51NYleyKA",[4393,4948,5188,5468,5685,5911,6172,6303,6420,6540,6777,6905,7435,7566,7687,7808,7941,8027,8154,8409,9020,9230,9453,10055,10236],{"id":4394,"title":4395,"body":4396,"description":561,"extension":597,"lastUpdated":952,"meta":4935,"navigation":634,"path":4936,"relatedFrameworks":4937,"relatedTerms":4940,"seo":4943,"slug":3467,"stem":4946,"term":4401,"__hash__":4947},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":29,"value":4397,"toc":4921},[4398,4402,4405,4409,4412,4438,4442,4448,4454,4460,4466,4470,4473,4479,4496,4502,4516,4522,4533,4537,4540,4589,4593,4596,4610,4614,4617,4640,4644,4647,4696,4700,4703,4817,4820,4823,4852,4856,4862,4865,4901,4904,4907,4910,4914],[32,4399,4401],{"id":4400},"what-is-access-control","What is Access Control?",[37,4403,4404],{},"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.",[50,4406,4408],{"id":4407},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[37,4410,4411],{},"Access control is built on several foundational principles:",[94,4413,4414,4420,4426,4432],{},[97,4415,4416,4419],{},[58,4417,4418],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[97,4421,4422,4425],{},[58,4423,4424],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[97,4427,4428,4431],{},[58,4429,4430],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[97,4433,4434,4437],{},[58,4435,4436],{},"Default deny"," — access is denied by default unless explicitly granted",[50,4439,4441],{"id":4440},"what-are-the-types-of-access-control","What are the types of access control?",[37,4443,4444,4447],{},[58,4445,4446],{},"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,4449,4450,4453],{},[58,4451,4452],{},"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,4455,4456,4459],{},[58,4457,4458],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[37,4461,4462,4465],{},[58,4463,4464],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[50,4467,4469],{"id":4468},"what-are-access-control-components","What are access control components?",[37,4471,4472],{},"A complete access control program addresses:",[37,4474,4475,4478],{},[58,4476,4477],{},"Authentication"," — verifying the identity of users:",[94,4480,4481,4484,4487,4490,4493],{},[97,4482,4483],{},"Passwords and passphrases",[97,4485,4486],{},"Multi-factor authentication (MFA)",[97,4488,4489],{},"Single sign-on (SSO)",[97,4491,4492],{},"Biometric authentication",[97,4494,4495],{},"Certificate-based authentication",[37,4497,4498,4501],{},[58,4499,4500],{},"Authorization"," — determining what authenticated users can do:",[94,4503,4504,4507,4510,4513],{},[97,4505,4506],{},"Permission assignments",[97,4508,4509],{},"Role definitions",[97,4511,4512],{},"Access control lists",[97,4514,4515],{},"Policy enforcement points",[37,4517,4518,4521],{},[58,4519,4520],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[94,4523,4524,4527,4530],{},[97,4525,4526],{},"Provisioning (granting access when hired or role changes)",[97,4528,4529],{},"Review (periodic access certification)",[97,4531,4532],{},"Deprovisioning (revoking access upon termination or role change)",[50,4534,4536],{"id":4535},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[37,4538,4539],{},"Every major framework requires access control:",[94,4541,4542,4549,4561,4575,4582],{},[97,4543,4544,4548],{},[58,4545,4546],{},[41,4547,128],{"href":127}," — CC6.1 through CC6.8 cover logical and physical access controls",[97,4550,4551,4555,4556,4560],{},[58,4552,4553],{},[41,4554,378],{"href":377}," — ",[41,4557,4559],{"href":4558},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[97,4562,4563,4569,4570,4574],{},[58,4564,4565],{},[41,4566,4568],{"href":4567},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[41,4571,4573],{"href":4572},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[97,4576,4577,4581],{},[58,4578,4579],{},[41,4580,1223],{"href":1222}," — Requirements 7 and 8 address access restriction and user identification",[97,4583,4584,4588],{},[58,4585,4586],{},[41,4587,633],{"href":635}," — PR.AC covers identity management, authentication, and access control",[50,4590,4592],{"id":4591},"what-are-access-reviews","What are access reviews?",[37,4594,4595],{},"Regular access reviews (also called access certifications) are a critical control:",[94,4597,4598,4601,4604,4607],{},[97,4599,4600],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[97,4602,4603],{},"Verify that access aligns with current job responsibilities",[97,4605,4606],{},"Identify and remove excessive or unnecessary access",[97,4608,4609],{},"Document review results and remediation actions",[50,4611,4613],{"id":4612},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[37,4615,4616],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[94,4618,4619,4622,4625,4628,4631,4634,4637],{},[97,4620,4621],{},"Excessive permissions that accumulate over time (privilege creep)",[97,4623,4624],{},"Shared or generic accounts that prevent individual accountability",[97,4626,4627],{},"Delayed deprovisioning when employees leave or change roles",[97,4629,4630],{},"Lack of MFA on critical systems and remote access paths",[97,4632,4633],{},"Inconsistent access review processes with no documented remediation",[97,4635,4636],{},"Service accounts with standing privileged access and no rotation schedule",[97,4638,4639],{},"Lack of visibility into SaaS application access outside the corporate IdP",[50,4641,4643],{"id":4642},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[37,4645,4646],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[510,4648,4649,4655,4661,4667,4673,4679,4690],{},[97,4650,4651,4654],{},[58,4652,4653],{},"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.",[97,4656,4657,4660],{},[58,4658,4659],{},"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.",[97,4662,4663,4666],{},[58,4664,4665],{},"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.",[97,4668,4669,4672],{},[58,4670,4671],{},"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.",[97,4674,4675,4678],{},[58,4676,4677],{},"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.",[97,4680,4681,4684,4685,4689],{},[58,4682,4683],{},"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 ",[41,4686,4688],{"href":4687},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[97,4691,4692,4695],{},[58,4693,4694],{},"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.",[50,4697,4699],{"id":4698},"what-are-the-access-control-requirements","What are the access control requirements?",[37,4701,4702],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[695,4704,4705,4722],{},[698,4706,4707],{},[701,4708,4709,4712,4714,4716,4718,4720],{},[704,4710,4711],{},"Requirement",[704,4713,128],{},[704,4715,378],{},[704,4717,4568],{},[704,4719,1223],{},[704,4721,633],{},[714,4723,4724,4744,4763,4783,4800],{},[701,4725,4726,4729,4732,4735,4738,4741],{},[719,4727,4728],{},"Unique user IDs",[719,4730,4731],{},"CC6.1",[719,4733,4734],{},"A.5.16",[719,4736,4737],{},"§164.312(a)(2)(i)",[719,4739,4740],{},"Req 8.2.1",[719,4742,4743],{},"PR.AC-1",[701,4745,4746,4749,4751,4754,4757,4760],{},[719,4747,4748],{},"MFA",[719,4750,4731],{},[719,4752,4753],{},"A.8.5",[719,4755,4756],{},"Addressable",[719,4758,4759],{},"Req 8.4",[719,4761,4762],{},"PR.AC-7",[701,4764,4765,4768,4771,4774,4777,4780],{},[719,4766,4767],{},"Access reviews",[719,4769,4770],{},"CC6.2",[719,4772,4773],{},"A.5.18",[719,4775,4776],{},"§164.312(a)(1)",[719,4778,4779],{},"Req 7.2",[719,4781,4782],{},"PR.AC-4",[701,4784,4785,4787,4790,4793,4795,4798],{},[719,4786,4418],{},[719,4788,4789],{},"CC6.3",[719,4791,4792],{},"A.5.15",[719,4794,4776],{},[719,4796,4797],{},"Req 7.1",[719,4799,4782],{},[701,4801,4802,4805,4807,4809,4812,4815],{},[719,4803,4804],{},"Deprovisioning",[719,4806,4770],{},[719,4808,4773],{},[719,4810,4811],{},"§164.312(a)(2)(ii)",[719,4813,4814],{},"Req 8.2.6",[719,4816,4743],{},[37,4818,4819],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[37,4821,4822],{},"A few notes on framework-specific nuances:",[94,4824,4825,4830,4838,4845],{},[97,4826,4827,4829],{},[58,4828,4568],{}," 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.",[97,4831,4832,4837],{},[58,4833,4834,4836],{},[41,4835,1223],{"href":1222}," 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.",[97,4839,4840,4844],{},[58,4841,4842],{},[41,4843,128],{"href":127}," 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.",[97,4846,4847,4851],{},[58,4848,4849],{},[41,4850,633],{"href":635}," 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.",[50,4853,4855],{"id":4854},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[37,4857,4858,4859,167],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[58,4860,4861],{},"never trust, always verify",[37,4863,4864],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[94,4866,4867,4873,4879,4889,4895],{},[97,4868,4869,4872],{},[58,4870,4871],{},"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.",[97,4874,4875,4878],{},[58,4876,4877],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[97,4880,4881,4884,4885,4888],{},[58,4882,4883],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[41,4886,3468],{"href":4887},"\u002Fglossary\u002Fencryption",") is evaluated before access is granted.",[97,4890,4891,4894],{},[58,4892,4893],{},"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.",[97,4896,4897,4900],{},[58,4898,4899],{},"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,4902,4903],{},"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,4905,4906],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[37,4908,4909],{},"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.",[50,4911,4913],{"id":4912},"how-does-episki-help-with-access-control","How does episki help with access control?",[37,4915,4916,4917,167],{},"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 ",[41,4918,4920],{"href":4919},"\u002Fframeworks","compliance platform",{"title":561,"searchDepth":562,"depth":562,"links":4922},[4923],{"id":4400,"depth":562,"text":4401,"children":4924},[4925,4926,4927,4928,4929,4930,4931,4932,4933,4934],{"id":4407,"depth":567,"text":4408},{"id":4440,"depth":567,"text":4441},{"id":4468,"depth":567,"text":4469},{"id":4535,"depth":567,"text":4536},{"id":4591,"depth":567,"text":4592},{"id":4612,"depth":567,"text":4613},{"id":4642,"depth":567,"text":4643},{"id":4698,"depth":567,"text":4699},{"id":4854,"depth":567,"text":4855},{"id":4912,"depth":567,"text":4913},{},"\u002Fglossary\u002Faccess-control",[4938,3177,3178,3179,4939,652],"cmmc","pci",[4941,956,3468,4942],"minimum-necessary-rule","user-entity-controls",{"title":4944,"description":4945},"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":4949,"title":4950,"body":4951,"description":561,"extension":597,"lastUpdated":952,"meta":5177,"navigation":634,"path":5178,"relatedFrameworks":5179,"relatedTerms":5180,"seo":5183,"slug":3747,"stem":5186,"term":4956,"__hash__":5187},"glossary\u002F8.glossary\u002Fbusiness-continuity.md","Business Continuity",{"type":29,"value":4952,"toc":5167},[4953,4957,4960,4964,4967,4981,4984,4988,4994,5005,5011,5028,5034,5051,5057,5074,5078,5101,5105,5108,5134,5137,5141,5158,5162],[32,4954,4956],{"id":4955},"what-is-business-continuity","What is Business Continuity?",[37,4958,4959],{},"Business continuity is the capability of an organization to continue delivering products and services at acceptable predefined levels following a disruptive incident. A business continuity plan (BCP) documents the procedures and resources needed to maintain operations during and after events such as natural disasters, cyberattacks, pandemics, infrastructure failures, or supply chain disruptions.",[50,4961,4963],{"id":4962},"what-is-the-difference-between-business-continuity-and-disaster-recovery","What is the difference between business continuity and disaster recovery?",[37,4965,4966],{},"While often discussed together, business continuity and disaster recovery serve different purposes:",[94,4968,4969,4975],{},[97,4970,4971,4974],{},[58,4972,4973],{},"Business continuity"," focuses on maintaining overall business operations — it encompasses people, processes, facilities, and technology",[97,4976,4977,4980],{},[58,4978,4979],{},"Disaster recovery"," focuses specifically on restoring IT systems and data after a disruption",[37,4982,4983],{},"Disaster recovery is a subset of business continuity. A comprehensive business continuity program includes disaster recovery as one of its components.",[50,4985,4987],{"id":4986},"what-are-the-components-of-a-business-continuity-plan","What are the components of a business continuity plan?",[37,4989,4990,4993],{},[58,4991,4992],{},"Business Impact Analysis (BIA)"," — identifies critical business functions, the impact of disrupting them, and the maximum tolerable downtime:",[94,4995,4996,4999,5002],{},[97,4997,4998],{},"Recovery Time Objective (RTO) — the maximum acceptable time to restore a function",[97,5000,5001],{},"Recovery Point Objective (RPO) — the maximum acceptable data loss measured in time",[97,5003,5004],{},"Maximum Tolerable Period of Disruption (MTPD) — the longest the business can survive without the function",[37,5006,5007,5010],{},[58,5008,5009],{},"Risk assessment"," — identifies threats that could disrupt operations and evaluates their likelihood and impact:",[94,5012,5013,5016,5019,5022,5025],{},[97,5014,5015],{},"Natural disasters (earthquakes, floods, severe weather)",[97,5017,5018],{},"Technology failures (hardware failure, software bugs, network outages)",[97,5020,5021],{},"Cyber incidents (ransomware, DDoS attacks, data breaches)",[97,5023,5024],{},"Human factors (key personnel loss, labor disputes)",[97,5026,5027],{},"Supply chain disruptions (vendor failures, logistics breakdowns)",[37,5029,5030,5033],{},[58,5031,5032],{},"Recovery strategies"," — defines how critical functions will be maintained or restored:",[94,5035,5036,5039,5042,5045,5048],{},[97,5037,5038],{},"Alternative work locations or remote work capabilities",[97,5040,5041],{},"Redundant systems and infrastructure",[97,5043,5044],{},"Manual workaround procedures",[97,5046,5047],{},"Third-party recovery services",[97,5049,5050],{},"Communication plans for employees, customers, and stakeholders",[37,5052,5053,5056],{},[58,5054,5055],{},"Plan documentation"," — the written BCP includes:",[94,5058,5059,5062,5065,5068,5071],{},[97,5060,5061],{},"Roles and responsibilities",[97,5063,5064],{},"Contact information for key personnel and vendors",[97,5066,5067],{},"Step-by-step recovery procedures for each critical function",[97,5069,5070],{},"Resource requirements",[97,5072,5073],{},"Communication templates",[50,5075,5077],{"id":5076},"how-do-compliance-frameworks-address-business-continuity","How do compliance frameworks address business continuity?",[94,5079,5080,5085,5090,5095],{},[97,5081,5082,5084],{},[58,5083,378],{}," — control A.5.29 addresses information security during disruption, and A.5.30 addresses ICT readiness for business continuity",[97,5086,5087,5089],{},[58,5088,633],{}," — the Recover function (RC) addresses recovery planning, improvements, and communications",[97,5091,5092,5094],{},[58,5093,128],{}," — the Availability criterion addresses system uptime and recovery capabilities",[97,5096,5097,5100],{},[58,5098,5099],{},"ISO 22301"," — the dedicated international standard for business continuity management systems",[50,5102,5104],{"id":5103},"how-do-you-test-a-business-continuity-plan","How do you test a business continuity plan?",[37,5106,5107],{},"A business continuity plan that has not been tested is unreliable. Testing approaches include:",[94,5109,5110,5116,5122,5128],{},[97,5111,5112,5115],{},[58,5113,5114],{},"Tabletop exercises"," — team discussions walking through scenarios",[97,5117,5118,5121],{},[58,5119,5120],{},"Structured walkthroughs"," — step-by-step review of procedures with assigned teams",[97,5123,5124,5127],{},[58,5125,5126],{},"Simulation tests"," — practicing response to a simulated disruption",[97,5129,5130,5133],{},[58,5131,5132],{},"Full interruption tests"," — actually activating recovery procedures (highest assurance but most disruptive)",[37,5135,5136],{},"Testing should occur at least annually and after significant changes to the business or infrastructure.",[50,5138,5140],{"id":5139},"what-are-common-pitfalls-with-business-continuity","What are common pitfalls with business continuity?",[94,5142,5143,5146,5149,5152,5155],{},[97,5144,5145],{},"BCP exists on paper but is never tested or updated",[97,5147,5148],{},"Critical dependencies on single points of failure are not identified",[97,5150,5151],{},"Communication plans do not account for the disruption itself (e.g., email is down)",[97,5153,5154],{},"Key personnel are not trained on their BCP responsibilities",[97,5156,5157],{},"The plan does not keep pace with business changes",[50,5159,5161],{"id":5160},"how-does-episki-help-with-business-continuity","How does episki help with business continuity?",[37,5163,5164,5165,167],{},"episki helps organizations document their business continuity plans, schedule and track testing exercises, and maintain evidence of BCP activities for auditors. The platform links BCP activities to ISO 27001 and NIST CSF requirements. Learn more on our ",[41,5166,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":5168},[5169],{"id":4955,"depth":562,"text":4956,"children":5170},[5171,5172,5173,5174,5175,5176],{"id":4962,"depth":567,"text":4963},{"id":4986,"depth":567,"text":4987},{"id":5076,"depth":567,"text":5077},{"id":5103,"depth":567,"text":5104},{"id":5139,"depth":567,"text":5140},{"id":5160,"depth":567,"text":5161},{},"\u002Fglossary\u002Fbusiness-continuity",[3178,652],[3748,3749,5181,5182],"risk-register","risk-treatment-plan",{"title":5184,"description":5185},"What is Business Continuity? Definition & Compliance Guide","Business continuity planning ensures an organization can maintain essential operations during and after a disruptive event. Learn the key components and frameworks.","8.glossary\u002Fbusiness-continuity","dyPU67gMtqXpCCrubDS7MtzzpZM4MS8zudQDFFznv_U",{"id":5189,"title":721,"body":5190,"description":561,"extension":597,"lastUpdated":952,"meta":5457,"navigation":634,"path":5458,"relatedFrameworks":5459,"relatedTerms":5460,"seo":5463,"slug":955,"stem":5466,"term":5195,"__hash__":5467},"glossary\u002F8.glossary\u002Fcontinuous-monitoring.md",{"type":29,"value":5191,"toc":5446},[5192,5196,5199,5203,5206,5226,5230,5233,5238,5252,5257,5271,5276,5287,5292,5306,5310,5333,5337,5392,5396,5399,5413,5416,5420,5437,5441],[32,5193,5195],{"id":5194},"what-is-continuous-monitoring","What is Continuous Monitoring?",[37,5197,5198],{},"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.",[50,5200,5202],{"id":5201},"why-does-continuous-monitoring-matter","Why does continuous monitoring matter?",[37,5204,5205],{},"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:",[94,5207,5208,5211,5214,5217,5220,5223],{},[97,5209,5210],{},"Detecting threats and vulnerabilities as they emerge, not months later",[97,5212,5213],{},"Verifying that controls remain effective on an ongoing basis",[97,5215,5216],{},"Identifying configuration drift and unauthorized changes",[97,5218,5219],{},"Providing evidence of sustained compliance for auditors",[97,5221,5222],{},"Enabling faster response to security incidents",[97,5224,5225],{},"Reducing the risk of surprises during audit cycles",[50,5227,5229],{"id":5228},"what-should-you-monitor-continuously","What should you monitor continuously?",[37,5231,5232],{},"Continuous monitoring spans multiple domains:",[37,5234,5235],{},[58,5236,5237],{},"Security controls:",[94,5239,5240,5243,5246,5249],{},[97,5241,5242],{},"Are access controls still properly configured?",[97,5244,5245],{},"Are encryption mechanisms active and using current standards?",[97,5247,5248],{},"Are security policies being followed?",[97,5250,5251],{},"Are patches being applied within defined timeframes?",[37,5253,5254],{},[58,5255,5256],{},"Systems and infrastructure:",[94,5258,5259,5262,5265,5268],{},[97,5260,5261],{},"Are systems operating normally?",[97,5263,5264],{},"Are there unauthorized configuration changes?",[97,5266,5267],{},"Are there new vulnerabilities affecting your environment?",[97,5269,5270],{},"Are all endpoints protected with current security agents?",[37,5272,5273],{},[58,5274,5275],{},"User activity:",[94,5277,5278,5281,5284],{},[97,5279,5280],{},"Are there unusual access patterns or privilege escalations?",[97,5282,5283],{},"Are terminated users' accounts being deactivated promptly?",[97,5285,5286],{},"Are there failed authentication attempts indicating brute-force attacks?",[37,5288,5289],{},[58,5290,5291],{},"Compliance status:",[94,5293,5294,5297,5300,5303],{},[97,5295,5296],{},"Are all required controls implemented and operating?",[97,5298,5299],{},"Is evidence being collected on schedule?",[97,5301,5302],{},"Are policy reviews and updates happening as planned?",[97,5304,5305],{},"Are vendor assessments current?",[50,5307,5309],{"id":5308},"how-do-compliance-frameworks-address-continuous-monitoring","How do compliance frameworks address continuous monitoring?",[94,5311,5312,5317,5322,5327],{},[97,5313,5314,5316],{},[58,5315,128],{}," — CC4.1 and CC4.2 require ongoing monitoring of the internal control system and evaluation of deficiencies",[97,5318,5319,5321],{},[58,5320,378],{}," — clause 9 (Performance evaluation) requires monitoring, measurement, analysis, and evaluation of the ISMS",[97,5323,5324,5326],{},[58,5325,633],{}," — DE.CM (Continuous Monitoring) specifically addresses monitoring information systems and assets for cybersecurity events",[97,5328,5329,5332],{},[58,5330,5331],{},"NIST SP 800-137"," provides detailed guidance on Information Security Continuous Monitoring (ISCM)",[50,5334,5336],{"id":5335},"how-do-you-implement-continuous-monitoring","How do you implement continuous monitoring?",[510,5338,5339,5345,5368,5374,5380,5386],{},[97,5340,5341,5344],{},[58,5342,5343],{},"Define monitoring objectives"," — determine what needs to be monitored based on risk assessment and compliance requirements",[97,5346,5347,5350,5351],{},[58,5348,5349],{},"Select monitoring tools"," — deploy appropriate technologies:\n",[94,5352,5353,5356,5359,5362,5365],{},[97,5354,5355],{},"SIEM (Security Information and Event Management) for log aggregation and correlation",[97,5357,5358],{},"EDR (Endpoint Detection and Response) for endpoint monitoring",[97,5360,5361],{},"Vulnerability scanners for continuous vulnerability assessment",[97,5363,5364],{},"Configuration management tools for drift detection",[97,5366,5367],{},"GRC platforms for compliance monitoring",[97,5369,5370,5373],{},[58,5371,5372],{},"Establish baselines"," — define normal operating parameters so deviations can be detected",[97,5375,5376,5379],{},[58,5377,5378],{},"Configure alerts"," — set meaningful alert thresholds to balance detection with alert fatigue",[97,5381,5382,5385],{},[58,5383,5384],{},"Define response procedures"," — establish processes for responding to monitoring alerts",[97,5387,5388,5391],{},[58,5389,5390],{},"Review and improve"," — regularly assess monitoring effectiveness and adjust as needed",[50,5393,5395],{"id":5394},"what-is-the-difference-between-continuous-monitoring-and-continuous-compliance","What is the difference between continuous monitoring and continuous compliance?",[37,5397,5398],{},"While related, these concepts differ:",[94,5400,5401,5407],{},[97,5402,5403,5406],{},[58,5404,5405],{},"Continuous monitoring"," focuses on security — detecting threats, vulnerabilities, and anomalies in real time",[97,5408,5409,5412],{},[58,5410,5411],{},"Continuous compliance"," focuses on maintaining compliance posture — ensuring controls remain effective and evidence stays current",[37,5414,5415],{},"An effective program addresses both. Security monitoring feeds compliance evidence, and compliance monitoring ensures security controls do not degrade.",[50,5417,5419],{"id":5418},"what-are-common-challenges-with-continuous-monitoring","What are common challenges with continuous monitoring?",[94,5421,5422,5425,5428,5431,5434],{},[97,5423,5424],{},"Alert fatigue from too many low-priority notifications",[97,5426,5427],{},"Gaps in monitoring coverage across all systems",[97,5429,5430],{},"Insufficient resources to investigate and respond to alerts",[97,5432,5433],{},"Monitoring tools that generate data but lack actionable insights",[97,5435,5436],{},"Difficulty correlating events across disparate systems",[50,5438,5440],{"id":5439},"how-does-episki-help-with-continuous-monitoring","How does episki help with continuous monitoring?",[37,5442,5443,5444,167],{},"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 ",[41,5445,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":5447},[5448],{"id":5194,"depth":562,"text":5195,"children":5449},[5450,5451,5452,5453,5454,5455,5456],{"id":5201,"depth":567,"text":5202},{"id":5228,"depth":567,"text":5229},{"id":5308,"depth":567,"text":5309},{"id":5335,"depth":567,"text":5336},{"id":5394,"depth":567,"text":5395},{"id":5418,"depth":567,"text":5419},{"id":5439,"depth":567,"text":5440},{},"\u002Fglossary\u002Fcontinuous-monitoring",[4938,3177,3178,652],[5461,956,3749,5462,2028],"evidence-collection","remediation",{"title":5464,"description":5465},"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.","8.glossary\u002Fcontinuous-monitoring","YFq0Sck1IHoKfMLlSRFboyiO1yOmbJP8o3dmYFvhgGk",{"id":5469,"title":5470,"body":5471,"description":561,"extension":597,"lastUpdated":952,"meta":5674,"navigation":634,"path":320,"relatedFrameworks":5675,"relatedTerms":5676,"seo":5680,"slug":2028,"stem":5683,"term":5476,"__hash__":5684},"glossary\u002F8.glossary\u002Fcontrol-framework.md","Control Framework",{"type":29,"value":5472,"toc":5664},[5473,5477,5480,5484,5487,5519,5523,5526,5561,5565,5568,5600,5604,5607,5610,5614,5617,5655,5659],[32,5474,5476],{"id":5475},"what-is-a-control-framework","What is a Control Framework?",[37,5478,5479],{},"A control framework is a structured collection of security controls, guidelines, and best practices that organizations use to design, implement, and evaluate their information security programs. Control frameworks provide a systematic approach to managing security risks by defining what controls should exist and how they should be organized.",[50,5481,5483],{"id":5482},"why-do-control-frameworks-matter","Why do control frameworks matter?",[37,5485,5486],{},"Without a framework, security programs tend to develop organically — addressing risks as they arise without a cohesive structure. This leads to gaps in coverage, duplicated efforts, and difficulty demonstrating security posture to stakeholders. Control frameworks provide:",[94,5488,5489,5495,5501,5507,5513],{},[97,5490,5491,5494],{},[58,5492,5493],{},"Comprehensiveness"," — a complete catalog of controls spanning all relevant security domains",[97,5496,5497,5500],{},[58,5498,5499],{},"Structure"," — logical organization of controls into categories and domains",[97,5502,5503,5506],{},[58,5504,5505],{},"Common language"," — standardized terminology for discussing security with auditors, customers, and partners",[97,5508,5509,5512],{},[58,5510,5511],{},"Benchmarking"," — a reference point for measuring maturity and identifying gaps",[97,5514,5515,5518],{},[58,5516,5517],{},"Compliance alignment"," — mapping to regulatory and contractual requirements",[50,5520,5522],{"id":5521},"what-are-common-control-frameworks","What are common control frameworks?",[37,5524,5525],{},"Several widely adopted control frameworks exist, each with a different focus:",[94,5527,5528,5534,5540,5546,5551,5556],{},[97,5529,5530,5533],{},[58,5531,5532],{},"SOC 2 Trust Services Criteria"," — evaluates controls across security, availability, processing integrity, confidentiality, and privacy for service organizations",[97,5535,5536,5539],{},[58,5537,5538],{},"ISO 27001 Annex A"," — provides 93 controls across organizational, people, physical, and technological themes for information security management",[97,5541,5542,5545],{},[58,5543,5544],{},"NIST Cybersecurity Framework (CSF)"," — organizes security activities into five functions: Identify, Protect, Detect, Respond, and Recover",[97,5547,5548,5550],{},[58,5549,123],{}," — a comprehensive catalog of security and privacy controls used primarily by US federal agencies and their contractors",[97,5552,5553,5555],{},[58,5554,4227],{}," — a prioritized set of actions (18 controls) that form a practical starting point for cybersecurity defense",[97,5557,5558,5560],{},[58,5559,4224],{}," — a framework for IT governance and management",[50,5562,5564],{"id":5563},"how-do-you-choose-a-control-framework","How do you choose a control framework?",[37,5566,5567],{},"The right framework depends on your organization's needs:",[94,5569,5570,5576,5582,5588,5594],{},[97,5571,5572,5575],{},[58,5573,5574],{},"Customer requirements"," — if customers require SOC 2 reports, the Trust Services Criteria will be your primary framework",[97,5577,5578,5581],{},[58,5579,5580],{},"Certification goals"," — if you need ISO 27001 certification, Annex A is the relevant control set",[97,5583,5584,5587],{},[58,5585,5586],{},"Industry"," — some industries have specific frameworks (HITRUST for healthcare, PCI DSS for payment cards)",[97,5589,5590,5593],{},[58,5591,5592],{},"Maturity level"," — organizations early in their security journey may start with CIS Controls, while more mature programs adopt NIST SP 800-53",[97,5595,5596,5599],{},[58,5597,5598],{},"Geography"," — ISO 27001 is globally recognized, while some frameworks are more region-specific",[50,5601,5603],{"id":5602},"how-do-you-map-controls-across-multiple-frameworks","How do you map controls across multiple frameworks?",[37,5605,5606],{},"Many organizations must comply with multiple frameworks simultaneously. Cross-framework mapping identifies where controls overlap, allowing a single control to satisfy requirements from multiple frameworks. For example, an access control policy might satisfy SOC 2 CC6.1, ISO 27001 A.5.15, and NIST CSF PR.AC-1.",[37,5608,5609],{},"Effective multi-framework mapping reduces duplication and helps organizations manage compliance efficiently.",[50,5611,5613],{"id":5612},"how-do-you-implement-a-control-framework","How do you implement a control framework?",[37,5615,5616],{},"Implementation typically follows these phases:",[510,5618,5619,5625,5631,5637,5643,5649],{},[97,5620,5621,5624],{},[58,5622,5623],{},"Gap assessment"," — compare current controls against the framework to identify gaps",[97,5626,5627,5630],{},[58,5628,5629],{},"Prioritization"," — rank gaps by risk impact and effort required",[97,5632,5633,5636],{},[58,5634,5635],{},"Control design"," — design controls to address identified gaps",[97,5638,5639,5642],{},[58,5640,5641],{},"Implementation"," — deploy controls through policies, processes, and technology",[97,5644,5645,5648],{},[58,5646,5647],{},"Evidence collection"," — establish processes to collect and maintain compliance evidence",[97,5650,5651,5654],{},[58,5652,5653],{},"Monitoring and review"," — continuously assess control effectiveness and address changes",[50,5656,5658],{"id":5657},"how-does-episki-help-with-control-frameworks","How does episki help with control frameworks?",[37,5660,5661,5662,167],{},"episki supports multiple control frameworks out of the box with pre-built mappings between them. The platform lets you manage a single set of controls that maps to SOC 2, ISO 27001, NIST CSF, and other frameworks simultaneously, eliminating duplicate effort. Learn more on our ",[41,5663,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":5665},[5666],{"id":5475,"depth":562,"text":5476,"children":5667},[5668,5669,5670,5671,5672,5673],{"id":5482,"depth":567,"text":5483},{"id":5521,"depth":567,"text":5522},{"id":5563,"depth":567,"text":5564},{"id":5602,"depth":567,"text":5603},{"id":5612,"depth":567,"text":5613},{"id":5657,"depth":567,"text":5658},{},[3177,3178,652],[5677,5181,1254,5678,5679],"control-objectives","trust-services-criteria","annex-a",{"title":5681,"description":5682},"What is a Control Framework? Definition & Compliance Guide","A control framework is a structured set of security controls and guidelines that organizations use to build and evaluate their security programs.","8.glossary\u002Fcontrol-framework","l51hViZJUNfZhxJcG_3gNPwVkEmK97R6TuCyFHlE8rs",{"id":5686,"title":5687,"body":5688,"description":561,"extension":597,"lastUpdated":952,"meta":5901,"navigation":634,"path":2167,"relatedFrameworks":5902,"relatedTerms":5903,"seo":5906,"slug":2324,"stem":5909,"term":5693,"__hash__":5910},"glossary\u002F8.glossary\u002Fdata-classification.md","Data Classification",{"type":29,"value":5689,"toc":5891},[5690,5694,5697,5701,5704,5736,5740,5743,5772,5775,5779,5801,5805,5861,5865,5882,5886],[32,5691,5693],{"id":5692},"what-is-data-classification","What is Data Classification?",[37,5695,5696],{},"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.",[50,5698,5700],{"id":5699},"why-does-data-classification-matter","Why does data classification matter?",[37,5702,5703],{},"Data classification is foundational to an effective security program for several reasons:",[94,5705,5706,5712,5718,5724,5730],{},[97,5707,5708,5711],{},[58,5709,5710],{},"Proportional protection"," — sensitive data receives stronger controls while less sensitive data does not burden operations with unnecessary restrictions",[97,5713,5714,5717],{},[58,5715,5716],{},"Regulatory compliance"," — many regulations require specific handling of certain data types (PHI under HIPAA, PAN under PCI DSS, personal data under GDPR)",[97,5719,5720,5723],{},[58,5721,5722],{},"Access control"," — classification determines who should have access to what data",[97,5725,5726,5729],{},[58,5727,5728],{},"Incident response"," — knowing the classification of compromised data helps determine the severity of an incident and notification requirements",[97,5731,5732,5735],{},[58,5733,5734],{},"Data lifecycle management"," — classification informs retention, archival, and destruction decisions",[50,5737,5739],{"id":5738},"what-are-the-common-data-classification-levels","What are the common data classification levels?",[37,5741,5742],{},"Most organizations use three to five classification levels:",[94,5744,5745,5751,5757,5763],{},[97,5746,5747,5750],{},[58,5748,5749],{},"Public"," — information intended for public consumption with no restrictions (marketing materials, public website content)",[97,5752,5753,5756],{},[58,5754,5755],{},"Internal"," — information for internal use that is not sensitive but should not be shared externally without authorization (internal memos, non-sensitive policies)",[97,5758,5759,5762],{},[58,5760,5761],{},"Confidential"," — sensitive business information that could cause harm if disclosed (financial data, strategic plans, customer lists)",[97,5764,5765,922,5768,5771],{},[58,5766,5767],{},"Restricted",[58,5769,5770],{},"Highly Confidential"," — the most sensitive data requiring the strongest protections (PHI, PAN, trade secrets, credentials, encryption keys)",[37,5773,5774],{},"Some organizations add additional levels or use different labels, but the principle remains: categorize data by the impact of unauthorized disclosure.",[50,5776,5778],{"id":5777},"how-do-compliance-frameworks-address-classification","How do compliance frameworks address classification?",[94,5780,5781,5786,5791,5796],{},[97,5782,5783,5785],{},[58,5784,378],{}," — 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.",[97,5787,5788,5790],{},[58,5789,633],{}," — the Identify function (ID.AM-5) addresses classification of resources based on criticality and business value",[97,5792,5793,5795],{},[58,5794,4568],{}," — while HIPAA does not prescribe a classification scheme, PHI is inherently a \"restricted\" classification that requires specific safeguards",[97,5797,5798,5800],{},[58,5799,1223],{}," — cardholder data (particularly PAN) must be identified and protected with specific controls",[50,5802,5804],{"id":5803},"how-do-you-implement-data-classification","How do you implement data classification?",[510,5806,5807,5813,5819,5825,5831,5837,5843,5849,5855],{},[97,5808,5809,5812],{},[58,5810,5811],{},"Define classification levels"," — establish clear, understandable categories with examples",[97,5814,5815,5818],{},[58,5816,5817],{},"Create a classification policy"," — document the scheme, responsibilities, and handling requirements for each level",[97,5820,5821,5824],{},[58,5822,5823],{},"Inventory data"," — identify what data the organization holds and where it resides",[97,5826,5827,5830],{},[58,5828,5829],{},"Classify data"," — assign classification levels to data based on sensitivity criteria",[97,5832,5833,5836],{},[58,5834,5835],{},"Label data"," — apply labels (metadata, headers, visual markings) to classified data",[97,5838,5839,5842],{},[58,5840,5841],{},"Define handling rules"," — specify how each classification level should be stored, transmitted, shared, and destroyed",[97,5844,5845,5848],{},[58,5846,5847],{},"Train employees"," — ensure all staff understand the classification scheme and their responsibilities",[97,5850,5851,5854],{},[58,5852,5853],{},"Enforce through controls"," — implement technical controls (DLP, access controls, encryption) aligned with classification levels",[97,5856,5857,5860],{},[58,5858,5859],{},"Review periodically"," — reassess classifications as data, regulations, and business needs change",[50,5862,5864],{"id":5863},"what-are-common-challenges-with-data-classification","What are common challenges with data classification?",[94,5866,5867,5870,5873,5876,5879],{},[97,5868,5869],{},"Data is distributed across many systems and formats, making classification difficult",[97,5871,5872],{},"Employees may not consistently apply classification labels",[97,5874,5875],{},"Automated classification tools have limitations, especially with unstructured data",[97,5877,5878],{},"Over-classification can reduce productivity while under-classification creates risk",[97,5880,5881],{},"Classification needs to be maintained as data evolves",[50,5883,5885],{"id":5884},"how-does-episki-help-with-data-classification","How does episki help with data classification?",[37,5887,5888,5889,167],{},"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 ",[41,5890,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":5892},[5893],{"id":5692,"depth":562,"text":5693,"children":5894},[5895,5896,5897,5898,5899,5900],{"id":5699,"depth":567,"text":5700},{"id":5738,"depth":567,"text":5739},{"id":5777,"depth":567,"text":5778},{"id":5803,"depth":567,"text":5804},{"id":5863,"depth":567,"text":5864},{"id":5884,"depth":567,"text":5885},{},[4938,3178,652],[3468,3467,5904,5905,5181],"phi","pan",{"title":5907,"description":5908},"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":5912,"title":5913,"body":5914,"description":561,"extension":597,"lastUpdated":952,"meta":6163,"navigation":634,"path":6164,"relatedFrameworks":6165,"relatedTerms":6166,"seo":6167,"slug":3748,"stem":6170,"term":5919,"__hash__":6171},"glossary\u002F8.glossary\u002Fdisaster-recovery.md","Disaster Recovery",{"type":29,"value":5915,"toc":6152},[5916,5920,5923,5927,5933,5939,5945,5949,5952,5978,5981,5985,5988,6037,6041,6044,6082,6086,6108,6112,6115,6140,6143,6147],[32,5917,5919],{"id":5918},"what-is-disaster-recovery","What is Disaster Recovery?",[37,5921,5922],{},"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.",[50,5924,5926],{"id":5925},"what-are-the-key-disaster-recovery-concepts","What are the key disaster recovery concepts?",[37,5928,5929,5932],{},[58,5930,5931],{},"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,5934,5935,5938],{},[58,5936,5937],{},"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,5940,5941,5944],{},[58,5942,5943],{},"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.",[50,5946,5948],{"id":5947},"what-are-common-disaster-recovery-strategies","What are common disaster recovery strategies?",[37,5950,5951],{},"DR strategies vary in cost, complexity, and recovery speed:",[94,5953,5954,5960,5966,5972],{},[97,5955,5956,5959],{},[58,5957,5958],{},"Backup and restore"," — the simplest approach: maintain regular backups and restore them to new or repaired infrastructure when needed. Lowest cost but highest RTO.",[97,5961,5962,5965],{},[58,5963,5964],{},"Pilot light"," — maintain a minimal version of the production environment in a secondary location that can be scaled up quickly during a disaster.",[97,5967,5968,5971],{},[58,5969,5970],{},"Warm standby"," — run a scaled-down but fully functional copy of the production environment that can be scaled to full capacity during failover.",[97,5973,5974,5977],{},[58,5975,5976],{},"Hot standby \u002F active-active"," — run full production environments in multiple locations simultaneously. Provides near-zero RTO but at the highest cost.",[37,5979,5980],{},"The right strategy depends on the business's RTO and RPO requirements and budget.",[50,5982,5984],{"id":5983},"what-are-the-components-of-a-disaster-recovery-plan","What are the components of a disaster recovery plan?",[37,5986,5987],{},"A comprehensive DR plan includes:",[94,5989,5990,5996,6002,6007,6013,6019,6025,6031],{},[97,5991,5992,5995],{},[58,5993,5994],{},"Scope"," — which systems and applications are covered",[97,5997,5998,6001],{},[58,5999,6000],{},"RTO and RPO targets"," — recovery objectives for each system",[97,6003,6004,6006],{},[58,6005,5061],{}," — who is responsible for each aspect of recovery",[97,6008,6009,6012],{},[58,6010,6011],{},"Recovery procedures"," — step-by-step instructions for restoring each system",[97,6014,6015,6018],{},[58,6016,6017],{},"Communication plan"," — how to notify stakeholders during a disaster",[97,6020,6021,6024],{},[58,6022,6023],{},"Vendor contacts"," — contact information for infrastructure and service providers",[97,6026,6027,6030],{},[58,6028,6029],{},"Dependencies"," — system interdependencies that affect recovery sequence",[97,6032,6033,6036],{},[58,6034,6035],{},"Testing schedule"," — how and when the plan will be tested",[50,6038,6040],{"id":6039},"how-do-you-manage-backups-for-disaster-recovery","How do you manage backups for disaster recovery?",[37,6042,6043],{},"Backups are the foundation of disaster recovery. Best practices include:",[94,6045,6046,6052,6058,6064,6070,6076],{},[97,6047,6048,6051],{},[58,6049,6050],{},"3-2-1 rule"," — maintain 3 copies of data, on 2 different types of media, with 1 copy offsite",[97,6053,6054,6057],{},[58,6055,6056],{},"Automated backups"," — schedule backups to run automatically at intervals aligned with RPO",[97,6059,6060,6063],{},[58,6061,6062],{},"Encryption"," — encrypt backups to protect data at rest",[97,6065,6066,6069],{},[58,6067,6068],{},"Regular testing"," — periodically restore from backups to verify they work",[97,6071,6072,6075],{},[58,6073,6074],{},"Monitoring"," — monitor backup jobs for failures and address issues immediately",[97,6077,6078,6081],{},[58,6079,6080],{},"Immutable backups"," — protect backups from ransomware by using immutable storage",[50,6083,6085],{"id":6084},"how-do-compliance-frameworks-address-disaster-recovery","How do compliance frameworks address disaster recovery?",[94,6087,6088,6093,6098,6103],{},[97,6089,6090,6092],{},[58,6091,378],{}," — control A.5.30 addresses ICT readiness for business continuity, including DR planning and testing",[97,6094,6095,6097],{},[58,6096,633],{}," — RC.RP (Recovery Planning) addresses establishing and testing recovery processes",[97,6099,6100,6102],{},[58,6101,128],{}," — the Availability criterion covers system recovery capabilities",[97,6104,6105,6107],{},[58,6106,1223],{}," — while not explicitly requiring a DR plan, requirements around data protection and system availability support DR practices",[50,6109,6111],{"id":6110},"how-do-you-test-a-disaster-recovery-plan","How do you test a disaster recovery plan?",[37,6113,6114],{},"DR testing is essential and should include:",[94,6116,6117,6123,6129,6135],{},[97,6118,6119,6122],{},[58,6120,6121],{},"Backup restoration tests"," — regularly restore data from backups to verify integrity",[97,6124,6125,6128],{},[58,6126,6127],{},"Failover tests"," — practice switching to secondary systems",[97,6130,6131,6134],{},[58,6132,6133],{},"Full DR tests"," — simulate a complete disaster and execute the full recovery plan",[97,6136,6137,6139],{},[58,6138,5114],{}," — walk through DR scenarios with the team",[37,6141,6142],{},"Testing should occur at least annually, with backup restoration tests performed more frequently.",[50,6144,6146],{"id":6145},"how-does-episki-help-with-disaster-recovery","How does episki help with disaster recovery?",[37,6148,6149,6150,167],{},"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 ",[41,6151,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":6153},[6154],{"id":5918,"depth":562,"text":5919,"children":6155},[6156,6157,6158,6159,6160,6161,6162],{"id":5925,"depth":567,"text":5926},{"id":5947,"depth":567,"text":5948},{"id":5983,"depth":567,"text":5984},{"id":6039,"depth":567,"text":6040},{"id":6084,"depth":567,"text":6085},{"id":6110,"depth":567,"text":6111},{"id":6145,"depth":567,"text":6146},{},"\u002Fglossary\u002Fdisaster-recovery",[4938,3178,652],[3747,3749,5181,3468],{"title":6168,"description":6169},"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.","8.glossary\u002Fdisaster-recovery","asnxcfYjct8iYic-NvOoNvliB3CqOtNwVc19GAVgxkw",{"id":6173,"title":6174,"body":6175,"description":561,"extension":597,"lastUpdated":952,"meta":6291,"navigation":634,"path":6292,"relatedFrameworks":6293,"relatedTerms":6294,"seo":6297,"slug":6300,"stem":6301,"term":6180,"__hash__":6302},"glossary\u002F8.glossary\u002Ffirewall.md","Firewall",{"type":29,"value":6176,"toc":6283},[6177,6181,6184,6188,6220,6224,6227,6249,6253,6274,6278],[32,6178,6180],{"id":6179},"what-is-a-firewall","What is a Firewall?",[37,6182,6183],{},"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.",[50,6185,6187],{"id":6186},"what-are-the-types-of-firewalls","What are the types of firewalls?",[94,6189,6190,6196,6202,6208,6214],{},[97,6191,6192,6195],{},[58,6193,6194],{},"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.",[97,6197,6198,6201],{},[58,6199,6200],{},"Stateful inspection firewalls"," — track the state of active connections and make decisions based on the context of traffic, not just individual packets.",[97,6203,6204,6207],{},[58,6205,6206],{},"Next-generation firewalls (NGFW)"," — combine traditional firewall capabilities with intrusion prevention, application awareness, and deep packet inspection.",[97,6209,6210,6213],{},[58,6211,6212],{},"Web application firewalls (WAF)"," — specifically protect web applications by filtering and monitoring HTTP traffic between the application and the internet.",[97,6215,6216,6219],{},[58,6217,6218],{},"Cloud firewalls"," — delivered as a service to protect cloud-based infrastructure and applications.",[50,6221,6223],{"id":6222},"how-do-compliance-frameworks-address-firewalls","How do compliance frameworks address firewalls?",[37,6225,6226],{},"Firewalls are a foundational control across compliance standards:",[94,6228,6229,6234,6239,6244],{},[97,6230,6231,6233],{},[58,6232,1223],{}," — Requirement 1 mandates installing and maintaining firewall configurations to protect cardholder data.",[97,6235,6236,6238],{},[58,6237,378],{}," — Network security controls (A.8.20, A.8.21) require network segmentation and filtering.",[97,6240,6241,6243],{},[58,6242,633],{}," — PR.AC and PR.PT cover network protection and access enforcement.",[97,6245,6246,6248],{},[58,6247,128],{}," — CC6.6 requires restricting access through network security controls.",[50,6250,6252],{"id":6251},"what-are-best-practices-for-firewalls","What are best practices for firewalls?",[94,6254,6255,6258,6261,6264,6267],{},[97,6256,6257],{},"Define explicit allow and deny rules rather than relying on default configurations",[97,6259,6260],{},"Segment networks to limit lateral movement in the event of a breach",[97,6262,6263],{},"Review and update firewall rules regularly to remove stale or overly permissive entries",[97,6265,6266],{},"Log all firewall activity and monitor logs for anomalies",[97,6268,6269,6270],{},"Test firewall configurations as part of regular ",[41,6271,6273],{"href":6272},"\u002Fglossary\u002Fpenetration-testing","penetration testing",[50,6275,6277],{"id":6276},"how-does-episki-help-with-firewalls","How does episki help with firewalls?",[37,6279,6280,6281,167],{},"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 ",[41,6282,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":6284},[6285],{"id":6179,"depth":562,"text":6180,"children":6286},[6287,6288,6289,6290],{"id":6186,"depth":567,"text":6187},{"id":6222,"depth":567,"text":6223},{"id":6251,"depth":567,"text":6252},{"id":6276,"depth":567,"text":6277},{},"\u002Fglossary\u002Ffirewall",[4938,4939,3178,652],[3467,6295,6296],"network-security","penetration-testing",{"title":6298,"description":6299},"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":6304,"title":6305,"body":6306,"description":561,"extension":597,"lastUpdated":952,"meta":6410,"navigation":634,"path":6411,"relatedFrameworks":6412,"relatedTerms":6413,"seo":6414,"slug":6417,"stem":6418,"term":6311,"__hash__":6419},"glossary\u002F8.glossary\u002Fframework.md","Framework",{"type":29,"value":6307,"toc":6402},[6308,6312,6315,6319,6346,6350,6353,6372,6376,6379,6393,6397],[32,6309,6311],{"id":6310},"what-is-a-framework","What is a Framework?",[37,6313,6314],{},"A framework is a structured set of guidelines, controls, and best practices that organizations follow to manage security, risk, and compliance. Frameworks provide a common language and systematic approach for identifying risks, implementing safeguards, and demonstrating due diligence to auditors, customers, and regulators.",[50,6316,6318],{"id":6317},"what-are-common-compliance-frameworks","What are common compliance frameworks?",[94,6320,6321,6326,6331,6336,6341],{},[97,6322,6323,6325],{},[58,6324,378],{}," — an international standard for information security management systems (ISMS) with a risk-based approach to protecting information assets.",[97,6327,6328,6330],{},[58,6329,128],{}," — a reporting framework developed by the AICPA based on five Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy.",[97,6332,6333,6335],{},[58,6334,4568],{}," — a US law that sets requirements for protecting health information, including the Security Rule and Privacy Rule.",[97,6337,6338,6340],{},[58,6339,1223],{}," — a set of security standards for organizations that handle payment card data.",[97,6342,6343,6345],{},[58,6344,633],{}," — a voluntary framework published by the National Institute of Standards and Technology that provides a common taxonomy for managing cybersecurity risk.",[50,6347,6349],{"id":6348},"what-is-the-difference-between-a-framework-a-standard-and-a-regulation","What is the difference between a framework, a standard, and a regulation?",[37,6351,6352],{},"These terms are often used interchangeably but have important distinctions:",[94,6354,6355,6360,6366],{},[97,6356,6357,6359],{},[58,6358,6305],{}," — a flexible structure of guidelines that can be adapted to an organization's context (e.g., NIST CSF).",[97,6361,6362,6365],{},[58,6363,6364],{},"Standard"," — a more prescriptive set of requirements that can be certified against (e.g., ISO 27001).",[97,6367,6368,6371],{},[58,6369,6370],{},"Regulation"," — a legally binding requirement enforced by a governing body (e.g., HIPAA, GDPR).",[50,6373,6375],{"id":6374},"how-do-you-choose-a-framework","How do you choose a framework?",[37,6377,6378],{},"When selecting a framework, consider:",[94,6380,6381,6384,6387,6390],{},[97,6382,6383],{},"Customer and market requirements — enterprise buyers often require SOC 2 or ISO 27001",[97,6385,6386],{},"Industry regulations — healthcare organizations must comply with HIPAA; payment processors with PCI DSS",[97,6388,6389],{},"Geographic scope — GDPR for organizations handling EU data",[97,6391,6392],{},"Organizational maturity — NIST CSF is often a good starting point for organizations new to formal security programs",[50,6394,6396],{"id":6395},"how-does-episki-help-with-compliance-frameworks","How does episki help with compliance frameworks?",[37,6398,6399,6400,167],{},"episki supports multiple frameworks in a single workspace, allowing organizations to map controls across standards and reuse evidence. Learn more on our ",[41,6401,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":6403},[6404],{"id":6310,"depth":562,"text":6311,"children":6405},[6406,6407,6408,6409],{"id":6317,"depth":567,"text":6318},{"id":6348,"depth":567,"text":6349},{"id":6374,"depth":567,"text":6375},{"id":6395,"depth":567,"text":6396},{},"\u002Fglossary\u002Fframework",[3177,3178,3179,4939,652],[2028,5677,1254],{"title":6415,"description":6416},"What is a Framework? Definition & Compliance Guide","A framework is a structured set of guidelines and controls organizations follow to manage security and compliance. Common examples include ISO 27001, SOC 2, and NIST CSF.","framework","8.glossary\u002Fframework","CdMCpQrbry3zSa1fdtsyViYMvkP88wOS8pALWkyZ5Mo",{"id":6421,"title":6422,"body":6423,"description":561,"extension":597,"lastUpdated":952,"meta":6531,"navigation":634,"path":6532,"relatedFrameworks":6533,"relatedTerms":6534,"seo":6535,"slug":1254,"stem":6538,"term":6428,"__hash__":6539},"glossary\u002F8.glossary\u002Fgrc.md","Grc",{"type":29,"value":6424,"toc":6522},[6425,6429,6436,6440,6443,6457,6461,6464,6478,6482,6494,6498,6501,6515,6519],[32,6426,6428],{"id":6427},"what-is-grc","What is GRC?",[37,6430,6431,6432,6435],{},"GRC stands for ",[58,6433,6434],{},"governance, risk, and compliance"," — a coordinated approach to aligning IT and security practices with business objectives, managing risk, and meeting regulatory requirements.",[50,6437,6439],{"id":6438},"what-is-governance-in-grc","What is governance in GRC?",[37,6441,6442],{},"Governance defines the policies, roles, and decision-making structures that guide how an organization operates. In a security context, governance includes:",[94,6444,6445,6448,6451,6454],{},[97,6446,6447],{},"Establishing security policies and standards",[97,6449,6450],{},"Assigning ownership for controls and programs",[97,6452,6453],{},"Setting risk appetite and tolerance levels",[97,6455,6456],{},"Board-level oversight of security posture",[50,6458,6460],{"id":6459},"what-is-risk-management-in-grc","What is risk management in GRC?",[37,6462,6463],{},"Risk management is the process of identifying, assessing, and treating threats that could affect the organization. Common activities include:",[94,6465,6466,6469,6472,6475],{},[97,6467,6468],{},"Maintaining a risk register with likelihood and impact scores",[97,6470,6471],{},"Prioritizing remediation based on business impact",[97,6473,6474],{},"Tracking treatment plans with owners and deadlines",[97,6476,6477],{},"Reviewing risk posture on a recurring schedule",[50,6479,6481],{"id":6480},"what-is-compliance-in-grc","What is compliance in GRC?",[37,6483,6484,6485,374,6487,374,6489,6491,6492,167],{},"Compliance means meeting the requirements of external standards, regulations, and contractual obligations. Common compliance frameworks include ",[41,6486,128],{"href":127},[41,6488,378],{"href":377},[41,6490,4568],{"href":4567},", and ",[41,6493,1223],{"href":1222},[50,6495,6497],{"id":6496},"why-does-grc-matter","Why does GRC matter?",[37,6499,6500],{},"Without a coordinated approach, organizations end up with fragmented policies, duplicated controls, and gaps between what auditors expect and what teams actually do. A GRC program brings these disciplines together so that:",[94,6502,6503,6506,6509,6512],{},[97,6504,6505],{},"Controls are mapped once and reused across frameworks",[97,6507,6508],{},"Risk decisions inform which controls get priority",[97,6510,6511],{},"Evidence is collected continuously rather than scrambled before audits",[97,6513,6514],{},"Leadership has visibility into security posture and compliance status",[50,6516,6518],{"id":6517},"what-is-grc-software","What is GRC software?",[37,6520,6521],{},"GRC platforms like episki centralize controls, evidence, risk registers, and auditor collaboration in one workspace. Instead of managing compliance in spreadsheets, teams can assign owners, track evidence, and run programs across multiple frameworks simultaneously.",{"title":561,"searchDepth":562,"depth":562,"links":6523},[6524],{"id":6427,"depth":562,"text":6428,"children":6525},[6526,6527,6528,6529,6530],{"id":6438,"depth":567,"text":6439},{"id":6459,"depth":567,"text":6460},{"id":6480,"depth":567,"text":6481},{"id":6496,"depth":567,"text":6497},{"id":6517,"depth":567,"text":6518},{},"\u002Fglossary\u002Fgrc",[3177,3178,3179,4939,652],[5181,2028,956,5461],{"title":6536,"description":6537},"What is GRC? Governance, Risk, and Compliance Explained","GRC stands for governance, risk, and compliance. Learn how GRC programs help organizations manage risk, meet regulatory requirements, and align security with business goals.","8.glossary\u002Fgrc","6r8Pzm3RtrpbRSlELLbyQ2mEbI0Rv-73CiQlZaZiv9g",{"id":6541,"title":6542,"body":6543,"description":561,"extension":597,"lastUpdated":952,"meta":6768,"navigation":634,"path":6769,"relatedFrameworks":6770,"relatedTerms":6771,"seo":6772,"slug":3749,"stem":6775,"term":6548,"__hash__":6776},"glossary\u002F8.glossary\u002Fincident-response.md","Incident Response",{"type":29,"value":6544,"toc":6758},[6545,6549,6552,6556,6559,6564,6584,6589,6606,6611,6628,6633,6650,6654,6657,6695,6699,6721,6725,6728,6732,6749,6753],[32,6546,6548],{"id":6547},"what-is-incident-response","What is Incident Response?",[37,6550,6551],{},"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.",[50,6553,6555],{"id":6554},"what-is-the-incident-response-lifecycle","What is the incident response lifecycle?",[37,6557,6558],{},"Most incident response programs follow the NIST SP 800-61 framework, which defines four phases:",[37,6560,6561],{},[58,6562,6563],{},"1. Preparation",[94,6565,6566,6569,6572,6575,6578,6581],{},[97,6567,6568],{},"Develop and document the incident response plan",[97,6570,6571],{},"Establish the incident response team and define roles",[97,6573,6574],{},"Deploy detection and monitoring tools",[97,6576,6577],{},"Conduct training and tabletop exercises",[97,6579,6580],{},"Establish communication channels and escalation procedures",[97,6582,6583],{},"Prepare forensic tools and evidence collection procedures",[37,6585,6586],{},[58,6587,6588],{},"2. Detection and analysis",[94,6590,6591,6594,6597,6600,6603],{},[97,6592,6593],{},"Monitor systems for indicators of compromise (IOCs)",[97,6595,6596],{},"Triage alerts to distinguish real incidents from false positives",[97,6598,6599],{},"Determine the scope, severity, and impact of the incident",[97,6601,6602],{},"Classify the incident (data breach, malware, unauthorized access, etc.)",[97,6604,6605],{},"Document findings and initial assessment",[37,6607,6608],{},[58,6609,6610],{},"3. Containment, eradication, and recovery",[94,6612,6613,6616,6619,6622,6625],{},[97,6614,6615],{},"Contain the incident to prevent further damage (short-term and long-term containment)",[97,6617,6618],{},"Eradicate the root cause (remove malware, close vulnerabilities, revoke compromised credentials)",[97,6620,6621],{},"Recover affected systems to normal operations",[97,6623,6624],{},"Verify that systems are clean and functioning properly",[97,6626,6627],{},"Monitor for signs of recurring activity",[37,6629,6630],{},[58,6631,6632],{},"4. Post-incident activity",[94,6634,6635,6638,6641,6644,6647],{},[97,6636,6637],{},"Conduct a lessons-learned review",[97,6639,6640],{},"Document the incident timeline, actions taken, and outcomes",[97,6642,6643],{},"Identify improvements to prevent similar incidents",[97,6645,6646],{},"Update the incident response plan based on lessons learned",[97,6648,6649],{},"Fulfill any regulatory notification requirements",[50,6651,6653],{"id":6652},"who-should-be-on-the-incident-response-team","Who should be on the incident response team?",[37,6655,6656],{},"An incident response team typically includes:",[94,6658,6659,6665,6671,6677,6683,6689],{},[97,6660,6661,6664],{},[58,6662,6663],{},"Incident commander"," — leads the response effort and makes key decisions",[97,6666,6667,6670],{},[58,6668,6669],{},"Security analysts"," — perform technical investigation and containment",[97,6672,6673,6676],{},[58,6674,6675],{},"IT operations"," — support system recovery and infrastructure changes",[97,6678,6679,6682],{},[58,6680,6681],{},"Legal counsel"," — advise on regulatory obligations and liability",[97,6684,6685,6688],{},[58,6686,6687],{},"Communications"," — manage internal and external communications",[97,6690,6691,6694],{},[58,6692,6693],{},"Executive sponsor"," — provides management authority and resources",[50,6696,6698],{"id":6697},"how-do-compliance-frameworks-address-incident-response","How do compliance frameworks address incident response?",[94,6700,6701,6706,6711,6716],{},[97,6702,6703,6705],{},[58,6704,128],{}," — CC7.3 and CC7.4 require procedures for responding to identified security events and recovering from incidents",[97,6707,6708,6710],{},[58,6709,378],{}," — controls A.5.24 through A.5.28 address incident management planning, assessment, response, and learning",[97,6712,6713,6715],{},[58,6714,4568],{}," — the Security Rule requires security incident procedures (45 CFR 164.308(a)(6)), and the Breach Notification Rule mandates notification following PHI breaches",[97,6717,6718,6720],{},[58,6719,633],{}," — the Respond function (RS) addresses response planning, communications, analysis, mitigation, and improvements",[50,6722,6724],{"id":6723},"what-is-an-incident-response-tabletop-exercise","What is an incident response tabletop exercise?",[37,6726,6727],{},"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.",[50,6729,6731],{"id":6730},"what-are-common-pitfalls-with-incident-response","What are common pitfalls with incident response?",[94,6733,6734,6737,6740,6743,6746],{},[97,6735,6736],{},"No documented incident response plan",[97,6738,6739],{},"Team members unsure of their roles during an incident",[97,6741,6742],{},"Failure to preserve evidence for investigation",[97,6744,6745],{},"Delayed or incomplete regulatory notification",[97,6747,6748],{},"Not conducting post-incident reviews",[50,6750,6752],{"id":6751},"how-does-episki-help-with-incident-response","How does episki help with incident response?",[37,6754,6755,6756,167],{},"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 ",[41,6757,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":6759},[6760],{"id":6547,"depth":562,"text":6548,"children":6761},[6762,6763,6764,6765,6766,6767],{"id":6554,"depth":567,"text":6555},{"id":6652,"depth":567,"text":6653},{"id":6697,"depth":567,"text":6698},{"id":6723,"depth":567,"text":6724},{"id":6730,"depth":567,"text":6731},{"id":6751,"depth":567,"text":6752},{},"\u002Fglossary\u002Fincident-response",[4938,3177,3178,3179,652],[4023,956,5462,3747,3748],{"title":6773,"description":6774},"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":6778,"title":6779,"body":6780,"description":561,"extension":597,"lastUpdated":952,"meta":6894,"navigation":634,"path":6895,"relatedFrameworks":6896,"relatedTerms":6897,"seo":6899,"slug":6902,"stem":6903,"term":6785,"__hash__":6904},"glossary\u002F8.glossary\u002Fleast-privilege.md","Least Privilege",{"type":29,"value":6781,"toc":6886},[6782,6786,6789,6793,6796,6810,6814,6846,6850,6877,6881],[32,6783,6785],{"id":6784},"what-is-least-privilege","What is Least Privilege?",[37,6787,6788],{},"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.",[50,6790,6792],{"id":6791},"why-does-least-privilege-matter","Why does least privilege matter?",[37,6794,6795],{},"Excessive permissions are one of the most common security weaknesses. When users have more access than they need:",[94,6797,6798,6801,6804,6807],{},[97,6799,6800],{},"A compromised account gives attackers a wider attack surface",[97,6802,6803],{},"Accidental changes to sensitive systems become more likely",[97,6805,6806],{},"Insider threats are harder to detect and contain",[97,6808,6809],{},"Audit findings for excessive access are common compliance gaps",[50,6811,6813],{"id":6812},"how-do-you-implement-least-privilege","How do you implement least privilege?",[94,6815,6816,6822,6828,6834,6840],{},[97,6817,6818,6821],{},[58,6819,6820],{},"Start with zero access"," — new accounts should have no permissions by default, with access granted based on documented role requirements",[97,6823,6824,6827],{},[58,6825,6826],{},"Use role-based access control (RBAC)"," — define roles with specific permission sets rather than assigning permissions individually",[97,6829,6830,6833],{},[58,6831,6832],{},"Conduct regular access reviews"," — quarterly reviews of user permissions help identify and remove access that is no longer needed",[97,6835,6836,6839],{},[58,6837,6838],{},"Remove access promptly"," — revoke permissions immediately when employees change roles or leave the organization",[97,6841,6842,6845],{},[58,6843,6844],{},"Apply to systems and applications too"," — service accounts, APIs, and automated processes should also follow least privilege",[50,6847,6849],{"id":6848},"how-do-compliance-frameworks-address-least-privilege","How do compliance frameworks address least privilege?",[94,6851,6852,6857,6862,6867,6872],{},[97,6853,6854,6856],{},[58,6855,128],{}," — CC6.1 through CC6.3 require logical access controls based on least privilege",[97,6858,6859,6861],{},[58,6860,378],{}," — A.5.15 (access control) and A.8.2 (privileged access rights) explicitly reference least privilege",[97,6863,6864,6866],{},[58,6865,4568],{}," — the minimum necessary standard (45 CFR 164.502(b)) is the healthcare equivalent of least privilege",[97,6868,6869,6871],{},[58,6870,1223],{}," — Requirement 7 restricts access to cardholder data on a need-to-know basis",[97,6873,6874,6876],{},[58,6875,633],{}," — PR.AC-4 addresses access permissions based on least privilege",[50,6878,6880],{"id":6879},"how-does-episki-help-with-least-privilege","How does episki help with least privilege?",[37,6882,6883,6884,167],{},"episki tracks access control policies, schedules periodic access reviews, and documents evidence of least privilege enforcement for auditors. Learn more on our ",[41,6885,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":6887},[6888],{"id":6784,"depth":562,"text":6785,"children":6889},[6890,6891,6892,6893],{"id":6791,"depth":567,"text":6792},{"id":6812,"depth":567,"text":6813},{"id":6848,"depth":567,"text":6849},{"id":6879,"depth":567,"text":6880},{},"\u002Fglossary\u002Fleast-privilege",[4938,3177,3178,3179,4939,652],[3467,6898,4942],"job-separation",{"title":6900,"description":6901},"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":6906,"title":6907,"body":6908,"description":561,"extension":597,"lastUpdated":952,"meta":7425,"navigation":634,"path":7426,"relatedFrameworks":7427,"relatedTerms":7428,"seo":7429,"slug":7432,"stem":7433,"term":6913,"__hash__":7434},"glossary\u002F8.glossary\u002Flog-management.md","Log Management",{"type":29,"value":6909,"toc":7413},[6910,6914,6917,6921,6924,6962,6966,6969,6974,6977,7015,7019,7022,7054,7058,7061,7087,7091,7094,7120,7124,7127,7192,7195,7199,7202,7206,7220,7224,7238,7242,7256,7260,7274,7278,7301,7305,7308,7352,7356,7383,7387,7404,7408],[32,6911,6913],{"id":6912},"what-is-log-management","What is Log Management?",[37,6915,6916],{},"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.",[50,6918,6920],{"id":6919},"what-gets-logged-in-a-log-management-program","What gets logged in a log management program?",[37,6922,6923],{},"Effective log management covers:",[94,6925,6926,6932,6938,6944,6950,6956],{},[97,6927,6928,6931],{},[58,6929,6930],{},"Authentication events"," — successful and failed login attempts, password changes, MFA challenges",[97,6933,6934,6937],{},[58,6935,6936],{},"Authorization events"," — access grants, denials, privilege escalations",[97,6939,6940,6943],{},[58,6941,6942],{},"System events"," — configuration changes, service starts and stops, errors",[97,6945,6946,6949],{},[58,6947,6948],{},"Network events"," — firewall decisions, DNS queries, connection attempts",[97,6951,6952,6955],{},[58,6953,6954],{},"Application events"," — user actions, API calls, data access patterns",[97,6957,6958,6961],{},[58,6959,6960],{},"Security events"," — malware detections, vulnerability scan results, intrusion alerts",[50,6963,6965],{"id":6964},"what-is-log-management-architecture","What is log management architecture?",[37,6967,6968],{},"A mature log management program combines multiple components into a pipeline that moves raw event data from source to searchable, retained storage.",[6970,6971,6973],"h4",{"id":6972},"log-sources","Log sources",[37,6975,6976],{},"Logs originate from every layer of the technology stack:",[94,6978,6979,6985,6991,6997,7003,7009],{},[97,6980,6981,6984],{},[58,6982,6983],{},"Servers and operating systems"," — Linux auth logs, Windows Event Log, macOS Unified Log",[97,6986,6987,6990],{},[58,6988,6989],{},"Cloud platforms"," — AWS CloudTrail, Azure Activity Log, GCP Admin Activity audit logs",[97,6992,6993,6996],{},[58,6994,6995],{},"SaaS applications"," — Microsoft 365 Unified Audit Log, Google Workspace audit logs, Salesforce event monitoring",[97,6998,6999,7002],{},[58,7000,7001],{},"Endpoints"," — EDR telemetry, local application logs, mobile device management events",[97,7004,7005,7008],{},[58,7006,7007],{},"Network devices"," — firewalls, routers, switches, load balancers, VPN concentrators",[97,7010,7011,7014],{},[58,7012,7013],{},"Security tools"," — IDS\u002FIPS alerts, vulnerability scanners, DLP engines, email gateways",[6970,7016,7018],{"id":7017},"collection-methods","Collection methods",[37,7020,7021],{},"Getting logs from source to a central platform requires reliable collection mechanisms:",[94,7023,7024,7030,7036,7042,7048],{},[97,7025,7026,7029],{},[58,7027,7028],{},"Agents"," — lightweight forwarders installed on hosts (Fluentd, Filebeat, NXLog, Splunk Universal Forwarder) that ship logs in near real time",[97,7031,7032,7035],{},[58,7033,7034],{},"Syslog"," — the legacy standard (RFC 5424) still widely used by network devices; syslog-ng and rsyslog add filtering and reliable delivery",[97,7037,7038,7041],{},[58,7039,7040],{},"API polling"," — scheduled calls to SaaS and cloud provider APIs to pull audit logs (e.g., Microsoft Graph API, AWS CloudTrail Lake queries)",[97,7043,7044,7047],{},[58,7045,7046],{},"Cloud-native streams"," — managed pipelines like AWS Kinesis Data Firehose, Azure Event Hubs, or GCP Pub\u002FSub that deliver logs without managing agents",[97,7049,7050,7053],{},[58,7051,7052],{},"Webhooks"," — event-driven push from SaaS applications that support real-time notification (Slack audit API, GitHub audit log streaming)",[6970,7055,7057],{"id":7056},"centralization","Centralization",[37,7059,7060],{},"Logs are only useful when they are searchable in one place:",[94,7062,7063,7069,7075,7081],{},[97,7064,7065,7068],{},[58,7066,7067],{},"Commercial SIEM"," — Splunk Enterprise Security, Microsoft Sentinel, IBM QRadar provide correlation, detection rules, and case management",[97,7070,7071,7074],{},[58,7072,7073],{},"Cloud-native logging"," — AWS CloudWatch Logs, Azure Monitor, Google Cloud Logging offer tight integration with their respective platforms",[97,7076,7077,7080],{},[58,7078,7079],{},"Open-source stacks"," — the Elastic Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, and OpenSearch provide cost-effective alternatives with community-driven detection content",[97,7082,7083,7086],{},[58,7084,7085],{},"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",[6970,7088,7090],{"id":7089},"storage-tiers","Storage tiers",[37,7092,7093],{},"Log storage strategies balance search speed against cost and compliance retention:",[94,7095,7096,7102,7108,7114],{},[97,7097,7098,7101],{},[58,7099,7100],{},"Hot storage"," — fully indexed, real-time searchable data for active investigations and alerting (typically 30–90 days)",[97,7103,7104,7107],{},[58,7105,7106],{},"Warm storage"," — recent history available for on-demand search with slightly slower query times (typically 90 days to 12 months)",[97,7109,7110,7113],{},[58,7111,7112],{},"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)",[97,7115,7116,7119],{},[58,7117,7118],{},"Immutable storage"," — write-once, read-many storage that prevents tampering, critical for audit trail integrity and legal hold requirements",[50,7121,7123],{"id":7122},"what-are-the-log-retention-requirements","What are the log retention requirements?",[37,7125,7126],{},"Different compliance frameworks set varying expectations for how long logs must be kept. The table below summarizes key requirements:",[695,7128,7129,7141],{},[698,7130,7131],{},[701,7132,7133,7135,7138],{},[704,7134,6305],{},[704,7136,7137],{},"Minimum retention",[704,7139,7140],{},"Key requirements",[714,7142,7143,7153,7163,7172,7182],{},[701,7144,7145,7147,7150],{},[719,7146,1223],{},[719,7148,7149],{},"12 months (3 months immediately available)",[719,7151,7152],{},"Req 10.7 — retain audit trail history",[701,7154,7155,7157,7160],{},[719,7156,128],{},[719,7158,7159],{},"Based on risk assessment",[719,7161,7162],{},"CC7.2 — monitor system components",[701,7164,7165,7167,7169],{},[719,7166,378],{},[719,7168,7159],{},[719,7170,7171],{},"A.8.15 — log retention policy required",[701,7173,7174,7176,7179],{},[719,7175,4568],{},[719,7177,7178],{},"6 years for policies; log retention not specified but implied",[719,7180,7181],{},"Audit controls for ePHI access",[701,7183,7184,7186,7189],{},[719,7185,633],{},[719,7187,7188],{},"Based on organizational needs",[719,7190,7191],{},"DE.CM — continuous monitoring",[37,7193,7194],{},"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.",[50,7196,7198],{"id":7197},"what-should-you-alert-on-in-log-management","What should you alert on in log management?",[37,7200,7201],{},"Collecting logs without monitoring them defeats the purpose. Effective alerting focuses on high-fidelity signals across several categories:",[6970,7203,7205],{"id":7204},"authentication-anomalies","Authentication anomalies",[94,7207,7208,7211,7214,7217],{},[97,7209,7210],{},"Brute-force attempts — multiple failed logins against the same account within a short window",[97,7212,7213],{},"Impossible travel — successful logins from geographically distant locations within an implausible time frame",[97,7215,7216],{},"New device or location — first-time access from an unrecognized device, IP range, or country",[97,7218,7219],{},"Credential stuffing patterns — failed logins across many accounts from a small set of source IPs",[6970,7221,7223],{"id":7222},"privilege-escalation","Privilege escalation",[94,7225,7226,7229,7232,7235],{},[97,7227,7228],{},"Sudo or run-as usage outside of expected maintenance windows",[97,7230,7231],{},"Admin role assignments or membership changes in identity providers (Azure AD, Okta, Google Workspace)",[97,7233,7234],{},"Permission changes on sensitive resources — S3 bucket policies, database grants, file share ACLs",[97,7236,7237],{},"Service account creation or key generation",[6970,7239,7241],{"id":7240},"data-exfiltration-signals","Data exfiltration signals",[94,7243,7244,7247,7250,7253],{},[97,7245,7246],{},"Unusual download volumes — user downloading significantly more data than their baseline",[97,7248,7249],{},"Access outside business hours — especially to sensitive repositories, databases, or file shares",[97,7251,7252],{},"Mass file access — sequential reads across large numbers of records in short succession",[97,7254,7255],{},"Outbound data transfers to uncommon destinations — cloud storage services, personal email, file-sharing sites",[6970,7257,7259],{"id":7258},"configuration-changes","Configuration changes",[94,7261,7262,7265,7268,7271],{},[97,7263,7264],{},"Firewall rule modifications — new allow rules, disabled security groups, removed deny entries",[97,7266,7267],{},"Security group changes in cloud environments — opening ports, widening IP ranges",[97,7269,7270],{},"IAM policy changes — new inline policies, permission boundary modifications, role trust policy updates",[97,7272,7273],{},"DNS changes — new records, zone transfers, nameserver modifications",[6970,7275,7277],{"id":7276},"compliance-specific-events","Compliance-specific events",[94,7279,7280,7288,7295,7298],{},[97,7281,7282,7283,7287],{},"Access to ",[41,7284,7286],{"href":7285},"\u002Fglossary\u002Fpci-dss","cardholder data"," environments — any read, write, or copy operation",[97,7289,7290,7291,7294],{},"PHI access in ",[41,7292,4568],{"href":7293},"\u002Fglossary\u002Fhipaa","-regulated systems — views, exports, or modifications of protected health information",[97,7296,7297],{},"Encryption key operations — key creation, rotation, deletion, or export",[97,7299,7300],{},"Audit log access or modification attempts — anyone trying to read, delete, or alter the logs themselves",[50,7302,7304],{"id":7303},"what-are-common-log-management-mistakes","What are common log management mistakes?",[37,7306,7307],{},"Even organizations that invest in logging often fall into patterns that undermine the value of their program:",[510,7309,7310,7316,7322,7328,7334,7340,7346],{},[97,7311,7312,7315],{},[58,7313,7314],{},"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.",[97,7317,7318,7321],{},[58,7319,7320],{},"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.",[97,7323,7324,7327],{},[58,7325,7326],{},"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.",[97,7329,7330,7333],{},[58,7331,7332],{},"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.",[97,7335,7336,7339],{},[58,7337,7338],{},"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.",[97,7341,7342,7345],{},[58,7343,7344],{},"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.",[97,7347,7348,7351],{},[58,7349,7350],{},"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.",[50,7353,7355],{"id":7354},"how-do-compliance-frameworks-address-log-management","How do compliance frameworks address log management?",[94,7357,7358,7363,7368,7373,7378],{},[97,7359,7360,7362],{},[58,7361,128],{}," — CC7.1 through CC7.4 require monitoring, detection, and response capabilities that depend on logging",[97,7364,7365,7367],{},[58,7366,378],{}," — A.8.15 (logging) and A.8.16 (monitoring activities) address log collection and analysis",[97,7369,7370,7372],{},[58,7371,4568],{}," — the Security Rule requires audit controls to record and examine activity in systems containing ePHI",[97,7374,7375,7377],{},[58,7376,1223],{}," — Requirement 10 mandates logging and monitoring all access to network resources and cardholder data",[97,7379,7380,7382],{},[58,7381,633],{}," — DE.CM (continuous monitoring) and DE.AE (anomaly detection) rely on log data",[50,7384,7386],{"id":7385},"what-are-best-practices-for-log-management","What are best practices for log management?",[94,7388,7389,7392,7395,7398,7401],{},[97,7390,7391],{},"Centralize logs in a SIEM or log aggregation platform for correlation and analysis",[97,7393,7394],{},"Set retention periods that meet both compliance requirements and operational needs (typically 90 days to one year)",[97,7396,7397],{},"Protect log integrity with immutable storage or tamper-evident mechanisms",[97,7399,7400],{},"Establish alerting rules for high-risk events like failed authentication spikes or unauthorized access attempts",[97,7402,7403],{},"Regularly review and tune logging to ensure coverage without excessive noise",[50,7405,7407],{"id":7406},"how-does-episki-help-with-log-management","How does episki help with log management?",[37,7409,7410,7411,167],{},"episki documents log management policies, tracks retention schedules, and links logging controls to evidence for audit readiness. Learn more on our ",[41,7412,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":7414},[7415],{"id":6912,"depth":562,"text":6913,"children":7416},[7417,7418,7419,7420,7421,7422,7423,7424],{"id":6919,"depth":567,"text":6920},{"id":6964,"depth":567,"text":6965},{"id":7122,"depth":567,"text":7123},{"id":7197,"depth":567,"text":7198},{"id":7303,"depth":567,"text":7304},{"id":7354,"depth":567,"text":7355},{"id":7385,"depth":567,"text":7386},{"id":7406,"depth":567,"text":7407},{},"\u002Fglossary\u002Flog-management",[4938,3177,3178,3179,4939,652],[956,955,3749],{"title":7430,"description":7431},"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":7436,"title":7437,"body":7438,"description":561,"extension":597,"lastUpdated":952,"meta":7556,"navigation":634,"path":7557,"relatedFrameworks":7558,"relatedTerms":7559,"seo":7560,"slug":7563,"stem":7564,"term":7443,"__hash__":7565},"glossary\u002F8.glossary\u002Fmalware.md","Malware",{"type":29,"value":7439,"toc":7548},[7440,7444,7447,7451,7489,7493,7515,7519,7539,7543],[32,7441,7443],{"id":7442},"what-is-malware","What is Malware?",[37,7445,7446],{},"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.",[50,7448,7450],{"id":7449},"what-are-the-types-of-malware","What are the types of malware?",[94,7452,7453,7459,7465,7471,7477,7483],{},[97,7454,7455,7458],{},[58,7456,7457],{},"Viruses"," — attach to legitimate programs and spread when the infected program runs",[97,7460,7461,7464],{},[58,7462,7463],{},"Ransomware"," — encrypts data and demands payment for the decryption key",[97,7466,7467,7470],{},[58,7468,7469],{},"Trojans"," — disguise themselves as legitimate software to trick users into installation",[97,7472,7473,7476],{},[58,7474,7475],{},"Spyware"," — silently collects information about user activity and sends it to an attacker",[97,7478,7479,7482],{},[58,7480,7481],{},"Worms"," — self-replicate across networks without requiring user interaction",[97,7484,7485,7488],{},[58,7486,7487],{},"Rootkits"," — hide deep within the operating system to maintain persistent, undetected access",[50,7490,7492],{"id":7491},"how-do-compliance-frameworks-address-malware-protection","How do compliance frameworks address malware protection?",[94,7494,7495,7500,7505,7510],{},[97,7496,7497,7499],{},[58,7498,128],{}," — CC6.8 requires controls to prevent and detect malicious software",[97,7501,7502,7504],{},[58,7503,378],{}," — A.8.7 addresses protection against malware",[97,7506,7507,7509],{},[58,7508,1223],{}," — Requirement 5 mandates deploying anti-malware solutions on all commonly affected systems",[97,7511,7512,7514],{},[58,7513,633],{}," — DE.CM-4 specifically addresses malicious code detection",[50,7516,7518],{"id":7517},"what-are-common-malware-defense-strategies","What are common malware defense strategies?",[94,7520,7521,7524,7527,7530,7533,7536],{},[97,7522,7523],{},"Deploy endpoint detection and response (EDR) tools across all endpoints",[97,7525,7526],{},"Keep operating systems and applications patched and up to date",[97,7528,7529],{},"Implement email filtering to block phishing and malicious attachments",[97,7531,7532],{},"Restrict administrative privileges to reduce malware installation risk",[97,7534,7535],{},"Train employees to recognize social engineering and phishing attempts",[97,7537,7538],{},"Maintain tested backup and recovery procedures to mitigate ransomware impact",[50,7540,7542],{"id":7541},"how-does-episki-help-with-malware","How does episki help with malware?",[37,7544,7545,7546,167],{},"episki tracks anti-malware controls, monitors policy compliance, and documents endpoint protection evidence for auditors. Learn more on our ",[41,7547,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":7549},[7550],{"id":7442,"depth":562,"text":7443,"children":7551},[7552,7553,7554,7555],{"id":7449,"depth":567,"text":7450},{"id":7491,"depth":567,"text":7492},{"id":7517,"depth":567,"text":7518},{"id":7541,"depth":567,"text":7542},{},"\u002Fglossary\u002Fmalware",[4938,3177,3178,4939,652],[3749,6296,955],{"title":7561,"description":7562},"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":7567,"title":6074,"body":7568,"description":561,"extension":597,"lastUpdated":952,"meta":7677,"navigation":634,"path":7678,"relatedFrameworks":7679,"relatedTerms":7680,"seo":7681,"slug":7684,"stem":7685,"term":7573,"__hash__":7686},"glossary\u002F8.glossary\u002Fmonitoring.md",{"type":29,"value":7569,"toc":7669},[7570,7574,7577,7581,7613,7617,7639,7643,7660,7664],[32,7571,7573],{"id":7572},"what-is-monitoring","What is Monitoring?",[37,7575,7576],{},"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.",[50,7578,7580],{"id":7579},"what-are-the-types-of-monitoring","What are the types of monitoring?",[94,7582,7583,7589,7595,7601,7607],{},[97,7584,7585,7588],{},[58,7586,7587],{},"Security monitoring"," — detecting threats, intrusions, and malicious activity through SIEM tools, IDS\u002FIPS, and endpoint detection",[97,7590,7591,7594],{},[58,7592,7593],{},"Compliance monitoring"," — tracking whether controls are operating effectively and whether the organization remains aligned with framework requirements",[97,7596,7597,7600],{},[58,7598,7599],{},"Infrastructure monitoring"," — observing system health, performance, and availability across servers, networks, and cloud services",[97,7602,7603,7606],{},[58,7604,7605],{},"User activity monitoring"," — tracking user behavior to detect insider threats, policy violations, or compromised accounts",[97,7608,7609,7612],{},[58,7610,7611],{},"Vulnerability monitoring"," — continuously scanning for known vulnerabilities across the technology stack",[50,7614,7616],{"id":7615},"how-do-compliance-frameworks-address-monitoring","How do compliance frameworks address monitoring?",[94,7618,7619,7624,7629,7634],{},[97,7620,7621,7623],{},[58,7622,128],{}," — CC7.1 requires the use of detection and monitoring activities to identify anomalies",[97,7625,7626,7628],{},[58,7627,378],{}," — A.8.16 covers monitoring activities across networks and systems",[97,7630,7631,7633],{},[58,7632,1223],{}," — Requirement 10 and 11 address logging, monitoring, and regular security testing",[97,7635,7636,7638],{},[58,7637,633],{}," — the Detect function (DE.CM, DE.AE) is entirely focused on continuous monitoring and anomaly detection",[50,7640,7642],{"id":7641},"what-are-best-practices-for-monitoring","What are best practices for monitoring?",[94,7644,7645,7648,7651,7654,7657],{},[97,7646,7647],{},"Define clear thresholds and alerting rules to minimize alert fatigue",[97,7649,7650],{},"Centralize monitoring data for correlation across systems",[97,7652,7653],{},"Establish escalation procedures so alerts lead to timely investigation",[97,7655,7656],{},"Review and tune monitoring rules regularly as the environment changes",[97,7658,7659],{},"Document monitoring coverage and gaps as part of risk assessments",[50,7661,7663],{"id":7662},"how-does-episki-help-with-monitoring","How does episki help with monitoring?",[37,7665,7666,7667,167],{},"episki tracks monitoring controls, documents coverage, and links monitoring evidence to framework requirements for continuous audit readiness. Learn more on our ",[41,7668,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":7670},[7671],{"id":7572,"depth":562,"text":7573,"children":7672},[7673,7674,7675,7676],{"id":7579,"depth":567,"text":7580},{"id":7615,"depth":567,"text":7616},{"id":7641,"depth":567,"text":7642},{"id":7662,"depth":567,"text":7663},{},"\u002Fglossary\u002Fmonitoring",[4938,3177,3178,4939,652],[955,7432,3749],{"title":7682,"description":7683},"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":7688,"title":7689,"body":7690,"description":561,"extension":597,"lastUpdated":952,"meta":7798,"navigation":634,"path":7799,"relatedFrameworks":7800,"relatedTerms":7801,"seo":7802,"slug":7805,"stem":7806,"term":7695,"__hash__":7807},"glossary\u002F8.glossary\u002Fmulti-factor-authentication.md","Multi Factor Authentication",{"type":29,"value":7691,"toc":7790},[7692,7696,7699,7703,7706,7726,7730,7733,7760,7764,7781,7785],[32,7693,7695],{"id":7694},"what-is-multi-factor-authentication","What is Multi-Factor Authentication?",[37,7697,7698],{},"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.",[50,7700,7702],{"id":7701},"what-are-the-authentication-factors-used-in-mfa","What are the authentication factors used in MFA?",[37,7704,7705],{},"MFA combines factors from different categories:",[94,7707,7708,7714,7720],{},[97,7709,7710,7713],{},[58,7711,7712],{},"Something you know"," — passwords, PINs, security questions",[97,7715,7716,7719],{},[58,7717,7718],{},"Something you have"," — mobile phones (SMS or authenticator apps), hardware tokens, smart cards",[97,7721,7722,7725],{},[58,7723,7724],{},"Something you are"," — biometrics such as fingerprints, facial recognition, or iris scans",[50,7727,7729],{"id":7728},"how-do-compliance-frameworks-address-mfa","How do compliance frameworks address MFA?",[37,7731,7732],{},"MFA is required or strongly recommended across all major frameworks:",[94,7734,7735,7740,7745,7750,7755],{},[97,7736,7737,7739],{},[58,7738,128],{}," — CC6.1 requires multi-factor authentication for access to sensitive systems",[97,7741,7742,7744],{},[58,7743,378],{}," — A.8.5 addresses secure authentication including multi-factor methods",[97,7746,7747,7749],{},[58,7748,4568],{}," — while not explicitly mandating MFA, the Security Rule requires access controls that effectively necessitate it for ePHI systems",[97,7751,7752,7754],{},[58,7753,1223],{}," — Requirement 8.3 mandates MFA for all remote access to the cardholder data environment",[97,7756,7757,7759],{},[58,7758,633],{}," — PR.AC-7 recommends multi-factor authentication as part of identity management",[50,7761,7763],{"id":7762},"what-are-implementation-best-practices","What are implementation best practices?",[94,7765,7766,7769,7772,7775,7778],{},[97,7767,7768],{},"Require MFA for all user accounts, not just administrators",[97,7770,7771],{},"Prefer authenticator apps or hardware tokens over SMS-based codes (which are vulnerable to SIM swapping)",[97,7773,7774],{},"Implement MFA on VPN, cloud console, email, and any system containing sensitive data",[97,7776,7777],{},"Provide backup recovery methods (recovery codes, backup devices) to prevent lockouts",[97,7779,7780],{},"Monitor and alert on MFA bypass attempts or disabled MFA",[50,7782,7784],{"id":7783},"how-does-episki-help-with-mfa","How does episki help with MFA?",[37,7786,7787,7788,167],{},"episki tracks MFA policies, monitors enforcement across systems, and documents MFA evidence for compliance audits. Learn more on our ",[41,7789,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":7791},[7792],{"id":7694,"depth":562,"text":7695,"children":7793},[7794,7795,7796,7797],{"id":7701,"depth":567,"text":7702},{"id":7728,"depth":567,"text":7729},{"id":7762,"depth":567,"text":7763},{"id":7783,"depth":567,"text":7784},{},"\u002Fglossary\u002Fmulti-factor-authentication",[4938,3177,3178,3179,4939,652],[3467,6902,3468],{"title":7803,"description":7804},"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":7809,"title":7810,"body":7811,"description":561,"extension":597,"lastUpdated":952,"meta":7932,"navigation":634,"path":7933,"relatedFrameworks":7934,"relatedTerms":7935,"seo":7936,"slug":6295,"stem":7939,"term":7816,"__hash__":7940},"glossary\u002F8.glossary\u002Fnetwork-security.md","Network Security",{"type":29,"value":7812,"toc":7924},[7813,7817,7820,7824,7862,7866,7888,7892,7915,7919],[32,7814,7816],{"id":7815},"what-is-network-security","What is Network Security?",[37,7818,7819],{},"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.",[50,7821,7823],{"id":7822},"what-are-the-core-components-of-network-security","What are the core components of network security?",[94,7825,7826,7832,7838,7844,7850,7856],{},[97,7827,7828,7831],{},[58,7829,7830],{},"Firewalls"," — filter traffic between trusted and untrusted networks based on security rules",[97,7833,7834,7837],{},[58,7835,7836],{},"Intrusion detection and prevention systems (IDS\u002FIPS)"," — monitor network traffic for suspicious activity and can automatically block threats",[97,7839,7840,7843],{},[58,7841,7842],{},"Network segmentation"," — divides the network into isolated zones to contain breaches and limit lateral movement",[97,7845,7846,7849],{},[58,7847,7848],{},"Virtual private networks (VPN)"," — encrypt traffic between remote users and the corporate network",[97,7851,7852,7855],{},[58,7853,7854],{},"Network access control (NAC)"," — enforces policies about which devices and users can connect to the network",[97,7857,7858,7861],{},[58,7859,7860],{},"DNS security"," — protects against DNS-based attacks like spoofing and cache poisoning",[50,7863,7865],{"id":7864},"how-do-compliance-frameworks-address-network-security","How do compliance frameworks address network security?",[94,7867,7868,7873,7878,7883],{},[97,7869,7870,7872],{},[58,7871,1223],{}," — Requirements 1 and 2 address firewall configuration and secure network architecture",[97,7874,7875,7877],{},[58,7876,378],{}," — A.8.20 (network security), A.8.21 (security of network services), and A.8.22 (segregation of networks)",[97,7879,7880,7882],{},[58,7881,128],{}," — CC6.6 requires security controls for network boundaries",[97,7884,7885,7887],{},[58,7886,633],{}," — PR.AC and PR.PT cover network access control and protective technology",[50,7889,7891],{"id":7890},"what-are-best-practices-for-network-security","What are best practices for network security?",[94,7893,7894,7897,7900,7903,7906,7909],{},[97,7895,7896],{},"Implement defense in depth with multiple layers of network controls",[97,7898,7899],{},"Regularly scan for open ports and unnecessary services",[97,7901,7902],{},"Encrypt data in transit using TLS\u002FSSL",[97,7904,7905],{},"Monitor network traffic for anomalies and potential intrusions",[97,7907,7908],{},"Document network architecture and maintain up-to-date network diagrams",[97,7910,7911,7912,7914],{},"Conduct regular ",[41,7913,6273],{"href":6272}," to identify network vulnerabilities",[50,7916,7918],{"id":7917},"how-does-episki-help-with-network-security","How does episki help with network security?",[37,7920,7921,7922,167],{},"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 ",[41,7923,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":7925},[7926],{"id":7815,"depth":562,"text":7816,"children":7927},[7928,7929,7930,7931],{"id":7822,"depth":567,"text":7823},{"id":7864,"depth":567,"text":7865},{"id":7890,"depth":567,"text":7891},{"id":7917,"depth":567,"text":7918},{},"\u002Fglossary\u002Fnetwork-security",[4938,3177,3178,4939,652],[6300,3467,3468,6296],{"title":7937,"description":7938},"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":7942,"title":7943,"body":7944,"description":561,"extension":597,"lastUpdated":952,"meta":8018,"navigation":634,"path":43,"relatedFrameworks":8019,"relatedTerms":8020,"seo":8021,"slug":8024,"stem":8025,"term":7949,"__hash__":8026},"glossary\u002F8.glossary\u002Fnist.md","Nist",{"type":29,"value":7945,"toc":8011},[7946,7950,7953,7957,7981,7985,7988,8002,8006],[32,7947,7949],{"id":7948},"what-is-nist","What is NIST?",[37,7951,7952],{},"NIST (National Institute of Standards and Technology) is a non-regulatory agency of the United States Department of Commerce that develops and publishes standards, guidelines, and best practices for technology and cybersecurity. NIST's publications are among the most widely referenced resources in information security worldwide, influencing both government and private sector organizations.",[50,7954,7956],{"id":7955},"what-are-the-key-nist-publications","What are the key NIST publications?",[94,7958,7959,7964,7969,7975],{},[97,7960,7961,7963],{},[58,7962,5544],{}," — a voluntary framework organized around five core functions (Identify, Protect, Detect, Respond, Recover) that provides a common language for managing cybersecurity risk. Widely adopted by organizations of all sizes.",[97,7965,7966,7968],{},[58,7967,123],{}," — a comprehensive catalog of security and privacy controls for federal information systems. Often used as a reference by private organizations building security programs.",[97,7970,7971,7974],{},[58,7972,7973],{},"NIST SP 800-171"," — security requirements for protecting Controlled Unclassified Information (CUI) in non-federal systems, required for defense contractors.",[97,7976,7977,7980],{},[58,7978,7979],{},"NIST SP 800-37"," — the Risk Management Framework (RMF) that guides organizations through a structured process for managing security risk.",[50,7982,7984],{"id":7983},"why-does-nist-matter-for-compliance","Why does NIST matter for compliance?",[37,7986,7987],{},"While NIST frameworks are voluntary for most private organizations, they serve as the foundation or reference point for many compliance requirements:",[94,7989,7990,7993,7996,7999],{},[97,7991,7992],{},"Federal agencies are required to follow NIST guidelines",[97,7994,7995],{},"Defense contractors must comply with NIST SP 800-171 (enforced through CMMC)",[97,7997,7998],{},"Many ISO 27001 and SOC 2 control mappings reference NIST publications",[97,8000,8001],{},"Cyber insurance providers increasingly reference NIST CSF alignment",[50,8003,8005],{"id":8004},"how-does-episki-help-with-nist","How does episki help with NIST?",[37,8007,8008,8009,167],{},"episki supports NIST CSF as a framework and provides control mappings between NIST and other standards like ISO 27001 and SOC 2. Learn more on our ",[41,8010,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":8012},[8013],{"id":7948,"depth":562,"text":7949,"children":8014},[8015,8016,8017],{"id":7955,"depth":567,"text":7956},{"id":7983,"depth":567,"text":7984},{"id":8004,"depth":567,"text":8005},{},[652,3178],[6417,2028,5181],{"title":8022,"description":8023},"What is NIST? Definition & Compliance Guide","NIST (National Institute of Standards and Technology) is a US government agency that publishes widely used cybersecurity frameworks and guidelines, including the NIST Cybersecurity Framework (CSF).","nist","8.glossary\u002Fnist","2ae4F06Rs2No0I7mHDHgivjpmqOCtVisAqiVyvGLz0Q",{"id":8028,"title":8029,"body":8030,"description":561,"extension":597,"lastUpdated":952,"meta":8144,"navigation":634,"path":8145,"relatedFrameworks":8146,"relatedTerms":8147,"seo":8148,"slug":8151,"stem":8152,"term":8035,"__hash__":8153},"glossary\u002F8.glossary\u002Foperational-risk.md","Operational Risk",{"type":29,"value":8031,"toc":8136},[8032,8036,8039,8043,8069,8073,8090,8094,8127,8131],[32,8033,8035],{"id":8034},"what-is-operational-risk","What is Operational Risk?",[37,8037,8038],{},"Operational risk is the potential for loss, disruption, or harm caused by failures in internal processes, people, systems, or external events. Unlike market or credit risk, operational risk arises from the day-to-day functioning of an organization and includes everything from human errors and system outages to fraud and natural disasters.",[50,8040,8042],{"id":8041},"what-are-the-sources-of-operational-risk","What are the sources of operational risk?",[94,8044,8045,8051,8057,8063],{},[97,8046,8047,8050],{},[58,8048,8049],{},"People"," — human error, insufficient training, insider threats, key person dependencies",[97,8052,8053,8056],{},[58,8054,8055],{},"Processes"," — poorly designed workflows, lack of documentation, inadequate controls",[97,8058,8059,8062],{},[58,8060,8061],{},"Systems"," — hardware failures, software bugs, cybersecurity incidents, integration breakdowns",[97,8064,8065,8068],{},[58,8066,8067],{},"External events"," — natural disasters, supply chain disruptions, regulatory changes, third-party failures",[50,8070,8072],{"id":8071},"how-do-compliance-frameworks-address-operational-risk","How do compliance frameworks address operational risk?",[94,8074,8075,8080,8085],{},[97,8076,8077,8079],{},[58,8078,128],{}," — CC3.1 through CC3.4 address risk assessment and management, including operational risks",[97,8081,8082,8084],{},[58,8083,378],{}," — clauses 6.1 and 8.2 require organizations to identify and treat information security risks, many of which are operational",[97,8086,8087,8089],{},[58,8088,633],{}," — the Identify function (ID.RA) covers risk assessment including operational risk factors",[50,8091,8093],{"id":8092},"how-do-you-manage-operational-risk","How do you manage operational risk?",[94,8095,8096,8104,8111,8121,8124],{},[97,8097,8098,8099,8103],{},"Maintain a ",[41,8100,8102],{"href":8101},"\u002Fglossary\u002Frisk-register","risk register"," that captures identified operational risks with likelihood and impact ratings",[97,8105,8106,8107],{},"Implement controls proportional to the risk level and document them in a ",[41,8108,8110],{"href":8109},"\u002Fglossary\u002Frisk-treatment-plan","risk treatment plan",[97,8112,8113,8114,336,8117,8120],{},"Establish ",[41,8115,8116],{"href":5178},"business continuity",[41,8118,8119],{"href":6164},"disaster recovery"," plans for high-impact scenarios",[97,8122,8123],{},"Conduct regular risk assessments to identify new or changing risks",[97,8125,8126],{},"Monitor key risk indicators (KRIs) to detect emerging operational issues",[50,8128,8130],{"id":8129},"how-does-episki-help-with-operational-risk","How does episki help with operational risk?",[37,8132,8133,8134,167],{},"episki provides risk registers, links risks to controls, and tracks risk treatment plans to help organizations manage operational risk systematically. Learn more on our ",[41,8135,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":8137},[8138],{"id":8034,"depth":562,"text":8035,"children":8139},[8140,8141,8142,8143],{"id":8041,"depth":567,"text":8042},{"id":8071,"depth":567,"text":8072},{"id":8092,"depth":567,"text":8093},{"id":8129,"depth":567,"text":8130},{},"\u002Fglossary\u002Foperational-risk",[3177,3178,652],[5181,5182,3747,3748],{"title":8149,"description":8150},"What is Operational Risk? Definition & Compliance Guide","Operational risk is the potential for loss or disruption caused by failed internal processes, human errors, system failures, or external events.","operational-risk","8.glossary\u002Foperational-risk","FHa7St6ZxdXS6nN4A99Zbld2Kt8WzJLlE0DHI0np8_o",{"id":8155,"title":8156,"body":8157,"description":561,"extension":597,"lastUpdated":952,"meta":8400,"navigation":634,"path":6272,"relatedFrameworks":8401,"relatedTerms":8402,"seo":8404,"slug":6296,"stem":8407,"term":8162,"__hash__":8408},"glossary\u002F8.glossary\u002Fpenetration-testing.md","Penetration Testing",{"type":29,"value":8158,"toc":8390},[8159,8163,8166,8170,8173,8178,8222,8227,8247,8251,8254,8304,8308,8311,8333,8337,8357,8361,8364,8381,8385],[32,8160,8162],{"id":8161},"what-is-penetration-testing","What is Penetration Testing?",[37,8164,8165],{},"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.",[50,8167,8169],{"id":8168},"what-are-the-types-of-penetration-testing","What are the types of penetration testing?",[37,8171,8172],{},"Penetration tests are categorized by scope and approach:",[37,8174,8175],{},[58,8176,8177],{},"By target:",[94,8179,8180,8186,8192,8198,8204,8210,8216],{},[97,8181,8182,8185],{},[58,8183,8184],{},"External testing"," — targets internet-facing assets such as web applications, APIs, email servers, and firewalls",[97,8187,8188,8191],{},[58,8189,8190],{},"Internal testing"," — simulates an attacker who has gained access to the internal network",[97,8193,8194,8197],{},[58,8195,8196],{},"Web application testing"," — focuses specifically on web application vulnerabilities (injection, authentication flaws, etc.)",[97,8199,8200,8203],{},[58,8201,8202],{},"API testing"," — evaluates the security of application programming interfaces",[97,8205,8206,8209],{},[58,8207,8208],{},"Mobile application testing"," — assesses mobile apps for security weaknesses",[97,8211,8212,8215],{},[58,8213,8214],{},"Wireless testing"," — tests wireless network security",[97,8217,8218,8221],{},[58,8219,8220],{},"Social engineering"," — tests human vulnerabilities through phishing, pretexting, or physical access attempts",[37,8223,8224],{},[58,8225,8226],{},"By knowledge level:",[94,8228,8229,8235,8241],{},[97,8230,8231,8234],{},[58,8232,8233],{},"Black box"," — the tester has no prior knowledge of the target environment, simulating an external attacker",[97,8236,8237,8240],{},[58,8238,8239],{},"White box"," — the tester has full access to source code, architecture documentation, and credentials",[97,8242,8243,8246],{},[58,8244,8245],{},"Gray box"," — the tester has partial knowledge, such as user-level credentials or limited documentation",[50,8248,8250],{"id":8249},"what-is-the-penetration-testing-process","What is the penetration testing process?",[37,8252,8253],{},"A professional penetration test follows a structured methodology:",[510,8255,8256,8262,8268,8274,8280,8286,8292,8298],{},[97,8257,8258,8261],{},[58,8259,8260],{},"Scoping"," — define the targets, objectives, rules of engagement, and testing window",[97,8263,8264,8267],{},[58,8265,8266],{},"Reconnaissance"," — gather information about the target through passive and active techniques",[97,8269,8270,8273],{},[58,8271,8272],{},"Vulnerability identification"," — discover potential weaknesses using automated tools and manual analysis",[97,8275,8276,8279],{},[58,8277,8278],{},"Exploitation"," — attempt to exploit identified vulnerabilities to demonstrate real-world impact",[97,8281,8282,8285],{},[58,8283,8284],{},"Post-exploitation"," — if access is gained, assess how far an attacker could go (lateral movement, data access, privilege escalation)",[97,8287,8288,8291],{},[58,8289,8290],{},"Reporting"," — document all findings with severity ratings, evidence, and remediation recommendations",[97,8293,8294,8297],{},[58,8295,8296],{},"Remediation support"," — assist the organization in understanding and addressing findings",[97,8299,8300,8303],{},[58,8301,8302],{},"Retest"," — verify that remediation efforts have effectively addressed the vulnerabilities",[50,8305,8307],{"id":8306},"how-do-compliance-frameworks-address-penetration-testing","How do compliance frameworks address penetration testing?",[37,8309,8310],{},"Multiple frameworks require or recommend penetration testing:",[94,8312,8313,8318,8323,8328],{},[97,8314,8315,8317],{},[58,8316,128],{}," — while not explicitly mandated, penetration testing supports CC7.1 (detection of vulnerabilities) and CC4.1 (monitoring)",[97,8319,8320,8322],{},[58,8321,1223],{}," — Requirement 11.4 requires annual penetration testing of the CDE, plus testing after significant changes",[97,8324,8325,8327],{},[58,8326,633],{}," — DE.CM (continuous monitoring) and ID.RA (risk assessment) are supported by penetration testing",[97,8329,8330,8332],{},[58,8331,378],{}," — control A.8.8 addresses management of technical vulnerabilities, which penetration testing supports",[50,8334,8336],{"id":8335},"how-often-should-penetration-tests-be-performed","How often should penetration tests be performed?",[94,8338,8339,8345,8351],{},[97,8340,8341,8344],{},[58,8342,8343],{},"Annual testing"," is the minimum standard for most compliance frameworks",[97,8346,8347,8350],{},[58,8348,8349],{},"After significant changes"," — major infrastructure changes, application releases, or acquisitions should trigger additional testing",[97,8352,8353,8356],{},[58,8354,8355],{},"Continuous testing programs"," — some organizations implement bug bounty programs or periodic testing throughout the year",[50,8358,8360],{"id":8359},"how-do-you-select-a-penetration-testing-firm","How do you select a penetration testing firm?",[37,8362,8363],{},"When choosing a penetration testing provider:",[94,8365,8366,8369,8372,8375,8378],{},[97,8367,8368],{},"Look for relevant certifications (OSCP, OSCE, CREST, GPEN)",[97,8370,8371],{},"Request sample reports to evaluate reporting quality",[97,8373,8374],{},"Verify the firm carries appropriate insurance",[97,8376,8377],{},"Confirm experience with your technology stack and industry",[97,8379,8380],{},"Ensure clear rules of engagement and communication protocols",[50,8382,8384],{"id":8383},"how-does-episki-help-with-penetration-testing","How does episki help with penetration testing?",[37,8386,8387,8388,167],{},"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 ",[41,8389,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":8391},[8392],{"id":8161,"depth":562,"text":8162,"children":8393},[8394,8395,8396,8397,8398,8399],{"id":8168,"depth":567,"text":8169},{"id":8249,"depth":567,"text":8250},{"id":8306,"depth":567,"text":8307},{"id":8335,"depth":567,"text":8336},{"id":8359,"depth":567,"text":8360},{"id":8383,"depth":567,"text":8384},{},[4938,3177,4939,652],[8403,5462,955,3467],"asv",{"title":8405,"description":8406},"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":8410,"title":8411,"body":8412,"description":561,"extension":597,"lastUpdated":952,"meta":9011,"navigation":634,"path":8101,"relatedFrameworks":9012,"relatedTerms":9013,"seo":9015,"slug":5181,"stem":9018,"term":8417,"__hash__":9019},"glossary\u002F8.glossary\u002Frisk-register.md","Risk Register",{"type":29,"value":8413,"toc":8996},[8414,8418,8421,8425,8428,8502,8506,8509,8559,8563,8566,8598,8602,8605,8611,8617,8623,8630,8634,8637,8724,8727,8731,8737,8763,8766,8770,8773,8809,8813,8816,8917,8920,8924,8927,8957,8961,8964,8984,8987,8991],[32,8415,8417],{"id":8416},"what-is-a-risk-register","What is a Risk Register?",[37,8419,8420],{},"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.",[50,8422,8424],{"id":8423},"what-does-a-risk-register-contain","What does a risk register contain?",[37,8426,8427],{},"A well-structured risk register typically includes the following fields for each risk:",[94,8429,8430,8436,8442,8448,8454,8460,8466,8472,8478,8484,8490,8496],{},[97,8431,8432,8435],{},[58,8433,8434],{},"Risk ID"," — a unique identifier for tracking",[97,8437,8438,8441],{},[58,8439,8440],{},"Risk description"," — a clear statement of the risk, typically describing the threat, vulnerability, and potential impact",[97,8443,8444,8447],{},[58,8445,8446],{},"Risk category"," — classification such as operational, technical, compliance, strategic, or third-party",[97,8449,8450,8453],{},[58,8451,8452],{},"Likelihood"," — the probability of the risk materializing (often rated on a scale such as 1-5 or low\u002Fmedium\u002Fhigh)",[97,8455,8456,8459],{},[58,8457,8458],{},"Impact"," — the potential consequence if the risk materializes (rated similarly)",[97,8461,8462,8465],{},[58,8463,8464],{},"Risk score"," — calculated from likelihood and impact (e.g., likelihood x impact)",[97,8467,8468,8471],{},[58,8469,8470],{},"Risk owner"," — the person accountable for managing the risk",[97,8473,8474,8477],{},[58,8475,8476],{},"Treatment option"," — mitigate, accept, transfer, or avoid",[97,8479,8480,8483],{},[58,8481,8482],{},"Controls"," — the specific controls implemented to address the risk",[97,8485,8486,8489],{},[58,8487,8488],{},"Residual risk"," — the remaining risk level after treatment is applied",[97,8491,8492,8495],{},[58,8493,8494],{},"Status"," — current state (open, in treatment, accepted, closed)",[97,8497,8498,8501],{},[58,8499,8500],{},"Review date"," — when the risk was last reviewed or when the next review is due",[50,8503,8505],{"id":8504},"how-do-you-build-a-risk-register","How do you build a risk register?",[37,8507,8508],{},"Creating a risk register follows a systematic process:",[510,8510,8511,8517,8523,8529,8535,8541,8547,8553],{},[97,8512,8513,8516],{},[58,8514,8515],{},"Identify risks"," — gather risks through workshops, interviews, threat modeling, vulnerability assessments, incident reviews, and industry threat intelligence",[97,8518,8519,8522],{},[58,8520,8521],{},"Assess each risk"," — evaluate the likelihood and impact of each risk to determine its severity",[97,8524,8525,8528],{},[58,8526,8527],{},"Prioritize"," — rank risks by their risk score to focus attention and resources on the most significant threats",[97,8530,8531,8534],{},[58,8532,8533],{},"Assign ownership"," — designate a responsible owner for each risk",[97,8536,8537,8540],{},[58,8538,8539],{},"Determine treatment"," — decide how each risk will be handled",[97,8542,8543,8546],{},[58,8544,8545],{},"Document controls"," — record the specific controls that address each risk",[97,8548,8549,8552],{},[58,8550,8551],{},"Calculate residual risk"," — assess the remaining risk after controls are applied",[97,8554,8555,8558],{},[58,8556,8557],{},"Review and approve"," — have management review and approve the register",[50,8560,8562],{"id":8561},"how-do-you-maintain-the-risk-register","How do you maintain the risk register?",[37,8564,8565],{},"A risk register is only valuable if it is kept current. Regular maintenance includes:",[94,8567,8568,8574,8580,8586,8592],{},[97,8569,8570,8573],{},[58,8571,8572],{},"Periodic reviews"," — review the full register at least quarterly, with management review at least annually",[97,8575,8576,8579],{},[58,8577,8578],{},"Triggered updates"," — update the register when significant changes occur (new systems, new services, organizational changes, incidents)",[97,8581,8582,8585],{},[58,8583,8584],{},"New risk identification"," — continuously identify and add new risks as the threat landscape evolves",[97,8587,8588,8591],{},[58,8589,8590],{},"Treatment progress tracking"," — monitor and update the status of risk treatment activities",[97,8593,8594,8597],{},[58,8595,8596],{},"Residual risk reassessment"," — re-evaluate residual risk as controls are implemented or change",[50,8599,8601],{"id":8600},"what-are-common-risk-scoring-methodologies","What are common risk scoring methodologies?",[37,8603,8604],{},"How you score risks determines how actionable the register is. The most common approaches:",[37,8606,8607,8610],{},[58,8608,8609],{},"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,8612,8613,8616],{},[58,8614,8615],{},"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,8618,8619,8622],{},[58,8620,8621],{},"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,8624,8625,8626,8629],{},"Most compliance programs start with a 5×5 matrix, then introduce quantitative methods for top-tier risks. Whichever scale you choose, ",[58,8627,8628],{},"document the definitions"," — what does \"likelihood 4\" actually mean in your organization? Without clear definitions, different raters produce wildly different scores.",[50,8631,8633],{"id":8632},"how-do-compliance-frameworks-address-risk-register","How do compliance frameworks address risk register?",[37,8635,8636],{},"Different frameworks require or recommend risk registers, often with specific expectations:",[695,8638,8639,8650],{},[698,8640,8641],{},[701,8642,8643,8645,8647],{},[704,8644,6305],{},[704,8646,4711],{},[704,8648,8649],{},"Specific reference",[714,8651,8652,8664,8676,8688,8700,8712],{},[701,8653,8654,8658,8661],{},[719,8655,8656],{},[58,8657,378],{},[719,8659,8660],{},"Documented risk assessment process with register as artifact",[719,8662,8663],{},"Clause 6.1.2 and 8.2",[701,8665,8666,8670,8673],{},[719,8667,8668],{},[58,8669,128],{},[719,8671,8672],{},"Risk identification, assessment, and response",[719,8674,8675],{},"CC3.1–CC3.4",[701,8677,8678,8682,8685],{},[719,8679,8680],{},[58,8681,633],{},[719,8683,8684],{},"Risk assessment and risk management strategy",[719,8686,8687],{},"ID.RA and GV.RM (new in 2.0)",[701,8689,8690,8694,8697],{},[719,8691,8692],{},[58,8693,4568],{},[719,8695,8696],{},"Risk analysis for ePHI",[719,8698,8699],{},"§164.308(a)(1)(ii)(A)",[701,8701,8702,8706,8709],{},[719,8703,8704],{},[58,8705,1223],{},[719,8707,8708],{},"Targeted risk analyses for specific requirements",[719,8710,8711],{},"PCI DSS v4.0 Req 12.3.1",[701,8713,8714,8718,8721],{},[719,8715,8716],{},[58,8717,386],{},[719,8719,8720],{},"Risk management practices",[719,8722,8723],{},"RA.L2-3.11.1 through 3.11.3",[37,8725,8726],{},"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.",[50,8728,8730],{"id":8729},"what-are-the-risk-treatment-options","What are the risk treatment options?",[37,8732,8733,8734,8736],{},"For each risk, pick one of four treatment strategies (often documented in a parallel ",[41,8735,8110],{"href":8109},"):",[94,8738,8739,8745,8751,8757],{},[97,8740,8741,8744],{},[58,8742,8743],{},"Mitigate"," — implement controls to reduce likelihood or impact. Most common choice. Example: deploy MFA to reduce account takeover likelihood.",[97,8746,8747,8750],{},[58,8748,8749],{},"Accept"," — acknowledge the risk as within tolerance and proceed. Requires documented rationale and, for significant risks, executive sign-off.",[97,8752,8753,8756],{},[58,8754,8755],{},"Transfer"," — shift the risk to a third party via insurance, contract, or outsourcing. Cyber insurance is the canonical example.",[97,8758,8759,8762],{},[58,8760,8761],{},"Avoid"," — eliminate the activity causing the risk. Example: decide not to launch a feature in a high-risk jurisdiction.",[37,8764,8765],{},"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.",[50,8767,8769],{"id":8768},"how-do-you-connect-the-risk-register-to-operational-workflows","How do you connect the risk register to operational workflows?",[37,8771,8772],{},"A risk register that lives in isolation quickly goes stale. High-performing programs integrate it with:",[94,8774,8775,8784,8791,8797,8803],{},[97,8776,8777,8783],{},[58,8778,8779],{},[41,8780,8782],{"href":8781},"\u002Fglossary\u002Fvendor-risk-management","Vendor risk management"," — third-party risks from vendor assessments feed into the enterprise register",[97,8785,8786,8790],{},[58,8787,8788],{},[41,8789,5728],{"href":6769}," — post-incident reviews identify new risks or update likelihood scores for known ones",[97,8792,8793,8796],{},[58,8794,8795],{},"Change management"," — significant system or business changes trigger a register update before deployment",[97,8798,8799,8802],{},[58,8800,8801],{},"Policy reviews"," — annual policy reviews check whether controls still address the risks they were designed for",[97,8804,8805,8808],{},[58,8806,8807],{},"Board reporting"," — top-tier risks roll up into executive dashboards showing trends, treatment progress, and heat maps",[50,8810,8812],{"id":8811},"what-does-an-example-risk-register-entry-look-like","What does an example risk register entry look like?",[37,8814,8815],{},"A concrete example makes the structure tangible. Consider a risk identified during an ISO 27001 internal audit:",[695,8817,8818,8828],{},[698,8819,8820],{},[701,8821,8822,8825],{},[704,8823,8824],{},"Field",[704,8826,8827],{},"Value",[714,8829,8830,8837,8844,8851,8858,8865,8873,8881,8888,8895,8903,8910],{},[701,8831,8832,8834],{},[719,8833,8434],{},[719,8835,8836],{},"R-042",[701,8838,8839,8841],{},[719,8840,1387],{},[719,8842,8843],{},"Unencrypted customer PII in database backups stored in S3",[701,8845,8846,8848],{},[719,8847,706],{},[719,8849,8850],{},"Data protection \u002F technical",[701,8852,8853,8855],{},[719,8854,8452],{},[719,8856,8857],{},"3 (possible — we have access logs but no automated detection)",[701,8859,8860,8862],{},[719,8861,8458],{},[719,8863,8864],{},"5 (severe — regulatory exposure under GDPR and state privacy laws)",[701,8866,8867,8870],{},[719,8868,8869],{},"Inherent score",[719,8871,8872],{},"15 (high)",[701,8874,8875,8878],{},[719,8876,8877],{},"Owner",[719,8879,8880],{},"CISO",[701,8882,8883,8886],{},[719,8884,8885],{},"Treatment",[719,8887,8743],{},[701,8889,8890,8892],{},[719,8891,8482],{},[719,8893,8894],{},"Enable S3 server-side encryption with KMS; rotate existing backups; add Macie scan",[701,8896,8897,8900],{},[719,8898,8899],{},"Residual score",[719,8901,8902],{},"4 (low — automated encryption + detection materially reduces both)",[701,8904,8905,8907],{},[719,8906,8494],{},[719,8908,8909],{},"In treatment — 60% complete",[701,8911,8912,8914],{},[719,8913,8500],{},[719,8915,8916],{},"2026-06-01 (quarterly cadence)",[37,8918,8919],{},"This level of detail turns the register into a practical management tool rather than a compliance artifact.",[50,8921,8923],{"id":8922},"what-are-common-pitfalls-with-a-risk-register","What are common pitfalls with a risk register?",[37,8925,8926],{},"Organizations often struggle with risk registers due to:",[94,8928,8929,8932,8935,8938,8941,8944,8951,8954],{},[97,8930,8931],{},"Making the register too complex or too simple",[97,8933,8934],{},"Failing to review and update regularly",[97,8936,8937],{},"Not assigning clear ownership or clear treatment deadlines",[97,8939,8940],{},"Rating all risks as \"high\" without meaningful differentiation",[97,8942,8943],{},"Treating the register as a compliance checkbox rather than a management tool",[97,8945,8946,8947,8950],{},"Disconnecting the register from ",[41,8948,8949],{"href":6769},"incident response"," and vendor management workflows",[97,8952,8953],{},"Keeping risks open indefinitely without closure criteria or residual risk acceptance",[97,8955,8956],{},"Not versioning the register, making it impossible to demonstrate historical decisions to auditors",[50,8958,8960],{"id":8959},"what-risk-register-tools-and-templates-are-available","What risk register tools and templates are available?",[37,8962,8963],{},"Organizations use a range of tools to maintain a register:",[94,8965,8966,8972,8978],{},[97,8967,8968,8971],{},[58,8969,8970],{},"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.",[97,8973,8974,8977],{},[58,8975,8976],{},"GRC platforms"," — purpose-built tools (including episki) handle scoring, ownership, treatment workflows, and evidence links out of the box.",[97,8979,8980,8983],{},[58,8981,8982],{},"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,8985,8986],{},"Whatever tool you choose, exportability matters: auditors frequently ask for point-in-time snapshots, and regulators may request historical registers during an investigation.",[50,8988,8990],{"id":8989},"how-does-episki-help-with-a-risk-register","How does episki help with a risk register?",[37,8992,8993,8994,167],{},"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 ",[41,8995,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":8997},[8998],{"id":8416,"depth":562,"text":8417,"children":8999},[9000,9001,9002,9003,9004,9005,9006,9007,9008,9009,9010],{"id":8423,"depth":567,"text":8424},{"id":8504,"depth":567,"text":8505},{"id":8561,"depth":567,"text":8562},{"id":8600,"depth":567,"text":8601},{"id":8632,"depth":567,"text":8633},{"id":8729,"depth":567,"text":8730},{"id":8768,"depth":567,"text":8769},{"id":8811,"depth":567,"text":8812},{"id":8922,"depth":567,"text":8923},{"id":8959,"depth":567,"text":8960},{"id":8989,"depth":567,"text":8990},{},[4938,3178,652,3177],[5182,5462,2028,9014],"vendor-risk-management",{"title":9016,"description":9017},"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":9021,"title":9022,"body":9023,"description":561,"extension":597,"lastUpdated":952,"meta":9221,"navigation":634,"path":8109,"relatedFrameworks":9222,"relatedTerms":9223,"seo":9225,"slug":5182,"stem":9228,"term":9028,"__hash__":9229},"glossary\u002F8.glossary\u002Frisk-treatment-plan.md","Risk Treatment Plan",{"type":29,"value":9024,"toc":9211},[9025,9029,9032,9034,9037,9059,9062,9066,9069,9119,9123,9126,9146,9149,9153,9156,9160,9163,9201,9205],[32,9026,9028],{"id":9027},"what-is-a-risk-treatment-plan","What is a Risk Treatment Plan?",[37,9030,9031],{},"A risk treatment plan is a formal document that outlines how an organization intends to address each identified information security risk. It specifies the treatment option selected for each risk, the controls to be implemented, responsible owners, timelines, and expected residual risk levels. Risk treatment plans are a core requirement of ISO 27001 and a recommended practice across most compliance frameworks.",[50,9033,8730],{"id":8729},[37,9035,9036],{},"For each identified risk, organizations typically choose one of four treatment options:",[94,9038,9039,9044,9049,9054],{},[97,9040,9041,9043],{},[58,9042,8743],{}," — implement controls to reduce the likelihood or impact of the risk to an acceptable level",[97,9045,9046,9048],{},[58,9047,8749],{}," — acknowledge the risk and decide not to take additional action, typically because the cost of treatment exceeds the potential impact",[97,9050,9051,9053],{},[58,9052,8755],{}," — shift the risk to a third party, such as through insurance or outsourcing to a specialized provider",[97,9055,9056,9058],{},[58,9057,8761],{}," — eliminate the risk entirely by discontinuing the activity or service that creates it",[37,9060,9061],{},"Most risks are treated through mitigation, with specific controls designed to address the identified threat.",[50,9063,9065],{"id":9064},"what-are-the-components-of-a-risk-treatment-plan","What are the components of a risk treatment plan?",[37,9067,9068],{},"A comprehensive risk treatment plan includes:",[94,9070,9071,9077,9082,9087,9092,9097,9103,9109,9114],{},[97,9072,9073,9076],{},[58,9074,9075],{},"Risk identifier"," — reference to the specific risk from the risk register",[97,9078,9079,9081],{},[58,9080,8440],{}," — a clear statement of the risk, including threat, vulnerability, and potential impact",[97,9083,9084,9086],{},[58,9085,8476],{}," — which of the four options has been selected",[97,9088,9089,9091],{},[58,9090,8482],{}," — the specific controls to be implemented for mitigated risks",[97,9093,9094,9096],{},[58,9095,8877],{}," — the person or team responsible for implementing the treatment",[97,9098,9099,9102],{},[58,9100,9101],{},"Timeline"," — target dates for implementation milestones",[97,9104,9105,9108],{},[58,9106,9107],{},"Resources required"," — budget, tools, or personnel needed",[97,9110,9111,9113],{},[58,9112,8488],{}," — the expected risk level after treatment is applied",[97,9115,9116,9118],{},[58,9117,8494],{}," — current implementation progress",[50,9120,9122],{"id":9121},"how-does-iso-27001-handle-risk-treatment","How does ISO 27001 handle risk treatment?",[37,9124,9125],{},"ISO 27001 clause 6.1.3 specifically requires organizations to formulate a risk treatment plan. The standard requires that:",[94,9127,9128,9131,9134,9137,9140,9143],{},[97,9129,9130],{},"Risk treatment options are determined for each assessed risk",[97,9132,9133],{},"Controls necessary to implement the treatment are identified",[97,9135,9136],{},"Selected controls are compared against Annex A to ensure completeness",[97,9138,9139],{},"A Statement of Applicability is produced",[97,9141,9142],{},"The risk treatment plan is approved by risk owners",[97,9144,9145],{},"Residual risk levels are accepted by management",[37,9147,9148],{},"The risk treatment plan is a key document reviewed during certification audits and surveillance audits.",[50,9150,9152],{"id":9151},"how-does-nist-csf-handle-risk-treatment","How does NIST CSF handle risk treatment?",[37,9154,9155],{},"While NIST CSF does not prescribe a specific risk treatment plan format, the framework's Identify function (particularly the Risk Assessment category) and Protect function align closely with risk treatment concepts. Organizations using NIST CSF often develop risk treatment plans as part of their implementation.",[50,9157,9159],{"id":9158},"how-do-you-build-an-effective-risk-treatment-plan","How do you build an effective risk treatment plan?",[37,9161,9162],{},"To create a practical and effective risk treatment plan:",[510,9164,9165,9171,9177,9183,9189,9195],{},[97,9166,9167,9170],{},[58,9168,9169],{},"Prioritize risks"," — start with the highest-rated risks from your risk register",[97,9172,9173,9176],{},[58,9174,9175],{},"Select realistic treatments"," — choose options that are feasible given your budget, resources, and timeline",[97,9178,9179,9182],{},[58,9180,9181],{},"Assign clear ownership"," — every risk treatment must have a named owner accountable for implementation",[97,9184,9185,9188],{},[58,9186,9187],{},"Set measurable milestones"," — define specific, trackable milestones rather than vague commitments",[97,9190,9191,9194],{},[58,9192,9193],{},"Review regularly"," — update the plan as risks change, new threats emerge, or controls are implemented",[97,9196,9197,9200],{},[58,9198,9199],{},"Communicate status"," — report progress to management and stakeholders",[50,9202,9204],{"id":9203},"how-does-episki-help-with-a-risk-treatment-plan","How does episki help with a risk treatment plan?",[37,9206,9207,9208,167],{},"episki links your risk register directly to your risk treatment plan, making it easy to assign treatments, track implementation progress, and measure residual risk. The platform sends reminders to risk owners and provides management dashboards showing treatment status across the organization. Learn more on our ",[41,9209,9210],{"href":377},"ISO 27001 compliance page",{"title":561,"searchDepth":562,"depth":562,"links":9212},[9213],{"id":9027,"depth":562,"text":9028,"children":9214},[9215,9216,9217,9218,9219,9220],{"id":8729,"depth":567,"text":8730},{"id":9064,"depth":567,"text":9065},{"id":9121,"depth":567,"text":9122},{"id":9151,"depth":567,"text":9152},{"id":9158,"depth":567,"text":9159},{"id":9203,"depth":567,"text":9204},{},[3178,652],[5181,9224,3178,2028,5462],"statement-of-applicability",{"title":9226,"description":9227},"What is a Risk Treatment Plan? Definition & Compliance Guide","A risk treatment plan documents how an organization will address identified risks through mitigation, acceptance, transfer, or avoidance strategies.","8.glossary\u002Frisk-treatment-plan","XKyLKWys4TbkZnZHspi5JeYYAOEqihsJOcykDIp7X_Y",{"id":9231,"title":9232,"body":9233,"description":561,"extension":597,"lastUpdated":952,"meta":9442,"navigation":634,"path":9443,"relatedFrameworks":9444,"relatedTerms":9445,"seo":9447,"slug":9450,"stem":9451,"term":9238,"__hash__":9452},"glossary\u002F8.glossary\u002Fthird-party-risk.md","Third Party Risk",{"type":29,"value":9234,"toc":9432},[9235,9239,9242,9246,9249,9293,9297,9300,9332,9336,9339,9366,9370,9373,9416,9420,9423,9427],[32,9236,9238],{"id":9237},"what-is-third-party-risk","What is Third-Party Risk?",[37,9240,9241],{},"Third-party risk is the potential for negative outcomes — including data breaches, operational disruptions, compliance violations, and reputational damage — arising from an organization's relationships with external vendors, partners, and service providers. As modern organizations depend on extensive networks of third parties, managing this risk has become a critical discipline within information security and compliance programs.",[50,9243,9245],{"id":9244},"what-are-the-types-of-third-party-risk","What are the types of third-party risk?",[37,9247,9248],{},"Third-party risk encompasses several categories:",[94,9250,9251,9257,9263,9269,9275,9281,9287],{},[97,9252,9253,9256],{},[58,9254,9255],{},"Security risk"," — the vendor's security weaknesses could lead to unauthorized access to your data or systems",[97,9258,9259,9262],{},[58,9260,9261],{},"Compliance risk"," — the vendor's practices may not meet regulatory requirements, creating liability for your organization",[97,9264,9265,9268],{},[58,9266,9267],{},"Operational risk"," — vendor outages, service failures, or business disruptions could impact your operations",[97,9270,9271,9274],{},[58,9272,9273],{},"Financial risk"," — vendor financial instability could threaten service continuity",[97,9276,9277,9280],{},[58,9278,9279],{},"Reputational risk"," — a vendor's public security incident or ethical violation could damage your brand",[97,9282,9283,9286],{},[58,9284,9285],{},"Strategic risk"," — over-reliance on a single vendor creates concentration risk",[97,9288,9289,9292],{},[58,9290,9291],{},"Data risk"," — the vendor may mishandle, lose, or improperly disclose your data",[50,9294,9296],{"id":9295},"why-is-third-party-risk-growing","Why is third-party risk growing?",[37,9298,9299],{},"Several trends are increasing third-party risk exposure:",[94,9301,9302,9308,9314,9320,9326],{},[97,9303,9304,9307],{},[58,9305,9306],{},"Cloud adoption"," — organizations store sensitive data with cloud providers and SaaS applications",[97,9309,9310,9313],{},[58,9311,9312],{},"Supply chain complexity"," — vendors use their own vendors (fourth parties), creating layers of risk",[97,9315,9316,9319],{},[58,9317,9318],{},"Data sharing"," — business processes increasingly require sharing data with external parties",[97,9321,9322,9325],{},[58,9323,9324],{},"Remote work"," — distributed workforces rely on more external tools and services",[97,9327,9328,9331],{},[58,9329,9330],{},"Regulatory expansion"," — regulators increasingly hold organizations accountable for their vendors' practices",[50,9333,9335],{"id":9334},"how-do-compliance-frameworks-address-third-party-risk","How do compliance frameworks address third-party risk?",[37,9337,9338],{},"Compliance frameworks address third-party risk explicitly:",[94,9340,9341,9346,9351,9356,9361],{},[97,9342,9343,9345],{},[58,9344,128],{}," — CC9.2 requires assessing risks from vendor relationships. The SSAE 18 standard also requires monitoring subservice organizations.",[97,9347,9348,9350],{},[58,9349,378],{}," — clauses A.5.19 through A.5.23 address supplier relationship security, including policies, assessment, and monitoring",[97,9352,9353,9355],{},[58,9354,633],{}," — the Govern function includes supply chain risk management expectations",[97,9357,9358,9360],{},[58,9359,4568],{}," — requires BAAs with business associates and oversight of how they handle PHI",[97,9362,9363,9365],{},[58,9364,1223],{}," — Requirement 12.8 requires maintaining and monitoring service provider relationships",[50,9367,9369],{"id":9368},"how-do-you-manage-third-party-risk","How do you manage third-party risk?",[37,9371,9372],{},"Effective third-party risk management involves:",[510,9374,9375,9381,9387,9393,9399,9405,9410],{},[97,9376,9377,9380],{},[58,9378,9379],{},"Inventory"," — know all your third parties and what data or systems they can access",[97,9382,9383,9386],{},[58,9384,9385],{},"Assess"," — evaluate each third party's security posture before and during the relationship",[97,9388,9389,9392],{},[58,9390,9391],{},"Tier"," — classify third parties by risk level to allocate assessment effort appropriately",[97,9394,9395,9398],{},[58,9396,9397],{},"Contract"," — include security requirements, breach notification clauses, and audit rights",[97,9400,9401,9404],{},[58,9402,9403],{},"Monitor"," — continuously track vendor security posture, not just at onboarding",[97,9406,9407,9409],{},[58,9408,218],{}," — have plans for responding to vendor incidents, including data breaches and service outages",[97,9411,9412,9415],{},[58,9413,9414],{},"Exit"," — plan for vendor transitions, ensuring data is returned or destroyed and access is revoked",[50,9417,9419],{"id":9418},"what-is-fourth-party-risk","What is fourth-party risk?",[37,9421,9422],{},"An often-overlooked dimension is fourth-party risk — the risk from your vendors' vendors. If your SaaS provider stores data on a cloud platform that is breached, you are affected even though you have no direct relationship with the cloud provider. Understanding and addressing fourth-party risk requires knowing your vendors' critical subservice organizations.",[50,9424,9426],{"id":9425},"how-does-episki-help-with-third-party-risk","How does episki help with third-party risk?",[37,9428,9429,9430,167],{},"episki provides a centralized platform for managing third-party risk, including vendor inventories, risk assessments, contract tracking, and continuous monitoring. The platform maps vendor relationships to compliance framework requirements and flags vendors that require reassessment. Learn more on our ",[41,9431,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":9433},[9434],{"id":9237,"depth":562,"text":9238,"children":9435},[9436,9437,9438,9439,9440,9441],{"id":9244,"depth":567,"text":9245},{"id":9295,"depth":567,"text":9296},{"id":9334,"depth":567,"text":9335},{"id":9368,"depth":567,"text":9369},{"id":9418,"depth":567,"text":9419},{"id":9425,"depth":567,"text":9426},{},"\u002Fglossary\u002Fthird-party-risk",[3177,3178,652],[9014,5181,5182,9446],"business-associate",{"title":9448,"description":9449},"What is Third-Party Risk? Definition & Compliance Guide","Third-party risk is the potential for security incidents, data breaches, or operational disruption originating from your vendors and service providers.","third-party-risk","8.glossary\u002Fthird-party-risk","Dxu5bTWIkyoD6ZHRPLQgh07uV8r8_KtcEKritXx39Ao",{"id":9454,"title":9455,"body":9456,"description":561,"extension":597,"lastUpdated":952,"meta":10046,"navigation":634,"path":8781,"relatedFrameworks":10047,"relatedTerms":10048,"seo":10050,"slug":9014,"stem":10053,"term":9461,"__hash__":10054},"glossary\u002F8.glossary\u002Fvendor-risk-management.md","Vendor Risk Management",{"type":29,"value":9457,"toc":10033},[9458,9462,9465,9469,9472,9499,9503,9506,9512,9526,9531,9545,9551,9565,9571,9588,9594,9608,9612,9615,9665,9669,9686,9690,9693,9758,9763,9768,9783,9788,9796,9800,9803,9809,9826,9832,9849,9855,9869,9875,9886,9892,9896,9899,9905,9911,9917,9923,9938,9942,9945,9951,9986,9992,10021,10024,10028],[32,9459,9461],{"id":9460},"what-is-vendor-risk-management","What is Vendor Risk Management?",[37,9463,9464],{},"Vendor risk management (VRM) is the process of identifying, assessing, monitoring, and mitigating risks associated with third-party vendors and service providers. As organizations increasingly rely on external partners for critical services — from cloud infrastructure to payroll processing — the security of those vendors directly impacts the organization's own risk posture.",[50,9466,9468],{"id":9467},"why-does-vendor-risk-management-matter","Why does vendor risk management matter?",[37,9470,9471],{},"Third-party vendors are a leading source of data breaches and security incidents. When a vendor that handles your data is compromised, you are compromised. Compliance frameworks recognize this reality:",[94,9473,9474,9479,9484,9489,9494],{},[97,9475,9476,9478],{},[58,9477,128],{}," — CC9.2 requires organizations to assess and manage risks associated with vendors and business partners",[97,9480,9481,9483],{},[58,9482,378],{}," — controls A.5.19 through A.5.23 address information security in supplier relationships",[97,9485,9486,9488],{},[58,9487,633],{}," — the Identify function includes supply chain risk management",[97,9490,9491,9493],{},[58,9492,4568],{}," — requires Business Associate Agreements with vendors handling PHI",[97,9495,9496,9498],{},[58,9497,1223],{}," — requires monitoring of service provider PCI DSS compliance",[50,9500,9502],{"id":9501},"what-are-the-components-of-a-vrm-program","What are the components of a VRM program?",[37,9504,9505],{},"An effective vendor risk management program includes:",[37,9507,9508,9511],{},[58,9509,9510],{},"Vendor inventory"," — maintain a complete list of all third-party vendors, including:",[94,9513,9514,9517,9520,9523],{},[97,9515,9516],{},"What services they provide",[97,9518,9519],{},"What data they can access",[97,9521,9522],{},"Their criticality to business operations",[97,9524,9525],{},"Contract terms and renewal dates",[37,9527,9528,9530],{},[58,9529,5009],{}," — evaluate each vendor's security posture through:",[94,9532,9533,9536,9539,9542],{},[97,9534,9535],{},"Security questionnaires (SIG, CAIQ, or custom)",[97,9537,9538],{},"Review of compliance reports (SOC 2, ISO 27001 certificates)",[97,9540,9541],{},"Technical assessments when appropriate",[97,9543,9544],{},"Review of publicly available security information",[37,9546,9547,9550],{},[58,9548,9549],{},"Risk tiering"," — classify vendors by risk level based on:",[94,9552,9553,9556,9559,9562],{},[97,9554,9555],{},"Sensitivity of data they access",[97,9557,9558],{},"Criticality of the service they provide",[97,9560,9561],{},"Volume of data handled",[97,9563,9564],{},"Regulatory requirements (e.g., HIPAA business associates)",[37,9566,9567,9570],{},[58,9568,9569],{},"Contractual protections"," — ensure vendor contracts include:",[94,9572,9573,9576,9579,9582,9585],{},[97,9574,9575],{},"Security requirements and responsibilities",[97,9577,9578],{},"Data protection obligations",[97,9580,9581],{},"Breach notification requirements",[97,9583,9584],{},"Right to audit",[97,9586,9587],{},"Compliance certifications",[37,9589,9590,9593],{},[58,9591,9592],{},"Ongoing monitoring"," — continuously monitor vendors through:",[94,9595,9596,9599,9602,9605],{},[97,9597,9598],{},"Annual or periodic reassessments",[97,9600,9601],{},"Review of updated compliance reports",[97,9603,9604],{},"Monitoring for security incidents or breaches",[97,9606,9607],{},"Tracking changes in the vendor's services or risk profile",[50,9609,9611],{"id":9610},"what-is-the-vendor-assessment-process","What is the vendor assessment process?",[37,9613,9614],{},"A typical vendor assessment follows these steps:",[510,9616,9617,9623,9629,9635,9641,9647,9653,9659],{},[97,9618,9619,9622],{},[58,9620,9621],{},"Categorize the vendor"," — determine risk tier based on data access and service criticality",[97,9624,9625,9628],{},[58,9626,9627],{},"Send questionnaire"," — distribute a security questionnaire appropriate to the risk tier",[97,9630,9631,9634],{},[58,9632,9633],{},"Review responses"," — evaluate the vendor's security practices against your requirements",[97,9636,9637,9640],{},[58,9638,9639],{},"Request evidence"," — ask for supporting documentation (SOC 2 report, policies, certifications)",[97,9642,9643,9646],{},[58,9644,9645],{},"Identify gaps"," — document areas where the vendor does not meet your standards",[97,9648,9649,9652],{},[58,9650,9651],{},"Make decision"," — approve, approve with conditions, or reject the vendor",[97,9654,9655,9658],{},[58,9656,9657],{},"Document results"," — record the assessment findings and decision",[97,9660,9661,9664],{},[58,9662,9663],{},"Schedule reassessment"," — set a date for the next review based on risk tier",[50,9666,9668],{"id":9667},"what-are-common-challenges-with-vendor-risk-management","What are common challenges with vendor risk management?",[94,9670,9671,9674,9677,9680,9683],{},[97,9672,9673],{},"Managing assessments across dozens or hundreds of vendors",[97,9675,9676],{},"Getting timely responses to security questionnaires",[97,9678,9679],{},"Assessing vendors that lack formal compliance certifications",[97,9681,9682],{},"Monitoring vendor risk between assessment cycles",[97,9684,9685],{},"Balancing thoroughness with business velocity",[50,9687,9689],{"id":9688},"what-is-vrm-requirements-by-compliance-framework","What is VRM requirements by compliance framework?",[37,9691,9692],{},"Different compliance frameworks address vendor risk management with varying depth and specificity. Understanding where each framework sets expectations helps you design a VRM program that satisfies multiple standards simultaneously.",[695,9694,9695,9706],{},[698,9696,9697],{},[701,9698,9699,9701,9703],{},[704,9700,6305],{},[704,9702,7140],{},[704,9704,9705],{},"Specific controls",[714,9707,9708,9718,9728,9738,9748],{},[701,9709,9710,9712,9715],{},[719,9711,128],{},[719,9713,9714],{},"Vendor risk assessment, monitoring",[719,9716,9717],{},"CC9.2, CC3.2",[701,9719,9720,9722,9725],{},[719,9721,378],{},[719,9723,9724],{},"Supplier security policies, monitoring, change management",[719,9726,9727],{},"A.5.19–A.5.23",[701,9729,9730,9732,9735],{},[719,9731,4568],{},[719,9733,9734],{},"BAAs required for PHI-handling vendors",[719,9736,9737],{},"§164.308(b), §164.314",[701,9739,9740,9742,9745],{},[719,9741,1223],{},[719,9743,9744],{},"Service provider compliance validation",[719,9746,9747],{},"Req 12.8, Req 12.9",[701,9749,9750,9752,9755],{},[719,9751,77],{},[719,9753,9754],{},"Dedicated supply chain governance",[719,9756,9757],{},"GV.SC (expanded in 2.0)",[37,9759,9760,9762],{},[58,9761,128],{}," treats vendor risk as part of the broader risk management criteria. CC9.2 requires organizations to assess risks arising from vendor and business partner relationships, while CC3.2 covers risk identification across the entity — including third-party risks. Auditors expect documented vendor inventories, risk assessments, and evidence of ongoing monitoring.",[37,9764,9765,9767],{},[58,9766,378],{}," provides the most prescriptive set of supplier controls. Controls A.5.19 through A.5.23 cover information security in supplier relationships, including establishing policies, addressing security within agreements, managing the ICT supply chain, monitoring and reviewing supplier services, and managing changes to supplier services.",[37,9769,9770,9772,9773,9777,9778,9782],{},[58,9771,4568],{}," takes a narrower but legally binding approach. Any vendor that creates, receives, maintains, or transmits ",[41,9774,9776],{"href":9775},"\u002Fglossary\u002Fphi","protected health information (PHI)"," on behalf of a covered entity must sign a ",[41,9779,9781],{"href":9780},"\u002Fglossary\u002Fbaa","Business Associate Agreement",". The BAA must specify permitted uses of PHI, breach notification obligations, and data return or destruction requirements.",[37,9784,9785,9787],{},[58,9786,1223],{}," Requirement 12.8 requires organizations to maintain a list of service providers, ensure a written agreement acknowledging the provider's security responsibilities, establish a process for engaging providers, and monitor their PCI DSS compliance status at least annually. Requirement 12.9 adds that service providers must themselves acknowledge their responsibilities in writing.",[37,9789,9790,9792,9793,167],{},[58,9791,77],{}," significantly expanded its supply chain risk management guidance, moving it from a sub-category into its own top-level function category — GV.SC — under the Govern function. This reflects the growing recognition that supply chain risk requires dedicated governance structures, not just ad hoc assessments. For a deeper look at these changes, see our guide to ",[41,9794,9795],{"href":141},"NIST CSF v2.0 changes",[50,9797,9799],{"id":9798},"how-do-you-build-a-vendor-risk-tiering-model","How do you build a vendor risk tiering model?",[37,9801,9802],{},"Not every vendor requires the same level of scrutiny. A risk tiering model lets you allocate assessment effort proportionally to the risk each vendor introduces. Most organizations use a four-tier model based on data sensitivity, service criticality, and replaceability.",[37,9804,9805,9808],{},[58,9806,9807],{},"Critical (Tier 1)"," — The vendor handles sensitive data (PII, PHI, cardholder data), provides a business-critical service, or would be difficult and costly to replace. Examples include your primary cloud infrastructure provider, EHR system, or payment processor.",[94,9810,9811,9814,9817,9820,9823],{},[97,9812,9813],{},"Full security assessment with detailed questionnaire (SIG or equivalent)",[97,9815,9816],{},"Review of SOC 2 Type II report and\u002For ISO 27001 certificate",[97,9818,9819],{},"Annual reassessment at minimum, with continuous monitoring where feasible",[97,9821,9822],{},"Comprehensive contractual security requirements, including breach notification, audit rights, and data handling obligations",[97,9824,9825],{},"Executive-level relationship management and regular security review meetings",[37,9827,9828,9831],{},[58,9829,9830],{},"High (Tier 2)"," — The vendor accesses internal systems or handles moderate-sensitivity data, but the service is not irreplaceable. Examples include HR\u002Fpayroll platforms, CRM systems, or development tools with access to production data.",[94,9833,9834,9837,9840,9843,9846],{},[97,9835,9836],{},"Standard security questionnaire",[97,9838,9839],{},"Review of available compliance certifications",[97,9841,9842],{},"Annual reassessment",[97,9844,9845],{},"Basic contractual protections including breach notification and data protection clauses",[97,9847,9848],{},"Periodic check-ins with vendor security contacts",[37,9850,9851,9854],{},[58,9852,9853],{},"Medium (Tier 3)"," — The vendor has limited data access, provides a replaceable service, and does not interact with regulated data. Examples include project management tools, marketing analytics platforms, or office productivity suites.",[94,9856,9857,9860,9863,9866],{},[97,9858,9859],{},"Abbreviated assessment or targeted questionnaire",[97,9861,9862],{},"Biennial reassessment (every two years)",[97,9864,9865],{},"Standard contract terms with security addendum",[97,9867,9868],{},"Reassess earlier if the vendor's scope of access changes",[37,9870,9871,9874],{},[58,9872,9873],{},"Low (Tier 4)"," — The vendor has no access to organizational data and provides a commodity service. Examples include office supply vendors, cleaning services, or publicly available information tools.",[94,9876,9877,9880,9883],{},[97,9878,9879],{},"Self-attestation or security waiver",[97,9881,9882],{},"Reassess on contract renewal",[97,9884,9885],{},"Standard procurement terms, no additional security clauses required",[37,9887,9888,9889,9891],{},"The tiering decision should be documented in your ",[41,9890,8102],{"href":8101}," and revisited whenever the vendor's scope of service changes. A vendor that starts at Tier 3 may move to Tier 1 if you later grant it access to sensitive data.",[50,9893,9895],{"id":9894},"what-vendor-assessment-tools-and-questionnaires-are-available","What vendor assessment tools and questionnaires are available?",[37,9897,9898],{},"Choosing the right assessment tool depends on the vendor's risk tier, your industry, and the depth of information you need.",[37,9900,9901,9904],{},[58,9902,9903],{},"SIG (Standardized Information Gathering) questionnaire"," — maintained by Shared Assessments, the SIG is the most widely used vendor assessment questionnaire. SIG Full covers 18 risk domains and is appropriate for Tier 1 and Tier 2 vendors. SIG Lite provides a condensed version for lower-risk vendors. The SIG maps to multiple compliance frameworks, making it efficient for organizations with overlapping regulatory requirements.",[37,9906,9907,9910],{},[58,9908,9909],{},"CAIQ (Consensus Assessment Initiative Questionnaire)"," — developed by the Cloud Security Alliance, the CAIQ is purpose-built for evaluating cloud service providers. It maps to the CSA Cloud Controls Matrix and covers cloud-specific risks such as multi-tenancy, data residency, and virtualization security. Use it alongside or in place of the SIG for cloud-heavy vendor portfolios.",[37,9912,9913,9916],{},[58,9914,9915],{},"Custom questionnaires"," — many organizations supplement standardized questionnaires with custom questions tailored to their specific regulatory environment or risk appetite. Custom questions are particularly useful for addressing industry-specific risks, such as PCI DSS requirements for payment processors or HIPAA requirements for healthcare vendors.",[37,9918,9919,9922],{},[58,9920,9921],{},"Automated risk rating platforms"," — tools like SecurityScorecard and BitSight provide continuous, outside-in assessments of a vendor's security posture by analyzing publicly observable signals such as DNS configuration, patching cadence, exposed services, and breach history. These platforms are useful for continuous monitoring between formal assessment cycles and for initial screening of prospective vendors.",[37,9924,9925,9928,9929,9933,9934,9937],{},[58,9926,9927],{},"Direct review of compliance reports"," — reviewing a vendor's ",[41,9930,9932],{"href":9931},"\u002Fglossary\u002Fsoc2-type-2","SOC 2 Type II"," report is often more valuable than a questionnaire response. A SOC 2 report is independently audited and covers the vendor's actual controls over a defined period, including any exceptions or control gaps identified by the auditor. Similarly, an ",[41,9935,378],{"href":9936},"\u002Fglossary\u002Fiso27001"," certificate confirms that the vendor's information security management system has been independently assessed. When a vendor can provide these reports, they should be your primary source of assurance — supplemented by questionnaires only for areas not covered by the audit scope.",[50,9939,9941],{"id":9940},"how-do-you-handle-vendor-offboarding-and-incident-response","How do you handle vendor offboarding and incident response?",[37,9943,9944],{},"Vendor risk management does not end when the contract is signed — it also requires structured processes for when the relationship ends or when something goes wrong.",[37,9946,9947,9950],{},[58,9948,9949],{},"Vendor offboarding"," — terminating a vendor relationship requires deliberate steps to protect your data and systems:",[94,9952,9953,9959,9965,9971,9980],{},[97,9954,9955,9958],{},[58,9956,9957],{},"Data return or destruction"," — require the vendor to return all organizational data in a usable format and certify destruction of any remaining copies. The contract should specify timelines and acceptable destruction methods (e.g., cryptographic erasure, physical destruction).",[97,9960,9961,9964],{},[58,9962,9963],{},"Access revocation"," — immediately revoke the vendor's access to all systems, networks, VPNs, and APIs. Disable any service accounts, API keys, or shared credentials associated with the vendor.",[97,9966,9967,9970],{},[58,9968,9969],{},"Certificate and key rotation"," — if the vendor had access to encryption keys, certificates, or shared secrets, rotate them promptly. This includes API tokens, SSH keys, and any credentials the vendor may have stored.",[97,9972,9973,9976,9977,9979],{},[58,9974,9975],{},"Risk register update"," — update your ",[41,9978,8102],{"href":8101}," to reflect the terminated relationship and document any residual risks, such as data that was processed during the engagement.",[97,9981,9982,9985],{},[58,9983,9984],{},"Knowledge transfer"," — if the vendor provided a critical service, ensure operational knowledge has been transferred to the replacement vendor or internal team before the relationship ends.",[37,9987,9988,9991],{},[58,9989,9990],{},"Vendor-side breach response"," — your contracts and BAAs should establish clear expectations for what happens when a vendor experiences a security incident:",[94,9993,9994,10000,10009,10015],{},[97,9995,9996,9999],{},[58,9997,9998],{},"Notification timelines"," — specify how quickly the vendor must notify you of a confirmed or suspected breach. Industry standards range from 24 to 72 hours, but for critical vendors handling regulated data, shorter timelines may be appropriate. HIPAA requires notification without unreasonable delay and no later than 60 days.",[97,10001,10002,10005,10006,10008],{},[58,10003,10004],{},"Cooperation requirements"," — the vendor should be contractually obligated to cooperate with your ",[41,10007,8949],{"href":6769}," investigation, including providing forensic evidence, access logs, and impact assessments.",[97,10010,10011,10014],{},[58,10012,10013],{},"Remediation obligations"," — define who bears responsibility for remediation costs, including notification to affected individuals, credit monitoring, legal fees, and regulatory fines. The contract should also specify timelines for implementing corrective actions.",[97,10016,10017,10020],{},[58,10018,10019],{},"Communication coordination"," — establish protocols for how breach-related communications will be coordinated between your organization and the vendor to ensure consistent messaging to regulators, customers, and the public.",[37,10022,10023],{},"A well-defined vendor offboarding and incident response process reduces the risk of lingering access, orphaned data, and confused responsibilities when the unexpected happens.",[50,10025,10027],{"id":10026},"how-does-episki-help-with-vendor-risk-management","How does episki help with vendor risk management?",[37,10029,10030,10031,167],{},"episki centralizes vendor risk management with vendor inventories, automated questionnaire distribution, risk scoring, and reassessment scheduling. The platform tracks vendor compliance status and flags vendors that require attention. Learn more on our ",[41,10032,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":10034},[10035],{"id":9460,"depth":562,"text":9461,"children":10036},[10037,10038,10039,10040,10041,10042,10043,10044,10045],{"id":9467,"depth":567,"text":9468},{"id":9501,"depth":567,"text":9502},{"id":9610,"depth":567,"text":9611},{"id":9667,"depth":567,"text":9668},{"id":9688,"depth":567,"text":9689},{"id":9798,"depth":567,"text":9799},{"id":9894,"depth":567,"text":9895},{"id":9940,"depth":567,"text":9941},{"id":10026,"depth":567,"text":10027},{},[3177,3178,652],[9450,5181,10049,5461],"baa",{"title":10051,"description":10052},"What is Vendor Risk Management? Definition & Compliance Guide","Vendor risk management (VRM) is the process of assessing and monitoring security risks from third-party vendors. Learn how to build an effective VRM program.","8.glossary\u002Fvendor-risk-management","zYUPNHD7rd1SYb6jxTVuGceKFAFQoewNnryA575dKLg",{"id":10056,"title":10057,"body":10058,"description":561,"extension":597,"lastUpdated":952,"meta":10225,"navigation":634,"path":10226,"relatedFrameworks":10227,"relatedTerms":10228,"seo":10230,"slug":10233,"stem":10234,"term":10063,"__hash__":10235},"glossary\u002F8.glossary\u002Fvulnerability-management.md","Vulnerability Management",{"type":29,"value":10059,"toc":10216},[10060,10064,10067,10071,10074,10110,10114,10117,10144,10148,10174,10178,10181,10207,10211],[32,10061,10063],{"id":10062},"what-is-vulnerability-management","What is Vulnerability Management?",[37,10065,10066],{},"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.",[50,10068,10070],{"id":10069},"what-is-the-vulnerability-management-lifecycle","What is the vulnerability management lifecycle?",[37,10072,10073],{},"An effective program follows a repeating cycle:",[510,10075,10076,10082,10088,10093,10099,10105],{},[97,10077,10078,10081],{},[58,10079,10080],{},"Asset discovery"," — maintain an accurate inventory of all hardware, software, and cloud resources in scope",[97,10083,10084,10087],{},[58,10085,10086],{},"Vulnerability scanning"," — use automated tools to detect known vulnerabilities across your environment on a regular schedule",[97,10089,10090,10092],{},[58,10091,5629],{}," — rank findings by severity (CVSS score), exploitability, asset criticality, and business context — not every \"critical\" CVE is critical to your organization",[97,10094,10095,10098],{},[58,10096,10097],{},"Remediation"," — apply patches, configuration changes, or compensating controls to address vulnerabilities within defined SLAs",[97,10100,10101,10104],{},[58,10102,10103],{},"Verification"," — rescan to confirm that remediation was effective and didn't introduce new issues",[97,10106,10107,10109],{},[58,10108,8290],{}," — track metrics like mean time to remediate (MTTR), vulnerability aging, and coverage rates",[50,10111,10113],{"id":10112},"how-do-compliance-frameworks-address-vulnerability-management","How do compliance frameworks address vulnerability management?",[37,10115,10116],{},"Most security frameworks require a formal vulnerability management program:",[94,10118,10119,10124,10129,10134,10139],{},[97,10120,10121,10123],{},[58,10122,1223],{}," — Requirement 6.3 requires patching critical vulnerabilities within defined timeframes; Requirement 11.3 requires internal and external vulnerability scanning",[97,10125,10126,10128],{},[58,10127,128],{}," — CC7.1 covers detection of vulnerabilities and CC8.1 addresses change management for remediation",[97,10130,10131,10133],{},[58,10132,378],{}," — A.8.8 (management of technical vulnerabilities) requires timely identification and remediation of vulnerabilities",[97,10135,10136,10138],{},[58,10137,633],{}," — ID.RA (risk assessment) and PR.IP (information protection) directly relate to vulnerability identification and remediation",[97,10140,10141,10143],{},[58,10142,386],{}," — RA.L2-3.11.2 requires remediation of vulnerabilities in accordance with risk assessments",[50,10145,10147],{"id":10146},"what-are-common-vulnerability-scanning-tools","What are common vulnerability scanning tools?",[94,10149,10150,10156,10162,10168],{},[97,10151,10152,10155],{},[58,10153,10154],{},"Infrastructure scanners"," — Nessus, Qualys, Rapid7 InsightVM for network and host-level vulnerabilities",[97,10157,10158,10161],{},[58,10159,10160],{},"Application scanners"," — OWASP ZAP, Burp Suite for web application vulnerabilities",[97,10163,10164,10167],{},[58,10165,10166],{},"Dependency scanners"," — Snyk, Dependabot, Trivy for software composition analysis (SCA)",[97,10169,10170,10173],{},[58,10171,10172],{},"Cloud security posture"," — AWS Inspector, Azure Defender, GCP Security Command Center for cloud misconfigurations",[50,10175,10177],{"id":10176},"what-are-sla-best-practices-for-vulnerability-management","What are SLA best practices for vulnerability management?",[37,10179,10180],{},"Define remediation timelines based on severity:",[94,10182,10183,10189,10195,10201],{},[97,10184,10185,10188],{},[58,10186,10187],{},"Critical"," — remediate within 24–72 hours",[97,10190,10191,10194],{},[58,10192,10193],{},"High"," — remediate within 7–14 days",[97,10196,10197,10200],{},[58,10198,10199],{},"Medium"," — remediate within 30 days",[97,10202,10203,10206],{},[58,10204,10205],{},"Low"," — remediate within 90 days or accept risk with documented justification",[50,10208,10210],{"id":10209},"how-does-episki-help-with-vulnerability-management","How does episki help with vulnerability management?",[37,10212,10213,10214,167],{},"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 ",[41,10215,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":10217},[10218],{"id":10062,"depth":562,"text":10063,"children":10219},[10220,10221,10222,10223,10224],{"id":10069,"depth":567,"text":10070},{"id":10112,"depth":567,"text":10113},{"id":10146,"depth":567,"text":10147},{"id":10176,"depth":567,"text":10177},{"id":10209,"depth":567,"text":10210},{},"\u002Fglossary\u002Fvulnerability-management",[3177,3178,4939,652,4938],[6296,5462,955,10229],"web-application-security",{"title":10231,"description":10232},"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",{"id":10237,"title":10238,"body":10239,"description":561,"extension":597,"lastUpdated":952,"meta":10362,"navigation":634,"path":10363,"relatedFrameworks":10364,"relatedTerms":10365,"seo":10366,"slug":10229,"stem":10369,"term":10244,"__hash__":10370},"glossary\u002F8.glossary\u002Fweb-application-security.md","Web Application Security",{"type":29,"value":10240,"toc":10354},[10241,10245,10248,10252,10255,10293,10297,10319,10323,10345,10349],[32,10242,10244],{"id":10243},"what-is-web-application-security","What is Web Application Security?",[37,10246,10247],{},"Web application security is the practice of protecting websites and web applications from attacks that exploit vulnerabilities in application code, configuration, or infrastructure. As organizations increasingly deliver services through web applications, securing these applications has become a critical component of any compliance program.",[50,10249,10251],{"id":10250},"what-are-common-web-application-threats","What are common web application threats?",[37,10253,10254],{},"The OWASP Top 10 provides a widely recognized list of the most critical web application security risks:",[94,10256,10257,10263,10269,10275,10281,10287],{},[97,10258,10259,10262],{},[58,10260,10261],{},"Injection attacks"," — including SQL injection, where attackers insert malicious code through input fields to manipulate databases",[97,10264,10265,10268],{},[58,10266,10267],{},"Cross-site scripting (XSS)"," — injecting malicious scripts into web pages viewed by other users",[97,10270,10271,10274],{},[58,10272,10273],{},"Broken authentication"," — weaknesses in authentication mechanisms that allow unauthorized access",[97,10276,10277,10280],{},[58,10278,10279],{},"Insecure direct object references"," — exposing internal implementation objects through URLs or parameters",[97,10282,10283,10286],{},[58,10284,10285],{},"Security misconfiguration"," — default credentials, unnecessary features enabled, or missing security headers",[97,10288,10289,10292],{},[58,10290,10291],{},"Cross-site request forgery (CSRF)"," — tricking authenticated users into performing unintended actions",[50,10294,10296],{"id":10295},"how-do-compliance-frameworks-address-web-application-security","How do compliance frameworks address web application security?",[94,10298,10299,10304,10309,10314],{},[97,10300,10301,10303],{},[58,10302,1223],{}," — Requirement 6 addresses secure development practices and web application firewalls for applications handling cardholder data",[97,10305,10306,10308],{},[58,10307,128],{}," — CC7.1 and CC8.1 cover vulnerability management and change management for applications",[97,10310,10311,10313],{},[58,10312,378],{}," — A.8.25 through A.8.28 address secure development lifecycle, testing, and application security",[97,10315,10316,10318],{},[58,10317,633],{}," — PR.IP covers security in development and information protection processes",[50,10320,10322],{"id":10321},"what-are-web-application-defense-strategies","What are web application defense strategies?",[94,10324,10325,10328,10331,10334,10339,10342],{},[97,10326,10327],{},"Implement a secure development lifecycle (SDLC) with security reviews at each stage",[97,10329,10330],{},"Use static application security testing (SAST) and dynamic application security testing (DAST) in CI\u002FCD pipelines",[97,10332,10333],{},"Deploy a web application firewall (WAF) to filter malicious traffic",[97,10335,7911,10336,10338],{},[41,10337,6273],{"href":6272}," focused on application-layer vulnerabilities",[97,10340,10341],{},"Keep application frameworks and dependencies patched and up to date",[97,10343,10344],{},"Validate and sanitize all user input on the server side",[50,10346,10348],{"id":10347},"how-does-episki-help-with-web-application-security","How does episki help with web application security?",[37,10350,10351,10352,167],{},"episki tracks web application security controls, manages vulnerability remediation workflows, and documents security testing evidence for auditors. Learn more on our ",[41,10353,4920],{"href":4919},{"title":561,"searchDepth":562,"depth":562,"links":10355},[10356],{"id":10243,"depth":562,"text":10244,"children":10357},[10358,10359,10360,10361],{"id":10250,"depth":567,"text":10251},{"id":10295,"depth":567,"text":10296},{"id":10321,"depth":567,"text":10322},{"id":10347,"depth":567,"text":10348},{},"\u002Fglossary\u002Fweb-application-security",[3177,3178,4939,652],[6296,6300,3468,10233],{"title":10367,"description":10368},"What is Web Application Security? Definition & Compliance Guide","Web application security is the practice of protecting websites and web apps from attacks such as SQL injection, cross-site scripting (XSS), and unauthorized access.","8.glossary\u002Fweb-application-security","qOQ02_z-vhAF1v25Yq_MRSjVS7VEGJjSiQUC3OPdzkc",[10372,10875,11451,11943,12318,12828],{"id":10373,"title":10374,"advantages":10375,"body":10397,"checklist":10806,"cta":10815,"description":561,"extension":597,"faq":10818,"hero":10836,"lastUpdated":631,"meta":10845,"name":386,"navigation":634,"path":10846,"resources":10847,"seo":10860,"slug":4938,"stats":10863,"stem":10873,"__hash__":10874},"frameworks\u002F5.frameworks\u002Fcmmc.md","Cmmc",[10376,10383,10390],{"title":10377,"description":10378,"bullets":10379},"NIST 800-171 control mapping","Every CMMC Level 2 practice is linked to its NIST SP 800-171 source requirement with pre-written narratives.",[10380,10381,10382],"14 control families mapped to 110 security requirements","AI-drafted implementation narratives and testing procedures","Gap analysis highlights missing controls before your assessment",{"title":10384,"description":10385,"bullets":10386},"Assessment preparation workspace","Whether you self-assess or engage a C3PAO, episki organizes evidence and scoring in one place.",[10387,10388,10389],"POA&M tracking with 180-day close-out reminders","Scoring methodology aligned to DoD assessment guide","Assessor portal with scoped read-only access",{"title":10391,"description":10392,"bullets":10393},"Cross-framework reuse","Controls mapped to CMMC automatically satisfy overlapping NIST CSF, ISO 27001, and FedRAMP requirements.",[10394,10395,10396],"Unified control graph eliminates duplicate documentation","Evidence collected once, reused across every framework","Framework coverage dashboard shows gaps at a glance",{"type":29,"value":10398,"toc":10789},[10399,10403,10406,10409,10413,10420,10431,10442,10446,10454,10486,10489,10493,10504,10514,10518,10521,10538,10551,10554,10558,10561,10572,10579,10583,10597,10600,10604,10612,10638,10642,10669,10673,10681,10685,10693,10697,10705,10709,10712,10750,10754,10786],[32,10400,10402],{"id":10401},"what-is-cmmc","What is CMMC?",[37,10404,10405],{},"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,10407,10408],{},"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.",[50,10410,10412],{"id":10411},"cmmc-10-to-cmmc-20","CMMC 1.0 to CMMC 2.0",[37,10414,10415,10416,10419],{},"The first version of CMMC — sometimes called CMMC 1.0 — was announced in January 2020. It had ",[58,10417,10418],{},"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,10421,10422,10423,10426,10427,10430],{},"In November 2021 the DoD announced ",[58,10424,10425],{},"CMMC 2.0",", a streamlined successor. CMMC 2.0 collapsed the five levels into ",[58,10428,10429],{},"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,10432,10433,10434,10437,10438,10441],{},"The CMMC 2.0 program rule (32 CFR Part 170) was published in the Federal Register on October 15, 2024, and took effect on ",[58,10435,10436],{},"December 16, 2024",". The companion DFARS rule (48 CFR) was published on September 10, 2025, and took effect on ",[58,10439,10440],{},"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.",[50,10443,10445],{"id":10444},"the-three-cmmc-levels","The three CMMC levels",[37,10447,10448,10449,10453],{},"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. ",[41,10450,10452],{"href":10451},"\u002Fframeworks\u002Fcmmc\u002Flevels","See the full breakdown of CMMC levels"," for control counts, assessment types, and scoping rules.",[94,10455,10456,10466,10476],{},[97,10457,10458,10461,10462,10465],{},[58,10459,10460],{},"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 ",[58,10463,10464],{},"annual self-assessment"," with a senior official affirming the results in the Supplier Performance Risk System (SPRS).",[97,10467,10468,10471,10472,10475],{},[58,10469,10470],{},"Level 2 — Advanced."," Protects Controlled Unclassified Information (CUI). It requires all ",[58,10473,10474],{},"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.",[97,10477,10478,10481,10482,10485],{},[58,10479,10480],{},"Level 3 — Expert."," Reserved for the most sensitive DoD programs where advanced persistent threats are a credible risk. It includes every Level 2 requirement ",[58,10483,10484],{},"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,10487,10488],{},"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.",[50,10490,10492],{"id":10491},"nist-sp-800-171-is-the-heart-of-cmmc","NIST SP 800-171 is the heart of CMMC",[37,10494,10495,10496,10499,10500,10503],{},"CMMC Level 2 is a ",[58,10497,10498],{},"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 ",[41,10501,10502],{"href":43},"NIST"," SP 800-171 compliance since 2017 did not have to start over.",[37,10505,10506,10507,10510,10511,10513],{},"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. ",[41,10508,10509],{"href":385},"See the detailed NIST SP 800-171 mapping"," for the full control family breakdown and cross-framework overlap with ",[41,10512,633],{"href":635}," and ISO 27001.",[50,10515,10517],{"id":10516},"who-needs-cmmc","Who needs CMMC?",[37,10519,10520],{},"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:",[94,10522,10523,10526,10529,10532,10535],{},[97,10524,10525],{},"Prime contractors holding contracts directly with the DoD",[97,10527,10528],{},"Subcontractors at every tier in the supply chain",[97,10530,10531],{},"Cloud service providers hosting DoD contractor data",[97,10533,10534],{},"Managed service providers and IT vendors with access to FCI or CUI",[97,10536,10537],{},"Foreign suppliers in the defense industrial base handling covered information",[37,10539,10540,10541,10545,10546,10550],{},"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. ",[41,10542,10544],{"href":10543},"\u002Fframeworks\u002Fcmmc\u002Fwho-needs-cmmc","See who needs CMMC"," for detailed scoping guidance, and our ",[41,10547,10549],{"href":10548},"\u002Findustry\u002Fgovernment","government industry page"," for broader public-sector compliance context.",[37,10552,10553],{},"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.",[50,10555,10557],{"id":10556},"the-cmmc-assessment-process","The CMMC assessment process",[37,10559,10560],{},"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,10562,10563,10564,10567,10568,10571],{},"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 ",[58,10565,10566],{},"88 or above"," with remaining gaps documented in a Plan of Action and Milestones (POA&M) yields a ",[58,10569,10570],{},"conditional"," certification with a 180-day remediation window. A score below 88 yields no certification at all.",[37,10573,10574,10578],{},[41,10575,10577],{"href":10576},"\u002Fframeworks\u002Fcmmc\u002Fassessment-process","See the full CMMC assessment process"," for scoring details, POA&M rules, and what you can and cannot defer.",[50,10580,10582],{"id":10581},"c3paos-and-certified-assessors","C3PAOs and certified assessors",[37,10584,10585,10586,10589,10590,336,10593,10596],{},"Third-party CMMC assessments are conducted by ",[58,10587,10588],{},"CMMC Third-Party Assessment Organizations (C3PAOs)"," accredited by the Cyber AB (the Cyber Accreditation Body, formerly the CMMC Accreditation Body). C3PAOs employ ",[58,10591,10592],{},"Certified CMMC Assessors (CCAs)",[58,10594,10595],{},"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,10598,10599],{},"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.",[50,10601,10603],{"id":10602},"cmmc-implementation-timeline","CMMC implementation timeline",[37,10605,10606,10607,10611],{},"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. ",[41,10608,10610],{"href":10609},"\u002Fframeworks\u002Fcmmc\u002Fimplementation-timeline","See the full CMMC implementation timeline"," for dates and milestones.",[94,10613,10614,10620,10626,10632],{},[97,10615,10616,10619],{},[58,10617,10618],{},"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.",[97,10621,10622,10625],{},[58,10623,10624],{},"Phase 2 (November 2026 – November 2027)."," CMMC Level 2 C3PAO certification requirements expand significantly. Level 3 requirements begin appearing in select solicitations.",[97,10627,10628,10631],{},[58,10629,10630],{},"Phase 3 (November 2027 – November 2028)."," CMMC Level 2 and Level 3 requirements appear broadly across applicable DoD contracts.",[97,10633,10634,10637],{},[58,10635,10636],{},"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.",[50,10639,10641],{"id":10640},"cmmc-and-dfars","CMMC and DFARS",[37,10643,10644,10645,10648,10649,336,10652,10655,10656,10659,10660,10664,10665,167],{},"CMMC is the certification. DFARS is the contractual mechanism that makes the certification binding. ",[58,10646,10647],{},"DFARS 252.204-7012"," has required safeguarding of covered defense information and rapid incident reporting since 2017. ",[58,10650,10651],{},"DFARS 252.204-7019",[58,10653,10654],{},"-7020"," added the requirement to post NIST SP 800-171 assessment scores to SPRS. ",[58,10657,10658],{},"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. ",[41,10661,10663],{"href":10662},"\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 ",[41,10666,10668],{"href":10667},"\u002Fnow\u002Fcompliance-framework-comparison","compliance framework comparison",[50,10670,10672],{"id":10671},"self-assessment-vs-third-party-assessment","Self-assessment vs third-party assessment",[37,10674,10675,10676,10680],{},"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. ",[41,10677,10679],{"href":10678},"\u002Fframeworks\u002Fcmmc\u002Fself-assessment-vs-third-party","Compare CMMC self-assessment vs third-party"," to decide which applies to you and how to budget.",[50,10682,10684],{"id":10683},"handling-cui-the-cmmc-way","Handling CUI the CMMC way",[37,10686,10687,10688,10692],{},"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. ",[41,10689,10691],{"href":10690},"\u002Fframeworks\u002Fcmmc\u002Fcui-handling","See CUI handling under CMMC"," for marking rules, scoping guidance, and common mistakes.",[50,10694,10696],{"id":10695},"subcontractor-requirements","Subcontractor requirements",[37,10698,10699,10700,10704],{},"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. ",[41,10701,10703],{"href":10702},"\u002Fframeworks\u002Fcmmc\u002Fsubcontractor-requirements","See CMMC subcontractor requirements"," for the full flow-down model and how to reduce the burden.",[50,10706,10708],{"id":10707},"getting-cmmc-ready","Getting CMMC ready",[37,10710,10711],{},"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:",[510,10713,10714,10720,10726,10732,10738,10744],{},[97,10715,10716,10719],{},[58,10717,10718],{},"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.",[97,10721,10722,10725],{},[58,10723,10724],{},"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.",[97,10727,10728,10731],{},[58,10729,10730],{},"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.",[97,10733,10734,10737],{},[58,10735,10736],{},"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.",[97,10739,10740,10743],{},[58,10741,10742],{},"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.",[97,10745,10746,10749],{},[58,10747,10748],{},"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.",[50,10751,10753],{"id":10752},"common-cmmc-challenges","Common CMMC challenges",[94,10755,10756,10762,10768,10774,10780],{},[97,10757,10758,10761],{},[58,10759,10760],{},"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.",[97,10763,10764,10767],{},[58,10765,10766],{},"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.",[97,10769,10770,10773],{},[58,10771,10772],{},"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.",[97,10775,10776,10779],{},[58,10777,10778],{},"Subcontractor flow-down."," Primes must verify subcontractor CMMC status continuously, not once at onboarding.",[97,10781,10782,10785],{},[58,10783,10784],{},"Evidence organization."," A CMMC assessment can touch hundreds of evidence artifacts. Without a single source of truth, assessors burn billable hours chasing documents.",[37,10787,10788],{},"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":561,"searchDepth":562,"depth":562,"links":10790},[10791],{"id":10401,"depth":562,"text":10402,"children":10792},[10793,10794,10795,10796,10797,10798,10799,10800,10801,10802,10803,10804,10805],{"id":10411,"depth":567,"text":10412},{"id":10444,"depth":567,"text":10445},{"id":10491,"depth":567,"text":10492},{"id":10516,"depth":567,"text":10517},{"id":10556,"depth":567,"text":10557},{"id":10581,"depth":567,"text":10582},{"id":10602,"depth":567,"text":10603},{"id":10640,"depth":567,"text":10641},{"id":10671,"depth":567,"text":10672},{"id":10683,"depth":567,"text":10684},{"id":10695,"depth":567,"text":10696},{"id":10707,"depth":567,"text":10708},{"id":10752,"depth":567,"text":10753},{"title":10807,"description":10808,"items":10809},"CMMC readiness checklist inside episki","Everything is preloaded in your free trial so you can start scoping your assessment and closing gaps immediately.",[10810,10811,10812,10813,10814],"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":10816,"description":10817},"Launch your CMMC workspace today","Import your NIST 800-171 controls, map them to CMMC levels, and start closing gaps before your next assessment.",{"title":10819,"items":10820},"CMMC frequently asked questions",[10821,10824,10827,10830,10833],{"label":10822,"content":10823},"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":10825,"content":10826},"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":10828,"content":10829},"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":10831,"content":10832},"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":10834,"content":10835},"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":10837,"title":10838,"description":10839,"links":10840},"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.",[10841,10843],{"label":10842,"icon":622,"to":623},"Start CMMC trial",{"label":625,"icon":10844,"color":627,"variant":628,"to":629,"target":630},"i-lucide-message-circle",{},"\u002Fframeworks\u002Fcmmc",{"headline":10848,"title":10848,"description":10849,"items":10850},"CMMC acceleration resources","Give leadership and contracting officers visibility into your cybersecurity posture at every stage.",[10851,10854,10857],{"title":10852,"description":10853},"Executive scorecard","Translate control work into CMMC readiness percentages and contract eligibility status.",{"title":10855,"description":10856},"Assessment readiness kit","Pre-assessment checklist, evidence package review, and mock scoring aligned to DIBCAC methodology.",{"title":10858,"description":10859},"Subcontractor flow-down tracker","Monitor which subcontractors need their own CMMC certification and track their progress.",{"title":10861,"description":10862},"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.",[10864,10867,10870],{"value":10865,"description":10866},"3 maturity levels","Pre-mapped practices for Level 1, Level 2, and Level 3 with assessment-type guidance for each.",{"value":10868,"description":10869},"110 practices","Full NIST SP 800-171 Rev 2 control set mapped to CMMC Level 2 objectives out of the box.",{"value":10871,"description":10872},"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",{"id":10876,"title":10877,"advantages":10878,"body":10900,"checklist":11384,"cta":11393,"description":561,"extension":597,"faq":11396,"hero":11414,"lastUpdated":631,"meta":11422,"name":4568,"navigation":634,"path":4567,"resources":11423,"seo":11436,"slug":3179,"stats":11439,"stem":11449,"__hash__":11450},"frameworks\u002F5.frameworks\u002Fhipaa.md","Hipaa",[10879,10886,10893],{"title":10880,"description":10881,"bullets":10882},"Safeguards mapped to your stack","Every HIPAA standard comes with plain-language owners, SLAs, and tests.",[10883,10884,10885],"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":10887,"description":10888,"bullets":10889},"PHI-aware evidence locker","Secure uploads, access controls, and audit trails keep regulators satisfied.",[10890,10891,10892],"Granular permissions for internal and external reviewers","Automated retention and deletion policies","Download tracking and access audit trails",{"title":10894,"description":10895,"bullets":10896},"Vendor & incident workflows","Track BAAs, vendor attestations, and incidents from discovery to closure.",[10897,10898,10899],"BAA repository tied to vendor risk levels","Incident response runbooks with reminders","Post-incident reports aligned to HIPAA timelines",{"type":29,"value":10901,"toc":11357},[10902,10906,10909,10920,10923,10927,10930,10973,10977,10980,10985,10989,10992,10996,11003,11023,11026,11030,11037,11044,11048,11051,11055,11058,11061,11074,11078,11081,11084,11088,11106,11110,11122,11126,11129,11134,11138,11141,11144,11151,11155,11162,11165,11169,11176,11179,11202,11206,11209,11212,11218,11222,11225,11251,11254,11257,11261,11264,11282,11285,11289,11295,11299,11302,11331,11339,11343,11346,11354],[32,10903,10905],{"id":10904},"what-is-hipaa","What is HIPAA?",[37,10907,10908],{},"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,10910,10911,10912,10915,10916,10919],{},"At its core, the law establishes national standards that protect sensitive patient information — known as ",[41,10913,10914],{"href":9775},"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 ",[41,10917,10918],{"href":7293},"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,10921,10922],{},"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,10924,10926],{"id":10925},"a-brief-history-of-hipaa","A brief history of HIPAA",[37,10928,10929],{},"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.",[94,10931,10932,10938,10944,10950,10961,10967],{},[97,10933,10934,10937],{},[58,10935,10936],{},"1996"," — Congress passes HIPAA, directing HHS to issue regulations on privacy, security, and electronic transactions.",[97,10939,10940,10943],{},[58,10941,10942],{},"2000"," — The HIPAA Privacy Rule is published; it takes full effect in 2003.",[97,10945,10946,10949],{},[58,10947,10948],{},"2003"," — The HIPAA Security Rule is finalized, with compliance required by 2005 for most entities.",[97,10951,10952,10955,10956,10960],{},[58,10953,10954],{},"2009"," — The Health Information Technology for Economic and Clinical Health Act (",[41,10957,10959],{"href":10958},"\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.",[97,10962,10963,10966],{},[58,10964,10965],{},"2013"," — The HIPAA Omnibus Rule implements HITECH and further strengthens HIPAA enforcement, fines, and patient rights.",[97,10968,10969,10972],{},[58,10970,10971],{},"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.",[50,10974,10976],{"id":10975},"hitech-and-the-omnibus-rule","HITECH and the Omnibus Rule",[37,10978,10979],{},"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,10981,10982,10983,167],{},"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 ",[41,10984,10976],{"href":10958},[32,10986,10988],{"id":10987},"who-hipaa-applies-to","Who HIPAA applies to",[37,10990,10991],{},"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.",[50,10993,10995],{"id":10994},"covered-entities","Covered entities",[37,10997,290,10998,11002],{},[41,10999,11001],{"href":11000},"\u002Fglossary\u002Fcovered-entity","covered entity"," is any of the following:",[94,11004,11005,11011,11017],{},[97,11006,11007,11010],{},[58,11008,11009],{},"Health plans"," — health insurance companies, HMOs, employer-sponsored group health plans, government programs like Medicare and Medicaid, and long-term care insurers.",[97,11012,11013,11016],{},[58,11014,11015],{},"Healthcare providers"," — hospitals, clinics, physician practices, dentists, pharmacies, psychologists, and any other provider that transmits health information electronically for billing or eligibility purposes.",[97,11018,11019,11022],{},[58,11020,11021],{},"Healthcare clearinghouses"," — entities that process nonstandard health information into standard formats (or vice versa), such as billing services and repricing companies.",[37,11024,11025],{},"If your organization directly delivers healthcare or finances it, you are almost certainly a covered entity.",[50,11027,11029],{"id":11028},"business-associates","Business associates",[37,11031,290,11032,11036],{},[41,11033,11035],{"href":11034},"\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,11038,11039,11040,11043],{},"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 ",[41,11041,11042],{"href":9780},"business associate agreement"," with every upstream and downstream partner that touches PHI is non-negotiable.",[50,11045,11047],{"id":11046},"who-is-not-covered-by-hipaa","Who is not covered by HIPAA?",[37,11049,11050],{},"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,11052,11054],{"id":11053},"the-hipaa-privacy-rule","The HIPAA Privacy Rule",[37,11056,11057],{},"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,11059,11060],{},"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,11062,11063,11064,11068,11069,11073],{},"For a comprehensive walkthrough of the HIPAA Privacy Rule, permitted disclosures, and patient rights, read the dedicated ",[41,11065,11067],{"href":11066},"\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 ",[41,11070,11072],{"href":11071},"\u002Fframeworks\u002Fhipaa\u002Fminimum-necessary-rule","minimum necessary rule"," page.",[32,11075,11077],{"id":11076},"the-hipaa-security-rule","The HIPAA Security Rule",[37,11079,11080],{},"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,11082,11083],{},"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.",[50,11085,11087],{"id":11086},"administrative-safeguards","Administrative safeguards",[37,11089,11090,11091,11095,11096,11100,11101,11105],{},"Administrative safeguards are the policies, procedures, and organizational measures that govern your HIPAA program. They include security management processes, a designated security official, ",[41,11092,11094],{"href":11093},"\u002Fframeworks\u002Fhipaa\u002Fworkforce-training","workforce training",", a ",[41,11097,11099],{"href":11098},"\u002Fframeworks\u002Fhipaa\u002Fsanctions-policy","sanctions policy"," for workforce violations, access management, ",[41,11102,11104],{"href":11103},"\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.",[50,11107,11109],{"id":11108},"physical-safeguards","Physical safeguards",[37,11111,11112,11113,374,11117,11121],{},"Physical safeguards protect the facilities, workstations, devices, and media that house ePHI. This category covers ",[41,11114,11116],{"href":11115},"\u002Fframeworks\u002Fhipaa\u002Ffacility-access-controls","facility access controls",[41,11118,11120],{"href":11119},"\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.",[50,11123,11125],{"id":11124},"technical-safeguards","Technical safeguards",[37,11127,11128],{},"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,11130,11131,11132,142],{},"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 ",[41,11133,4234],{"href":4572},[32,11135,11137],{"id":11136},"the-hipaa-breach-notification-rule","The HIPAA Breach Notification Rule",[37,11139,11140],{},"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,11142,11143],{},"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,11145,11146,11147,142],{},"For full details on timelines, content requirements, and documentation expectations, see the ",[41,11148,11150],{"href":11149},"\u002Fframeworks\u002Fhipaa\u002Fbreach-notification","HIPAA Breach Notification Rule",[32,11152,11154],{"id":11153},"business-associate-agreements","Business associate agreements",[37,11156,11157,11158,11161],{},"No PHI should ever leave a covered entity — or a business associate — without a properly executed BAA in place. A ",[41,11159,11042],{"href":11160},"\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,11163,11164],{},"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,11166,11168],{"id":11167},"hipaa-compliance-checklist","HIPAA compliance checklist",[37,11170,11171,11172,11175],{},"Translating the regulatory language into day-to-day operations is where most programs struggle. The ",[41,11173,11168],{"href":11174},"\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,11177,11178],{},"At a high level, a complete HIPAA program includes:",[94,11180,11181,11184,11187,11190,11193,11196,11199],{},[97,11182,11183],{},"A current risk analysis and documented risk management plan.",[97,11185,11186],{},"Written policies and procedures covering Privacy, Security, and Breach Notification obligations.",[97,11188,11189],{},"A signed BAA with every vendor, subcontractor, and customer that exchanges PHI.",[97,11191,11192],{},"Workforce training at hire and at least annually thereafter, with documented completion.",[97,11194,11195],{},"Access control, audit logging, encryption, and contingency planning for every system that touches ePHI.",[97,11197,11198],{},"An incident response runbook aligned to the Breach Notification Rule.",[97,11200,11201],{},"Documentation retained for at least six years from creation or last effective date, whichever is later.",[32,11203,11205],{"id":11204},"hipaa-risk-analysis","HIPAA risk analysis",[37,11207,11208],{},"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,11210,11211],{},"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,11213,11214,11215,142],{},"For a full breakdown of methodology, documentation requirements, and common pitfalls, read the ",[41,11216,11205],{"href":11217},"\u002Fframeworks\u002Fhipaa\u002Frisk-analysis",[32,11219,11221],{"id":11220},"penalties-and-enforcement","Penalties and enforcement",[37,11223,11224],{},"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.",[94,11226,11227,11233,11239,11245],{},[97,11228,11229,11232],{},[58,11230,11231],{},"Tier 1 — Unknowing violation"," — $100 to $50,000 per violation; annual cap $25,000 for identical violations.",[97,11234,11235,11238],{},[58,11236,11237],{},"Tier 2 — Reasonable cause"," — $1,000 to $50,000 per violation; annual cap $100,000.",[97,11240,11241,11244],{},[58,11242,11243],{},"Tier 3 — Willful neglect, corrected"," — $10,000 to $50,000 per violation; annual cap $250,000.",[97,11246,11247,11250],{},[58,11248,11249],{},"Tier 4 — Willful neglect, uncorrected"," — $50,000 per violation; annual cap $1.5 million per violation category.",[37,11252,11253],{},"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,11255,11256],{},"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,11258,11260],{"id":11259},"hipaa-vs-hitech-vs-hitrust","HIPAA vs HITECH vs HITRUST",[37,11262,11263],{},"These three acronyms sit close together in healthcare conversations and are often conflated. They are related but distinct.",[94,11265,11266,11271,11276],{},[97,11267,11268,11270],{},[58,11269,4568],{}," is the underlying federal law and its implementing regulations (Privacy, Security, Breach Notification, and Enforcement Rules). HIPAA defines the legal obligations.",[97,11272,11273,11275],{},[58,11274,10959],{}," 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.",[97,11277,11278,11281],{},[58,11279,11280],{},"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,11283,11284],{},"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.",[50,11286,11288],{"id":11287},"hipaa-and-soc-2","HIPAA and SOC 2",[37,11290,11291,11292,11294],{},"Many SaaS companies pursue ",[41,11293,128],{"href":127}," 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,11296,11298],{"id":11297},"getting-hipaa-compliant","Getting HIPAA compliant",[37,11300,11301],{},"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.",[510,11303,11304,11307,11310,11313,11316,11319,11322,11325,11328],{},[97,11305,11306],{},"Confirm your status as a covered entity, business associate, or both, and inventory the PHI you handle today.",[97,11308,11309],{},"Appoint a security official and a privacy official (the same person may hold both roles at small companies).",[97,11311,11312],{},"Conduct a risk analysis scoped to every system that creates, receives, maintains, or transmits ePHI.",[97,11314,11315],{},"Implement the administrative, physical, and technical safeguards required by the Security Rule, informed by your risk analysis.",[97,11317,11318],{},"Draft and publish policies and procedures covering Privacy, Security, and Breach Notification obligations.",[97,11320,11321],{},"Execute BAAs with every vendor that touches PHI, and require a signed BAA before onboarding any new customer that qualifies as a covered entity.",[97,11323,11324],{},"Deliver workforce training at hire and annually thereafter, and document completion.",[97,11326,11327],{},"Stand up an incident response runbook aligned to the Breach Notification Rule.",[97,11329,11330],{},"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,11332,11333,11334,11338],{},"For companies operating in the broader ",[41,11335,11337],{"href":11336},"\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,11340,11342],{"id":11341},"how-episki-helps-with-hipaa-compliance","How episki helps with HIPAA compliance",[37,11344,11345],{},"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,11347,11348,11349,11353],{},"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 ",[41,11350,11352],{"href":11351},"\u002Fnow\u002Fhipaa-compliance-healthtech","HIPAA for healthtech"," playbook for a closer look at how modern SaaS companies operate HIPAA at startup speed.",[37,11355,11356],{},"Ready to tighten your HIPAA program? Start a free trial or book a demo from the top of this page.",{"title":561,"searchDepth":562,"depth":562,"links":11358},[11359,11360,11363,11368,11369,11374,11375,11376,11377,11378,11379,11382,11383],{"id":10904,"depth":562,"text":10905},{"id":10925,"depth":562,"text":10926,"children":11361},[11362],{"id":10975,"depth":567,"text":10976},{"id":10987,"depth":562,"text":10988,"children":11364},[11365,11366,11367],{"id":10994,"depth":567,"text":10995},{"id":11028,"depth":567,"text":11029},{"id":11046,"depth":567,"text":11047},{"id":11053,"depth":562,"text":11054},{"id":11076,"depth":562,"text":11077,"children":11370},[11371,11372,11373],{"id":11086,"depth":567,"text":11087},{"id":11108,"depth":567,"text":11109},{"id":11124,"depth":567,"text":11125},{"id":11136,"depth":562,"text":11137},{"id":11153,"depth":562,"text":11154},{"id":11167,"depth":562,"text":11168},{"id":11204,"depth":562,"text":11205},{"id":11220,"depth":562,"text":11221},{"id":11259,"depth":562,"text":11260,"children":11380},[11381],{"id":11287,"depth":567,"text":11288},{"id":11297,"depth":562,"text":11298},{"id":11341,"depth":562,"text":11342},{"title":11385,"description":11386,"items":11387},"HIPAA launch kit","Guided steps keep privacy, security, and ops in sync from day one.",[11388,11389,11390,11391,11392],"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":11394,"description":11395},"Launch HIPAA monitoring in minutes","Kick off the free trial and invite stakeholders before your next diligence call.",{"title":11397,"items":11398},"HIPAA compliance frequently asked questions",[11399,11402,11405,11408,11411],{"label":11400,"content":11401},"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":11403,"content":11404},"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":11406,"content":11407},"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":11409,"content":11410},"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":11412,"content":11413},"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":11415,"title":11416,"description":11417,"links":11418},"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.",[11419,11421],{"label":11420,"icon":622,"to":623},"Start HIPAA trial",{"label":625,"icon":10844,"color":627,"variant":628,"to":629,"target":630},{},{"headline":11424,"title":11424,"description":11425,"items":11426},"HIPAA enablement","Keep leadership, customers, and partners aligned.",[11427,11430,11433],{"title":11428,"description":11429},"Board-ready posture report","Shows maturity score, risk trends, and upcoming audits.",{"title":11431,"description":11432},"Customer FAQ pack","Answers the most common HIPAA diligence questions.",{"title":11434,"description":11435},"Ops automation guide","Explains how to plug security tasks into existing tools.",{"title":11437,"description":11438},"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.",[11440,11443,11446],{"value":11441,"description":11442},"30-day rollout","Average time to production monitoring across safeguards.",{"value":11444,"description":11445},"PHI-safe sharing","Role-based portals keep sensitive documents organized and protected.",{"value":11447,"description":11448},"24\u002F7 alerts","Continuous monitoring for access, logging, and vendor risks.","5.frameworks\u002Fhipaa","9IldK-wXldOkZs8WFGmDWXYF8To1wETqwKkhsGGUW04",{"id":11452,"title":11453,"advantages":11454,"body":11476,"checklist":11876,"cta":11887,"description":561,"extension":597,"faq":11890,"hero":11908,"lastUpdated":631,"meta":11916,"name":378,"navigation":634,"path":377,"resources":11917,"seo":11930,"slug":3178,"stats":11933,"stem":11941,"__hash__":11942},"frameworks\u002F5.frameworks\u002Fiso27001.md","Iso27001",[11455,11462,11469],{"title":11456,"description":11457,"bullets":11458},"Statement of Applicability in minutes","Generate and maintain your SoA directly from your control graph with justification notes for every inclusion and exclusion.",[11459,11460,11461],"Auto-populate applicability status from existing controls","Link each control to risk treatment decisions","Export auditor-ready SoA documents on demand",{"title":11463,"description":11464,"bullets":11465},"Risk-driven control management","Connect your risk register to Annex A controls so treatment plans and evidence stay aligned as threats evolve.",[11466,11467,11468],"Risk assessment templates following ISO 27005 guidance","Heat maps show residual risk by domain","Treatment plans tie directly to control tasks and owners",{"title":11470,"description":11471,"bullets":11472},"Surveillance audit confidence","Keep your ISMS current between certification cycles with continuous monitoring and internal audit workflows.",[11473,11474,11475],"Automated evidence refresh and expiration alerts","Internal audit scheduling with finding tracking","Management review templates with trend data",{"type":29,"value":11477,"toc":11858},[11478,11482,11492,11495,11498,11501,11505,11508,11511,11514,11518,11521,11534,11538,11541,11548,11551,11555,11562,11565,11573,11577,11584,11587,11595,11599,11602,11646,11654,11662,11666,11669,11672,11679,11683,11686,11689,11701,11705,11708,11716,11720,11723,11730,11734,11737,11763,11770,11774,11777,11785,11789,11792,11800,11804,11807,11827,11833,11837,11840,11852,11855],[32,11479,11481],{"id":11480},"what-is-iso-27001","What is ISO 27001?",[37,11483,11484,11486,11487,11491],{},[41,11485,378],{"href":9936}," 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 ",[41,11488,11490],{"href":11489},"\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,11493,11494],{},"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,11496,11497],{},"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,11499,11500],{},"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,11502,11504],{"id":11503},"why-iso-27001-matters","Why ISO 27001 matters",[37,11506,11507],{},"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,11509,11510],{},"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,11512,11513],{},"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,11515,11517],{"id":11516},"the-iso-27001-certification-process","The ISO 27001 certification process",[37,11519,11520],{},"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,11522,11523,11524,11528,11529,11533],{},"For a deep walkthrough of every phase of the journey, including timelines, auditor expectations, and common pitfalls, see the ",[41,11525,11527],{"href":11526},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification process guide",". If you are still evaluating whether to pursue ISO 27001 at all, the ",[41,11530,11532],{"href":11531},"\u002Fnow\u002Fiso27001-certification-guide","ISO 27001 certification guide"," covers the business case and sequencing decisions.",[32,11535,11537],{"id":11536},"iso-270012022-what-changed","ISO 27001:2022 — What changed",[37,11539,11540],{},"The 2022 revision is the current version of the standard. Two changes matter most for teams implementing ISO 27001 today.",[37,11542,11543,11544,11547],{},"First, the control set was restructured. The 2013 edition had 114 controls across 14 domains. ISO 27001:2022 consolidates these into ",[58,11545,11546],{},"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,11549,11550],{},"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,11552,11554],{"id":11553},"annex-a-controls","Annex A controls",[37,11556,11557,11558,11561],{},"Annex A of ISO 27001 is the reference control set. The ",[41,11559,11560],{"href":4558},"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,11563,11564],{},"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,11566,11567,11568,11572],{},"For a full breakdown of every theme, example controls in each, and how to prioritize implementation, see the ",[41,11569,11571],{"href":11570},"\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,11574,11576],{"id":11575},"statement-of-applicability-soa","Statement of Applicability (SoA)",[37,11578,159,11579,11583],{},[41,11580,11582],{"href":11581},"\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,11585,11586],{},"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,11588,11589,11590,11594],{},"See the dedicated guide on the ",[41,11591,11593],{"href":11592},"\u002Fframeworks\u002Fiso27001\u002Fstatement-of-applicability","ISO 27001 Statement of Applicability"," for format examples, justification patterns, and common SoA mistakes.",[32,11596,11598],{"id":11597},"building-your-isms","Building your ISMS",[37,11600,11601],{},"Implementing ISO 27001 is primarily an exercise in building a functioning ISMS. The standard walks through this in clauses 4 through 10:",[94,11603,11604,11610,11616,11622,11628,11634,11640],{},[97,11605,11606,11609],{},[58,11607,11608],{},"Clause 4 — Context of the organization."," Understand internal and external issues, interested parties, and define the ISMS scope.",[97,11611,11612,11615],{},[58,11613,11614],{},"Clause 5 — Leadership."," Top management must demonstrate commitment, approve the information security policy, and assign roles.",[97,11617,11618,11621],{},[58,11619,11620],{},"Clause 6 — Planning."," Identify risks and opportunities, set information security objectives, and plan how to achieve them.",[97,11623,11624,11627],{},[58,11625,11626],{},"Clause 7 — Support."," Provide resources, competence, awareness, communication, and documented information.",[97,11629,11630,11633],{},[58,11631,11632],{},"Clause 8 — Operation."," Execute the risk assessment and risk treatment process and operate the ISMS on an ongoing basis.",[97,11635,11636,11639],{},[58,11637,11638],{},"Clause 9 — Performance evaluation."," Monitor, measure, analyze, evaluate, conduct internal audits, and hold management reviews.",[97,11641,11642,11645],{},[58,11643,11644],{},"Clause 10 — Improvement."," Handle nonconformities and drive continual improvement.",[37,11647,11648,11649,11653],{},"Each clause has mandatory documented information and mandatory activities. The ",[41,11650,11652],{"href":11651},"\u002Fframeworks\u002Fiso27001\u002Fisms-implementation","ISO 27001 ISMS implementation guide"," breaks down exactly what to produce at each stage.",[37,11655,11656,11657,11661],{},"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 ",[41,11658,11660],{"href":11659},"\u002Fframeworks\u002Fiso27001\u002Fisms-scope","ISMS scope"," guide walks through how to draw the right boundaries for your business.",[32,11663,11665],{"id":11664},"iso-27001-risk-assessment","ISO 27001 risk assessment",[37,11667,11668],{},"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,11670,11671],{},"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,11673,11674,11675,167],{},"For methodology, risk register structure, treatment options, and residual risk handling, see the ",[41,11676,11678],{"href":11677},"\u002Fframeworks\u002Fiso27001\u002Frisk-assessment","ISO 27001 risk assessment guide",[32,11680,11682],{"id":11681},"internal-audits-and-management-review","Internal audits and management review",[37,11684,11685],{},"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,11687,11688],{},"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,11690,11691,11692,11696,11697,167],{},"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 ",[41,11693,11695],{"href":11694},"\u002Fframeworks\u002Fiso27001\u002Finternal-audit","internal audit guide"," and the ",[41,11698,11700],{"href":11699},"\u002Fframeworks\u002Fiso27001\u002Fmanagement-review","management review guide",[32,11702,11704],{"id":11703},"nonconformities-and-corrective-action","Nonconformities and corrective action",[37,11706,11707],{},"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,11709,11710,11711,11715],{},"Mature organizations treat nonconformities as valuable signals rather than failures. The ",[41,11712,11714],{"href":11713},"\u002Fframeworks\u002Fiso27001\u002Fnonconformity-and-corrective-action","nonconformity and corrective action"," guide walks through the full CAPA workflow auditors expect to see.",[32,11717,11719],{"id":11718},"continual-improvement","Continual improvement",[37,11721,11722],{},"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,11724,11725,11726,167],{},"Learn how to set ISMS metrics that auditors respect and leadership actually uses in the ",[41,11727,11729],{"href":11728},"\u002Fframeworks\u002Fiso27001\u002Fcontinual-improvement","continual improvement guide",[32,11731,11733],{"id":11732},"cost-and-timeline","Cost and timeline",[37,11735,11736],{},"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:",[94,11738,11739,11745,11751,11757],{},[97,11740,11741,11744],{},[58,11742,11743],{},"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.",[97,11746,11747,11750],{},[58,11748,11749],{},"External consulting (optional)."," Gap analysis and implementation support from a consultancy typically runs $20,000 to $100,000 depending on scope.",[97,11752,11753,11756],{},[58,11754,11755],{},"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.",[97,11758,11759,11762],{},[58,11760,11761],{},"Platform and tooling."," GRC platforms like episki typically replace $30,000 or more in spreadsheet-driven consulting labor annually.",[37,11764,11765,11766,11769],{},"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 ",[41,11767,11768],{"href":11526},"cost and timeline discussion in the certification process guide"," for more detail.",[32,11771,11773],{"id":11772},"choosing-a-certification-body","Choosing a certification body",[37,11775,11776],{},"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,11778,11779,11780,11784],{},"Selection criteria include accreditation scope, industry experience, auditor availability, geographic coverage, and cost transparency. The ",[41,11781,11783],{"href":11782},"\u002Fframeworks\u002Fiso27001\u002Fcertification-body-selection","certification body selection guide"," walks through the full evaluation.",[32,11786,11788],{"id":11787},"surveillance-audits-and-recertification","Surveillance audits and recertification",[37,11790,11791],{},"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,11793,11794,11795,11799],{},"See the ",[41,11796,11798],{"href":11797},"\u002Fframeworks\u002Fiso27001\u002Fsurveillance-audits","surveillance audits guide"," for preparation checklists and what auditors typically sample during year-one and year-two visits.",[32,11801,11803],{"id":11802},"iso-27001-vs-soc-2-vs-nist-csf","ISO 27001 vs SOC 2 vs NIST CSF",[37,11805,11806],{},"Customers and leadership teams frequently ask how ISO 27001 compares to other frameworks. The short version:",[94,11808,11809,11817],{},[97,11810,11811,11816],{},[58,11812,11813,11814,167],{},"ISO 27001 vs ",[41,11815,128],{"href":127}," 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.",[97,11818,11819,11822,11823,11826],{},[58,11820,11821],{},"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 ",[41,11824,11825],{"href":393},"NIST CSF mapping to other frameworks"," for a side-by-side comparison.",[37,11828,11829,11830,11832],{},"If you are weighing which framework to pursue first, the ",[41,11831,11532],{"href":11531}," covers framework sequencing for growing companies.",[32,11834,11836],{"id":11835},"getting-certified-with-episki","Getting certified with episki",[37,11838,11839],{},"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,11841,11842,11843,336,11847,11851],{},"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 ",[41,11844,11846],{"href":11845},"\u002Fcompare\u002Fvanta","episki vs Vanta",[41,11848,11850],{"href":11849},"\u002Fcompare\u002Fdrata","episki vs Drata"," for honest side-by-side views.",[37,11853,11854],{},"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,11856,11857],{},"Start a free trial, import your controls, and run your first ISO 27001 gap analysis in under an hour.",{"title":561,"searchDepth":562,"depth":562,"links":11859},[11860,11861,11862,11863,11864,11865,11866,11867,11868,11869,11870,11871,11872,11873,11874,11875],{"id":11480,"depth":562,"text":11481},{"id":11503,"depth":562,"text":11504},{"id":11516,"depth":562,"text":11517},{"id":11536,"depth":562,"text":11537},{"id":11553,"depth":562,"text":11554},{"id":11575,"depth":562,"text":11576},{"id":11597,"depth":562,"text":11598},{"id":11664,"depth":562,"text":11665},{"id":11681,"depth":562,"text":11682},{"id":11703,"depth":562,"text":11704},{"id":11718,"depth":562,"text":11719},{"id":11732,"depth":562,"text":11733},{"id":11772,"depth":562,"text":11773},{"id":11787,"depth":562,"text":11788},{"id":11802,"depth":562,"text":11803},{"id":11835,"depth":562,"text":11836},{"title":11877,"description":11878,"items":11879},"ISO 27001 certification checklist inside episki","Everything you need to scope, implement, and certify your ISMS is preloaded in your free trial.",[11880,11881,11882,11883,11884,11885,11886],"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":11888,"description":11889},"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":11891,"items":11892},"ISO 27001 frequently asked questions",[11893,11896,11899,11902,11905],{"label":11894,"content":11895},"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":11897,"content":11898},"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":11900,"content":11901},"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":11903,"content":11904},"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":11906,"content":11907},"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":11909,"title":11910,"description":11911,"links":11912},"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.",[11913,11915],{"label":11914,"icon":622,"to":623},"Start ISO 27001 trial",{"label":625,"icon":10844,"color":627,"variant":628,"to":629,"target":630},{},{"headline":11918,"title":11918,"description":11919,"items":11920},"ISO 27001 certification resources","Give leadership, auditors, and customers visibility into your ISMS maturity.",[11921,11924,11927],{"title":11922,"description":11923},"ISMS maturity dashboard","Visual progress across all Annex A domains with gap analysis and trending.",{"title":11925,"description":11926},"Auditor collaboration portal","Scoped access for certification bodies with evidence requests and Q&A threads.",{"title":11928,"description":11929},"Customer trust pack","Shareable ISO 27001 certification summary with scope details and control highlights.",{"title":11931,"description":11932},"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.",[11934,11936,11939],{"value":11560,"description":11935},"Pre-mapped to your control graph with owners, evidence, and review cadences.",{"value":11937,"description":11938},"60% less prep","Average reduction in Stage 2 audit preparation time with episki's automation.",{"value":5411,"description":11940},"Surveillance audits stay painless with always-current evidence and risk registers.","5.frameworks\u002Fiso27001","aThn2G4vv-MUlfe5mhRJFQHtMgpdfJi3-UMVou77OZs",{"id":4,"title":5,"advantages":11944,"body":11951,"checklist":12293,"cta":12295,"description":561,"extension":597,"faq":12296,"hero":12303,"lastUpdated":631,"meta":12307,"name":633,"navigation":634,"path":635,"resources":12308,"seo":12313,"slug":652,"stats":12314,"stem":663,"__hash__":664},[11945,11947,11949],{"title":8,"description":9,"bullets":11946},[11,12,13],{"title":15,"description":16,"bullets":11948},[18,19,20],{"title":22,"description":23,"bullets":11950},[25,26,27],{"type":29,"value":11952,"toc":12271},[11953,11955,11959,11961,11963,11967,11969,11971,11973,11979,11981,11983,11985,12011,12015,12017,12019,12021,12023,12029,12031,12037,12039,12045,12047,12053,12055,12061,12063,12069,12071,12073,12077,12095,12099,12101,12105,12107,12117,12119,12125,12127,12133,12145,12149,12151,12157,12161,12167,12169,12171,12203,12205,12207,12209,12229,12231,12233,12235,12237,12267,12269],[32,11954,35],{"id":34},[37,11956,39,11957,45],{},[41,11958,44],{"href":43},[37,11960,48],{},[50,11962,53],{"id":52},[37,11964,56,11965,61],{},[58,11966,60],{},[37,11968,64],{},[50,11970,68],{"id":67},[37,11972,71],{},[37,11974,74,11975,78,11977,82],{},[58,11976,77],{},[58,11978,81],{},[32,11980,86],{"id":85},[37,11982,89],{},[37,11984,92],{},[94,11986,11987,11991,11995,11999,12007],{},[97,11988,11989,102],{},[58,11990,101],{},[97,11992,11993,108],{},[58,11994,107],{},[97,11996,11997,114],{},[58,11998,113],{},[97,12000,12001,120,12003,124,12005,129],{},[58,12002,119],{},[41,12004,123],{"href":43},[41,12006,128],{"href":127},[97,12008,12009,135],{},[58,12010,134],{},[37,12012,138,12013,142],{},[41,12014,86],{"href":141},[32,12016,146],{"id":145},[37,12018,149],{},[37,12020,152],{},[50,12022,156],{"id":155},[37,12024,159,12025,162,12027,167],{},[58,12026,81],{},[41,12028,166],{"href":165},[50,12030,171],{"id":170},[37,12032,159,12033,177,12035,167],{},[58,12034,176],{},[41,12036,181],{"href":180},[50,12038,185],{"id":184},[37,12040,159,12041,191,12043,167],{},[58,12042,190],{},[41,12044,195],{"href":194},[50,12046,199],{"id":198},[37,12048,159,12049,205,12051,167],{},[58,12050,204],{},[41,12052,209],{"href":208},[50,12054,213],{"id":212},[37,12056,159,12057,219,12059,167],{},[58,12058,218],{},[41,12060,223],{"href":222},[50,12062,227],{"id":226},[37,12064,159,12065,233,12067,167],{},[58,12066,232],{},[41,12068,237],{"href":236},[37,12070,240],{},[32,12072,244],{"id":243},[37,12074,247,12075,251],{},[58,12076,250],{},[94,12078,12079,12083,12087,12091],{},[97,12080,12081,259],{},[58,12082,258],{},[97,12084,12085,265],{},[58,12086,264],{},[97,12088,12089,271],{},[58,12090,270],{},[97,12092,12093,277],{},[58,12094,276],{},[37,12096,280,12097,142],{},[41,12098,244],{"href":283},[32,12100,287],{"id":286},[37,12102,290,12103,294],{},[58,12104,293],{},[37,12106,297],{},[94,12108,12109,12113],{},[97,12110,290,12111,305],{},[58,12112,304],{},[97,12114,290,12115,311],{},[58,12116,310],{},[37,12118,314],{},[37,12120,317,12121,322,12123,167],{},[41,12122,321],{"href":320},[41,12124,287],{"href":325},[32,12126,329],{"id":328},[37,12128,332,12129,336,12131,340],{},[58,12130,335],{},[58,12132,339],{},[94,12134,12135,12141],{},[97,12136,12137,348,12139,352],{},[58,12138,347],{},[58,12140,351],{},[97,12142,12143,357],{},[58,12144,77],{},[37,12146,360,12147,364],{},[58,12148,363],{},[32,12150,368],{"id":367},[37,12152,371,12153,374,12155,379],{},[41,12154,128],{"href":127},[41,12156,378],{"href":377},[37,12158,382,12159,387],{},[41,12160,386],{"href":385},[37,12162,390,12163,394,12165,399],{},[41,12164,368],{"href":393},[41,12166,398],{"href":397},[32,12168,403],{"id":402},[37,12170,406],{},[94,12172,12173,12177,12183,12187,12191,12195,12199],{},[97,12174,12175,414],{},[58,12176,413],{},[97,12178,12179,420,12181,167],{},[58,12180,419],{},[41,12182,423],{"href":385},[97,12184,12185,429],{},[58,12186,428],{},[97,12188,12189,435],{},[58,12190,434],{},[97,12192,12193,441],{},[58,12194,440],{},[97,12196,12197,447],{},[58,12198,446],{},[97,12200,12201,453],{},[58,12202,452],{},[37,12204,456],{},[32,12206,460],{"id":459},[37,12208,463],{},[94,12210,12211,12217,12223],{},[97,12212,12213,471,12215,475],{},[58,12214,470],{},[58,12216,474],{},[97,12218,12219,481,12221,485],{},[58,12220,480],{},[58,12222,484],{},[97,12224,12225,491,12227,495],{},[58,12226,490],{},[58,12228,494],{},[37,12230,498],{},[37,12232,501],{},[32,12234,505],{"id":504},[37,12236,508],{},[510,12238,12239,12243,12247,12251,12255,12259,12263],{},[97,12240,12241,517],{},[58,12242,516],{},[97,12244,12245,523],{},[58,12246,522],{},[97,12248,12249,529],{},[58,12250,528],{},[97,12252,12253,535],{},[58,12254,534],{},[97,12256,12257,541],{},[58,12258,540],{},[97,12260,12261,547],{},[58,12262,546],{},[97,12264,12265,553],{},[58,12266,552],{},[37,12268,556],{},[37,12270,559],{},{"title":561,"searchDepth":562,"depth":562,"links":12272},[12273,12277,12278,12286,12287,12288,12289,12290,12291,12292],{"id":34,"depth":562,"text":35,"children":12274},[12275,12276],{"id":52,"depth":567,"text":53},{"id":67,"depth":567,"text":68},{"id":85,"depth":562,"text":86},{"id":145,"depth":562,"text":146,"children":12279},[12280,12281,12282,12283,12284,12285],{"id":155,"depth":567,"text":156},{"id":170,"depth":567,"text":171},{"id":184,"depth":567,"text":185},{"id":198,"depth":567,"text":199},{"id":212,"depth":567,"text":213},{"id":226,"depth":567,"text":227},{"id":243,"depth":562,"text":244},{"id":286,"depth":562,"text":287},{"id":328,"depth":562,"text":329},{"id":367,"depth":562,"text":368},{"id":402,"depth":562,"text":403},{"id":459,"depth":562,"text":460},{"id":504,"depth":562,"text":505},{"title":586,"description":587,"items":12294},[589,590,591,592,593],{"title":595,"description":596},{"title":599,"items":12297},[12298,12299,12300,12301,12302],{"label":35,"content":602},{"label":604,"content":605},{"label":607,"content":608},{"label":610,"content":611},{"label":613,"content":614},{"headline":616,"title":617,"description":618,"links":12304},[12305,12306],{"label":621,"icon":622,"to":623},{"label":625,"icon":626,"color":627,"variant":628,"to":629,"target":630},{},{"headline":637,"title":637,"description":638,"items":12309},[12310,12311,12312],{"title":641,"description":642},{"title":644,"description":645},{"title":647,"description":648},{"title":650,"description":651},[12315,12316,12317],{"value":655,"description":656},{"value":658,"description":659},{"value":661,"description":662},{"id":12319,"title":12320,"advantages":12321,"body":12343,"checklist":12760,"cta":12769,"description":561,"extension":597,"faq":12772,"hero":12790,"lastUpdated":631,"meta":12799,"name":1223,"navigation":634,"path":1222,"resources":12800,"seo":12813,"slug":4939,"stats":12816,"stem":12826,"__hash__":12827},"frameworks\u002F5.frameworks\u002Fpci.md","Pci",[12322,12329,12336],{"title":12323,"description":12324,"bullets":12325},"Cardholder data mapped","Visualize systems, networks, and data flows tied to each DSS requirement.",[12326,12327,12328],"Track segmentation documentation and approvals","Connect SIEM and log tools for retention evidence","Link vulnerability scans and pen tests to controls",{"title":12330,"description":12331,"bullets":12332},"Task orchestration for engineering","Send prioritized remediation tasks to Jira or Linear with context.",[12333,12334,12335],"Auto-created tickets with required evidence","SLA tracking ensures high-risk remediations close on time","Change management logs sync back automatically",{"title":12337,"description":12338,"bullets":12339},"QSA-ready collaboration","Centralize requests, walkthroughs, and findings with secure file sharing.",[12340,12341,12342],"QSA comments resolve next to each control","Expiring links for sensitive diagrams","Exportable ROC narrative drafts",{"type":29,"value":12344,"toc":12747},[12345,12349,12355,12358,12361,12365,12372,12460,12463,12467,12474,12478,12491,12495,12503,12556,12568,12572,12583,12586,12589,12593,12610,12614,12617,12655,12663,12667,12670,12674,12687,12691,12694,12744],[32,12346,12348],{"id":12347},"what-is-pci-dss","What is PCI DSS?",[37,12350,12351,12352,12354],{},"The Payment Card Industry Data Security Standard -- universally known as ",[41,12353,1223],{"href":7285}," -- 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,12356,12357],{},"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,12359,12360],{},"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,12362,12364],{"id":12363},"the-12-pci-dss-requirements","The 12 PCI DSS requirements",[37,12366,12367,12368,12371],{},"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 ",[41,12369,12370],{"href":3017},"PCI DSS requirements page","; at a glance they are:",[510,12373,12374,12384,12390,12406,12412,12418,12424,12430,12436,12442,12448,12454],{},[97,12375,12376,12379,12380,167],{},[58,12377,12378],{},"Install and maintain network security controls"," -- firewalls and equivalent controls around the ",[41,12381,12383],{"href":12382},"\u002Fglossary\u002Fcardholder-data-environment","cardholder data environment",[97,12385,12386,12389],{},[58,12387,12388],{},"Apply secure configurations to all system components"," -- hardening standards, default credential elimination, and secure build baselines.",[97,12391,12392,12395,12396,12400,12401,12405],{},[58,12393,12394],{},"Protect stored account data"," -- encryption, truncation, hashing, or ",[41,12397,12399],{"href":12398},"\u002Fglossary\u002Ftokenization","tokenization"," of the ",[41,12402,12404],{"href":12403},"\u002Fglossary\u002Fpan","PAN"," and prohibition on storing sensitive authentication data.",[97,12407,12408,12411],{},[58,12409,12410],{},"Protect cardholder data with strong cryptography during transmission"," over open, public networks.",[97,12413,12414,12417],{},[58,12415,12416],{},"Protect all systems and networks from malicious software"," -- anti-malware on in-scope systems and defenses against script-based threats.",[97,12419,12420,12423],{},[58,12421,12422],{},"Develop and maintain secure systems and software"," -- secure SDLC, patching, and vulnerability management for in-scope systems.",[97,12425,12426,12429],{},[58,12427,12428],{},"Restrict access to system components and cardholder data by business need to know"," -- least-privilege role design.",[97,12431,12432,12435],{},[58,12433,12434],{},"Identify users and authenticate access to system components"," -- unique IDs, strong authentication, and phishing-resistant MFA.",[97,12437,12438,12441],{},[58,12439,12440],{},"Restrict physical access to cardholder data"," -- physical security for facilities, media, and devices.",[97,12443,12444,12447],{},[58,12445,12446],{},"Log and monitor all access to system components and cardholder data"," -- centralized logging, daily review, and tamper protection.",[97,12449,12450,12453],{},[58,12451,12452],{},"Test security of systems and networks regularly"," -- ASV scans, internal scans, pen tests, and segmentation validation.",[97,12455,12456,12459],{},[58,12457,12458],{},"Support information security with organizational policies and programs"," -- governance, awareness, incident response, and third-party oversight.",[37,12461,12462],{},"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,12464,12466],{"id":12465},"pci-dss-v40-changes","PCI DSS v4.0 changes",[37,12468,12469,12470,167],{},"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 ",[41,12471,12473],{"href":12472},"\u002Fframeworks\u002Fpci\u002Fv4-changes","PCI DSS v4.0 changes guide",[32,12475,12477],{"id":12476},"merchant-compliance-levels-1-4","Merchant compliance levels 1-4",[37,12479,12480,12481,12485,12486,12490],{},"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 ",[41,12482,12484],{"href":12483},"\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 ",[41,12487,12489],{"href":12488},"\u002Fframeworks\u002Fpci\u002Fcompliance-levels","PCI DSS compliance levels page"," breaks down every threshold by card brand and the validation path each level owes.",[32,12492,12494],{"id":12493},"self-assessment-questionnaires-saqs","Self-Assessment Questionnaires (SAQs)",[37,12496,12497,12498,12502],{},"Merchants and service providers that are not required to complete a full PCI DSS Report on Compliance validate using a ",[41,12499,12501],{"href":12500},"\u002Fglossary\u002Fsaq","Self-Assessment Questionnaire",", or SAQ. The PCI SSC publishes nine SAQ types, each tailored to a specific acceptance channel and technology profile:",[94,12504,12505,12511,12517,12523,12529,12535,12541,12547],{},[97,12506,12507,12510],{},[58,12508,12509],{},"SAQ A"," -- card-not-present merchants that fully outsource all cardholder data functions.",[97,12512,12513,12516],{},[58,12514,12515],{},"SAQ A-EP"," -- e-commerce merchants that partially outsource payment processing but host pages that could affect payment page security.",[97,12518,12519,12522],{},[58,12520,12521],{},"SAQ B"," -- merchants using only imprint machines or standalone dial-out terminals.",[97,12524,12525,12528],{},[58,12526,12527],{},"SAQ B-IP"," -- merchants using only standalone IP-connected POI devices.",[97,12530,12531,12534],{},[58,12532,12533],{},"SAQ C-VT"," -- merchants entering transactions into a virtual payment terminal.",[97,12536,12537,12540],{},[58,12538,12539],{},"SAQ C"," -- merchants with payment application systems connected to the internet.",[97,12542,12543,12546],{},[58,12544,12545],{},"SAQ P2PE"," -- merchants using PCI-listed point-to-point encryption solutions.",[97,12548,12549,336,12552,12555],{},[58,12550,12551],{},"SAQ D for Merchants",[58,12553,12554],{},"SAQ D for Service Providers"," -- the catch-all SAQs for entities that store cardholder data or do not qualify for a simpler SAQ.",[37,12557,12558,12559,11696,12563,12567],{},"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 ",[41,12560,12562],{"href":12561},"\u002Fframeworks\u002Fpci\u002Fself-assessment-questionnaire","SAQ reference",[41,12564,12566],{"href":12565},"\u002Fframeworks\u002Fpci\u002Fsaq-types-explained","SAQ types explained"," page walk through each SAQ's eligibility, question count, and typical pitfalls.",[32,12569,12571],{"id":12570},"cardholder-data-environment-cde-and-scoping","Cardholder data environment (CDE) and scoping",[37,12573,12574,12575,12577,12578,12582],{},"Every PCI DSS program begins with scoping. The ",[41,12576,12383],{"href":12382},", 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 ",[41,12579,12581],{"href":12580},"\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,12584,12585],{},"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,12587,12588],{},"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,12590,12592],{"id":12591},"scope-reduction-strategies","Scope reduction strategies",[37,12594,12595,12596,12600,12601,12605,12606,12609],{},"Because PCI DSS obligations scale with the CDE, shrinking the CDE is the fastest way to cut PCI DSS cost and risk. Effective ",[41,12597,12599],{"href":12598},"\u002Fframeworks\u002Fpci\u002Fscope-reduction","PCI DSS scope reduction"," typically combines four levers: strong ",[41,12602,12604],{"href":12603},"\u002Fframeworks\u002Fpci\u002Fnetwork-segmentation","network segmentation"," that isolates the CDE onto dedicated VLANs with tightly controlled firewall rules; ",[41,12607,12399],{"href":12608},"\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,12611,12613],{"id":12612},"key-pci-dss-roles-qsas-asvs-and-isas","Key PCI DSS roles: QSAs, ASVs, and ISAs",[37,12615,12616],{},"Three accredited roles support every PCI DSS program:",[94,12618,12619,12634,12649],{},[97,12620,12621,12628,12629,12633],{},[58,12622,12623,12624,12627],{},"Qualified Security Assessors (",[41,12625,12626],{"href":12483},"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 ",[41,12630,12632],{"href":12631},"\u002Fframeworks\u002Fpci\u002Fqsa-selection","QSA selection guide"," covers how to evaluate firms, cost drivers, and red flags.",[97,12635,12636,12643,12644,12648],{},[58,12637,12638,12639,12627],{},"Approved Scanning Vendors (",[41,12640,12642],{"href":12641},"\u002Fglossary\u002Fasv","ASVs"," -- PCI SSC-approved firms that run the quarterly external vulnerability scans required by PCI DSS Requirement 11.3.2. The ",[41,12645,12647],{"href":12646},"\u002Fframeworks\u002Fpci\u002Fasv-program","ASV program guide"," covers vendor selection, scanning cadence, passing thresholds, and remediation workflows.",[97,12650,12651,12654],{},[58,12652,12653],{},"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,12656,12657,12658,12662],{},"Penetration testing (Requirement 11.4) sits alongside ASV scanning and is a frequent source of PCI DSS findings. The ",[41,12659,12661],{"href":12660},"\u002Fframeworks\u002Fpci\u002Fpenetration-testing","PCI DSS penetration testing guide"," covers internal vs external scope, segmentation testing, and frequency.",[32,12664,12666],{"id":12665},"penalties-for-non-compliance","Penalties for non-compliance",[37,12668,12669],{},"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,12671,12673],{"id":12672},"pci-dss-vs-other-frameworks","PCI DSS vs other frameworks",[37,12675,12676,12677,12681,12682,12686],{},"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 ",[41,12678,12680],{"href":12679},"\u002Findustry\u002Ffinance","finance industry"," or running ",[41,12683,12685],{"href":12684},"\u002Findustry\u002Fecommerce","e-commerce"," platforms, PCI DSS almost always becomes the binding constraint that the rest of the security program organizes around.",[32,12688,12690],{"id":12689},"getting-pci-compliant","Getting PCI compliant",[37,12692,12693],{},"A typical path to PCI DSS compliance looks like this:",[510,12695,12696,12702,12708,12714,12720,12726,12732,12738],{},[97,12697,12698,12701],{},[58,12699,12700],{},"Define scope"," -- inventory every place card data lives, moves, or could move. Produce annotated network and data-flow diagrams.",[97,12703,12704,12707],{},[58,12705,12706],{},"Reduce scope"," -- apply segmentation, tokenization, P2PE, and outsourcing to shrink the CDE before assessment.",[97,12709,12710,12713],{},[58,12711,12712],{},"Select your validation path"," -- confirm your PCI DSS level with your acquirer and determine whether you owe a ROC or an SAQ.",[97,12715,12716,12719],{},[58,12717,12718],{},"Gap assess"," -- map your current controls to every applicable PCI DSS requirement and prioritize remediation.",[97,12721,12722,12725],{},[58,12723,12724],{},"Remediate and document"," -- close gaps, write the policies and procedures PCI DSS expects, and stand up the logging, monitoring, scanning, and testing programs.",[97,12727,12728,12731],{},[58,12729,12730],{},"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.",[97,12733,12734,12737],{},[58,12735,12736],{},"Validate and attest"," -- produce the ROC or SAQ plus Attestation of Compliance, and submit to your acquirer on the required cadence.",[97,12739,12740,12743],{},[58,12741,12742],{},"Operate continuously"," -- PCI DSS v4.0 expects continuous monitoring, targeted risk analyses, and evidence that controls stay effective between assessments.",[37,12745,12746],{},"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":561,"searchDepth":562,"depth":562,"links":12748},[12749,12750,12751,12752,12753,12754,12755,12756,12757,12758,12759],{"id":12347,"depth":562,"text":12348},{"id":12363,"depth":562,"text":12364},{"id":12465,"depth":562,"text":12466},{"id":12476,"depth":562,"text":12477},{"id":12493,"depth":562,"text":12494},{"id":12570,"depth":562,"text":12571},{"id":12591,"depth":562,"text":12592},{"id":12612,"depth":562,"text":12613},{"id":12665,"depth":562,"text":12666},{"id":12672,"depth":562,"text":12673},{"id":12689,"depth":562,"text":12690},{"title":12761,"description":12762,"items":12763},"PCI DSS playbook","Follow structured milestones from scoping through ROC submission.",[12764,12765,12766,12767,12768],"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":12770,"description":12771},"Keep PCI DSS audit-ready around the clock","Spin up your trial, sync evidence, and invite your QSA in a single day.",{"title":12773,"items":12774},"PCI DSS frequently asked questions",[12775,12778,12781,12784,12787],{"label":12776,"content":12777},"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":12779,"content":12780},"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":12782,"content":12783},"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":12785,"content":12786},"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":12788,"content":12789},"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":12791,"title":12792,"description":12793,"links":12794},"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.",[12795,12797],{"label":12796,"icon":622,"to":623},"Start PCI trial",{"label":625,"icon":12798,"color":627,"variant":628,"to":629,"target":630},"i-lucide-calendar",{},{"headline":12801,"title":12801,"description":12802,"items":12803},"PCI enablement kit","Give leadership, ops, and QSAs a single source of truth.",[12804,12807,12810],{"title":12805,"description":12806},"CDE architecture report","Share sanitized diagrams and segmentation notes with prospects.",{"title":12808,"description":12809},"Risk and remediation digest","Weekly summary of open items, owners, and due dates.",{"title":12811,"description":12812},"Assessor workspace","Prebuilt template keeps every requirement, artifact, and note aligned.",{"title":12814,"description":12815},"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.",[12817,12820,12823],{"value":12818,"description":12819},"90% automation","Evidence coverage across access, logging, segmentation, and monitoring.",{"value":12821,"description":12822},"QSA portal","Scoped access keeps your assessor in sync without endless spreadsheets.",{"value":12824,"description":12825},"Weekly drift checks","Automated alerts highlight misconfigurations before audits.","5.frameworks\u002Fpci","wxvQHRYeBHEsDrDF1QZg43Nio6AvwX3DWW21RftBG2c",{"id":12829,"title":12830,"advantages":12831,"body":12853,"checklist":13357,"cta":13366,"description":561,"extension":597,"faq":13369,"hero":13386,"lastUpdated":631,"meta":13394,"name":13395,"navigation":634,"path":127,"resources":13396,"seo":13408,"slug":3177,"stats":13411,"stem":13421,"__hash__":13422},"frameworks\u002F5.frameworks\u002Fsoc2.md","Soc2",[12832,12839,12846],{"title":12833,"description":12834,"bullets":12835},"Mapped once, reused forever","Applies Trust Service Criteria to your existing controls and keeps overlaps synced.",[12836,12837,12838],"Control graph highlights reuse across security, availability, and confidentiality","AI suggests narratives and testing procedures","Version history shows every update for auditors",{"title":12840,"description":12841,"bullets":12842},"Evidence organized by control","Upload and track screenshots, configs, and exports in a structured evidence locker.",[12843,12844,12845],"Organized screenshots, configs, and test exports","Alerting when evidence expires or SLAs slip","Immutable locker with reviewer threads",{"title":12847,"description":12848,"bullets":12849},"Auditor collaboration hub","Invite your auditor with scoped access and keep Q&A right next to each control.",[12850,12851,12852],"Bulk requests & fulfillment tracking","Redacted file sharing with access controls","One-click SOC 2 summaries for customers",{"type":29,"value":12854,"toc":13339},[12855,12859,12862,12870,12878,12884,12888,12891,12897,12902,12916,12920,12925,12929,12932,12936,12944,12948,12951,12955,12963,12967,12974,12978,12981,12984,13001,13009,13013,13020,13062,13065,13069,13072,13075,13113,13121,13125,13128,13184,13187,13191,13194,13201,13208,13215,13226,13234,13238,13246,13278,13281,13285,13288,13291,13329],[32,12856,12858],{"id":12857},"what-is-soc-2","What is SOC 2?",[37,12860,12861],{},"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,12863,12864,12865,12869],{},"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 ",[41,12866,12868],{"href":12867},"\u002Fglossary\u002Fssae-18","SSAE 18"," framework.",[37,12871,12872,12873,12877],{},"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 ",[41,12874,12876],{"href":12875},"\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,12879,12880,12881,12883],{},"SOC 2 is built on five ",[58,12882,12876],{},": 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,12885,12887],{"id":12886},"soc-2-type-i-vs-type-ii","SOC 2 Type I vs Type II",[37,12889,12890],{},"Every SOC 2 engagement is either Type I or Type II, and the difference matters.",[37,12892,290,12893,12896],{},[58,12894,12895],{},"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,12898,290,12899,12901],{},[58,12900,9932],{}," 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,12903,12904,12905,12909,12910,336,12913,167],{},"For a full comparison including cost benchmarks, observation period tradeoffs, and decision frameworks, see ",[41,12906,12908],{"href":12907},"\u002Fframeworks\u002Fsoc2\u002Ftype-1-vs-type-2","SOC 2 Type 1 vs Type 2",". Related glossary terms: ",[41,12911,12912],{"href":9931},"SOC 2 Type 2",[41,12914,12876],{"href":12915},"\u002Fglossary\u002Ftrust-services-criteria",[32,12917,12919],{"id":12918},"the-five-trust-services-criteria","The five Trust Services Criteria",[37,12921,159,12922,12924],{},[41,12923,12876],{"href":12875}," define the principles your controls must satisfy. Each criterion addresses a different aspect of how a service organization protects and manages customer data.",[50,12926,12928],{"id":12927},"security-common-criteria-required","Security (Common Criteria) — required",[37,12930,12931],{},"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.",[50,12933,12935],{"id":12934},"availability","Availability",[37,12937,12938,12939,12943],{},"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 ",[41,12940,12942],{"href":12941},"\u002Fframeworks\u002Fsoc2\u002Favailability-criteria","availability criteria deep dive"," for common controls and implementation patterns.",[50,12945,12947],{"id":12946},"processing-integrity","Processing integrity",[37,12949,12950],{},"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.",[50,12952,12954],{"id":12953},"confidentiality","Confidentiality",[37,12956,12957,12958,12962],{},"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 ",[41,12959,12961],{"href":12960},"\u002Fframeworks\u002Fsoc2\u002Fconfidentiality-criteria","confidentiality criteria deep dive"," for details.",[50,12964,12966],{"id":12965},"privacy","Privacy",[37,12968,12969,12970,167],{},"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 ",[41,12971,12973],{"href":12972},"\u002Fframeworks\u002Fsoc2\u002Fprivacy-criteria","privacy criteria deep dive",[32,12975,12977],{"id":12976},"who-needs-soc-2-compliance","Who needs SOC 2 compliance?",[37,12979,12980],{},"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,12982,12983],{},"Companies typically pursue SOC 2 when one or more of the following is true:",[94,12985,12986,12989,12992,12995,12998],{},[97,12987,12988],{},"Enterprise prospects are asking for a report during procurement or vendor reviews.",[97,12990,12991],{},"Sales cycles are slowing because buyers are blocking deals on security questionnaires.",[97,12993,12994],{},"Existing customers are requesting a current SOC 2 report during annual reviews.",[97,12996,12997],{},"Investors or partners are asking about the company's security posture.",[97,12999,13000],{},"The business is entering regulated verticals like financial services, healthcare, or government.",[37,13002,13003,13004,13008],{},"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 ",[41,13005,13007],{"href":13006},"\u002Fnow\u002Fsoc2-for-saas","SOC 2 for SaaS"," for a deeper discussion.",[32,13010,13012],{"id":13011},"the-soc-2-audit-process-overview","The SOC 2 audit process overview",[37,13014,159,13015,13019],{},[41,13016,13018],{"href":13017},"\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.",[510,13021,13022,13038,13044,13050,13056],{},[97,13023,13024,13027,13028,13032,13033,13037],{},[58,13025,13026],{},"Scoping and readiness assessment."," Define what systems and Trust Services Criteria are in scope, then perform a ",[41,13029,13031],{"href":13030},"\u002Fframeworks\u002Fsoc2\u002Freadiness-assessment","readiness assessment"," to compare current controls against ",[41,13034,13036],{"href":13035},"\u002Fframeworks\u002Fsoc2\u002Frequirements","SOC 2 requirements",". The output is a prioritized remediation plan.",[97,13039,13040,13043],{},[58,13041,13042],{},"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.",[97,13045,13046,13049],{},[58,13047,13048],{},"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.",[97,13051,13052,13055],{},[58,13053,13054],{},"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.",[97,13057,13058,13061],{},[58,13059,13060],{},"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,13063,13064],{},"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,13066,13068],{"id":13067},"what-does-soc-2-cost","What does SOC 2 cost?",[37,13070,13071],{},"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,13073,13074],{},"Typical benchmarks for a first-time SOC 2 engagement:",[94,13076,13077,13083,13089,13095,13101,13107],{},[97,13078,13079,13082],{},[58,13080,13081],{},"Type I auditor fees",": $15,000 to $40,000",[97,13084,13085,13088],{},[58,13086,13087],{},"Type II auditor fees",": $25,000 to $80,000",[97,13090,13091,13094],{},[58,13092,13093],{},"Readiness consulting"," (optional): $10,000 to $40,000",[97,13096,13097,13100],{},[58,13098,13099],{},"Compliance platform",": $6,000 to $60,000 annually depending on vendor",[97,13102,13103,13106],{},[58,13104,13105],{},"Penetration testing",": $8,000 to $30,000 per test",[97,13108,13109,13112],{},[58,13110,13111],{},"Internal staff time",": 200 to 600 hours across the first cycle",[37,13114,13115,13116,13120],{},"Total first-year cost for most growth-stage SaaS companies lands between $40,000 and $200,000. See the full ",[41,13117,13119],{"href":13118},"\u002Fframeworks\u002Fsoc2\u002Fcost","SOC 2 cost breakdown"," for detailed ranges and cost-reduction strategies.",[32,13122,13124],{"id":13123},"common-soc-2-challenges","Common SOC 2 challenges",[37,13126,13127],{},"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.",[94,13129,13130,13136,13142,13148,13154,13165,13175],{},[97,13131,13132,13135],{},[58,13133,13134],{},"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.",[97,13137,13138,13141],{},[58,13139,13140],{},"Evidence gaps."," Screenshots expire. Configurations change. Ownership drifts between quarters. By the time the auditor asks, the evidence trail is broken.",[97,13143,13144,13147],{},[58,13145,13146],{},"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.",[97,13149,13150,13153],{},[58,13151,13152],{},"Policy drift."," Policies written for the audit do not match how the team actually operates. Auditors detect this quickly during interviews and walkthroughs.",[97,13155,13156,13159,13160,13164],{},[58,13157,13158],{},"Vendor oversight."," Third-party vendors handle critical data but are rarely monitored with the same rigor as internal systems. See ",[41,13161,13163],{"href":13162},"\u002Fframeworks\u002Fsoc2\u002Fvendor-management","vendor management"," for how to close this gap.",[97,13166,13167,13170,13171,13174],{},[58,13168,13169],{},"Change management."," Production changes bypass approval workflows, leaving no audit trail. ",[41,13172,8795],{"href":13173},"\u002Fframeworks\u002Fsoc2\u002Fchange-management"," is a frequent source of Type II exceptions.",[97,13176,13177,13180,13181,167],{},[58,13178,13179],{},"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 ",[41,13182,8949],{"href":13183},"\u002Fframeworks\u002Fsoc2\u002Fincident-response",[37,13185,13186],{},"A structured approach — mapping controls, evidence, and owners from day one — removes most of these friction points before they become audit findings.",[32,13188,13190],{"id":13189},"how-soc-2-compares-to-other-frameworks","How SOC 2 compares to other frameworks",[37,13192,13193],{},"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,13195,13196,13200],{},[58,13197,13198],{},[41,13199,378],{"href":377}," 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,13202,13203,13207],{},[58,13204,13205],{},[41,13206,4568],{"href":4567}," 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,13209,13210,13214],{},[58,13211,13212],{},[41,13213,1223],{"href":1222}," 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,13216,13217,374,13220,6491,13223,13225],{},[58,13218,13219],{},"NIST Cybersecurity Framework",[58,13221,13222],{},"FedRAMP",[58,13224,386],{}," 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,13227,13228,13229,13233],{},"If you are comparing SOC 2 tooling options, our ",[41,13230,13232],{"href":13231},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata comparison"," covers the leading compliance automation platforms.",[32,13235,13237],{"id":13236},"soc-2-readiness-checklist","SOC 2 readiness checklist",[37,13239,13240,13241,13245],{},"A readiness checklist keeps your team focused during the months before the audit begins. The ",[41,13242,13244],{"href":13243},"\u002Fframeworks\u002Fsoc2\u002Fchecklist","full SOC 2 checklist"," covers every category, but at a high level expect to address:",[94,13247,13248,13251,13254,13257,13260,13263,13266,13269,13272,13275],{},[97,13249,13250],{},"Governance and policies (information security policy, acceptable use, code of conduct)",[97,13252,13253],{},"Access control (SSO, MFA, role-based access, quarterly access reviews)",[97,13255,13256],{},"Change management (code review, deployment approvals, production change logs)",[97,13258,13259],{},"Vendor risk management (inventory, assessments, monitoring)",[97,13261,13262],{},"Incident response (documented plan, tested at least annually)",[97,13264,13265],{},"Business continuity and disaster recovery (plan with defined RPO\u002FRTO, tested)",[97,13267,13268],{},"Logging and monitoring (centralized logs, alerting, incident tickets)",[97,13270,13271],{},"Security awareness training (annual minimum, tracked completion)",[97,13273,13274],{},"HR controls (background checks, onboarding, offboarding, confidentiality agreements)",[97,13276,13277],{},"Risk assessment (annual risk review, risk register, treatment plans)",[37,13279,13280],{},"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,13282,13284],{"id":13283},"getting-started-with-soc-2","Getting started with SOC 2",[37,13286,13287],{},"The best time to start a SOC 2 program is before the first buyer demands it. The second best time is now.",[37,13289,13290],{},"A reasonable starting sequence:",[510,13292,13293,13299,13305,13311,13317,13323],{},[97,13294,13295,13298],{},[58,13296,13297],{},"Pick your Trust Services Criteria."," Security is required. Add others only if you have customer commitments that map to them.",[97,13300,13301,13304],{},[58,13302,13303],{},"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.",[97,13306,13307,13310],{},[58,13308,13309],{},"Run a readiness assessment."," Either internally or with a consultant. The goal is a prioritized remediation list, not a polished report.",[97,13312,13313,13316],{},[58,13314,13315],{},"Remediate in priority order."," Address policy gaps, access control weaknesses, and logging first — these are the most common sources of findings.",[97,13318,13319,13322],{},[58,13320,13321],{},"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.",[97,13324,13325,13328],{},[58,13326,13327],{},"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,13330,13331,13332,922,13336,13338],{},"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. ",[41,13333,13335],{"href":623,"rel":13334},[920],"Start a free trial",[41,13337,925],{"href":629}," to see how SOC 2 looks with the scramble removed.",{"title":561,"searchDepth":562,"depth":562,"links":13340},[13341,13342,13343,13350,13351,13352,13353,13354,13355,13356],{"id":12857,"depth":562,"text":12858},{"id":12886,"depth":562,"text":12887},{"id":12918,"depth":562,"text":12919,"children":13344},[13345,13346,13347,13348,13349],{"id":12927,"depth":567,"text":12928},{"id":12934,"depth":567,"text":12935},{"id":12946,"depth":567,"text":12947},{"id":12953,"depth":567,"text":12954},{"id":12965,"depth":567,"text":12966},{"id":12976,"depth":562,"text":12977},{"id":13011,"depth":562,"text":13012},{"id":13067,"depth":562,"text":13068},{"id":13123,"depth":562,"text":13124},{"id":13189,"depth":562,"text":13190},{"id":13236,"depth":562,"text":13237},{"id":13283,"depth":562,"text":13284},{"title":13358,"description":13359,"items":13360},"SOC 2 readiness checklist inside episki","Everything is preloaded in your free trial so you can start assigning ownership and collecting proof immediately.",[13361,13362,13363,13364,13365],"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":13367,"description":13368},"Launch your SOC 2 workspace today","Import your controls, connect evidence, and invite your auditor in under an hour.",{"title":13370,"items":13371},"SOC 2 frequently asked questions",[13372,13375,13378,13381,13383],{"label":13373,"content":13374},"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":13376,"content":13377},"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":13379,"content":13380},"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":12977,"content":13382},"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":13384,"content":13385},"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":13387,"title":13388,"description":13389,"links":13390},"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.",[13391,13393],{"label":13392,"icon":622,"to":623},"Start SOC 2 trial",{"label":625,"icon":10844,"color":627,"variant":628,"to":629,"target":630},{},"SOC 2 Type I\u002FII",{"headline":13397,"title":13397,"description":13398,"items":13399},"SOC 2 acceleration resources","Give execs and customers visibility into progress at every stage.",[13400,13402,13405],{"title":10852,"description":13401},"Summaries translate control work into risk reduction and deals unlocked.",{"title":13403,"description":13404},"Sales enablement kit","SOC 2 FAQ answers and trust collateral ready for GTM teams.",{"title":13406,"description":13407},"Audit retro template","Capture what worked, track remediations, and prep the next period.",{"title":13409,"description":13410},"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.",[13412,13415,13418],{"value":13413,"description":13414},"45 days faster","Average time saved reaching Type II readiness with episki’s automation.",{"value":13416,"description":13417},"120+ controls","Pre-mapped control narratives with owners, evidence, and review cadences.",{"value":13419,"description":13420},"100% coverage","Auditor portal with control health dashboards and SOC 2 exports.","5.frameworks\u002Fsoc2","bJbRF5XSL9ALksj1QWkHTg9lO2E2kfmot3QsCAz1naE",1778494662429]