[{"data":1,"prerenderedAt":18619},["ShallowReactive",2],{"\u002Fframeworks\u002Fiso27001":3,"framework-hub-topics-iso27001":527,"related-glossary-iso27001":5520,"related-frameworks-iso27001":15539},{"id":4,"title":5,"advantages":6,"body":28,"checklist":446,"cta":457,"description":427,"extension":460,"faq":461,"hero":479,"lastUpdated":495,"meta":496,"name":43,"navigation":497,"path":498,"resources":499,"seo":512,"slug":515,"stats":516,"stem":525,"__hash__":526},"frameworks\u002F5.frameworks\u002Fiso27001.md","Iso27001",[7,14,21],{"title":8,"description":9,"bullets":10},"Statement of Applicability in minutes","Generate and maintain your SoA directly from your control graph with justification notes for every inclusion and exclusion.",[11,12,13],"Auto-populate applicability status from existing controls","Link each control to risk treatment decisions","Export auditor-ready SoA documents on demand",{"title":15,"description":16,"bullets":17},"Risk-driven control management","Connect your risk register to Annex A controls so treatment plans and evidence stay aligned as threats evolve.",[18,19,20],"Risk assessment templates following ISO 27005 guidance","Heat maps show residual risk by domain","Treatment plans tie directly to control tasks and owners",{"title":22,"description":23,"bullets":24},"Surveillance audit confidence","Keep your ISMS current between certification cycles with continuous monitoring and internal audit workflows.",[25,26,27],"Automated evidence refresh and expiration alerts","Internal audit scheduling with finding tracking","Management review templates with trend data",{"type":29,"value":30,"toc":426},"minimark",[31,36,50,53,56,59,63,66,69,72,76,79,92,96,99,107,110,114,122,125,133,137,145,148,156,160,163,209,217,225,229,232,235,243,247,250,253,265,269,272,280,284,287,294,298,301,327,334,338,341,349,353,356,364,368,371,394,400,404,407,420,423],[32,33,35],"h2",{"id":34},"what-is-iso-27001","What is ISO 27001?",[37,38,39,44,45,49],"p",{},[40,41,43],"a",{"href":42},"\u002Fglossary\u002Fiso27001","ISO 27001"," 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 ",[40,46,48],{"href":47},"\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,51,52],{},"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,54,55],{},"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,57,58],{},"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,60,62],{"id":61},"why-iso-27001-matters","Why ISO 27001 matters",[37,64,65],{},"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,67,68],{},"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,70,71],{},"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,73,75],{"id":74},"the-iso-27001-certification-process","The ISO 27001 certification process",[37,77,78],{},"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,80,81,82,86,87,91],{},"For a deep walkthrough of every phase of the journey, including timelines, auditor expectations, and common pitfalls, see the ",[40,83,85],{"href":84},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification process guide",". If you are still evaluating whether to pursue ISO 27001 at all, the ",[40,88,90],{"href":89},"\u002Fnow\u002Fiso27001-certification-guide","ISO 27001 certification guide"," covers the business case and sequencing decisions.",[32,93,95],{"id":94},"iso-270012022-what-changed","ISO 27001:2022 — What changed",[37,97,98],{},"The 2022 revision is the current version of the standard. Two changes matter most for teams implementing ISO 27001 today.",[37,100,101,102,106],{},"First, the control set was restructured. The 2013 edition had 114 controls across 14 domains. ISO 27001:2022 consolidates these into ",[103,104,105],"strong",{},"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,108,109],{},"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,111,113],{"id":112},"annex-a-controls","Annex A controls",[37,115,116,117,121],{},"Annex A of ISO 27001 is the reference control set. The ",[40,118,120],{"href":119},"\u002Fglossary\u002Fannex-a","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,123,124],{},"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,126,127,128,132],{},"For a full breakdown of every theme, example controls in each, and how to prioritize implementation, see the ",[40,129,131],{"href":130},"\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,134,136],{"id":135},"statement-of-applicability-soa","Statement of Applicability (SoA)",[37,138,139,140,144],{},"The ",[40,141,143],{"href":142},"\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,146,147],{},"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,149,150,151,155],{},"See the dedicated guide on the ",[40,152,154],{"href":153},"\u002Fframeworks\u002Fiso27001\u002Fstatement-of-applicability","ISO 27001 Statement of Applicability"," for format examples, justification patterns, and common SoA mistakes.",[32,157,159],{"id":158},"building-your-isms","Building your ISMS",[37,161,162],{},"Implementing ISO 27001 is primarily an exercise in building a functioning ISMS. The standard walks through this in clauses 4 through 10:",[164,165,166,173,179,185,191,197,203],"ul",{},[167,168,169,172],"li",{},[103,170,171],{},"Clause 4 — Context of the organization."," Understand internal and external issues, interested parties, and define the ISMS scope.",[167,174,175,178],{},[103,176,177],{},"Clause 5 — Leadership."," Top management must demonstrate commitment, approve the information security policy, and assign roles.",[167,180,181,184],{},[103,182,183],{},"Clause 6 — Planning."," Identify risks and opportunities, set information security objectives, and plan how to achieve them.",[167,186,187,190],{},[103,188,189],{},"Clause 7 — Support."," Provide resources, competence, awareness, communication, and documented information.",[167,192,193,196],{},[103,194,195],{},"Clause 8 — Operation."," Execute the risk assessment and risk treatment process and operate the ISMS on an ongoing basis.",[167,198,199,202],{},[103,200,201],{},"Clause 9 — Performance evaluation."," Monitor, measure, analyze, evaluate, conduct internal audits, and hold management reviews.",[167,204,205,208],{},[103,206,207],{},"Clause 10 — Improvement."," Handle nonconformities and drive continual improvement.",[37,210,211,212,216],{},"Each clause has mandatory documented information and mandatory activities. The ",[40,213,215],{"href":214},"\u002Fframeworks\u002Fiso27001\u002Fisms-implementation","ISO 27001 ISMS implementation guide"," breaks down exactly what to produce at each stage.",[37,218,219,220,224],{},"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 ",[40,221,223],{"href":222},"\u002Fframeworks\u002Fiso27001\u002Fisms-scope","ISMS scope"," guide walks through how to draw the right boundaries for your business.",[32,226,228],{"id":227},"iso-27001-risk-assessment","ISO 27001 risk assessment",[37,230,231],{},"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,233,234],{},"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,236,237,238,242],{},"For methodology, risk register structure, treatment options, and residual risk handling, see the ",[40,239,241],{"href":240},"\u002Fframeworks\u002Fiso27001\u002Frisk-assessment","ISO 27001 risk assessment guide",".",[32,244,246],{"id":245},"internal-audits-and-management-review","Internal audits and management review",[37,248,249],{},"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,251,252],{},"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,254,255,256,260,261,242],{},"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 ",[40,257,259],{"href":258},"\u002Fframeworks\u002Fiso27001\u002Finternal-audit","internal audit guide"," and the ",[40,262,264],{"href":263},"\u002Fframeworks\u002Fiso27001\u002Fmanagement-review","management review guide",[32,266,268],{"id":267},"nonconformities-and-corrective-action","Nonconformities and corrective action",[37,270,271],{},"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,273,274,275,279],{},"Mature organizations treat nonconformities as valuable signals rather than failures. The ",[40,276,278],{"href":277},"\u002Fframeworks\u002Fiso27001\u002Fnonconformity-and-corrective-action","nonconformity and corrective action"," guide walks through the full CAPA workflow auditors expect to see.",[32,281,283],{"id":282},"continual-improvement","Continual improvement",[37,285,286],{},"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,288,289,290,242],{},"Learn how to set ISMS metrics that auditors respect and leadership actually uses in the ",[40,291,293],{"href":292},"\u002Fframeworks\u002Fiso27001\u002Fcontinual-improvement","continual improvement guide",[32,295,297],{"id":296},"cost-and-timeline","Cost and timeline",[37,299,300],{},"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:",[164,302,303,309,315,321],{},[167,304,305,308],{},[103,306,307],{},"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.",[167,310,311,314],{},[103,312,313],{},"External consulting (optional)."," Gap analysis and implementation support from a consultancy typically runs $20,000 to $100,000 depending on scope.",[167,316,317,320],{},[103,318,319],{},"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.",[167,322,323,326],{},[103,324,325],{},"Platform and tooling."," GRC platforms like episki typically replace $30,000 or more in spreadsheet-driven consulting labor annually.",[37,328,329,330,333],{},"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 ",[40,331,332],{"href":84},"cost and timeline discussion in the certification process guide"," for more detail.",[32,335,337],{"id":336},"choosing-a-certification-body","Choosing a certification body",[37,339,340],{},"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,342,343,344,348],{},"Selection criteria include accreditation scope, industry experience, auditor availability, geographic coverage, and cost transparency. The ",[40,345,347],{"href":346},"\u002Fframeworks\u002Fiso27001\u002Fcertification-body-selection","certification body selection guide"," walks through the full evaluation.",[32,350,352],{"id":351},"surveillance-audits-and-recertification","Surveillance audits and recertification",[37,354,355],{},"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,357,358,359,363],{},"See the ",[40,360,362],{"href":361},"\u002Fframeworks\u002Fiso27001\u002Fsurveillance-audits","surveillance audits guide"," for preparation checklists and what auditors typically sample during year-one and year-two visits.",[32,365,367],{"id":366},"iso-27001-vs-soc-2-vs-nist-csf","ISO 27001 vs SOC 2 vs NIST CSF",[37,369,370],{},"Customers and leadership teams frequently ask how ISO 27001 compares to other frameworks. The short version:",[164,372,373,383],{},[167,374,375,382],{},[103,376,377,378,242],{},"ISO 27001 vs ",[40,379,381],{"href":380},"\u002Fframeworks\u002Fsoc2","SOC 2"," 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.",[167,384,385,388,389,393],{},[103,386,387],{},"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 ",[40,390,392],{"href":391},"\u002Fframeworks\u002Fnistcsf\u002Fmapping-to-other-frameworks","NIST CSF mapping to other frameworks"," for a side-by-side comparison.",[37,395,396,397,399],{},"If you are weighing which framework to pursue first, the ",[40,398,90],{"href":89}," covers framework sequencing for growing companies.",[32,401,403],{"id":402},"getting-certified-with-episki","Getting certified with episki",[37,405,406],{},"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,408,409,410,414,415,419],{},"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 ",[40,411,413],{"href":412},"\u002Fcompare\u002Fvanta","episki vs Vanta"," and ",[40,416,418],{"href":417},"\u002Fcompare\u002Fdrata","episki vs Drata"," for honest side-by-side views.",[37,421,422],{},"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,424,425],{},"Start a free trial, import your controls, and run your first ISO 27001 gap analysis in under an hour.",{"title":427,"searchDepth":428,"depth":428,"links":429},"",2,[430,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445],{"id":34,"depth":428,"text":35},{"id":61,"depth":428,"text":62},{"id":74,"depth":428,"text":75},{"id":94,"depth":428,"text":95},{"id":112,"depth":428,"text":113},{"id":135,"depth":428,"text":136},{"id":158,"depth":428,"text":159},{"id":227,"depth":428,"text":228},{"id":245,"depth":428,"text":246},{"id":267,"depth":428,"text":268},{"id":282,"depth":428,"text":283},{"id":296,"depth":428,"text":297},{"id":336,"depth":428,"text":337},{"id":351,"depth":428,"text":352},{"id":366,"depth":428,"text":367},{"id":402,"depth":428,"text":403},{"title":447,"description":448,"items":449},"ISO 27001 certification checklist inside episki","Everything you need to scope, implement, and certify your ISMS is preloaded in your free trial.",[450,451,452,453,454,455,456],"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":458,"description":459},"Start your ISO 27001 journey today","Import your controls, define your ISMS scope, and generate your first Statement of Applicability in under an hour.","md",{"title":462,"items":463},"ISO 27001 frequently asked questions",[464,467,470,473,476],{"label":465,"content":466},"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":468,"content":469},"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":471,"content":472},"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":474,"content":475},"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":477,"content":478},"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":480,"title":481,"description":482,"links":483},"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.",[484,488],{"label":485,"icon":486,"to":487},"Start ISO 27001 trial","i-lucide-rocket","https:\u002F\u002Fepiski.app\u002Fauth\u002Fregister",{"label":489,"icon":490,"color":491,"variant":492,"to":493,"target":494},"Book a demo","i-lucide-message-circle","neutral","subtle","\u002Fdemo","_blank","2026-04-27",{},true,"\u002Fframeworks\u002Fiso27001",{"headline":500,"title":500,"description":501,"items":502},"ISO 27001 certification resources","Give leadership, auditors, and customers visibility into your ISMS maturity.",[503,506,509],{"title":504,"description":505},"ISMS maturity dashboard","Visual progress across all Annex A domains with gap analysis and trending.",{"title":507,"description":508},"Auditor collaboration portal","Scoped access for certification bodies with evidence requests and Q&A threads.",{"title":510,"description":511},"Customer trust pack","Shareable ISO 27001 certification summary with scope details and control highlights.",{"title":513,"description":514},"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.","iso27001",[517,519,522],{"value":120,"description":518},"Pre-mapped to your control graph with owners, evidence, and review cadences.",{"value":520,"description":521},"60% less prep","Average reduction in Stage 2 audit preparation time with episki's automation.",{"value":523,"description":524},"Continuous compliance","Surveillance audits stay painless with always-current evidence and risk registers.","5.frameworks\u002Fiso27001","aThn2G4vv-MUlfe5mhRJFQHtMgpdfJi3-UMVou77OZs",[528,994,1370,1930,2397,2705,3160,3548,3843,4233,4647,5048],{"id":529,"title":530,"body":531,"description":977,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":980,"navigation":497,"path":130,"relatedTerms":981,"relatedTopics":983,"seo":989,"stem":992,"__hash__":993},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fannex-a-controls.md","ISO 27001 Annex A Controls",{"type":29,"value":532,"toc":957},[533,542,545,549,552,555,559,564,567,570,614,620,624,627,630,674,678,681,684,728,732,735,738,836,840,843,875,882,886,892,895,899,903,909,913,916,920,923,927,930,934,937,941,948,951],[37,534,535,536,538,539,541],{},"Annex A of ",[40,537,43],{"href":498}," is the reference set of information security controls that organizations evaluate and, where applicable, implement within their ",[40,540,48],{"href":47},". The 2022 revision of the standard restructured these controls significantly, consolidating the previous 114 controls across 14 domains into 93 controls organized under four themes.",[37,543,544],{},"Understanding the structure, purpose, and implementation expectations of Annex A is fundamental to building a compliant and effective security program.",[32,546,548],{"id":547},"what-changed-in-iso-270012022","What Changed in ISO 27001:2022",[37,550,551],{},"The 2022 update replaced the 14-domain structure from the 2013 edition with four broader themes. Eleven new controls were introduced to address modern threats and practices. Several existing controls were merged where overlap existed, and all controls received updated guidance in the companion standard ISO 27002:2022.",[37,553,554],{},"Organizations certified under the 2013 version were given a transition period to align with the 2022 structure. New certifications are now assessed against the 2022 edition exclusively.",[32,556,558],{"id":557},"the-four-themes","The Four Themes",[560,561,563],"h3",{"id":562},"_1-organizational-controls-37-controls","1. Organizational Controls (37 Controls)",[37,565,566],{},"Organizational controls address the governance, policy, and procedural foundations of information security. They cover the \"who decides what\" and \"how things work\" aspects of your ISMS.",[37,568,569],{},"Key controls in this theme include:",[164,571,572,578,584,590,596,602,608],{},[167,573,574,577],{},[103,575,576],{},"Policies for information security."," Establishing and maintaining a set of information security policies approved by management.",[167,579,580,583],{},[103,581,582],{},"Roles and responsibilities."," Defining and allocating information security responsibilities across the organization.",[167,585,586,589],{},[103,587,588],{},"Threat intelligence."," Collecting and analyzing information about threats relevant to the organization. This is a new control in 2022.",[167,591,592,595],{},[103,593,594],{},"Information security in project management."," Integrating security considerations into project management practices regardless of project type.",[167,597,598,601],{},[103,599,600],{},"Supplier relationships."," Managing security risks introduced by suppliers and third-party service providers.",[167,603,604,607],{},[103,605,606],{},"Incident management."," Planning, detecting, reporting, and responding to information security incidents.",[167,609,610,613],{},[103,611,612],{},"Business continuity."," Ensuring information security requirements are addressed during disruption.",[37,615,616,617,242],{},"Organizational controls form the backbone of your ISMS and are heavily examined during both Stage 1 and Stage 2 of the ",[40,618,619],{"href":84},"certification process",[560,621,623],{"id":622},"_2-people-controls-8-controls","2. People Controls (8 Controls)",[37,625,626],{},"People controls focus on the human element of information security. Despite being the smallest theme by count, these controls address one of the most significant risk areas.",[37,628,629],{},"Controls in this theme cover:",[164,631,632,638,644,650,656,662,668],{},[167,633,634,637],{},[103,635,636],{},"Screening."," Background verification of personnel before and during employment.",[167,639,640,643],{},[103,641,642],{},"Terms and conditions of employment."," Contractual obligations related to information security.",[167,645,646,649],{},[103,647,648],{},"Information security awareness, education, and training."," Ensuring all personnel understand their security responsibilities.",[167,651,652,655],{},[103,653,654],{},"Disciplinary process."," Formal processes for addressing security policy violations.",[167,657,658,661],{},[103,659,660],{},"Responsibilities after termination or change of employment."," Protecting information when people leave or change roles.",[167,663,664,667],{},[103,665,666],{},"Remote working."," Security measures for personnel working outside traditional office environments. This control was updated significantly in 2022.",[167,669,670,673],{},[103,671,672],{},"Information security event reporting."," Mechanisms for personnel to report suspected security events.",[560,675,677],{"id":676},"_3-physical-controls-14-controls","3. Physical Controls (14 Controls)",[37,679,680],{},"Physical controls protect the tangible assets and environments where information is processed and stored.",[37,682,683],{},"This theme includes controls for:",[164,685,686,692,698,704,710,716,722],{},[167,687,688,691],{},[103,689,690],{},"Physical security perimeters and entry."," Controlling access to buildings, data centers, and secure areas.",[167,693,694,697],{},[103,695,696],{},"Securing offices, rooms, and facilities."," Appropriate physical protection based on risk.",[167,699,700,703],{},[103,701,702],{},"Physical security monitoring."," Surveillance and detection systems.",[167,705,706,709],{},[103,707,708],{},"Protecting against physical and environmental threats."," Fire, flood, power loss, and other environmental risks.",[167,711,712,715],{},[103,713,714],{},"Equipment security."," Protecting hardware from theft, damage, and unauthorized access, including off-site equipment and secure disposal.",[167,717,718,721],{},[103,719,720],{},"Clear desk and clear screen."," Reducing exposure of sensitive information in work areas.",[167,723,724,727],{},[103,725,726],{},"Storage media."," Managing the lifecycle of removable and fixed storage media.",[560,729,731],{"id":730},"_4-technological-controls-34-controls","4. Technological Controls (34 Controls)",[37,733,734],{},"Technological controls address the technical safeguards that protect information systems and data.",[37,736,737],{},"Notable controls include:",[164,739,740,746,752,758,764,770,776,782,788,794,800,806,812,818,824,830],{},[167,741,742,745],{},[103,743,744],{},"User endpoint devices."," Securing laptops, phones, and other devices that access organizational information.",[167,747,748,751],{},[103,749,750],{},"Privileged access rights."," Restricting and monitoring the use of elevated system privileges.",[167,753,754,757],{},[103,755,756],{},"Access control."," Managing who can access what information and systems based on business and security requirements.",[167,759,760,763],{},[103,761,762],{},"Secure authentication."," Implementing strong authentication mechanisms.",[167,765,766,769],{},[103,767,768],{},"Configuration management."," Ensuring systems are configured securely and consistently. This is new in 2022.",[167,771,772,775],{},[103,773,774],{},"Information deletion."," Securely removing information when it is no longer needed. Also new in 2022.",[167,777,778,781],{},[103,779,780],{},"Data masking."," Protecting sensitive data through masking techniques. New in 2022.",[167,783,784,787],{},[103,785,786],{},"Data leakage prevention."," Detecting and preventing unauthorized disclosure of information. New in 2022.",[167,789,790,793],{},[103,791,792],{},"Monitoring activities."," Monitoring systems, networks, and applications for anomalous behavior. New in 2022.",[167,795,796,799],{},[103,797,798],{},"Web filtering."," Controlling access to external websites to reduce exposure to malicious content. New in 2022.",[167,801,802,805],{},[103,803,804],{},"Secure coding."," Applying security principles in software development. New in 2022.",[167,807,808,811],{},[103,809,810],{},"Logging and monitoring."," Recording events and reviewing logs for security purposes.",[167,813,814,817],{},[103,815,816],{},"Network security."," Protecting networks and network services.",[167,819,820,823],{},[103,821,822],{},"Cryptography."," Using encryption and related techniques to protect information confidentiality, integrity, and authenticity.",[167,825,826,829],{},[103,827,828],{},"Vulnerability management."," Identifying and addressing technical vulnerabilities.",[167,831,832,835],{},[103,833,834],{},"Backup."," Maintaining and testing backup copies of information and software.",[32,837,839],{"id":838},"control-attributes","Control Attributes",[37,841,842],{},"ISO 27001:2022 introduced a set of attributes that can be applied to each control, making it easier to filter and organize controls based on different perspectives:",[164,844,845,851,857,863,869],{},[167,846,847,850],{},[103,848,849],{},"Control type:"," Preventive, detective, or corrective.",[167,852,853,856],{},[103,854,855],{},"Information security properties:"," Confidentiality, integrity, or availability.",[167,858,859,862],{},[103,860,861],{},"Cybersecurity concepts:"," Identify, protect, detect, respond, or recover (aligned with NIST CSF).",[167,864,865,868],{},[103,866,867],{},"Operational capabilities:"," Governance, asset management, access control, and other operational groupings.",[167,870,871,874],{},[103,872,873],{},"Security domains:"," Governance and ecosystem, protection, defense, or resilience.",[37,876,877,878,881],{},"These attributes are not mandatory to implement but provide useful ways to map controls to your ",[40,879,880],{"href":240},"risk assessment"," outcomes and to communicate control coverage to different stakeholders.",[32,883,885],{"id":884},"relationship-to-the-statement-of-applicability","Relationship to the Statement of Applicability",[37,887,888,889,891],{},"Every Annex A control must be evaluated and either declared applicable or excluded in your ",[40,890,143],{"href":153},". The SoA documents which controls you have selected, why, and how they are implemented. You cannot simply ignore a control without justification. Even controls that are not applicable must be listed with a rationale for their exclusion.",[37,893,894],{},"This evaluation is driven by your risk assessment. Controls are selected based on the risks they mitigate, regulatory requirements, contractual obligations, and business needs.",[32,896,898],{"id":897},"implementation-approach","Implementation Approach",[560,900,902],{"id":901},"start-with-risk-not-controls","Start with Risk, Not Controls",[37,904,905,906,908],{},"A common mistake is to start by trying to implement all 93 controls and then retrofit risk justifications. The standard requires the opposite flow: identify risks first through your ",[40,907,880],{"href":240}," process, then select controls that treat those risks appropriately.",[560,910,912],{"id":911},"prioritize-based-on-risk-treatment","Prioritize Based on Risk Treatment",[37,914,915],{},"Not all controls carry equal weight for every organization. A cloud-native SaaS company will invest heavily in technological controls around access management, secure coding, and monitoring while spending less effort on physical perimeter security. A manufacturing firm with on-premises data centers will have the opposite emphasis.",[560,917,919],{"id":918},"use-iso-27002-for-guidance","Use ISO 27002 for Guidance",[37,921,922],{},"ISO 27002:2022 is the companion standard that provides detailed implementation guidance for each control. While ISO 27001 tells you what controls exist, ISO 27002 tells you how to implement them. It is not mandatory to follow ISO 27002 prescriptively, but it is an invaluable reference.",[560,924,926],{"id":925},"document-proportionally","Document Proportionally",[37,928,929],{},"Each control needs evidence of implementation, but the level of documentation should be proportionate to the risk and complexity involved. A small organization does not need the same volume of documentation as a multinational enterprise. Auditors look for effectiveness, not paperwork volume.",[560,931,933],{"id":932},"map-controls-to-existing-practices","Map Controls to Existing Practices",[37,935,936],{},"Many organizations already have security practices in place that satisfy Annex A controls without realizing it. During your gap analysis, map existing practices to controls before building new processes. This reduces duplication and avoids creating parallel systems.",[32,938,940],{"id":939},"keeping-controls-current","Keeping Controls Current",[37,942,943,944,947],{},"Annex A controls are not a set-and-forget exercise. Your control implementation should evolve as your risk landscape changes, new threats emerge, and your business grows. Regular internal audits, management reviews, and ",[40,945,946],{"href":361},"surveillance audits"," provide structured checkpoints to assess whether controls remain effective.",[37,949,950],{},"Platforms like episki help organizations maintain a living map between risks, controls, and evidence so that control coverage stays visible and gaps are identified early rather than during an external audit.",[37,952,953,954,956],{},"For a broader view of how ",[40,955,43],{"href":42}," fits into your compliance strategy, explore the full framework overview.",{"title":427,"searchDepth":428,"depth":428,"links":958},[959,960,967,968,969,976],{"id":547,"depth":428,"text":548},{"id":557,"depth":428,"text":558,"children":961},[962,964,965,966],{"id":562,"depth":963,"text":563},3,{"id":622,"depth":963,"text":623},{"id":676,"depth":963,"text":677},{"id":730,"depth":963,"text":731},{"id":838,"depth":428,"text":839},{"id":884,"depth":428,"text":885},{"id":897,"depth":428,"text":898,"children":970},[971,972,973,974,975],{"id":901,"depth":963,"text":902},{"id":911,"depth":963,"text":912},{"id":918,"depth":963,"text":919},{"id":925,"depth":963,"text":926},{"id":932,"depth":963,"text":933},{"id":939,"depth":428,"text":940},"An overview of all 93 Annex A controls in the ISO 27001:2022 standard, organized by their four themes, with guidance on implementation and prioritization.",null,"2026-04-16",{},[515,982],"isms",[984,985,986,987,988],"statement-of-applicability","risk-assessment","isms-implementation","certification-process","surveillance-audits",{"title":990,"description":991},"ISO 27001 Annex A Controls — All 93 Controls Explained (2022)","Explore the 93 Annex A controls in ISO 27001:2022 organized by four themes. Learn implementation approaches and how controls map to your ISMS.","5.frameworks\u002Fiso27001\u002Fannex-a-controls","0iPvCsRN3ufyW68RrURLICsdaAOeZDSPxFbI4OyTGlQ",{"id":995,"title":996,"body":997,"description":1342,"extension":460,"faq":1343,"frameworkSlug":515,"lastUpdated":979,"meta":1360,"navigation":497,"path":346,"relatedTerms":1361,"relatedTopics":1363,"seo":1365,"stem":1368,"__hash__":1369},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fcertification-body-selection.md","Choosing an ISO 27001 Certification Body",{"type":29,"value":998,"toc":1323},[999,1008,1011,1015,1018,1038,1041,1045,1048,1051,1083,1090,1093,1097,1100,1111,1114,1118,1121,1125,1128,1132,1135,1139,1142,1146,1149,1153,1156,1179,1182,1186,1189,1193,1196,1200,1203,1229,1232,1236,1239,1242,1246,1255,1261,1267,1271,1309,1313,1316],[37,1000,1001,1002,1004,1005,1007],{},"You cannot self-certify ",[40,1003,43],{"href":498},". A certificate is only meaningful if it is issued by an accredited certification body that audited your ",[40,1006,48],{"href":214}," against the standard and found it conforming. The certification body you choose will be your audit partner for at least three years through the initial audit, two surveillance audits, and eventual recertification. The decision deserves more care than most teams give it.",[37,1009,1010],{},"This guide walks through what a certification body actually is, how accreditation works, how to evaluate options, and what to ask before signing.",[32,1012,1014],{"id":1013},"what-a-certification-body-does","What a certification body does",[37,1016,1017],{},"A certification body, sometimes called a registrar, is an organization accredited to audit management systems against ISO standards and issue certificates. For ISO 27001, the certification body:",[164,1019,1020,1023,1026,1029,1032,1035],{},[167,1021,1022],{},"Plans the audit engagement based on your scope.",[167,1024,1025],{},"Conducts Stage 1 and Stage 2 audits during initial certification.",[167,1027,1028],{},"Issues your certificate if Stage 2 passes.",[167,1030,1031],{},"Conducts annual surveillance audits.",[167,1033,1034],{},"Conducts full recertification every three years.",[167,1036,1037],{},"Maintains your certificate in their public register.",[37,1039,1040],{},"The certification body's authority comes from its accreditation, not from the certification body itself. Without accreditation, the certificate is essentially a vendor's opinion.",[32,1042,1044],{"id":1043},"accreditation-explained","Accreditation explained",[37,1046,1047],{},"Accreditation is the layer above certification. Accreditation bodies assess certification bodies for competence and impartiality. They do not audit your ISMS directly. They audit the firms that audit your ISMS.",[37,1049,1050],{},"Major accreditation bodies relevant to ISO 27001 include:",[164,1052,1053,1059,1065,1071,1077],{},[167,1054,1055,1058],{},[103,1056,1057],{},"UKAS (United Kingdom Accreditation Service)."," The UK national accreditation body. UKAS accreditation is well-respected globally and often specified in enterprise procurement.",[167,1060,1061,1064],{},[103,1062,1063],{},"ANAB (ANSI National Accreditation Board)."," The US equivalent, part of ANSI. ANAB accreditation is the default for US-headquartered buyers.",[167,1066,1067,1070],{},[103,1068,1069],{},"JAS-ANZ (Joint Accreditation System of Australia and New Zealand)."," Covers Australia and New Zealand.",[167,1072,1073,1076],{},[103,1074,1075],{},"DAkkS (Deutsche Akkreditierungsstelle)."," Germany.",[167,1078,1079,1082],{},[103,1080,1081],{},"A2LA (American Association for Laboratory Accreditation)."," Another US accreditation body covering some certification bodies.",[37,1084,1085,1086,1089],{},"All legitimate accreditation bodies are members of the ",[103,1087,1088],{},"International Accreditation Forum (IAF)",", which operates a multilateral recognition arrangement. An IAF MLA certificate from one member body is recognized by the others. When evaluating a certification body, the core question is: are they accredited for ISO\u002FIEC 27001 by an IAF member?",[37,1091,1092],{},"Non-accredited \"certificates\" exist. Some are issued by firms that never sought accreditation. Some are issued by firms whose accreditation was withdrawn. Enterprise procurement teams increasingly verify accreditation through the IAF CertSearch database before accepting a certificate. A non-accredited certificate may be worse than no certificate because it signals that the customer expected compliance and the supplier cut a corner.",[32,1094,1096],{"id":1095},"major-certification-bodies-in-the-iso-27001-market","Major certification bodies in the ISO 27001 market",[37,1098,1099],{},"Without recommending any specific provider, the ISO 27001 market includes:",[164,1101,1102,1105,1108],{},[167,1103,1104],{},"Multinational certification bodies such as BSI, DNV, TÜV, SGS, and Bureau Veritas, which originated in broader quality and standards certification.",[167,1106,1107],{},"Security-focused firms such as Schellman, Coalfire ISO, A-LIGN, and Prescient Assurance, which also offer SOC 2 and other security attestations.",[167,1109,1110],{},"Regional firms with strong accreditation from specific bodies.",[37,1112,1113],{},"Each has tradeoffs. Larger firms offer geographic coverage and brand recognition. Security-focused firms tend to have deeper technical auditors but may have longer lead times due to demand. Regional firms often offer faster scheduling and lower cost but may lack the brand recognition enterprise customers look for.",[32,1115,1117],{"id":1116},"evaluation-criteria","Evaluation criteria",[37,1119,1120],{},"Use the following criteria to evaluate certification bodies.",[560,1122,1124],{"id":1123},"accreditation-scope","Accreditation scope",[37,1126,1127],{},"Confirm the certification body is accredited specifically for ISO\u002FIEC 27001. Some bodies are accredited for ISO 9001 or other standards but not 27001. Check the accreditation body's register directly, such as the UKAS or ANAB directories, rather than relying on marketing material.",[560,1129,1131],{"id":1130},"industry-and-technology-experience","Industry and technology experience",[37,1133,1134],{},"Auditors vary dramatically in their familiarity with modern technology estates. A cloud-native SaaS company benefits from an auditor who understands AWS shared responsibility, CI\u002FCD security, and SaaS identity patterns. A financial services firm benefits from auditors familiar with PCI overlap. Ask for example clients in your sector and for auditor bios.",[560,1136,1138],{"id":1137},"auditor-availability-and-scheduling","Auditor availability and scheduling",[37,1140,1141],{},"Lead times vary by certification body and by season. Some firms are booking new ISO 27001 clients three to six months out during peak periods. If you have a customer deadline driving certification timing, confirm availability before shortlisting.",[560,1143,1145],{"id":1144},"geographic-coverage","Geographic coverage",[37,1147,1148],{},"If you have multi-site operations, a certification body that can audit all locations is more efficient than coordinating multiple firms. For remote-first companies, ask how the certification body handles remote audits and travel expectations.",[560,1150,1152],{"id":1151},"cost-structure-and-transparency","Cost structure and transparency",[37,1154,1155],{},"Request a detailed proposal that breaks out:",[164,1157,1158,1161,1164,1167,1170,1173,1176],{},[167,1159,1160],{},"Stage 1 audit days and fees.",[167,1162,1163],{},"Stage 2 audit days and fees.",[167,1165,1166],{},"Surveillance audit days and fees for years one and two.",[167,1168,1169],{},"Recertification audit days and fees.",[167,1171,1172],{},"Travel and expenses policy.",[167,1174,1175],{},"Scope change fees.",[167,1177,1178],{},"Certificate maintenance fees.",[37,1180,1181],{},"Be wary of quotes that only cover the initial audit. The full three-year cycle is what matters.",[560,1183,1185],{"id":1184},"customer-reputation","Customer reputation",[37,1187,1188],{},"Ask for references from existing clients, ideally in your industry and size bracket. Talk to those references about audit quality, auditor professionalism, scheduling responsiveness, and how disputes were handled. Social proof from peers matters more than vendor testimonials.",[560,1190,1192],{"id":1191},"audit-approach","Audit approach",[37,1194,1195],{},"Different certification bodies emphasize different audit styles. Some are heavily documentation-focused. Others are more interview-driven. Some are collaborative. Others are adversarial. Ask how they handle findings, how disputes are resolved, and what the escalation path looks like.",[32,1197,1199],{"id":1198},"typical-cost-ranges","Typical cost ranges",[37,1201,1202],{},"For a small to mid-sized technology company with a single-site ISMS scope:",[164,1204,1205,1211,1217,1223],{},[167,1206,1207,1210],{},[103,1208,1209],{},"Stage 1 audit."," One to two auditor days. $3,000 to $8,000.",[167,1212,1213,1216],{},[103,1214,1215],{},"Stage 2 audit."," Three to ten auditor days depending on scope complexity. $10,000 to $35,000.",[167,1218,1219,1222],{},[103,1220,1221],{},"Surveillance audits."," One to three auditor days per year. $5,000 to $15,000 annually.",[167,1224,1225,1228],{},[103,1226,1227],{},"Recertification."," Similar to Stage 2. $10,000 to $30,000 every three years.",[37,1230,1231],{},"Across a three-year cycle, total certification body fees usually land between $40,000 and $90,000 for a mid-sized company. Multi-site scopes and global audits can push this significantly higher.",[32,1233,1235],{"id":1234},"independence-from-consulting","Independence from consulting",[37,1237,1238],{},"ISO 27001 accreditation rules prohibit the same firm from providing consulting or implementation services and then certifying the same client. Many certification bodies have consulting affiliates or offer related services, but the accreditation rules force separation between those and the audit engagement.",[37,1240,1241],{},"If you engaged a consultancy for gap analysis or ISMS implementation, that firm cannot also be your certification body for the same engagement. Plan accordingly and select the certification body independently of your consulting partner.",[32,1243,1245],{"id":1244},"how-this-fits-into-your-isms","How this fits into your ISMS",[37,1247,1248,1249,260,1252,1254],{},"Certification body selection sits between ",[40,1250,1251],{"href":214},"ISMS implementation",[40,1253,619],{"href":84},". Ideally, the certification body is selected three to six months before you plan to begin Stage 1, giving time for scheduling and any pre-audit conversations.",[37,1256,1257,1258,1260],{},"After initial certification, the relationship continues through ",[40,1259,946],{"href":361},". Changing certification bodies is possible but carries some friction: the new firm will usually require a transfer audit to confirm your certificate is valid and in good standing. Most organizations stay with their initial certification body for at least one three-year cycle.",[37,1262,1263,1264,1266],{},"The certification body's audit approach also interacts with your ",[40,1265,223],{"href":222},". A clear scope statement reduces audit days and audit cost. Ambiguous scope drives longer audits.",[32,1268,1270],{"id":1269},"common-pitfalls","Common pitfalls",[164,1272,1273,1279,1285,1291,1297,1303],{},[167,1274,1275,1278],{},[103,1276,1277],{},"Choosing based on price alone."," A cheap audit from an unfamiliar body can fail to carry weight in enterprise procurement and end up costing more in lost deals.",[167,1280,1281,1284],{},[103,1282,1283],{},"Not verifying accreditation."," Marketing sites sometimes overstate accreditation. Check the accreditation body's register directly.",[167,1286,1287,1290],{},[103,1288,1289],{},"Ignoring auditor tenure."," Newly minted ISO 27001 auditors may not spot the issues experienced auditors do. Ask about specific auditors likely to be assigned.",[167,1292,1293,1296],{},[103,1294,1295],{},"Selecting too late."," Scheduling pressure pushes organizations to accept the first available body rather than the best-fit body.",[167,1298,1299,1302],{},[103,1300,1301],{},"Assuming the same firm can audit across all frameworks."," Some certification bodies also issue SOC 2 reports, but ISO 27001 and SOC 2 require different qualifications. Evaluate each separately.",[167,1304,1305,1308],{},[103,1306,1307],{},"Ignoring surveillance audit cost."," A low initial audit with high surveillance fees can be more expensive over three years than a higher initial quote.",[32,1310,1312],{"id":1311},"how-episki-helps","How episki helps",[37,1314,1315],{},"episki helps by keeping your ISMS in an audit-ready state regardless of which certification body you choose. The platform generates the scope statement, Statement of Applicability, evidence pack, and audit trail that every accredited certification body expects. Customers entering certification body conversations can share a clean summary of their programme to get faster, more accurate proposals.",[37,1317,1318,1319,1322],{},"Return to the ",[40,1320,1321],{"href":498},"ISO 27001 framework overview"," for the full certification journey and how certification body selection fits in.",{"title":427,"searchDepth":428,"depth":428,"links":1324},[1325,1326,1327,1328,1337,1338,1339,1340,1341],{"id":1013,"depth":428,"text":1014},{"id":1043,"depth":428,"text":1044},{"id":1095,"depth":428,"text":1096},{"id":1116,"depth":428,"text":1117,"children":1329},[1330,1331,1332,1333,1334,1335,1336],{"id":1123,"depth":963,"text":1124},{"id":1130,"depth":963,"text":1131},{"id":1137,"depth":963,"text":1138},{"id":1144,"depth":963,"text":1145},{"id":1151,"depth":963,"text":1152},{"id":1184,"depth":963,"text":1185},{"id":1191,"depth":963,"text":1192},{"id":1198,"depth":428,"text":1199},{"id":1234,"depth":428,"text":1235},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"How to evaluate and select an ISO 27001 certification body, including accreditation (UKAS, ANAB, JAS-ANZ), cost, scope, and what to ask during selection.",{"items":1344},[1345,1348,1351,1354,1357],{"label":1346,"content":1347},"What is an ISO 27001 certification body?","A certification body, sometimes called a registrar, is an accredited organization that audits your ISMS and issues your ISO 27001 certificate if you pass. Examples include BSI, DNV, TÜV, Schellman, Coalfire ISO, and A-LIGN.",{"label":1349,"content":1350},"What does accreditation mean and why does it matter?","Accreditation is independent oversight of the certification body itself. Accreditation bodies like UKAS in the UK and ANAB in the US audit certification bodies to ensure they are competent and impartial. A certificate from a non-accredited body has limited value in enterprise procurement.",{"label":1352,"content":1353},"How much does an ISO 27001 certification body cost?","Certification audit costs typically range from $15,000 to $40,000 for Stage 1 and Stage 2 combined, depending on scope, complexity, and auditor location. Annual surveillance audits typically run $8,000 to $20,000. Recertification in year three is similar in scale to the original audit.",{"label":1355,"content":1356},"Should I pick the cheapest certification body?","No. The cheapest option is rarely the best. Accreditation status, industry familiarity, auditor availability, and customer reputation usually outweigh small price differences. A cheap audit that your customers do not respect is worse than no audit.",{"label":1358,"content":1359},"Can the same firm that helped us prepare also certify us?","No. ISO 27001 requires certification bodies to be independent. A firm that provided consulting, gap analysis, or implementation support cannot also perform your certification audit. Many firms have separate consulting and certification arms, and the accreditation rules still prohibit overlap on the same client.",{},[515,1362,982],"certification-body",[987,988,1364,986],"isms-scope",{"title":1366,"description":1367},"ISO 27001 Certification Body Selection — UKAS, ANAB & More","Pick the right ISO 27001 certification body. Compare accreditation, cost, industry fit, and auditor availability with a practical evaluation checklist.","5.frameworks\u002Fiso27001\u002Fcertification-body-selection","_OesFcheTLTJMpFIixfiRWtY7P0oEz2AiyQV3Q_iltA",{"id":1371,"title":1372,"body":1373,"description":1921,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":1922,"navigation":497,"path":84,"relatedTerms":1923,"relatedTopics":1924,"seo":1925,"stem":1928,"__hash__":1929},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fcertification-process.md","ISO 27001 Certification Process",{"type":29,"value":1374,"toc":1905},[1375,1381,1384,1388,1394,1397,1400,1403,1435,1438,1442,1445,1484,1487,1491,1494,1497,1517,1520,1524,1527,1530,1562,1565,1585,1588,1592,1595,1670,1673,1676,1705,1709,1719,1722,1726,1729,1733,1794,1798,1831,1835,1874,1878],[37,1376,1377,1378,1380],{},"Achieving ",[40,1379,43],{"href":498}," certification demonstrates to customers, partners, and regulators that your organization manages information security through a systematic, risk-based approach. The certification process can feel opaque if you have never been through it, but it follows a well-defined sequence of stages that are consistent worldwide.",[37,1382,1383],{},"This guide breaks down each phase so you know exactly what to expect, how long it takes, and where organizations commonly stumble.",[32,1385,1387],{"id":1386},"why-pursue-certification","Why Pursue Certification?",[37,1389,1390,1391,1393],{},"Many organizations operate an Information Security Management System (",[40,1392,48],{"href":47},") without seeking formal certification. Certification adds external validation: an accredited certification body independently verifies that your ISMS meets the requirements of ISO\u002FIEC 27001. This is increasingly important when enterprise customers require proof of security maturity during procurement, when regulators accept ISO 27001 as evidence of due diligence, or when your organization wants a structured improvement cycle rather than ad-hoc security efforts.",[32,1395,1396],{"id":336},"Choosing a Certification Body",[37,1398,1399],{},"A certification body (CB), sometimes called a registrar, is the organization that conducts your audit and issues your certificate. Only accredited CBs can issue recognized ISO 27001 certificates. Accreditation is granted by national bodies such as UKAS in the United Kingdom, ANAB in the United States, or JAS-ANZ in Australia and New Zealand.",[37,1401,1402],{},"When selecting a CB, consider:",[164,1404,1405,1411,1417,1423,1429],{},[167,1406,1407,1410],{},[103,1408,1409],{},"Accreditation status."," Confirm the CB is accredited for ISO\u002FIEC 27001 by a member of the International Accreditation Forum (IAF).",[167,1412,1413,1416],{},[103,1414,1415],{},"Industry experience."," Some CBs have deeper expertise in specific sectors like financial services, healthcare, or cloud technology.",[167,1418,1419,1422],{},[103,1420,1421],{},"Auditor availability."," Lead times can vary from weeks to months depending on the CB's schedule.",[167,1424,1425,1428],{},[103,1426,1427],{},"Geographic coverage."," If you have offices in multiple countries, choose a CB that can coordinate auditors across regions.",[167,1430,1431,1434],{},[103,1432,1433],{},"Cost and transparency."," Fees vary. Request a detailed proposal that includes audit days, travel costs, and the surveillance audit schedule.",[37,1436,1437],{},"It is perfectly acceptable to get quotes from several CBs before committing. The CB should be independent and have no consulting relationship with your organization to avoid conflicts of interest.",[32,1439,1441],{"id":1440},"pre-certification-preparation","Pre-Certification Preparation",[37,1443,1444],{},"Before engaging a certification body, most organizations go through a preparation phase that takes anywhere from three to twelve months depending on the maturity of existing security practices. Key activities during this phase include:",[1446,1447,1448,1454,1460,1472,1478],"ol",{},[167,1449,1450,1453],{},[103,1451,1452],{},"Scoping the ISMS."," Define the boundaries of your ISMS including locations, business processes, technologies, and organizational units. The scope statement is foundational and will be scrutinized during the audit.",[167,1455,1456,1459],{},[103,1457,1458],{},"Conducting a gap analysis."," Compare your current practices against the requirements in clauses 4 through 10 of ISO 27001 and the controls listed in Annex A. This reveals what needs to be built, documented, or improved.",[167,1461,1462,1465,1466,1468,1469,1471],{},[103,1463,1464],{},"Implementing the ISMS."," Build or refine your ",[40,1467,880],{"href":240}," process, create your ",[40,1470,143],{"href":153},", deploy controls, and establish the documentation required by the standard.",[167,1473,1474,1477],{},[103,1475,1476],{},"Running an internal audit."," ISO 27001 requires that you perform at least one internal audit before the certification audit. This is your chance to catch nonconformities while there is still time to fix them.",[167,1479,1480,1483],{},[103,1481,1482],{},"Conducting a management review."," Top management must review the ISMS to confirm it remains suitable, adequate, and effective. Document the inputs, decisions, and actions from this review.",[37,1485,1486],{},"Many organizations also run a pre-assessment or readiness review with their chosen CB. This optional step gives auditors a preliminary look at your documentation and controls without the formality of the certification audit.",[32,1488,1490],{"id":1489},"stage-1-audit-documentation-review","Stage 1 Audit — Documentation Review",[37,1492,1493],{},"The Stage 1 audit is the first formal interaction with your certification body. Its primary purpose is to evaluate whether your ISMS documentation is in place and whether your organization is ready for the more detailed Stage 2 audit.",[37,1495,1496],{},"During Stage 1 the auditor will typically:",[164,1498,1499,1505,1508,1511,1514],{},[167,1500,1501,1502,1504],{},"Review your ISMS scope, information security policy, risk assessment methodology, ",[40,1503,143],{"href":153},", and risk treatment plan.",[167,1506,1507],{},"Assess whether internal audits and management reviews have been completed.",[167,1509,1510],{},"Confirm that mandatory documented information exists for all required clauses.",[167,1512,1513],{},"Identify any areas of concern that could become nonconformities in Stage 2.",[167,1515,1516],{},"Visit your primary site (though some CBs conduct Stage 1 remotely for smaller scopes).",[37,1518,1519],{},"The Stage 1 audit usually lasts one to two days for small to mid-sized organizations. At the end the auditor issues a report highlighting any gaps that need to be resolved before Stage 2. There is typically a window of two to six months between Stage 1 and Stage 2 to address findings.",[32,1521,1523],{"id":1522},"stage-2-audit-implementation-verification","Stage 2 Audit — Implementation Verification",[37,1525,1526],{},"Stage 2 is the main certification audit. Auditors verify that your ISMS is not just documented but actually implemented, effective, and operating as described.",[37,1528,1529],{},"Stage 2 activities include:",[164,1531,1532,1538,1544,1550,1556],{},[167,1533,1534,1537],{},[103,1535,1536],{},"Interviews with staff"," across departments to confirm that policies are understood and followed.",[167,1539,1540,1543],{},[103,1541,1542],{},"Evidence sampling."," Auditors select samples of records, logs, change tickets, access reviews, incident reports, and other artifacts to confirm controls are working.",[167,1545,1546,1549],{},[103,1547,1548],{},"Process observation."," Auditors may observe processes like onboarding, change management, or incident handling in real time.",[167,1551,1552,1555],{},[103,1553,1554],{},"Technical verification."," Depending on scope, auditors may review firewall configurations, access control lists, backup procedures, or vulnerability scan results.",[167,1557,1558,1561],{},[103,1559,1560],{},"Evaluation of all Annex A controls"," declared applicable in your SoA.",[37,1563,1564],{},"Stage 2 typically takes three to ten audit days on-site depending on the size and complexity of the scope. At the conclusion the audit team classifies findings into three categories:",[164,1566,1567,1573,1579],{},[167,1568,1569,1572],{},[103,1570,1571],{},"Major nonconformities."," Significant failures that prevent certification until resolved.",[167,1574,1575,1578],{},[103,1576,1577],{},"Minor nonconformities."," Isolated issues that must be corrected, usually within 90 days, but do not block certification.",[167,1580,1581,1584],{},[103,1582,1583],{},"Opportunities for improvement."," Suggestions that are not mandatory but are noted for consideration.",[37,1586,1587],{},"If there are no major nonconformities, the auditor recommends certification. The CB's internal review panel then confirms the recommendation and issues the certificate.",[32,1589,1591],{"id":1590},"realistic-timelines","Realistic Timelines",[37,1593,1594],{},"A realistic timeline from project kickoff to certificate in hand looks roughly like this:",[1596,1597,1598,1611],"table",{},[1599,1600,1601],"thead",{},[1602,1603,1604,1608],"tr",{},[1605,1606,1607],"th",{},"Phase",[1605,1609,1610],{},"Duration",[1612,1613,1614,1623,1630,1638,1646,1654,1662],"tbody",{},[1602,1615,1616,1620],{},[1617,1618,1619],"td",{},"Gap analysis and planning",[1617,1621,1622],{},"1–2 months",[1602,1624,1625,1627],{},[1617,1626,1251],{},[1617,1628,1629],{},"3–9 months",[1602,1631,1632,1635],{},[1617,1633,1634],{},"Internal audit and management review",[1617,1636,1637],{},"1 month",[1602,1639,1640,1643],{},[1617,1641,1642],{},"Stage 1 audit",[1617,1644,1645],{},"1–2 days",[1602,1647,1648,1651],{},[1617,1649,1650],{},"Gap remediation between Stage 1 and Stage 2",[1617,1652,1653],{},"1–3 months",[1602,1655,1656,1659],{},[1617,1657,1658],{},"Stage 2 audit",[1617,1660,1661],{},"3–10 days",[1602,1663,1664,1667],{},[1617,1665,1666],{},"Certificate issuance",[1617,1668,1669],{},"2–6 weeks after Stage 2",[37,1671,1672],{},"For a mid-sized technology company starting from moderate maturity, a nine to twelve month timeline is typical. Organizations with very little existing security structure should plan for twelve to eighteen months.",[32,1674,1675],{"id":1269},"Common Pitfalls",[164,1677,1678,1684,1693,1699],{},[167,1679,1680,1683],{},[103,1681,1682],{},"Underestimating documentation requirements."," ISO 27001 is specific about what must be documented. Missing a mandatory record can result in a nonconformity.",[167,1685,1686,1689,1690,1692],{},[103,1687,1688],{},"Treating it as a one-time project."," Certification is the starting point, not the finish line. You will face ",[40,1691,946],{"href":361}," annually and full recertification every three years.",[167,1694,1695,1698],{},[103,1696,1697],{},"Scope creep or scope too narrow."," A scope that is too broad inflates cost and effort; a scope that is too narrow may not satisfy customer expectations.",[167,1700,1701,1704],{},[103,1702,1703],{},"Lack of management commitment."," The standard explicitly requires top management involvement. Auditors look for evidence of leadership engagement, not just a signed policy.",[32,1706,1708],{"id":1707},"after-certification","After Certification",[37,1710,1711,1712,1714,1715,1718],{},"Receiving your certificate is a milestone, but the certification cycle continues with annual ",[40,1713,946],{"href":361}," and a full recertification audit in year three. Maintaining a living ISMS with current ",[40,1716,1717],{"href":240},"risk assessments",", up-to-date controls, and regular internal audits is essential to keeping your certification active.",[37,1720,1721],{},"Tools like episki help organizations stay audit-ready year-round by linking controls to evidence, automating review schedules, and surfacing gaps before external auditors arrive.",[32,1723,1725],{"id":1724},"certification-readiness-checklist","Certification Readiness Checklist",[37,1727,1728],{},"Use this checklist to track your progress toward ISO 27001 certification:",[560,1730,1732],{"id":1731},"preparation-phase","Preparation phase",[164,1734,1737,1746,1752,1758,1764,1770,1776,1782,1788],{"className":1735},[1736],"contains-task-list",[167,1738,1741,1745],{"className":1739},[1740],"task-list-item",[1742,1743],"input",{"disabled":497,"type":1744},"checkbox"," Define ISMS scope (locations, processes, technologies, and organizational units)",[167,1747,1749,1751],{"className":1748},[1740],[1742,1750],{"disabled":497,"type":1744}," Assign an ISMS owner and project team",[167,1753,1755,1757],{"className":1754},[1740],[1742,1756],{"disabled":497,"type":1744}," Conduct a gap analysis against ISO 27001 clauses 4–10 and Annex A",[167,1759,1761,1763],{"className":1760},[1740],[1742,1762],{"disabled":497,"type":1744}," Complete a risk assessment and produce a risk treatment plan",[167,1765,1767,1769],{"className":1766},[1740],[1742,1768],{"disabled":497,"type":1744}," Draft the Statement of Applicability (SoA)",[167,1771,1773,1775],{"className":1772},[1740],[1742,1774],{"disabled":497,"type":1744}," Write or update required policies (information security policy, access control, acceptable use, etc.)",[167,1777,1779,1781],{"className":1778},[1740],[1742,1780],{"disabled":497,"type":1744}," Implement controls identified in the risk treatment plan",[167,1783,1785,1787],{"className":1784},[1740],[1742,1786],{"disabled":497,"type":1744}," Establish an incident response process",[167,1789,1791,1793],{"className":1790},[1740],[1742,1792],{"disabled":497,"type":1744}," Set up a document control process for ISMS records",[560,1795,1797],{"id":1796},"internal-readiness","Internal readiness",[164,1799,1801,1807,1813,1819,1825],{"className":1800},[1736],[167,1802,1804,1806],{"className":1803},[1740],[1742,1805],{"disabled":497,"type":1744}," Conduct at least one internal audit covering all ISMS clauses",[167,1808,1810,1812],{"className":1809},[1740],[1742,1811],{"disabled":497,"type":1744}," Address nonconformities identified in the internal audit",[167,1814,1816,1818],{"className":1815},[1740],[1742,1817],{"disabled":497,"type":1744}," Hold a formal management review with documented minutes and decisions",[167,1820,1822,1824],{"className":1821},[1740],[1742,1823],{"disabled":497,"type":1744}," Verify all mandatory documented information is complete and current",[167,1826,1828,1830],{"className":1827},[1740],[1742,1829],{"disabled":497,"type":1744}," Confirm staff awareness — key personnel can explain relevant policies and their roles",[560,1832,1834],{"id":1833},"certification-body-engagement","Certification body engagement",[164,1836,1838,1844,1850,1856,1862,1868],{"className":1837},[1736],[167,1839,1841,1843],{"className":1840},[1740],[1742,1842],{"disabled":497,"type":1744}," Research and shortlist accredited certification bodies",[167,1845,1847,1849],{"className":1846},[1740],[1742,1848],{"disabled":497,"type":1744}," Request proposals and confirm accreditation status (IAF member)",[167,1851,1853,1855],{"className":1852},[1740],[1742,1854],{"disabled":497,"type":1744}," Schedule Stage 1 audit",[167,1857,1859,1861],{"className":1858},[1740],[1742,1860],{"disabled":497,"type":1744}," Complete Stage 1 and resolve any findings",[167,1863,1865,1867],{"className":1864},[1740],[1742,1866],{"disabled":497,"type":1744}," Schedule Stage 2 audit",[167,1869,1871,1873],{"className":1870},[1740],[1742,1872],{"disabled":497,"type":1744}," Prepare evidence packs for all applicable Annex A controls",[560,1875,1877],{"id":1876},"post-certification","Post-certification",[164,1879,1881,1887,1893,1899],{"className":1880},[1736],[167,1882,1884,1886],{"className":1883},[1740],[1742,1885],{"disabled":497,"type":1744}," Plan surveillance audit schedule (annually)",[167,1888,1890,1892],{"className":1889},[1740],[1742,1891],{"disabled":497,"type":1744}," Assign ongoing ISMS maintenance responsibilities",[167,1894,1896,1898],{"className":1895},[1740],[1742,1897],{"disabled":497,"type":1744}," Schedule periodic risk reassessments",[167,1900,1902,1904],{"className":1901},[1740],[1742,1903],{"disabled":497,"type":1744}," Set review cadence for policies and the Statement of Applicability",{"title":427,"searchDepth":428,"depth":428,"links":1906},[1907,1908,1909,1910,1911,1912,1913,1914,1915],{"id":1386,"depth":428,"text":1387},{"id":336,"depth":428,"text":1396},{"id":1440,"depth":428,"text":1441},{"id":1489,"depth":428,"text":1490},{"id":1522,"depth":428,"text":1523},{"id":1590,"depth":428,"text":1591},{"id":1269,"depth":428,"text":1675},{"id":1707,"depth":428,"text":1708},{"id":1724,"depth":428,"text":1725,"children":1916},[1917,1918,1919,1920],{"id":1731,"depth":963,"text":1732},{"id":1796,"depth":963,"text":1797},{"id":1833,"depth":963,"text":1834},{"id":1876,"depth":963,"text":1877},"A complete walkthrough of the ISO 27001 certification journey, from selecting a certification body through Stage 1 and Stage 2 audits to achieving certified status.",{},[515,982],[112,985,984,986,988],{"title":1926,"description":1927},"ISO 27001 Certification Process — Stages, Audits & Timeline","Learn every stage of the ISO 27001 certification process including Stage 1 and Stage 2 audits, certification body selection, and realistic timelines.","5.frameworks\u002Fiso27001\u002Fcertification-process","MSlNYNlme0S3E3sHdYpwuiBv3zf4zFP-UzqfRV7RXz0",{"id":1931,"title":1932,"body":1933,"description":2366,"extension":460,"faq":2367,"frameworkSlug":515,"lastUpdated":979,"meta":2384,"navigation":497,"path":292,"relatedTerms":2385,"relatedTopics":2388,"seo":2392,"stem":2395,"__hash__":2396},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fcontinual-improvement.md","ISO 27001 Continual Improvement (Clause 10.3)",{"type":29,"value":1934,"toc":2341},[1935,1944,1947,1951,1954,1957,1977,1980,1984,1987,1990,2007,2010,2014,2017,2021,2028,2032,2038,2042,2045,2049,2052,2056,2062,2066,2069,2073,2076,2080,2083,2086,2112,2115,2119,2136,2140,2151,2155,2169,2173,2187,2191,2205,2208,2212,2215,2218,2232,2238,2242,2245,2265,2268,2270,2276,2279,2285,2287,2331,2333,2336],[37,1936,1937,1938,1940,1941,1943],{},"Clause 10.3 of ",[40,1939,43],{"href":498}," is only two sentences long, but it shapes whether your ",[40,1942,48],{"href":47}," stays alive or calcifies into documentation that everyone ignores. The clause requires the organization to continually improve the suitability, adequacy, and effectiveness of the ISMS. Certification auditors consistently test this by comparing the ISMS today against the ISMS a year ago and asking what actually changed and why.",[37,1945,1946],{},"Continual improvement done well is a strategic muscle. Done poorly, it becomes a checkbox activity where the same three PowerPoint slides get presented annually with no real movement. This guide is about the difference.",[32,1948,1950],{"id":1949},"what-clause-103-requires","What Clause 10.3 requires",[37,1952,1953],{},"The full text of Clause 10.3 is: \"The organization shall continually improve the suitability, adequacy, and effectiveness of the information security management system.\"",[37,1955,1956],{},"Three concepts carry weight in that sentence:",[164,1958,1959,1965,1971],{},[167,1960,1961,1964],{},[103,1962,1963],{},"Suitability."," Is the ISMS appropriate for the organization's context, scope, and risks? As the business changes, suitability can erode even when nothing in the ISMS looks broken.",[167,1966,1967,1970],{},[103,1968,1969],{},"Adequacy."," Does the ISMS actually cover what it needs to cover? Gaps between the documented ISMS and operational reality undermine adequacy.",[167,1972,1973,1976],{},[103,1974,1975],{},"Effectiveness."," Is the ISMS producing the outcomes it is supposed to produce? Reducing risk, preventing incidents, meeting objectives, satisfying interested parties.",[37,1978,1979],{},"Continual improvement targets all three. An audit finding that says \"the ISMS is documented but suitability has drifted\" is just as serious as a finding that a specific control does not work.",[32,1981,1983],{"id":1982},"continual-versus-continuous","Continual versus continuous",[37,1985,1986],{},"ISO 27001 uses \"continual\" deliberately. Continual means improvement in defined cycles with measurable progress. Continuous implies unbroken ongoing change. An ISMS that changes constantly without structure is harder to audit than one that improves in cycles.",[37,1988,1989],{},"Most organizations implement continual improvement through a combination of:",[164,1991,1992,1995,1998,2001],{},[167,1993,1994],{},"Regular measurement against defined metrics.",[167,1996,1997],{},"Periodic improvement planning, often tied to annual objectives.",[167,1999,2000],{},"Documented improvement actions with owners and due dates.",[167,2002,2003,2004,242],{},"Periodic reviews of improvement progress through ",[40,2005,2006],{"href":263},"management review",[37,2008,2009],{},"This maps cleanly to the Plan-Do-Check-Act model that underpins all ISO management system standards.",[32,2011,2013],{"id":2012},"inputs-to-continual-improvement","Inputs to continual improvement",[37,2015,2016],{},"Continual improvement feeds on structured signals from across the ISMS. The most valuable inputs include:",[560,2018,2020],{"id":2019},"audit-findings","Audit findings",[37,2022,2023,2024,2027],{},"Trends in ",[40,2025,2026],{"href":258},"internal audit"," findings reveal systemic weaknesses. Three consecutive audits with access control findings point to a structural issue rather than an isolated problem.",[560,2029,2031],{"id":2030},"nonconformities-and-corrective-actions","Nonconformities and corrective actions",[37,2033,2034,2035,2037],{},"Patterns across the ",[40,2036,278],{"href":277}," log often reveal that localized fixes are not addressing root causes. Clause 10.3 benefits when systemic learnings are extracted from CAPA.",[560,2039,2041],{"id":2040},"incident-and-near-miss-data","Incident and near-miss data",[37,2043,2044],{},"Actual security incidents and near-misses show where controls are failing or where controls are working but are too slow, too noisy, or too fragile to be relied on.",[560,2046,2048],{"id":2047},"metrics-and-kpi-trends","Metrics and KPI trends",[37,2050,2051],{},"Measurement over time beats snapshot measurement. A phishing simulation click rate of 7 percent is not inherently good or bad. A decline from 18 percent to 7 percent over four quarters is powerful evidence of continual improvement.",[560,2053,2055],{"id":2054},"risk-assessment-updates","Risk assessment updates",[37,2057,2058,2059,2061],{},"Changes to the ",[40,2060,880],{"href":240}," over time show whether the organization is actually reducing risk or merely tracking it. Residual risk should trend down or hold steady with a valid reason.",[560,2063,2065],{"id":2064},"customer-and-regulator-feedback","Customer and regulator feedback",[37,2067,2068],{},"Security questionnaire trends, customer-reported issues, regulatory comments, and auditor observations from other engagements all surface improvement opportunities.",[560,2070,2072],{"id":2071},"staff-feedback","Staff feedback",[37,2074,2075],{},"People operating controls daily are often the first to notice friction or failure. Channels for staff to suggest improvements feed the improvement backlog.",[32,2077,2079],{"id":2078},"building-useful-isms-metrics","Building useful ISMS metrics",[37,2081,2082],{},"The quality of your continual improvement is directly proportional to the quality of your metrics. Poor metrics produce vanity dashboards that leadership tolerates for one meeting and ignores thereafter. Good metrics drive decisions.",[37,2084,2085],{},"A useful ISMS metric meets four tests:",[164,2087,2088,2094,2100,2106],{},[167,2089,2090,2093],{},[103,2091,2092],{},"Relevant."," It measures something the organization actually cares about.",[167,2095,2096,2099],{},[103,2097,2098],{},"Measurable."," It can be collected consistently without heroic effort.",[167,2101,2102,2105],{},[103,2103,2104],{},"Actionable."," Changes in the metric lead to specific decisions or actions.",[167,2107,2108,2111],{},[103,2109,2110],{},"Trendable."," It makes sense over time, not just at a single point.",[37,2113,2114],{},"Examples of useful metrics by category:",[560,2116,2118],{"id":2117},"control-effectiveness","Control effectiveness",[164,2120,2121,2124,2127,2130,2133],{},[167,2122,2123],{},"Patch compliance rate against SLA.",[167,2125,2126],{},"Access review completion rate.",[167,2128,2129],{},"Mean time to remediate critical vulnerabilities.",[167,2131,2132],{},"Backup test success rate.",[167,2134,2135],{},"Control coverage against the scope (percentage of in-scope systems with required controls verified).",[560,2137,2139],{"id":2138},"risk","Risk",[164,2141,2142,2145,2148],{},[167,2143,2144],{},"Number of open risks by severity.",[167,2146,2147],{},"Residual risk trend across quarters.",[167,2149,2150],{},"Time to close risk treatments after identification.",[560,2152,2154],{"id":2153},"incident-and-detection","Incident and detection",[164,2156,2157,2160,2163,2166],{},[167,2158,2159],{},"Mean time to detect.",[167,2161,2162],{},"Mean time to respond.",[167,2164,2165],{},"Incident volume by category and trend.",[167,2167,2168],{},"Near-miss reports per quarter.",[560,2170,2172],{"id":2171},"people","People",[164,2174,2175,2178,2181,2184],{},[167,2176,2177],{},"Training completion rate by role.",[167,2179,2180],{},"Phishing simulation click and report rates.",[167,2182,2183],{},"Time from hire to security onboarding completion.",[167,2185,2186],{},"Time from termination to access revocation.",[560,2188,2190],{"id":2189},"isms-operation","ISMS operation",[164,2192,2193,2196,2199,2202],{},[167,2194,2195],{},"Internal audit coverage against plan.",[167,2197,2198],{},"Nonconformity aging.",[167,2200,2201],{},"Management review decision completion rate.",[167,2203,2204],{},"Policy review cadence adherence.",[37,2206,2207],{},"A leadership-facing ISMS dashboard with ten to twenty curated metrics across these categories is far more useful than a hundred-metric report that nobody reads.",[32,2209,2211],{"id":2210},"setting-information-security-objectives","Setting information security objectives",[37,2213,2214],{},"Clause 6.2 requires documented information security objectives that are measurable, monitored, communicated, and updated as appropriate. These objectives are a primary vehicle for continual improvement.",[37,2216,2217],{},"Good ISO 27001 objectives look like:",[164,2219,2220,2223,2226,2229],{},[167,2221,2222],{},"\"Reduce mean time to detect critical security incidents from 18 hours to under 6 hours by end of Q4 2026.\"",[167,2224,2225],{},"\"Achieve 98 percent patch compliance on critical CVEs within 14 days, sustained across four consecutive quarters.\"",[167,2227,2228],{},"\"Reduce phishing simulation click rate below 5 percent organization-wide by year end.\"",[167,2230,2231],{},"\"Close 100 percent of major internal audit findings within 60 days.\"",[37,2233,2234,2235,2237],{},"Each has a defined metric, a baseline, a target, and a timeframe. Each is evaluated during ",[40,2236,2006],{"href":263}," and produces evidence of continual improvement or of gaps requiring correction.",[32,2239,2241],{"id":2240},"demonstrating-continual-improvement-to-auditors","Demonstrating continual improvement to auditors",[37,2243,2244],{},"Certification auditors will not ask \"are you continually improving?\" directly. They will probe for evidence such as:",[164,2246,2247,2250,2253,2256,2259,2262],{},[167,2248,2249],{},"Year-over-year comparison of audit findings, nonconformities, and incidents.",[167,2251,2252],{},"Progress against information security objectives.",[167,2254,2255],{},"Documented decisions from management review that resulted in change.",[167,2257,2258],{},"Metrics trends presented over multiple periods.",[167,2260,2261],{},"Specific improvement actions completed since the last audit.",[167,2263,2264],{},"Evidence that identified improvement opportunities were either pursued, deferred with rationale, or declined with rationale.",[37,2266,2267],{},"A blank section in management review minutes under \"opportunities for improvement\" is a red flag. So is an identical action log across several reviews with no closures.",[32,2269,1245],{"id":1244},[37,2271,2272,2273,2275],{},"Continual improvement sits inside Clause 10 alongside ",[40,2274,278],{"href":277},". Together they form the improvement engine of the ISMS. Clause 10.2 handles specific problems. Clause 10.3 handles systemic progress.",[37,2277,2278],{},"Continual improvement is fed by Clause 9 activities: monitoring, measurement, analysis, evaluation, internal audit, and management review. Without Clause 9 discipline, Clause 10.3 has nothing to act on.",[37,2280,2281,2282,2284],{},"During the ",[40,2283,619],{"href":84},", evidence of continual improvement is particularly important for surveillance audits and recertification. First-time certifiers have less history to show, so auditors focus on whether the improvement machinery exists. Recertification audits focus on whether the machinery actually produced improvement.",[32,2286,1270],{"id":1269},[164,2288,2289,2295,2301,2307,2313,2319,2325],{},[167,2290,2291,2294],{},[103,2292,2293],{},"Metrics that do not drive decisions."," A dashboard that is updated but never discussed in leadership meetings is not functioning.",[167,2296,2297,2300],{},[103,2298,2299],{},"Objectives that are not measurable."," \"Improve security culture\" is not an objective. \"Reduce phishing click rate below 5 percent by year end\" is.",[167,2302,2303,2306],{},[103,2304,2305],{},"Documenting improvement activities that never happen."," Listing initiatives on a roadmap that never start undermines the credibility of the entire ISMS.",[167,2308,2309,2312],{},[103,2310,2311],{},"Treating improvement as a project rather than a practice."," A one-time improvement sprint before an audit does not meet Clause 10.3.",[167,2314,2315,2318],{},[103,2316,2317],{},"Only measuring what is easy."," The easy metrics are often not the meaningful ones.",[167,2320,2321,2324],{},[103,2322,2323],{},"Ignoring regression."," Metrics that get worse over time deserve as much attention as metrics that get better. Regression without explanation is a finding.",[167,2326,2327,2330],{},[103,2328,2329],{},"No link between improvement and strategy."," Continual improvement should connect to business and security strategy, not exist in a compliance silo.",[32,2332,1312],{"id":1311},[37,2334,2335],{},"episki turns continual improvement from a narrative into a running system. The platform tracks ISMS metrics against targets, surfaces trends automatically, links improvement actions back to the controls, risks, and objectives they address, and produces the evidence pack auditors use to confirm Clause 10.3 is operating. Year-over-year comparisons are built in, so teams can present real progress at management reviews and certification audits without assembling it by hand.",[37,2337,1318,2338,2340],{},[40,2339,1321],{"href":498}," for how continual improvement closes the Plan-Do-Check-Act cycle at the heart of the ISMS.",{"title":427,"searchDepth":428,"depth":428,"links":2342},[2343,2344,2345,2354,2361,2362,2363,2364,2365],{"id":1949,"depth":428,"text":1950},{"id":1982,"depth":428,"text":1983},{"id":2012,"depth":428,"text":2013,"children":2346},[2347,2348,2349,2350,2351,2352,2353],{"id":2019,"depth":963,"text":2020},{"id":2030,"depth":963,"text":2031},{"id":2040,"depth":963,"text":2041},{"id":2047,"depth":963,"text":2048},{"id":2054,"depth":963,"text":2055},{"id":2064,"depth":963,"text":2065},{"id":2071,"depth":963,"text":2072},{"id":2078,"depth":428,"text":2079,"children":2355},[2356,2357,2358,2359,2360],{"id":2117,"depth":963,"text":2118},{"id":2138,"depth":963,"text":2139},{"id":2153,"depth":963,"text":2154},{"id":2171,"depth":963,"text":2172},{"id":2189,"depth":963,"text":2190},{"id":2210,"depth":428,"text":2211},{"id":2240,"depth":428,"text":2241},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"Drive ISO 27001 continual improvement under Clause 10.3 with ISMS metrics, KPIs, effectiveness measurement, and trend analysis auditors and leadership respect.",{"items":2368},[2369,2372,2375,2378,2381],{"label":2370,"content":2371},"What does Clause 10.3 of ISO 27001 actually require?","Clause 10.3 requires that the organization continually improve the suitability, adequacy, and effectiveness of the ISMS. It does not prescribe a specific method, but auditors will look for evidence that improvement is planned, measured, and acted on rather than accidental.",{"label":2373,"content":2374},"What is the difference between continual and continuous improvement?","Continual improvement means ongoing improvement with defined intervals and measurable progress. Continuous improvement implies improvement at all times without pause. ISO 27001 uses continual deliberately: the standard expects structured, cyclical improvement rather than perpetual change.",{"label":2376,"content":2377},"What ISMS metrics should we track?","Track metrics that measure control effectiveness, risk reduction, incident trends, audit findings over time, training and awareness, and objective completion. Useful examples include mean time to detect, patch compliance rate, phishing simulation click rate, and access review completion. The best metrics drive decisions, not just reports.",{"label":2379,"content":2380},"How do we demonstrate continual improvement to auditors?","Show measurement over time, documented decisions that changed the ISMS, completed improvement actions, and trend data that indicates progress. A static ISMS that looks identical year over year is hard to present as continually improving.",{"label":2382,"content":2383},"Who owns continual improvement in the ISMS?","The ISMS owner typically coordinates continual improvement activities, but responsibility is distributed. Control owners drive improvements in their areas, top management drives strategic improvement through management review, and staff contribute through feedback and suggestions.",{},[515,982,2386,2387],"continuous-monitoring","monitoring",[2389,2390,2391,987],"internal-audit","management-review","nonconformity-and-corrective-action",{"title":2393,"description":2394},"ISO 27001 Continual Improvement — Clause 10.3 Metrics & KPIs","Operate ISO 27001 Clause 10.3 continual improvement with metrics, KPIs, and effectiveness measurement that drive real ISMS maturity.","5.frameworks\u002Fiso27001\u002Fcontinual-improvement","mOCRTlhApKK2k7KncKvMQlgV4aUg9bEfMsST8_xRWvY",{"id":2398,"title":2399,"body":2400,"description":2677,"extension":460,"faq":2678,"frameworkSlug":515,"lastUpdated":979,"meta":2695,"navigation":497,"path":258,"relatedTerms":2696,"relatedTopics":2699,"seo":2700,"stem":2703,"__hash__":2704},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Finternal-audit.md","ISO 27001 Internal Audit (Clause 9.2)",{"type":29,"value":2401,"toc":2660},[2402,2411,2414,2418,2421,2424,2438,2441,2445,2448,2451,2483,2489,2493,2496,2499,2502,2506,2509,2513,2516,2520,2523,2527,2530,2534,2537,2541,2544,2548,2551,2555,2558,2578,2581,2587,2589,2595,2602,2608,2610,2648,2650,2653],[37,2403,2404,2405,2407,2408,2410],{},"If there is a single activity that separates an ISO 27001 programme that will pass audit from one that will not, it is the internal audit. Clause 9.2 of ",[40,2406,43],{"href":498}," requires that you audit your own ",[40,2409,48],{"href":47}," at planned intervals to confirm it conforms to the standard, to your own requirements, and that it is effectively implemented and maintained. This is not a bureaucratic formality. A well-run internal audit programme is the single best signal of whether your organization is actually operating an ISMS or merely documenting one.",[37,2412,2413],{},"This guide walks through how to plan, staff, execute, evidence, and close out ISO 27001 internal audits so that both Stage 2 and surveillance auditors find a mature, self-correcting programme.",[32,2415,2417],{"id":2416},"what-clause-92-actually-requires","What Clause 9.2 actually requires",[37,2419,2420],{},"Clause 9.2 of ISO 27001 has two subclauses. Clause 9.2.1 requires that the organization conduct internal audits at planned intervals to provide information on whether the ISMS conforms to the organization's own requirements and the requirements of ISO 27001, and whether it is effectively implemented and maintained. Clause 9.2.2 requires that you plan, establish, implement, and maintain an audit programme that includes frequency, methods, responsibilities, planning requirements, and reporting.",[37,2422,2423],{},"In practice, this translates into four expectations that certification auditors will look for:",[164,2425,2426,2429,2432,2435],{},[167,2427,2428],{},"A documented audit programme that covers the full scope of the ISMS over a defined cycle, typically one to three years.",[167,2430,2431],{},"Objective and competent auditors who do not audit their own work.",[167,2433,2434],{},"Evidence-based audit results with findings categorized and documented.",[167,2436,2437],{},"A closure process where findings are tracked through to corrective action.",[37,2439,2440],{},"Teams often treat the audit programme itself as a compliance artifact rather than a plan. Auditors can tell the difference. A real programme shows evidence of actually being followed, including signed schedules, rescheduled audits, and audit reports with real findings.",[32,2442,2444],{"id":2443},"designing-the-audit-programme","Designing the audit programme",[37,2446,2447],{},"The audit programme is the multi-year plan for how your entire ISMS gets audited. For a small to mid-sized organization, a one-year cycle covering every ISO 27001 clause and every applicable Annex A control is typical. Larger organizations often operate a three-year cycle, covering different sections each year so that the full ISMS is audited by the end of the cycle.",[37,2449,2450],{},"A good audit programme defines:",[164,2452,2453,2459,2465,2471,2477],{},[167,2454,2455,2458],{},[103,2456,2457],{},"Scope of each audit."," Which clauses, which controls, which business units, which systems.",[167,2460,2461,2464],{},[103,2462,2463],{},"Frequency."," When each scope is audited. Higher-risk areas such as change management and access control often get more frequent coverage.",[167,2466,2467,2470],{},[103,2468,2469],{},"Methods."," Document review, interviews, observation, sampling of records, technical testing.",[167,2472,2473,2476],{},[103,2474,2475],{},"Auditor assignments."," Who will audit what, and confirmation that they are independent of the area being audited.",[167,2478,2479,2482],{},[103,2480,2481],{},"Reporting requirements."," Format of audit reports, required sign-offs, distribution list.",[37,2484,2485,2486,2488],{},"Build the programme from your ",[40,2487,880],{"href":240}," output rather than auditing everything equally. An access control failure is a higher-impact risk than a minor documentation gap, so access control deserves deeper sampling.",[32,2490,2492],{"id":2491},"auditor-independence-and-competence","Auditor independence and competence",[37,2494,2495],{},"Clause 9.2 requires that auditors be objective and impartial. In plain language: the person who built a control cannot audit that control.",[37,2497,2498],{},"Organizations achieve independence in several ways. Some rotate auditors between teams so that an engineer from the platform team audits the people and HR controls while the HR team audits platform controls. Others use a dedicated internal audit function. Many small companies contract with external consultants to audit areas where no internal independence is possible, such as the single ISMS owner auditing their own programme.",[37,2500,2501],{},"Auditor competence matters as well. Auditors should understand ISO 27001 requirements and auditing practice. ISO 19011 provides guidance on management system auditing and is a good training reference. Certification bodies do not require that internal auditors hold a specific credential, but they will ask how you determined the auditor was competent.",[32,2503,2505],{"id":2504},"running-the-audit-a-practical-flow","Running the audit — a practical flow",[37,2507,2508],{},"The actual audit follows a predictable pattern.",[560,2510,2512],{"id":2511},"_1-opening-meeting","1. Opening meeting",[37,2514,2515],{},"The auditor and the auditees meet to confirm scope, timing, and expectations. For large audits this is formal. For a small scope it can be a short conversation.",[560,2517,2519],{"id":2518},"_2-document-review","2. Document review",[37,2521,2522],{},"The auditor reviews the relevant policies, procedures, and records before or during the audit. This sets up interview questions and evidence requests.",[560,2524,2526],{"id":2525},"_3-interviews","3. Interviews",[37,2528,2529],{},"Auditors interview the people who actually operate the controls. The goal is to confirm that documented processes match real practice. Interviews often reveal process drift that documentation alone cannot.",[560,2531,2533],{"id":2532},"_4-evidence-sampling","4. Evidence sampling",[37,2535,2536],{},"Auditors request samples of records to verify control operation. Examples include a sample of access reviews, a sample of change tickets, a sample of incident records, a sample of backup test logs. Sample sizes should be documented so that the sampling approach is reproducible.",[560,2538,2540],{"id":2539},"_5-observation-and-technical-verification","5. Observation and technical verification",[37,2542,2543],{},"Where relevant, auditors observe processes happening in real time or verify technical configurations. Watching an on-call engineer handle a test alert is often more valuable than reading the incident response policy.",[560,2545,2547],{"id":2546},"_6-closing-meeting-and-draft-findings","6. Closing meeting and draft findings",[37,2549,2550],{},"The auditor debriefs the audited team, outlines preliminary findings, and gives the team a chance to provide additional context before the report is finalized.",[32,2552,2554],{"id":2553},"documenting-findings","Documenting findings",[37,2556,2557],{},"Every internal audit must produce a documented report. The report typically includes:",[164,2559,2560,2563,2566,2569,2572,2575],{},[167,2561,2562],{},"The audit scope and objectives.",[167,2564,2565],{},"The criteria used, which is usually ISO 27001 and your internal policies.",[167,2567,2568],{},"The audit team and their independence.",[167,2570,2571],{},"Methods used and samples reviewed.",[167,2573,2574],{},"Findings, each categorized as a nonconformity, observation, or opportunity for improvement.",[167,2576,2577],{},"Agreed timelines for corrective actions.",[37,2579,2580],{},"Findings should quote the specific requirement that was not met, describe the evidence of the gap, and state who owns the correction. A finding that says \"access reviews are not always completed\" is weaker than one that says \"Clause 9.2 of your Access Control Policy requires quarterly access reviews. Four of ten sampled systems had no documented review in Q1 2026. Owner: IT Operations.\"",[37,2582,2583,2584,2586],{},"Findings then flow into the ",[40,2585,278],{"href":277}," process, where root causes are identified and fixes are tracked to closure.",[32,2588,1245],{"id":1244},[37,2590,2591,2592,2594],{},"Internal audits are one of three major inputs to the ",[40,2593,2006],{"href":263}," required by Clause 9.3. Management review uses internal audit results along with risk changes, incidents, and performance metrics to make decisions about the direction of the ISMS.",[37,2596,2597,2598,2601],{},"Internal audits also interact directly with ",[40,2599,2600],{"href":292},"continual improvement"," under Clause 10.3. Patterns in audit findings over time often reveal systemic weaknesses that individual corrective actions cannot resolve. A mature ISMS uses internal audit trends to justify broader process changes, tooling investments, or staffing adjustments.",[37,2603,2604,2605,2607],{},"For first-time certifiers, at least one full internal audit must be complete before the Stage 2 audit in the ",[40,2606,619],{"href":84},". Certification auditors will ask to see the internal audit programme, the reports, and evidence that findings were tracked and closed.",[32,2609,1270],{"id":1269},[164,2611,2612,2618,2624,2630,2636,2642],{},[167,2613,2614,2617],{},[103,2615,2616],{},"Writing findings but not closing them."," An open finding that sits for a year is worse than no finding at all. It proves the organization does not act on its own audits.",[167,2619,2620,2623],{},[103,2621,2622],{},"Sampling only happy paths."," Pulling the three best-documented change tickets does not prove the change management process works. Randomized or risk-weighted sampling produces credible evidence.",[167,2625,2626,2629],{},[103,2627,2628],{},"Auditing documentation instead of practice."," A control that is beautifully documented but never operated will fail certification. Interviews and observation matter more than document review alone.",[167,2631,2632,2635],{},[103,2633,2634],{},"Single-person audit team for every audit."," If the same person audits every area, independence is fragile. Rotate auditors or introduce external support.",[167,2637,2638,2641],{},[103,2639,2640],{},"Skipping the opening and closing meetings."," These bookend activities create accountability and reduce the risk of disputed findings after the fact.",[167,2643,2644,2647],{},[103,2645,2646],{},"No audit trail of evidence."," Auditors should record what they reviewed, when, and where it came from. Without this, findings are hard to defend.",[32,2649,1312],{"id":1311},[37,2651,2652],{},"episki ships with an ISO 27001 internal audit workflow that generates the audit programme from your control graph, assigns independent auditors based on ownership history, captures evidence directly against the control being audited, and tracks findings through to verified closure. Audit reports export in an auditor-ready format that satisfies Clause 9.2 expectations without pulling days of manual effort from your ISMS owner.",[37,2654,2655,2656,2659],{},"See the full ",[40,2657,2658],{"href":498},"ISO 27001 framework"," for how internal audits connect to the broader certification cycle.",{"title":427,"searchDepth":428,"depth":428,"links":2661},[2662,2663,2664,2665,2673,2674,2675,2676],{"id":2416,"depth":428,"text":2417},{"id":2443,"depth":428,"text":2444},{"id":2491,"depth":428,"text":2492},{"id":2504,"depth":428,"text":2505,"children":2666},[2667,2668,2669,2670,2671,2672],{"id":2511,"depth":963,"text":2512},{"id":2518,"depth":963,"text":2519},{"id":2525,"depth":963,"text":2526},{"id":2532,"depth":963,"text":2533},{"id":2539,"depth":963,"text":2540},{"id":2546,"depth":963,"text":2547},{"id":2553,"depth":428,"text":2554},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"How to plan, conduct, and document ISO 27001 Clause 9.2 internal audits including scheduling, auditor independence, evidence collection, and reporting.",{"items":2679},[2680,2683,2686,2689,2692],{"label":2681,"content":2682},"How often are ISO 27001 internal audits required?","ISO 27001 requires internal audits at planned intervals. Most organizations run at least one full internal audit per year covering all clauses and applicable Annex A controls, often split into smaller audits throughout the year on a rolling programme.",{"label":2684,"content":2685},"Who can perform an ISO 27001 internal audit?","Anyone objective and competent can perform an ISO 27001 internal audit. The key requirement under Clause 9.2 is that auditors do not audit their own work. Many organizations use a mix of internal staff, rotated between teams, and external consultants for areas where internal independence is not possible.",{"label":2687,"content":2688},"What evidence do internal auditors review?","Internal auditors review policies, procedures, the risk register, the Statement of Applicability, control operation evidence such as logs, tickets, access reviews, training records, and meeting minutes. They also interview personnel to confirm practices match documentation.",{"label":2690,"content":2691},"What is the difference between an internal audit and a certification audit?","An internal audit is performed by or on behalf of your organization to assess your own ISMS. A certification audit is performed by an accredited certification body to decide whether to issue a certificate. Internal audits are inputs to management review. Certification audits grant or maintain certification.",{"label":2693,"content":2694},"Do minor nonconformities in an internal audit block certification?","No. Internal audit findings are your early warning system. Finding issues internally is a sign the programme is working. The risk is failing to track and close them, which can then surface as a nonconformity during the external audit.",{},[515,982,2697,2698],"audit-trail","evidence-collection",[2390,2391,987,282],{"title":2701,"description":2702},"ISO 27001 Internal Audit — Clause 9.2 Guide & Checklist","Plan ISO 27001 Clause 9.2 internal audits with proper scheduling, independent auditors, evidence collection, and audit reports auditors respect.","5.frameworks\u002Fiso27001\u002Finternal-audit","8EcVsjllAAQ6BBjLuTHwZuoR-qrrq7v51marcETHLSg",{"id":2706,"title":2707,"body":2708,"description":3151,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":3152,"navigation":497,"path":214,"relatedTerms":3153,"relatedTopics":3154,"seo":3155,"stem":3158,"__hash__":3159},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fisms-implementation.md","ISMS Implementation Guide",{"type":29,"value":2709,"toc":3118},[2710,2719,2723,2726,2752,2755,2759,2763,2766,2770,2776,2782,2788,2793,2797,2800,2803,2806,2812,2818,2824,2827,2831,2834,2837,2840,2848,2854,2865,2871,2875,2878,2881,2884,2890,2896,2902,2908,2914,2917,2921,2924,2927,2930,2936,2942,2948,2954,2958,2961,2964,2967,2973,2979,2986,2992,2996,2999,3002,3005,3011,3017,3020,3024,3027,3074,3077,3081,3087,3093,3099,3112],[37,2711,2712,2713,2715,2716,2718],{},"An Information Security Management System (",[40,2714,48],{"href":47},") is the structured framework of policies, processes, and controls that an organization uses to manage information security risks. ",[40,2717,43],{"href":498}," defines the requirements for establishing, implementing, maintaining, and continually improving an ISMS. This guide walks through each major clause of the standard and translates requirements into practical implementation steps.",[32,2720,2722],{"id":2721},"understanding-the-structure","Understanding the Structure",[37,2724,2725],{},"ISO 27001 clauses 4 through 10 contain the mandatory requirements for the ISMS. These clauses follow the Plan-Do-Check-Act (PDCA) cycle that underpins all ISO management system standards:",[164,2727,2728,2734,2740,2746],{},[167,2729,2730,2733],{},[103,2731,2732],{},"Plan (Clauses 4-6):"," Establish the ISMS context, secure leadership support, and plan for risk treatment.",[167,2735,2736,2739],{},[103,2737,2738],{},"Do (Clause 8):"," Implement the plans.",[167,2741,2742,2745],{},[103,2743,2744],{},"Check (Clause 9):"," Monitor, measure, audit, and review performance.",[167,2747,2748,2751],{},[103,2749,2750],{},"Act (Clause 10):"," Address nonconformities and drive continual improvement.",[37,2753,2754],{},"Clause 7 covers support requirements (resources, competence, awareness, communication, and documentation) that span the entire cycle.",[32,2756,2758],{"id":2757},"clause-4-context-of-the-organization","Clause 4: Context of the Organization",[560,2760,2762],{"id":2761},"what-the-standard-requires","What the Standard Requires",[37,2764,2765],{},"You must understand the internal and external issues relevant to your purpose that affect your ability to achieve the intended outcomes of the ISMS. You must also identify the needs and expectations of interested parties and determine the scope of the ISMS.",[560,2767,2769],{"id":2768},"how-to-implement","How to Implement",[37,2771,2772,2775],{},[103,2773,2774],{},"Identify context."," Document the internal factors (organizational structure, culture, capabilities, governance) and external factors (regulatory environment, market conditions, threat landscape, technology trends) that influence your ISMS.",[37,2777,2778,2781],{},[103,2779,2780],{},"Identify interested parties."," List the stakeholders who have requirements related to information security: customers, regulators, employees, shareholders, suppliers, and partners. Document their specific requirements.",[37,2783,2784,2787],{},[103,2785,2786],{},"Define the ISMS scope."," Write a clear scope statement that specifies which parts of the organization, which locations, which information assets, and which processes are covered. The scope should be achievable and meaningful. It must be available as documented information.",[37,2789,2790,2791,242],{},"A well-defined scope prevents scope creep during implementation and gives auditors a clear boundary for assessment during the ",[40,2792,619],{"href":84},[32,2794,2796],{"id":2795},"clause-5-leadership","Clause 5: Leadership",[560,2798,2762],{"id":2799},"what-the-standard-requires-1",[37,2801,2802],{},"Top management must demonstrate leadership and commitment to the ISMS, establish an information security policy, and assign roles, responsibilities, and authorities.",[560,2804,2769],{"id":2805},"how-to-implement-1",[37,2807,2808,2811],{},[103,2809,2810],{},"Secure executive sponsorship."," Identify a member of senior leadership who will champion the ISMS. This person must actively participate, not just sign documents.",[37,2813,2814,2817],{},[103,2815,2816],{},"Create the information security policy."," Draft a high-level policy that is appropriate to the organization's purpose, includes a commitment to satisfying applicable requirements, and includes a commitment to continual improvement. The policy must be communicated to all personnel.",[37,2819,2820,2823],{},[103,2821,2822],{},"Assign ISMS roles."," Formally assign responsibility for maintaining the ISMS, typically to an Information Security Manager or CISO. Define who is accountable for reporting ISMS performance to top management.",[37,2825,2826],{},"Auditors specifically look for evidence of genuine management engagement, not just signatures. Meeting minutes, resource allocation decisions, and management review records all serve as evidence.",[32,2828,2830],{"id":2829},"clause-6-planning","Clause 6: Planning",[560,2832,2762],{"id":2833},"what-the-standard-requires-2",[37,2835,2836],{},"Plan actions to address risks and opportunities, establish information security objectives, and plan how to achieve them.",[560,2838,2769],{"id":2839},"how-to-implement-2",[37,2841,2842,2845,2846,242],{},[103,2843,2844],{},"Conduct risk assessment."," Follow a defined methodology to identify, analyze, and evaluate information security risks. See the detailed guide on ",[40,2847,228],{"href":240},[37,2849,2850,2853],{},[103,2851,2852],{},"Create the risk treatment plan."," For each risk above your acceptance threshold, document the treatment option (mitigate, transfer, avoid, accept), the specific controls to implement, responsible owners, and timelines.",[37,2855,2856,2859,2860,2862,2863,242],{},[103,2857,2858],{},"Develop the Statement of Applicability."," Evaluate all 93 ",[40,2861,113],{"href":130}," and document applicability decisions in your ",[40,2864,143],{"href":153},[37,2866,2867,2870],{},[103,2868,2869],{},"Set information security objectives."," Define measurable objectives that are consistent with the information security policy. Objectives should be specific enough to be monitored and should be communicated to relevant functions. Examples include reducing incident response time, achieving a patching SLA, or completing security awareness training for all employees.",[32,2872,2874],{"id":2873},"clause-7-support","Clause 7: Support",[560,2876,2762],{"id":2877},"what-the-standard-requires-3",[37,2879,2880],{},"The organization must provide resources, ensure personnel competence, build awareness, establish communications, and manage documented information.",[560,2882,2769],{"id":2883},"how-to-implement-3",[37,2885,2886,2889],{},[103,2887,2888],{},"Allocate resources."," Budget for personnel, tools, training, and external services needed to establish and maintain the ISMS.",[37,2891,2892,2895],{},[103,2893,2894],{},"Ensure competence."," Identify the skills needed for ISMS roles and verify that personnel possess them. Maintain records of education, training, and experience. Where gaps exist, provide training or hire accordingly.",[37,2897,2898,2901],{},[103,2899,2900],{},"Build awareness."," All personnel must be aware of the information security policy, their contribution to the ISMS, and the consequences of not conforming. Awareness programs should be ongoing, not one-time events.",[37,2903,2904,2907],{},[103,2905,2906],{},"Define communication processes."," Determine what information about the ISMS needs to be communicated, when, to whom, and by what methods. This includes internal communications (policy updates, incident notifications) and external communications (customer inquiries, regulatory notifications).",[37,2909,2910,2913],{},[103,2911,2912],{},"Manage documentation."," ISO 27001 requires specific documented information including the scope, policy, risk assessment process, risk treatment plan, SoA, objectives, evidence of competence, operational planning records, risk assessment results, risk treatment results, monitoring and measurement results, internal audit results, management review results, and records of nonconformities and corrective actions.",[37,2915,2916],{},"Establish a documentation control process that covers creation, approval, distribution, revision, and retention. Documents must be available to those who need them and protected against unauthorized changes.",[32,2918,2920],{"id":2919},"clause-8-operation","Clause 8: Operation",[560,2922,2762],{"id":2923},"what-the-standard-requires-4",[37,2925,2926],{},"Plan, implement, and control the processes needed to meet ISMS requirements. Perform risk assessments at planned intervals and implement the risk treatment plan.",[560,2928,2769],{"id":2929},"how-to-implement-4",[37,2931,2932,2935],{},[103,2933,2934],{},"Implement controls."," Deploy the technical, organizational, people, and physical controls identified in your risk treatment plan and SoA. This is typically the most time-consuming phase.",[37,2937,2938,2941],{},[103,2939,2940],{},"Execute operational processes."," Establish the day-to-day processes that keep the ISMS running: change management, incident management, access control procedures, backup procedures, and vendor management.",[37,2943,2944,2947],{},[103,2945,2946],{},"Perform risk assessments."," Conduct risk assessments according to your planned schedule and when significant changes occur. Retain documented results.",[37,2949,2950,2953],{},[103,2951,2952],{},"Manage changes."," When planned changes are needed, control them. When unintended changes occur, review the consequences and take action to mitigate adverse effects.",[32,2955,2957],{"id":2956},"clause-9-performance-evaluation","Clause 9: Performance Evaluation",[560,2959,2762],{"id":2960},"what-the-standard-requires-5",[37,2962,2963],{},"Monitor, measure, analyze, and evaluate the ISMS. Conduct internal audits. Perform management reviews.",[560,2965,2769],{"id":2966},"how-to-implement-5",[37,2968,2969,2972],{},[103,2970,2971],{},"Define monitoring and measurement."," Determine what needs to be monitored (control effectiveness, incident trends, compliance metrics), when, by whom, and how results are analyzed. Common metrics include the number of security incidents, time to patch critical vulnerabilities, training completion rates, and audit finding closure rates.",[37,2974,2975,2978],{},[103,2976,2977],{},"Conduct internal audits."," Plan and execute internal audits at planned intervals. Audits must cover all ISMS requirements and be performed by auditors who are objective and impartial (they should not audit their own work). Document the audit program, criteria, scope, findings, and reports.",[37,2980,2981,2982,2985],{},"Internal audits are critical preparation for external ",[40,2983,2984],{"href":84},"certification audits",". They reveal nonconformities while there is still time to correct them.",[37,2987,2988,2991],{},[103,2989,2990],{},"Perform management reviews."," Top management must review the ISMS at planned intervals. Required inputs include the status of previous review actions, changes in context, feedback on performance (nonconformities, monitoring results, audit results), and opportunities for improvement. Outputs must include decisions and actions related to continual improvement.",[32,2993,2995],{"id":2994},"clause-10-improvement","Clause 10: Improvement",[560,2997,2762],{"id":2998},"what-the-standard-requires-6",[37,3000,3001],{},"Address nonconformities through corrective action and continually improve the ISMS.",[560,3003,2769],{"id":3004},"how-to-implement-6",[37,3006,3007,3010],{},[103,3008,3009],{},"Manage nonconformities."," When a nonconformity is identified (from audits, incidents, reviews, or operational issues), react to it, evaluate the need for corrective action, implement corrections, and review their effectiveness. Maintain records of nonconformities and corrective actions.",[37,3012,3013,3016],{},[103,3014,3015],{},"Drive continual improvement."," Establish mechanisms for identifying and implementing improvements. This can include trend analysis of incidents, benchmarking against industry practices, incorporating lessons learned, and acting on management review outputs.",[37,3018,3019],{},"The PDCA cycle means you are never finished. Each cycle of planning, implementing, checking, and acting should result in an ISMS that is incrementally more effective.",[32,3021,3023],{"id":3022},"documentation-requirements-summary","Documentation Requirements Summary",[37,3025,3026],{},"The following documented information is explicitly required by ISO 27001:",[164,3028,3029,3032,3035,3038,3041,3044,3047,3050,3053,3056,3059,3062,3065,3068,3071],{},[167,3030,3031],{},"ISMS scope (4.3)",[167,3033,3034],{},"Information security policy (5.2)",[167,3036,3037],{},"Risk assessment process (6.1.2)",[167,3039,3040],{},"Risk treatment plan (6.1.3)",[167,3042,3043],{},"Statement of Applicability (6.1.3)",[167,3045,3046],{},"Information security objectives (6.2)",[167,3048,3049],{},"Evidence of competence (7.2)",[167,3051,3052],{},"Documented information determined as necessary (7.5.1)",[167,3054,3055],{},"Operational planning and control (8.1)",[167,3057,3058],{},"Risk assessment results (8.2)",[167,3060,3061],{},"Risk treatment results (8.3)",[167,3063,3064],{},"Monitoring and measurement results (9.1)",[167,3066,3067],{},"Internal audit program and results (9.2)",[167,3069,3070],{},"Management review results (9.3)",[167,3072,3073],{},"Nonconformities and corrective actions (10.1)",[37,3075,3076],{},"Beyond these mandatory items, organizations typically create additional documentation including procedures, work instructions, technical standards, and operational guides. The volume should be proportionate to organizational size and complexity.",[32,3078,3080],{"id":3079},"practical-tips","Practical Tips",[37,3082,3083,3086],{},[103,3084,3085],{},"Start small and iterate."," You do not need to have everything perfect before starting. Implement the core processes, run a cycle, and improve based on what you learn.",[37,3088,3089,3092],{},[103,3090,3091],{},"Engage the whole organization."," An ISMS is not an IT project. It requires participation from HR, legal, operations, facilities, and every department that handles information within scope.",[37,3094,3095,3098],{},[103,3096,3097],{},"Automate where possible."," Manual evidence collection and documentation management become unsustainable as the ISMS matures. Platforms like episki automate control tracking, evidence linking, and review scheduling to reduce operational overhead.",[37,3100,3101,3104,3105,3108,3109,3111],{},[103,3102,3103],{},"Plan for surveillance from day one."," After ",[40,3106,3107],{"href":84},"certification",", you will face annual ",[40,3110,946],{"href":361},". Building sustainable processes from the start is far easier than retrofitting them later.",[37,3113,3114,3115,3117],{},"Learn more about how ",[40,3116,43],{"href":42}," works as a comprehensive framework for information security management.",{"title":427,"searchDepth":428,"depth":428,"links":3119},[3120,3121,3125,3129,3133,3137,3141,3145,3149,3150],{"id":2721,"depth":428,"text":2722},{"id":2757,"depth":428,"text":2758,"children":3122},[3123,3124],{"id":2761,"depth":963,"text":2762},{"id":2768,"depth":963,"text":2769},{"id":2795,"depth":428,"text":2796,"children":3126},[3127,3128],{"id":2799,"depth":963,"text":2762},{"id":2805,"depth":963,"text":2769},{"id":2829,"depth":428,"text":2830,"children":3130},[3131,3132],{"id":2833,"depth":963,"text":2762},{"id":2839,"depth":963,"text":2769},{"id":2873,"depth":428,"text":2874,"children":3134},[3135,3136],{"id":2877,"depth":963,"text":2762},{"id":2883,"depth":963,"text":2769},{"id":2919,"depth":428,"text":2920,"children":3138},[3139,3140],{"id":2923,"depth":963,"text":2762},{"id":2929,"depth":963,"text":2769},{"id":2956,"depth":428,"text":2957,"children":3142},[3143,3144],{"id":2960,"depth":963,"text":2762},{"id":2966,"depth":963,"text":2769},{"id":2994,"depth":428,"text":2995,"children":3146},[3147,3148],{"id":2998,"depth":963,"text":2762},{"id":3004,"depth":963,"text":2769},{"id":3022,"depth":428,"text":3023},{"id":3079,"depth":428,"text":3080},"A step-by-step guide to implementing an Information Security Management System aligned with ISO 27001 clauses 4 through 10, including documentation requirements and practical advice.",{},[515,982],[985,112,984,987,988],{"title":3156,"description":3157},"ISMS Implementation Guide for ISO 27001 — Step-by-Step (Clauses 4-10)","Implement your ISMS with this step-by-step ISO 27001 guide covering clauses 4-10, documentation requirements, and practical implementation advice.","5.frameworks\u002Fiso27001\u002Fisms-implementation","dA5km-AiOdo_UVdB7QLLNNeCYkQVBlPFeRQL-lgBKBE",{"id":3161,"title":3162,"body":3163,"description":3521,"extension":460,"faq":3522,"frameworkSlug":515,"lastUpdated":979,"meta":3539,"navigation":497,"path":222,"relatedTerms":3540,"relatedTopics":3541,"seo":3543,"stem":3546,"__hash__":3547},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fisms-scope.md","ISO 27001 ISMS Scope — Boundaries, Interfaces, and Context",{"type":29,"value":3164,"toc":3503},[3165,3168,3177,3181,3184,3204,3207,3211,3214,3218,3221,3225,3228,3232,3235,3239,3242,3246,3249,3253,3256,3260,3263,3266,3292,3295,3299,3302,3305,3337,3340,3344,3347,3350,3367,3370,3387,3392,3396,3399,3419,3424,3426,3444,3447,3449,3493,3495,3498],[37,3166,3167],{},"The scope statement is the shortest document in your ISMS and the one with the most leverage. It decides what your ISO 27001 certificate covers and what it does not. Certification auditors read it first. Enterprise customers read it when evaluating your certificate. And the scope you set determines how much effort, cost, and risk your ISMS programme carries for years.",[37,3169,3170,3171,3173,3174,3176],{},"Clause 4.3 of ",[40,3172,43],{"href":498}," requires that the organization determine the boundaries and applicability of the ",[40,3175,48],{"href":47}," to establish its scope. That sounds simple. In practice, scope decisions are where many ISO 27001 programmes quietly set themselves up for trouble.",[32,3178,3180],{"id":3179},"what-iso-27001-requires","What ISO 27001 requires",[37,3182,3183],{},"Clause 4.3 has three inputs that must be considered when setting scope:",[164,3185,3186,3192,3198],{},[167,3187,3188,3191],{},[103,3189,3190],{},"The external and internal issues identified under Clause 4.1."," Market conditions, regulatory landscape, internal culture, technology dependencies.",[167,3193,3194,3197],{},[103,3195,3196],{},"The requirements of interested parties identified under Clause 4.2."," Customers, regulators, investors, employees, partners, and their relevant information security expectations.",[167,3199,3200,3203],{},[103,3201,3202],{},"The interfaces and dependencies between activities performed by the organization and those performed by other organizations."," Cloud providers, managed services, contractors, subsidiaries, and shared services.",[37,3205,3206],{},"The scope must be available as documented information. Most organizations produce a formal scope statement as part of the ISMS manual, with enough detail to stand on its own if extracted.",[32,3208,3210],{"id":3209},"what-a-scope-statement-should-include","What a scope statement should include",[37,3212,3213],{},"A credible ISO 27001 scope statement covers six dimensions:",[560,3215,3217],{"id":3216},"_1-organizational-boundaries","1. Organizational boundaries",[37,3219,3220],{},"Which legal entities, business units, divisions, or subsidiaries are covered. If your parent company operates multiple regulated subsidiaries, the scope should be explicit about which are included.",[560,3222,3224],{"id":3223},"_2-locations","2. Locations",[37,3226,3227],{},"Physical and logical locations within scope. Offices, data centers, colocation facilities, remote work arrangements, and cloud regions. For distributed organizations, scope often covers specific regions or excludes locations without in-scope activities.",[560,3229,3231],{"id":3230},"_3-products-and-services","3. Products and services",[37,3233,3234],{},"Which products or services the ISMS protects. A SaaS company might scope its ISMS to the production platform and supporting functions, explicitly excluding unrelated consulting arms.",[560,3236,3238],{"id":3237},"_4-processes","4. Processes",[37,3240,3241],{},"Which business processes are within scope. Customer data processing, product development, incident response, HR onboarding, finance, and so on. Processes that handle in-scope information must be included even if they sit in a business function that is otherwise out of scope.",[560,3243,3245],{"id":3244},"_5-technology","5. Technology",[37,3247,3248],{},"Which systems, platforms, and infrastructure are within scope. This often overlaps with products and services but should also call out supporting tooling like identity providers, monitoring platforms, collaboration tools, and ticketing systems.",[560,3250,3252],{"id":3251},"_6-information-types","6. Information types",[37,3254,3255],{},"Which information assets the ISMS protects. Customer data, intellectual property, employee records, financial data, or specific regulated data types.",[32,3257,3259],{"id":3258},"defining-boundaries","Defining boundaries",[37,3261,3262],{},"Boundaries are the edges of your ISMS. Inside the boundary, ISO 27001 controls apply. Outside, they do not. Clear boundaries prevent audit disputes about whether a control failure falls within scope.",[37,3264,3265],{},"Boundaries should be drawn by:",[164,3267,3268,3274,3280,3286],{},[167,3269,3270,3273],{},[103,3271,3272],{},"Logical separation."," Networks, accounts, environments, and data flows that can be cleanly isolated from out-of-scope systems.",[167,3275,3276,3279],{},[103,3277,3278],{},"Organizational separation."," Distinct teams, reporting lines, and access controls between in-scope and out-of-scope operations.",[167,3281,3282,3285],{},[103,3283,3284],{},"Physical separation."," Different buildings, floors, or secured areas.",[167,3287,3288,3291],{},[103,3289,3290],{},"Contractual separation."," Documented agreements with parent entities, subsidiaries, or shared service providers that clarify responsibility.",[37,3293,3294],{},"Where separation is weaker, the case for including those adjacent activities in scope strengthens. Trying to carve a tight scope through tightly integrated operations creates more risk than it saves.",[32,3296,3298],{"id":3297},"defining-interfaces","Defining interfaces",[37,3300,3301],{},"Interfaces are where in-scope activities meet out-of-scope activities, either inside your organization or with third parties. Clause 4.3 specifically requires that interfaces be considered when scoping. Auditors will ask how you handle each interface.",[37,3303,3304],{},"Typical interfaces include:",[164,3306,3307,3313,3319,3325,3331],{},[167,3308,3309,3312],{},[103,3310,3311],{},"Cloud providers."," You consume their services. They provide infrastructure, platform, or software controls. Your ISMS covers how you use their services, configure them, and manage your responsibilities under the shared responsibility model.",[167,3314,3315,3318],{},[103,3316,3317],{},"Managed service providers."," Third parties operating in-scope activities on your behalf. Scope should address contractual controls, monitoring, and right to audit.",[167,3320,3321,3324],{},[103,3322,3323],{},"Parent or sister companies."," Shared HR, finance, IT, or security functions that cross the ISMS boundary. Scope should clarify how those shared functions are controlled.",[167,3326,3327,3330],{},[103,3328,3329],{},"Contractors and consultants."," Time-limited access to in-scope systems or data. Scope should describe how access is governed.",[167,3332,3333,3336],{},[103,3334,3335],{},"Customer-facing interfaces."," How customer data flows in and out, and where responsibility transitions.",[37,3338,3339],{},"A common auditor test is to trace a piece of customer data through every interface and confirm that controls and responsibilities are clear at each boundary crossing.",[32,3341,3343],{"id":3342},"organizational-context-clause-41","Organizational context (Clause 4.1)",[37,3345,3346],{},"Clause 4.1 requires the organization to determine external and internal issues relevant to its purpose that affect its ability to achieve the intended outcomes of the ISMS. The scope flows from this context.",[37,3348,3349],{},"External issues commonly include:",[164,3351,3352,3355,3358,3361,3364],{},[167,3353,3354],{},"Regulatory environment. GDPR, HIPAA, state privacy laws, sector regulation.",[167,3356,3357],{},"Customer expectations. Enterprise procurement requirements, vertical-specific standards.",[167,3359,3360],{},"Threat landscape. Ransomware trends, supply chain attacks, relevant threat actors.",[167,3362,3363],{},"Technology trends. Cloud adoption, AI integration, remote work norms.",[167,3365,3366],{},"Economic and geopolitical conditions. Sanctions, export controls, market pressures.",[37,3368,3369],{},"Internal issues commonly include:",[164,3371,3372,3375,3378,3381,3384],{},[167,3373,3374],{},"Organizational structure. Growth stage, distributed or centralized operations.",[167,3376,3377],{},"Culture. Security maturity, engineering velocity, risk tolerance.",[167,3379,3380],{},"Technology estate. Legacy systems, cloud-native architecture, SaaS sprawl.",[167,3382,3383],{},"Resourcing. Team size, budget constraints, leadership engagement.",[167,3385,3386],{},"Change pace. Product release frequency, M&A activity, reorganizations.",[37,3388,3389,3390,242],{},"The context analysis is usually captured in a short document that feeds into the scope statement and into ",[40,3391,880],{"href":240},[32,3393,3395],{"id":3394},"interested-parties-clause-42","Interested parties (Clause 4.2)",[37,3397,3398],{},"Clause 4.2 requires identifying interested parties relevant to the ISMS and their relevant requirements. Interested parties typically include:",[164,3400,3401,3404,3407,3410,3413,3416],{},[167,3402,3403],{},"Customers, particularly enterprise and regulated customers with security requirements in contracts.",[167,3405,3406],{},"Regulators whose rules touch the in-scope information or services.",[167,3408,3409],{},"Employees, whose data is typically in scope and who depend on the ISMS for their own protection.",[167,3411,3412],{},"Shareholders and investors.",[167,3414,3415],{},"Partners and suppliers.",[167,3417,3418],{},"Certification bodies and accreditation bodies.",[37,3420,3421,3422,242],{},"For each, record the requirements relevant to the ISMS. Customer security addenda, regulatory obligations, and investor due diligence expectations all inform scope and control decisions. These requirements also frequently drive the ",[40,3423,143],{"href":153},[32,3425,1245],{"id":1244},[37,3427,3428,3429,3431,3432,3434,3435,3437,3438,3441,3442,242],{},"Scope sits at the foundation of the entire ISMS. Everything downstream depends on it. ",[40,3430,1251],{"href":214}," builds inside the scope boundary. The ",[40,3433,143],{"href":153}," selects controls for the scope. The ",[40,3436,880],{"href":240}," assesses risks to assets within scope. The ",[40,3439,3440],{"href":346},"certification body"," audits against scope during the ",[40,3443,619],{"href":84},[37,3445,3446],{},"When scope changes, everything downstream must be reviewed. Adding a new product line, a new office, or a major new service usually triggers a scope update that cascades through the rest of the ISMS.",[32,3448,1270],{"id":1269},[164,3450,3451,3457,3463,3469,3475,3481,3487],{},[167,3452,3453,3456],{},[103,3454,3455],{},"Scope too narrow."," Excluding activities that customers expect to be covered. A SaaS scope that excludes the shared identity provider used by the platform will raise procurement objections.",[167,3458,3459,3462],{},[103,3460,3461],{},"Scope too broad."," Including every activity in the organization inflates audit cost and effort. Consulting practices, sales operations, and unrelated business lines often do not belong.",[167,3464,3465,3468],{},[103,3466,3467],{},"Vague scope statement."," \"All operations\" is not a scope. Auditors need specificity.",[167,3470,3471,3474],{},[103,3472,3473],{},"Ignoring interfaces."," Cloud providers, shared services, and contractors are almost always in scope in some capacity and must be addressed.",[167,3476,3477,3480],{},[103,3478,3479],{},"Copying scope from a competitor's certificate."," What works for one organization may not match yours.",[167,3482,3483,3486],{},[103,3484,3485],{},"Failing to revisit scope."," Business changes quickly. A scope written in year one may not match the organization by year three.",[167,3488,3489,3492],{},[103,3490,3491],{},"Disconnection between scope and SoA."," Controls listed as applicable in the SoA must cover the scope described in the scope statement.",[32,3494,1312],{"id":1311},[37,3496,3497],{},"episki captures your ISMS scope, interfaces, interested parties, and organizational context as structured data rather than a static document. When scope changes, downstream controls, risks, and SoA entries are flagged for review automatically. The platform produces a clean, auditor-ready scope statement linked to the supporting context artifacts so certification bodies and customers can understand exactly what the ISMS covers.",[37,3499,1318,3500,3502],{},[40,3501,1321],{"href":498}," for how scope connects to the full certification journey.",{"title":427,"searchDepth":428,"depth":428,"links":3504},[3505,3506,3514,3515,3516,3517,3518,3519,3520],{"id":3179,"depth":428,"text":3180},{"id":3209,"depth":428,"text":3210,"children":3507},[3508,3509,3510,3511,3512,3513],{"id":3216,"depth":963,"text":3217},{"id":3223,"depth":963,"text":3224},{"id":3230,"depth":963,"text":3231},{"id":3237,"depth":963,"text":3238},{"id":3244,"depth":963,"text":3245},{"id":3251,"depth":963,"text":3252},{"id":3258,"depth":428,"text":3259},{"id":3297,"depth":428,"text":3298},{"id":3342,"depth":428,"text":3343},{"id":3394,"depth":428,"text":3395},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"Define an ISO 27001 ISMS scope that satisfies auditors and customers, covering boundaries, interfaces, interested parties, and organizational context.",{"items":3523},[3524,3527,3530,3533,3536],{"label":3525,"content":3526},"What is the ISMS scope in ISO 27001?","The ISMS scope defines the boundaries of your information security management system. It states which business units, locations, processes, technologies, and information are covered by the ISMS and, by extension, by your ISO 27001 certificate.",{"label":3528,"content":3529},"Can the ISMS scope cover only part of the organization?","Yes. ISO 27001 allows a scope limited to specific business lines, products, or locations. However, the boundaries must be justified, and interfaces with out-of-scope parts of the organization must be defined and controlled. Customers may probe the scope to ensure it covers what matters to them.",{"label":3531,"content":3532},"What is the difference between scope and Statement of Applicability?","The scope defines what the ISMS covers. The Statement of Applicability defines which Annex A controls apply within that scope. Scope is about boundaries. The SoA is about control selection.",{"label":3534,"content":3535},"Do I need to include all cloud services in scope?","Yes, if they process or store information within the ISMS scope. You need to describe the interface with cloud providers, the responsibilities handled by those providers, and the controls you apply to the services. The cloud provider itself is not certified under your ISMS, but your use of it must be.",{"label":3537,"content":3538},"How often should I review the ISMS scope?","Review scope at least annually as part of management review, and whenever significant change occurs such as a new business line, acquisition, major product launch, or geographic expansion.",{},[515,982,984],[986,984,3542,987],"certification-body-selection",{"title":3544,"description":3545},"ISO 27001 ISMS Scope — Define Boundaries & Interfaces","Define your ISO 27001 ISMS scope with clear boundaries, interfaces, interested parties, and context. Avoid scoping mistakes that fail audits.","5.frameworks\u002Fiso27001\u002Fisms-scope","s9ML_L2njzE8Qcwzv2Q-w0FJdwLGCcsUhG9cfDUoMgE",{"id":3549,"title":3550,"body":3551,"description":3816,"extension":460,"faq":3817,"frameworkSlug":515,"lastUpdated":979,"meta":3834,"navigation":497,"path":263,"relatedTerms":3835,"relatedTopics":3837,"seo":3838,"stem":3841,"__hash__":3842},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fmanagement-review.md","ISO 27001 Management Review (Clause 9.3)",{"type":29,"value":3552,"toc":3805},[3553,3562,3565,3569,3572,3575,3579,3582,3585,3589,3592,3666,3669,3673,3676,3708,3711,3715,3718,3721,3725,3728,3742,3745,3747,3750,3755,3757,3795,3797,3800],[37,3554,3555,3556,3558,3559,3561],{},"Clause 9.3 of ",[40,3557,43],{"href":498}," requires top management to review the organization's ",[40,3560,48],{"href":47}," at planned intervals to ensure its continuing suitability, adequacy, and effectiveness. Of all the clauses in ISO 27001, this is the one where certification auditors most consistently find weak evidence. A calendar invite titled \"Security Review\" with no agenda, no minutes, and no decisions will not pass Stage 2.",[37,3563,3564],{},"Management review is also the clause where ISO 27001 most clearly communicates a cultural expectation: information security is a leadership responsibility, not a technical hobby. Done well, the management review becomes one of the most valuable recurring events in the security calendar because it forces leadership to see the ISMS as it really is, not how anyone wishes it looked.",[32,3566,3568],{"id":3567},"what-clause-93-requires","What Clause 9.3 requires",[37,3570,3571],{},"Clause 9.3.1 requires top management to review the ISMS at planned intervals to ensure it remains suitable, adequate, and effective. Clause 9.3.2 lists specific required inputs. Clause 9.3.3 requires that outputs of the review include decisions related to continual improvement opportunities and any need for changes to the ISMS, and that the organization retain documented information as evidence of the results of management reviews.",[37,3573,3574],{},"The implication is that management review is not just a meeting. It is an evidence-producing event with defined inputs, documented decisions, and traceable outputs.",[32,3576,3578],{"id":3577},"cadence-how-often-to-review","Cadence — how often to review",[37,3580,3581],{},"The standard says \"at planned intervals\" without prescribing a specific cadence. In practice, certification bodies expect at least one comprehensive management review per year covering all required inputs. Many organizations run a lighter quarterly review focused on specific topics like risk changes, audit findings, or metrics trends, and reserve the full review for an annual off-site or strategic session.",[37,3583,3584],{},"Very high-growth companies or those in heavily regulated industries sometimes run monthly management reviews. Smaller or more stable organizations can credibly operate on an annual cycle. Whatever cadence you choose, document it in your ISMS procedures and stick to it. Auditors will ask when the last review happened and compare that against your stated cadence.",[32,3586,3588],{"id":3587},"required-inputs","Required inputs",[37,3590,3591],{},"Clause 9.3.2 lists the inputs the review must consider. A complete management review agenda covers:",[164,3593,3594,3600,3606,3612,3618,3627,3636,3645,3651,3660],{},[167,3595,3596,3599],{},[103,3597,3598],{},"Status of actions from previous management reviews."," Which decisions were executed, which are still in progress, which were dropped and why.",[167,3601,3602,3605],{},[103,3603,3604],{},"Changes in external and internal issues relevant to the ISMS."," Regulatory shifts, new customers with different requirements, major technology changes, organizational restructuring.",[167,3607,3608,3611],{},[103,3609,3610],{},"Feedback on information security performance."," Metrics on incidents, control effectiveness, training completion, phishing simulation results, patch compliance.",[167,3613,3614,3617],{},[103,3615,3616],{},"Feedback from interested parties."," Customer security questionnaires, regulatory feedback, auditor observations from external parties.",[167,3619,3620,3623,3624,3626],{},[103,3621,3622],{},"Results of risk assessment and risk treatment plan status."," Changes to the ",[40,3625,880],{"href":240},", new risks identified, status of risk treatments.",[167,3628,3629,3632,3633,3635],{},[103,3630,3631],{},"Opportunities for continual improvement."," Ideas surfaced from internal ",[40,3634,2600],{"href":292}," efforts, staff suggestions, or industry changes.",[167,3637,3638,3641,3642,242],{},[103,3639,3640],{},"Nonconformities and corrective actions."," Status of open and closed ",[40,3643,3644],{"href":277},"nonconformities and corrective actions",[167,3646,3647,3650],{},[103,3648,3649],{},"Monitoring and measurement results."," KPIs tracked against the ISMS.",[167,3652,3653,3656,3657,3659],{},[103,3654,3655],{},"Audit results."," Internal audit findings from the ",[40,3658,2026],{"href":258}," programme and external audit findings if any.",[167,3661,3662,3665],{},[103,3663,3664],{},"Fulfillment of information security objectives."," Progress against the measurable objectives set under Clause 6.2.",[37,3667,3668],{},"Not every input needs to be a deep dive at every review. A quarterly cycle might rotate focus, while the annual review covers everything. What auditors want to see is evidence that over the course of your review cycle, every input was considered.",[32,3670,3672],{"id":3671},"required-outputs","Required outputs",[37,3674,3675],{},"Clause 9.3.3 requires outputs related to continual improvement opportunities and any changes needed in the ISMS. Documented outputs typically include:",[164,3677,3678,3684,3690,3696,3702],{},[167,3679,3680,3683],{},[103,3681,3682],{},"Decisions."," Specific, assigned, time-bound decisions. \"We will increase the security engineering headcount by one in Q3 2026\" is a decision. \"Security is important\" is not.",[167,3685,3686,3689],{},[103,3687,3688],{},"Changes to the ISMS."," Updates to scope, policies, controls, or procedures.",[167,3691,3692,3695],{},[103,3693,3694],{},"Resource commitments."," Budget, headcount, or tooling decisions.",[167,3697,3698,3701],{},[103,3699,3700],{},"Updated information security objectives."," Revised or reaffirmed objectives for the next period.",[167,3703,3704,3707],{},[103,3705,3706],{},"Acknowledged risks."," Risks that leadership has reviewed and accepted.",[37,3709,3710],{},"The management review output is often the strongest evidence auditors use to confirm that top management is genuinely engaged with the ISMS. Vague outputs signal a rubber-stamp review and invite deeper questioning.",[32,3712,3714],{"id":3713},"who-attends","Who attends",[37,3716,3717],{},"Top management means people with the authority to allocate resources and change organizational direction. In a small technology company this is typically the CEO, CTO, and COO. In a larger organization it may be a dedicated information security committee chaired by the CISO and including department heads with revenue, product, legal, and operations responsibility.",[37,3719,3720],{},"Supporting roles such as the ISMS owner, compliance lead, internal audit lead, and risk manager usually present material. Their attendance is expected, but they cannot substitute for the actual decision-makers. A management review where no one with budget authority is present will not satisfy Clause 9.3.",[32,3722,3724],{"id":3723},"documentation-expectations","Documentation expectations",[37,3726,3727],{},"The review must produce documented information as evidence. At a minimum, retain:",[164,3729,3730,3733,3736,3739],{},[167,3731,3732],{},"Meeting minutes or a review report capturing inputs discussed, participants, and outputs.",[167,3734,3735],{},"A record of attendees including roles, to demonstrate top management participation.",[167,3737,3738],{},"Supporting materials such as metrics dashboards, audit reports, and risk updates presented at the review.",[167,3740,3741],{},"Action logs tracking decisions to closure.",[37,3743,3744],{},"Minutes should be specific enough that an outside reader can reconstruct what was considered and decided. \"Discussed risk\" is not enough. \"Reviewed residual risk on vendor management, noting three vendors with overdue annual reviews. Decision: reassign vendor review owner by April 30 and complete reviews by May 31. Owner: CTO.\" is the right level of detail.",[32,3746,1245],{"id":1244},[37,3748,3749],{},"Management review sits inside Clause 9 (Performance Evaluation) alongside monitoring, measurement, analysis, evaluation, and internal audit. It is the moment where all of those inputs converge and leadership formally acts on them. Without management review, the rest of Clause 9 produces information but no decisions.",[37,3751,3752,3753,242],{},"Management review is also a critical bridge into Clause 10 (Improvement). Outputs feed directly into nonconformity handling and continual improvement. For first-time certifiers, at least one management review with complete inputs and outputs must be documented before Stage 2 of the ",[40,3754,619],{"href":84},[32,3756,1270],{"id":1269},[164,3758,3759,3765,3771,3777,3783,3789],{},[167,3760,3761,3764],{},[103,3762,3763],{},"Running the meeting but not documenting it."," Verbal commitments do not satisfy ISO 27001. If it is not in the minutes, it did not happen.",[167,3766,3767,3770],{},[103,3768,3769],{},"Skipping inputs."," Omitting risk assessment results or audit findings from the agenda will surface as a nonconformity.",[167,3772,3773,3776],{},[103,3774,3775],{},"No top management in the room."," Delegating the entire review to the security team invalidates it as a management review.",[167,3778,3779,3782],{},[103,3780,3781],{},"Repeating the same outputs every cycle."," Outputs should evolve as the ISMS matures. Identical decisions year after year suggest the review is ceremonial.",[167,3784,3785,3788],{},[103,3786,3787],{},"Treating the review as a report-out, not a decision forum."," The purpose is to decide, not to inform.",[167,3790,3791,3794],{},[103,3792,3793],{},"Holding the review too close to the certification audit."," Auditors want to see the review in normal operating cadence, not a one-time event manufactured for audit preparation.",[32,3796,1312],{"id":1311},[37,3798,3799],{},"episki generates the management review pack automatically from your control graph, risk register, audit findings, and metrics, so the ISMS owner is not spending a week assembling slides every quarter. Decisions made during the review are captured as tracked actions with owners and due dates, and the full review record is retained as documented information ready for external auditors.",[37,3801,1318,3802,3804],{},[40,3803,1321],{"href":498}," for how management review connects to the rest of the ISMS lifecycle.",{"title":427,"searchDepth":428,"depth":428,"links":3806},[3807,3808,3809,3810,3811,3812,3813,3814,3815],{"id":3567,"depth":428,"text":3568},{"id":3577,"depth":428,"text":3578},{"id":3587,"depth":428,"text":3588},{"id":3671,"depth":428,"text":3672},{"id":3713,"depth":428,"text":3714},{"id":3723,"depth":428,"text":3724},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"How ISO 27001 Clause 9.3 management reviews work, including required inputs and outputs, cadence, documentation, and demonstrating leadership engagement.",{"items":3818},[3819,3822,3825,3828,3831],{"label":3820,"content":3821},"How often should ISO 27001 management reviews happen?","ISO 27001 requires management reviews at planned intervals. Most organizations hold at least one full review annually, and many run a lighter quarterly review to keep leadership engaged between annual deep reviews.",{"label":3823,"content":3824},"Who must attend an ISO 27001 management review?","Top management must participate. For most companies this means executives with authority to allocate resources and change direction, such as the CEO, CTO, CISO, or equivalent. Supporting roles like the ISMS owner, compliance lead, and risk manager typically present material but do not substitute for top management attendance.",{"label":3826,"content":3827},"What are the required inputs to a management review?","Clause 9.3.2 lists required inputs including the status of actions from prior reviews, changes in external and internal issues, ISMS performance and effectiveness, audit results, risk assessment results, fulfillment of information security objectives, nonconformities and corrective actions, monitoring and measurement results, and opportunities for improvement.",{"label":3829,"content":3830},"What counts as an output of management review?","Outputs are decisions that drive action. Typical outputs include changes to the ISMS, resource decisions, updated information security objectives, improvement opportunities to pursue, and acknowledged risks requiring attention. Outputs must be documented.",{"label":3832,"content":3833},"Can management review be combined with other executive meetings?","Yes, as long as ISO 27001 inputs are covered and outputs are specifically documented as management review outputs. Many organizations run management review as a standing agenda item in an existing risk or security steering committee.",{},[515,982,3836],"grc",[2389,282,2391,987],{"title":3839,"description":3840},"ISO 27001 Management Review — Clause 9.3 Inputs & Outputs","Run ISO 27001 Clause 9.3 management reviews with the right inputs, outputs, cadence, and documentation to satisfy auditors and drive ISMS improvement.","5.frameworks\u002Fiso27001\u002Fmanagement-review","EaBJSbCxJGE_pc_vp9p3EShtml69D9FHZLwWNi5UQn8",{"id":3844,"title":3845,"body":3846,"description":4206,"extension":460,"faq":4207,"frameworkSlug":515,"lastUpdated":979,"meta":4224,"navigation":497,"path":277,"relatedTerms":4225,"relatedTopics":4227,"seo":4228,"stem":4231,"__hash__":4232},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fnonconformity-and-corrective-action.md","ISO 27001 Nonconformity and Corrective Action (Clauses 10.1 and 10.2)",{"type":29,"value":3847,"toc":4189},[3848,3857,3860,3864,3867,3870,3890,3893,3896,3900,3903,3953,3956,3960,3964,3967,3987,3990,3994,3997,4001,4004,4007,4011,4014,4028,4032,4035,4039,4042,4053,4056,4060,4063,4067,4070,4077,4091,4094,4099,4110,4113,4115,4128,4133,4135,4179,4181,4184],[37,3849,3850,3851,3853,3854,3856],{},"Clauses 10.1 and 10.2 of ",[40,3852,43],{"href":498}," govern how your ",[40,3855,48],{"href":47}," responds when something fails to meet a requirement. Every ISMS will generate nonconformities. The question is not whether they happen but whether your organization handles them in a structured, evidence-producing way that drives real improvement rather than just documentation theater.",[37,3858,3859],{},"The corrective action process, often referred to as CAPA (corrective and preventive action, inherited from quality management systems), is one of the most auditor-visible parts of your ISO 27001 programme. Certification auditors will sample open and closed nonconformities, verify that root causes were actually identified, and check that corrective actions were verified for effectiveness. Weakness here reliably produces findings.",[32,3861,3863],{"id":3862},"what-clauses-101-and-102-actually-say","What Clauses 10.1 and 10.2 actually say",[37,3865,3866],{},"Clause 10.1 (Continual Improvement) sets the expectation that the organization continually improves the suitability, adequacy, and effectiveness of the ISMS. In the 2022 revision this clause is short and points forward to the improvement activities described in the rest of Clause 10 and elsewhere.",[37,3868,3869],{},"Clause 10.2 (Nonconformity and Corrective Action) is the operational heart. When a nonconformity occurs, the organization must:",[164,3871,3872,3875,3878,3881,3884,3887],{},[167,3873,3874],{},"React to the nonconformity and take action to control and correct it.",[167,3876,3877],{},"Deal with the consequences.",[167,3879,3880],{},"Evaluate the need for action to eliminate the causes of the nonconformity so it does not recur, by reviewing the nonconformity, determining its causes, and determining if similar nonconformities exist or could occur.",[167,3882,3883],{},"Implement any action needed.",[167,3885,3886],{},"Review the effectiveness of any corrective action taken.",[167,3888,3889],{},"Make changes to the ISMS if necessary.",[37,3891,3892],{},"The organization must also retain documented information as evidence of the nature of the nonconformities, actions taken, and results.",[37,3894,3895],{},"This is a complete loop: detect, contain, analyze, fix, verify, evidence. Miss a step and the finding is effectively incomplete.",[32,3897,3899],{"id":3898},"where-nonconformities-come-from","Where nonconformities come from",[37,3901,3902],{},"Nonconformities surface from many sources. A well-designed ISMS captures them from all of them:",[164,3904,3905,3914,3920,3926,3932,3938,3947],{},[167,3906,3907,3913],{},[103,3908,3909,3912],{},[40,3910,3911],{"href":258},"Internal audit"," findings."," The most structured source. Internal auditors identify gaps against ISO 27001, your own policies, or contractual requirements.",[167,3915,3916,3919],{},[103,3917,3918],{},"External audit findings."," From certification bodies during Stage 1, Stage 2, or surveillance audits.",[167,3921,3922,3925],{},[103,3923,3924],{},"Security incidents."," An incident that reveals a control was not operating as documented is a nonconformity even after the incident is contained.",[167,3927,3928,3931],{},[103,3929,3930],{},"Customer or regulator feedback."," A customer reporting a policy violation or a regulator flagging noncompliance.",[167,3933,3934,3937],{},[103,3935,3936],{},"Self-reported issues."," Engineers, ops staff, or managers noticing that a process is not being followed and raising it.",[167,3939,3940,3946],{},[103,3941,3942,3945],{},[40,3943,3944],{"href":263},"Management review"," discussions."," Leadership identifying systemic issues during review.",[167,3948,3949,3952],{},[103,3950,3951],{},"Risk assessment updates."," Reassessing risk and finding existing controls are insufficient.",[37,3954,3955],{},"The more paths you have for nonconformities to surface, the healthier your ISMS. Organizations where all nonconformities come from external audits are not catching problems themselves.",[32,3957,3959],{"id":3958},"the-capa-workflow-step-by-step","The CAPA workflow step by step",[560,3961,3963],{"id":3962},"_1-identification-and-recording","1. Identification and recording",[37,3965,3966],{},"When a nonconformity is identified, record it immediately. Every nonconformity record should include:",[164,3968,3969,3972,3975,3978,3981,3984],{},[167,3970,3971],{},"Unique identifier.",[167,3973,3974],{},"Date identified and by whom.",[167,3976,3977],{},"Source (internal audit, incident, etc.).",[167,3979,3980],{},"Description referencing the specific requirement that was not met.",[167,3982,3983],{},"Evidence of the nonconformity.",[167,3985,3986],{},"Initial severity classification.",[37,3988,3989],{},"Entering nonconformities into a structured system, not an email thread, is essential for later auditor review.",[560,3991,3993],{"id":3992},"_2-immediate-correction-and-containment","2. Immediate correction and containment",[37,3995,3996],{},"Before root cause analysis, contain the problem. If an access review was missed, complete it. If a control stopped operating, restart it. If an incident is in progress, follow incident response to contain it. Correction addresses the immediate issue and limits the blast radius.",[560,3998,4000],{"id":3999},"_3-root-cause-analysis","3. Root cause analysis",[37,4002,4003],{},"This is where weak programmes fail. Root cause analysis asks why the nonconformity happened, not just what happened. Techniques include 5 Whys, fishbone diagrams, and fault tree analysis. The depth should match the severity: a minor isolated issue may only need a brief analysis, while a systemic issue deserves deeper investigation.",[37,4005,4006],{},"Root cause analysis should end with a statement of underlying cause that could plausibly lead to a corrective action. \"The access review was not completed because the owner was on vacation\" is a symptom. \"The access review process has no backup owner and no automated reminder, so it fails whenever the primary owner is unavailable\" is a root cause.",[560,4008,4010],{"id":4009},"_4-corrective-action-planning","4. Corrective action planning",[37,4012,4013],{},"Based on the root cause, plan corrective actions. A corrective action should be:",[164,4015,4016,4019,4022,4025],{},[167,4017,4018],{},"Specific. Not \"improve the process\" but \"assign a backup owner and enable automated reminders in the GRC platform.\"",[167,4020,4021],{},"Owned. A named person is responsible.",[167,4023,4024],{},"Time-bound. With a target completion date appropriate to severity.",[167,4026,4027],{},"Evidence-producing. The action should generate artifacts that prove completion.",[560,4029,4031],{"id":4030},"_5-implementation","5. Implementation",[37,4033,4034],{},"Execute the corrective action. Retain evidence of implementation, such as updated policies, new automation, training records, or configuration changes.",[560,4036,4038],{"id":4037},"_6-verification-of-effectiveness","6. Verification of effectiveness",[37,4040,4041],{},"ISO 27001 specifically requires review of effectiveness, not just evidence of implementation. This is the step most often missed. Verification asks whether the corrective action actually prevented recurrence. Depending on the nature of the action, verification might include:",[164,4043,4044,4047,4050],{},[167,4045,4046],{},"Re-auditing the affected area after a defined interval.",[167,4048,4049],{},"Reviewing metrics for the affected control over time.",[167,4051,4052],{},"Sampling additional records to confirm the fix is operating.",[37,4054,4055],{},"Only after verification is the nonconformity closed.",[560,4057,4059],{"id":4058},"_7-systemic-evaluation","7. Systemic evaluation",[37,4061,4062],{},"Clause 10.2 also requires evaluating whether similar nonconformities exist elsewhere or could occur. A single missed access review in one system might point to a gap in every access review process across the organization. This step is what separates corrective action from reactive firefighting.",[32,4064,4066],{"id":4065},"distinguishing-major-and-minor-nonconformities","Distinguishing major and minor nonconformities",[37,4068,4069],{},"Classifications affect how urgently a nonconformity must be handled and, in the case of external audits, whether certification is at risk.",[37,4071,4072,4073,4076],{},"A ",[103,4074,4075],{},"major nonconformity"," is typically:",[164,4078,4079,4082,4085,4088],{},[167,4080,4081],{},"Absence of a required element of the ISMS.",[167,4083,4084],{},"Systemic failure of a process.",[167,4086,4087],{},"Multiple minor nonconformities in the same area indicating a broader issue.",[167,4089,4090],{},"A control that is fundamentally not operating.",[37,4092,4093],{},"A major nonconformity from a certification body must be resolved before a certificate is issued or will suspend an existing certificate if not addressed.",[37,4095,4072,4096,4076],{},[103,4097,4098],{},"minor nonconformity",[164,4100,4101,4104,4107],{},[167,4102,4103],{},"An isolated failure within an otherwise functioning process.",[167,4105,4106],{},"A documentation gap that does not affect control operation.",[167,4108,4109],{},"A process deviation that is not yet systemic.",[37,4111,4112],{},"Minor nonconformities usually have a fixed remediation window, often 90 days, before the certification body follows up.",[32,4114,1245],{"id":1244},[37,4116,4117,4118,414,4121,4124,4125,4127],{},"Nonconformity handling is where Clauses 9 and 10 meet. ",[40,4119,4120],{"href":258},"Internal audits",[40,4122,4123],{"href":263},"management reviews"," under Clause 9 surface nonconformities. Clause 10 processes them. Outputs from corrective action feed back into ",[40,4126,2600],{"href":292}," as systemic learnings and often trigger updates to risk treatment or the Statement of Applicability.",[37,4129,2281,4130,4132],{},[40,4131,619],{"href":84},", auditors will review your nonconformity log both from internal audits and from operational sources. Closed nonconformities with weak root cause analysis or no effectiveness verification are a leading cause of findings during Stage 2.",[32,4134,1270],{"id":1269},[164,4136,4137,4143,4149,4155,4161,4167,4173],{},[167,4138,4139,4142],{},[103,4140,4141],{},"Correction without corrective action."," Fixing the immediate issue without addressing the root cause guarantees recurrence.",[167,4144,4145,4148],{},[103,4146,4147],{},"Root causes that are not really root causes."," Stopping at \"the person forgot\" rather than investigating why the process allowed forgetting is a shallow analysis.",[167,4150,4151,4154],{},[103,4152,4153],{},"No effectiveness verification."," Closing a nonconformity the day the fix ships misses the point. Effectiveness must be reviewed after the action has had time to operate.",[167,4156,4157,4160],{},[103,4158,4159],{},"Closing nonconformities too quickly to clear the backlog."," Auditors notice, and reopening a closed nonconformity looks worse than leaving it open with a plan.",[167,4162,4163,4166],{},[103,4164,4165],{},"Not looking for systemic occurrences."," Clause 10.2 specifically requires checking whether similar issues exist elsewhere.",[167,4168,4169,4172],{},[103,4170,4171],{},"Treating every issue as a minor."," Downgrading severity to reduce pressure produces audit findings when the pattern becomes visible.",[167,4174,4175,4178],{},[103,4176,4177],{},"Weak documentation trail."," If the nonconformity, root cause, action, and verification cannot be reconstructed from your records, the corrective action is effectively incomplete.",[32,4180,1312],{"id":1311},[37,4182,4183],{},"episki provides a structured nonconformity workflow that captures findings from internal audits, incidents, and ad-hoc reports into a single register, enforces the full CAPA lifecycle including mandatory root cause analysis and effectiveness verification, links each nonconformity back to the controls and risks it affects, and produces the documented evidence ISO 27001 auditors expect. Patterns across nonconformities surface automatically so systemic issues are caught before they become external audit findings.",[37,4185,4186,4187,242],{},"For the broader context of how nonconformity handling fits the ISMS cycle, return to the ",[40,4188,1321],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":4190},[4191,4192,4193,4202,4203,4204,4205],{"id":3862,"depth":428,"text":3863},{"id":3898,"depth":428,"text":3899},{"id":3958,"depth":428,"text":3959,"children":4194},[4195,4196,4197,4198,4199,4200,4201],{"id":3962,"depth":963,"text":3963},{"id":3992,"depth":963,"text":3993},{"id":3999,"depth":963,"text":4000},{"id":4009,"depth":963,"text":4010},{"id":4030,"depth":963,"text":4031},{"id":4037,"depth":963,"text":4038},{"id":4058,"depth":963,"text":4059},{"id":4065,"depth":428,"text":4066},{"id":1244,"depth":428,"text":1245},{"id":1269,"depth":428,"text":1270},{"id":1311,"depth":428,"text":1312},"Handle ISO 27001 nonconformities and corrective actions under Clauses 10.1 and 10.2 with root cause analysis, CAPA workflows, and effectiveness verification.",{"items":4208},[4209,4212,4215,4218,4221],{"label":4210,"content":4211},"What counts as a nonconformity in ISO 27001?","A nonconformity is any failure to meet a requirement. That includes a requirement from ISO 27001 itself, from your own policies, from contractual obligations, or from regulations your ISMS references. Missing a required record, a control that is not operating, or a policy that is not being followed all qualify.",{"label":4213,"content":4214},"What is the difference between a major and minor nonconformity?","A major nonconformity is a significant failure that threatens the effectiveness of the ISMS, such as a systemic process breakdown or total absence of a required control. A minor nonconformity is an isolated issue that does not threaten the ISMS overall, such as a single missing record within an otherwise well-run process.",{"label":4216,"content":4217},"What is corrective action versus correction?","A correction fixes the immediate problem. A corrective action addresses the root cause so the problem does not recur. Correction patches the hole. Corrective action changes why the hole appeared in the first place.",{"label":4219,"content":4220},"How long should it take to close a nonconformity?","Most certification bodies expect minor nonconformities from external audits to close within 90 days. Internal nonconformities vary by severity. What matters most is that the timeline is documented, defensible, and actually met.",{"label":4222,"content":4223},"Do I need a separate CAPA system to satisfy Clause 10?","No, but you need a consistent, documented process. Many organizations use a ticketing system, a dedicated GRC platform, or a structured spreadsheet. The form matters less than the evidence of real root cause analysis and verification of effectiveness.",{},[515,982,4226,2698],"incident-response",[2389,2390,282,987],{"title":4229,"description":4230},"ISO 27001 Nonconformity & Corrective Action — 10.1 & 10.2","Run ISO 27001 nonconformity and corrective action handling with root cause analysis, CAPA, and evidence auditors accept under Clauses 10.1 and 10.2.","5.frameworks\u002Fiso27001\u002Fnonconformity-and-corrective-action","WNFxiXuMxVt0--7gDQAZipXa1a9929Tc5iHAHtUAVBU",{"id":4234,"title":4235,"body":4236,"description":4638,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":4639,"navigation":497,"path":240,"relatedTerms":4640,"relatedTopics":4641,"seo":4642,"stem":4645,"__hash__":4646},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Frisk-assessment.md","ISO 27001 Risk Assessment",{"type":29,"value":4237,"toc":4617},[4238,4247,4250,4253,4273,4276,4280,4283,4287,4290,4300,4304,4307,4315,4319,4322,4330,4337,4341,4345,4348,4352,4355,4359,4362,4379,4383,4386,4390,4393,4397,4400,4404,4407,4437,4440,4454,4460,4464,4467,4517,4525,4529,4532,4564,4567,4571,4577,4583,4589,4595,4604,4608,4611],[37,4239,4240,4241,4243,4244,4246],{},"Risk assessment is the engine that drives every decision within an ",[40,4242,43],{"href":498}," ",[40,4245,48],{"href":47},". The standard does not prescribe a specific methodology but requires that your approach is systematic, repeatable, and produces comparable results over time. Getting risk assessment right determines which controls you implement, how you allocate resources, and ultimately whether your security program addresses real threats or just checks boxes.",[32,4248,4249],{"id":3179},"What ISO 27001 Requires",[37,4251,4252],{},"Clauses 6.1.2 and 8.2 of ISO 27001 set out the requirements for risk assessment. At a high level the standard requires you to:",[1446,4254,4255,4261,4267],{},[167,4256,4257,4260],{},[103,4258,4259],{},"Define a risk assessment process"," that establishes criteria for risk acceptance, criteria for performing assessments, and ensures that repeated assessments produce consistent and comparable results.",[167,4262,4263,4266],{},[103,4264,4265],{},"Identify information security risks"," by identifying risks associated with the loss of confidentiality, integrity, and availability of information within the scope of the ISMS, and identifying the risk owners.",[167,4268,4269,4272],{},[103,4270,4271],{},"Analyze and evaluate risks"," by assessing the realistic likelihood and potential impact of each risk, determining the level of risk, and comparing results against your risk criteria to prioritize treatment.",[37,4274,4275],{},"These requirements give you flexibility in choosing a methodology while ensuring the outcome is rigorous enough to withstand audit scrutiny.",[32,4277,4279],{"id":4278},"choosing-a-risk-assessment-methodology","Choosing a Risk Assessment Methodology",[37,4281,4282],{},"There is no single correct methodology. The key is that your chosen approach meets the standard's requirements for consistency and comparability. Common approaches include:",[560,4284,4286],{"id":4285},"qualitative-assessment","Qualitative Assessment",[37,4288,4289],{},"The most widely used approach for ISO 27001, qualitative assessment uses descriptive scales (such as low, medium, high, or critical) for both likelihood and impact. Risks are plotted on a matrix and ranked accordingly.",[37,4291,4292,4295,4296,4299],{},[103,4293,4294],{},"Advantages:"," Accessible to non-technical stakeholders, faster to execute, easier to maintain.\n",[103,4297,4298],{},"Limitations:"," Subjective by nature, can produce inconsistent results if criteria are not well-defined.",[560,4301,4303],{"id":4302},"semi-quantitative-assessment","Semi-Quantitative Assessment",[37,4305,4306],{},"This approach assigns numerical values to qualitative scales (for example, 1 through 5 for likelihood and impact). The risk level is calculated by multiplying or adding these values, producing a numerical score that enables more granular ranking.",[37,4308,4309,4311,4312,4314],{},[103,4310,4294],{}," More granular than pure qualitative, still manageable without complex data.\n",[103,4313,4298],{}," The numbers can create a false sense of precision if the underlying scales are poorly calibrated.",[560,4316,4318],{"id":4317},"quantitative-assessment","Quantitative Assessment",[37,4320,4321],{},"Fully quantitative approaches express risk in financial or operational terms, often using methods like Factor Analysis of Information Risk (FAIR). Likelihood is expressed as frequency, and impact is expressed in monetary loss.",[37,4323,4324,4326,4327,4329],{},[103,4325,4294],{}," Enables cost-benefit analysis for control investments, speaks the language of business leadership.\n",[103,4328,4298],{}," Requires reliable data that many organizations do not have, significantly more complex.",[37,4331,4332,4333,4336],{},"Most organizations pursuing ",[40,4334,4335],{"href":84},"ISO 27001 certification"," start with a qualitative or semi-quantitative approach. The standard does not require quantitative analysis, and auditors are primarily concerned that your methodology is defined, documented, and consistently applied.",[32,4338,4340],{"id":4339},"building-your-risk-assessment-process","Building Your Risk Assessment Process",[560,4342,4344],{"id":4343},"step-1-define-the-scope-and-context","Step 1: Define the Scope and Context",[37,4346,4347],{},"Before identifying risks, confirm the scope of your ISMS and understand the internal and external context (clause 4). This includes the regulatory environment, contractual obligations, organizational structure, technology landscape, and threat landscape relevant to your operations.",[560,4349,4351],{"id":4350},"step-2-identify-assets-and-information","Step 2: Identify Assets and Information",[37,4353,4354],{},"Create an inventory of information assets within scope. Assets include data repositories, applications, infrastructure, personnel, processes, and third-party services. Some organizations take an asset-based approach where risks are identified per asset. Others take a scenario-based or threat-based approach. Either is acceptable.",[560,4356,4358],{"id":4357},"step-3-identify-threats-and-vulnerabilities","Step 3: Identify Threats and Vulnerabilities",[37,4360,4361],{},"For each asset or scenario, identify realistic threats (what could go wrong) and vulnerabilities (weaknesses that a threat could exploit). Common threat categories include:",[164,4363,4364,4367,4370,4373,4376],{},[167,4365,4366],{},"Malicious external attacks (ransomware, phishing, DDoS)",[167,4368,4369],{},"Insider threats (accidental or deliberate)",[167,4371,4372],{},"System failures (hardware, software, infrastructure)",[167,4374,4375],{},"Natural events (fire, flood, power outage)",[167,4377,4378],{},"Third-party and supply chain failures",[560,4380,4382],{"id":4381},"step-4-assess-likelihood-and-impact","Step 4: Assess Likelihood and Impact",[37,4384,4385],{},"Using your defined scales, rate each risk for likelihood (how probable is this event given current controls) and impact (what damage would result in terms of confidentiality, integrity, or availability). Document the rationale for each rating so it can be reviewed and challenged.",[560,4387,4389],{"id":4388},"step-5-calculate-and-rank-risk-levels","Step 5: Calculate and Rank Risk Levels",[37,4391,4392],{},"Combine likelihood and impact ratings to determine the overall risk level. Plot risks on a risk matrix or score them numerically. This ranking drives prioritization.",[560,4394,4396],{"id":4395},"step-6-evaluate-against-risk-criteria","Step 6: Evaluate Against Risk Criteria",[37,4398,4399],{},"Compare each risk level against your organization's risk acceptance criteria. Risks that fall below the acceptance threshold may be accepted with documentation. Risks above the threshold require treatment.",[32,4401,4403],{"id":4402},"the-risk-treatment-plan","The Risk Treatment Plan",[37,4405,4406],{},"Clause 6.1.3 requires a risk treatment plan that documents how each unacceptable risk will be addressed. For each risk, you select one or more treatment options:",[164,4408,4409,4419,4425,4431],{},[167,4410,4411,4414,4415,4418],{},[103,4412,4413],{},"Mitigate."," Apply controls to reduce likelihood, impact, or both. Controls are typically selected from ",[40,4416,4417],{"href":130},"Annex A"," but can come from any source.",[167,4420,4421,4424],{},[103,4422,4423],{},"Transfer."," Shift the risk to a third party, commonly through insurance or outsourcing to a provider with contractual security commitments.",[167,4426,4427,4430],{},[103,4428,4429],{},"Avoid."," Eliminate the activity or condition that creates the risk.",[167,4432,4433,4436],{},[103,4434,4435],{},"Accept."," Acknowledge the risk and choose not to treat it further, with formal approval from the risk owner.",[37,4438,4439],{},"The risk treatment plan must specify:",[164,4441,4442,4445,4448,4451],{},[167,4443,4444],{},"The controls or actions selected",[167,4446,4447],{},"Who is responsible for implementation",[167,4449,4450],{},"Implementation timelines",[167,4452,4453],{},"How effectiveness will be measured",[37,4455,4456,4457,4459],{},"This plan feeds directly into your ",[40,4458,143],{"href":153},", which declares which Annex A controls are applicable based on your risk treatment decisions.",[32,4461,4463],{"id":4462},"the-risk-register","The Risk Register",[37,4465,4466],{},"The risk register is the central repository that tracks all identified risks, their assessments, treatment decisions, and current status. While ISO 27001 does not mandate a specific format, your risk register should capture:",[164,4468,4469,4475,4481,4487,4493,4499,4505,4511],{},[167,4470,4471,4474],{},[103,4472,4473],{},"Risk ID and description."," A unique identifier and clear description of the risk scenario.",[167,4476,4477,4480],{},[103,4478,4479],{},"Risk owner."," The person accountable for managing the risk.",[167,4482,4483,4486],{},[103,4484,4485],{},"Likelihood and impact ratings."," Both inherent (before controls) and residual (after controls).",[167,4488,4489,4492],{},[103,4490,4491],{},"Risk level."," The calculated overall risk score.",[167,4494,4495,4498],{},[103,4496,4497],{},"Treatment decision."," Mitigate, transfer, avoid, or accept.",[167,4500,4501,4504],{},[103,4502,4503],{},"Controls applied."," Links to specific Annex A controls or custom controls.",[167,4506,4507,4510],{},[103,4508,4509],{},"Residual risk."," The remaining risk level after treatment is applied.",[167,4512,4513,4516],{},[103,4514,4515],{},"Status and review date."," Whether the risk is open, in treatment, or closed, and when it was last reviewed.",[37,4518,4519,4520,414,4522,4524],{},"A well-maintained risk register is one of the most scrutinized artifacts during ",[40,4521,2984],{"href":84},[40,4523,946],{"href":361},". Auditors want to see that it is current, that risks have been reviewed on schedule, and that treatment plans are progressing.",[32,4526,4528],{"id":4527},"continuous-risk-monitoring","Continuous Risk Monitoring",[37,4530,4531],{},"Risk assessment is not a one-time activity. ISO 27001 requires ongoing monitoring and review of risks (clause 8.2 states risk assessments must be performed at planned intervals or when significant changes occur). Triggers for reassessment include:",[164,4533,4534,4540,4546,4552,4558],{},[167,4535,4536,4539],{},[103,4537,4538],{},"Organizational changes."," Mergers, new products, entering new markets, significant staffing changes.",[167,4541,4542,4545],{},[103,4543,4544],{},"Technology changes."," Migrating to new platforms, adopting new tools, decommissioning legacy systems.",[167,4547,4548,4551],{},[103,4549,4550],{},"Threat landscape changes."," New vulnerability disclosures, emerging attack patterns, incidents at peer organizations.",[167,4553,4554,4557],{},[103,4555,4556],{},"Incident outcomes."," Lessons learned from security incidents or near-misses within your own organization.",[167,4559,4560,4563],{},[103,4561,4562],{},"Audit findings."," Results from internal audits, external audits, or penetration tests.",[37,4565,4566],{},"Embed risk review into existing operational rhythms. Monthly or quarterly risk review meetings, integrated with change management processes, keep the risk register alive without creating a separate bureaucratic process.",[32,4568,4570],{"id":4569},"common-mistakes","Common Mistakes",[37,4572,4573,4576],{},[103,4574,4575],{},"Boiling the ocean."," Trying to identify every conceivable risk creates an unwieldy register that no one maintains. Focus on realistic, material risks within your scope.",[37,4578,4579,4582],{},[103,4580,4581],{},"Inconsistent criteria."," If different assessors interpret \"medium likelihood\" differently, your risk rankings become meaningless. Invest time in calibrating your scales with concrete examples.",[37,4584,4585,4588],{},[103,4586,4587],{},"Static risk registers."," A risk register that is updated once a year for audit purposes provides little actual security value. Risks change continuously, and your register should reflect that.",[37,4590,4591,4594],{},[103,4592,4593],{},"Ignoring residual risk."," After applying controls, you must reassess the remaining risk. If residual risk still exceeds your acceptance criteria, additional treatment is needed.",[37,4596,4597,4600,4601,4603],{},[103,4598,4599],{},"Disconnecting risk from controls."," Every control in your ",[40,4602,143],{"href":153}," should trace back to one or more risks. Controls without risk justification and risks without corresponding controls both indicate process problems.",[32,4605,4607],{"id":4606},"making-risk-assessment-practical","Making Risk Assessment Practical",[37,4609,4610],{},"The goal is not to create perfect risk models but to make informed, defensible decisions about where to invest in security. Keep your methodology as simple as your context allows, ensure risk owners are genuinely engaged, and use tooling that makes the risk register a living document rather than a static spreadsheet.",[37,4612,4613,4614,4616],{},"Platforms like episki link risk register entries directly to controls, evidence, and review schedules, ensuring that risk treatment decisions stay connected to operational reality. Explore the full ",[40,4615,43],{"href":42}," framework to see how risk assessment integrates with the rest of your compliance program.",{"title":427,"searchDepth":428,"depth":428,"links":4618},[4619,4620,4625,4633,4634,4635,4636,4637],{"id":3179,"depth":428,"text":4249},{"id":4278,"depth":428,"text":4279,"children":4621},[4622,4623,4624],{"id":4285,"depth":963,"text":4286},{"id":4302,"depth":963,"text":4303},{"id":4317,"depth":963,"text":4318},{"id":4339,"depth":428,"text":4340,"children":4626},[4627,4628,4629,4630,4631,4632],{"id":4343,"depth":963,"text":4344},{"id":4350,"depth":963,"text":4351},{"id":4357,"depth":963,"text":4358},{"id":4381,"depth":963,"text":4382},{"id":4388,"depth":963,"text":4389},{"id":4395,"depth":963,"text":4396},{"id":4402,"depth":428,"text":4403},{"id":4462,"depth":428,"text":4463},{"id":4527,"depth":428,"text":4528},{"id":4569,"depth":428,"text":4570},{"id":4606,"depth":428,"text":4607},"A practical guide to performing ISO 27001 risk assessments, building risk treatment plans, maintaining a risk register, and embedding continuous risk monitoring into your ISMS.",{},[515,982],[112,984,986,987,988],{"title":4643,"description":4644},"ISO 27001 Risk Assessment — Methodology, Treatment & Monitoring","Master ISO 27001 risk assessment with practical guidance on methodology selection, risk treatment plans, risk registers, and continuous monitoring.","5.frameworks\u002Fiso27001\u002Frisk-assessment","EX-SLf_30WxGvY2gz6FAsCwDhxazyCDACEivFYrJ-9o",{"id":4648,"title":136,"body":4649,"description":5039,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":5040,"navigation":497,"path":153,"relatedTerms":5041,"relatedTopics":5042,"seo":5043,"stem":5046,"__hash__":5047},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fstatement-of-applicability.md",{"type":29,"value":4650,"toc":5013},[4651,4662,4667,4671,4677,4680,4694,4697,4701,4705,4708,4712,4715,4719,4722,4726,4730,4736,4740,4743,4747,4750,4776,4779,4783,4786,4806,4809,4817,4821,4824,4828,4831,4909,4912,4916,4922,4925,4928,4930,4934,4937,4941,4944,4948,4951,4955,4960,4964,4967,4971,4974,4978,4981,5007],[37,4652,4653,4654,4243,4656,4658,4659,4661],{},"The Statement of Applicability is one of the most important documents in an ",[40,4655,43],{"href":498},[40,4657,48],{"href":47},". It serves as the bridge between your ",[40,4660,880],{"href":240}," outcomes and the controls you implement, providing a complete picture of which security controls your organization has selected, why, and their implementation status.",[37,4663,4664,4665,242],{},"Auditors consider the SoA a mandatory document, and it is often the first artifact they request during both Stage 1 and Stage 2 of the ",[40,4666,619],{"href":84},[32,4668,4670],{"id":4669},"what-is-the-statement-of-applicability","What Is the Statement of Applicability?",[37,4672,4673,4674,4676],{},"The SoA is a document that lists all the controls from ",[40,4675,4417],{"href":130}," of ISO 27001 and, for each control, states whether it is applicable or not applicable to your organization. For applicable controls, the SoA describes how the control is implemented. For excluded controls, it provides the justification for exclusion.",[37,4678,4679],{},"Clause 6.1.3(d) of ISO 27001 specifies that the SoA must contain:",[164,4681,4682,4685,4688,4691],{},[167,4683,4684],{},"The necessary controls (those determined through risk treatment and any additional controls from other sources)",[167,4686,4687],{},"Justification for their inclusion",[167,4689,4690],{},"Whether the controls are implemented or not",[167,4692,4693],{},"Justification for excluding any Annex A controls",[37,4695,4696],{},"The SoA is not just a compliance checkbox. It is the definitive map of your security control landscape and serves as a reference point for auditors, management, and operational teams.",[32,4698,4700],{"id":4699},"why-the-soa-matters","Why the SoA Matters",[560,4702,4704],{"id":4703},"for-auditors","For Auditors",[37,4706,4707],{},"The SoA is the roadmap auditors use to plan their assessment. During the Stage 2 audit, auditors systematically verify that each control declared as applicable in the SoA is actually implemented and operating effectively. A well-structured SoA makes audits smoother and demonstrates organizational maturity.",[560,4709,4711],{"id":4710},"for-management","For Management",[37,4713,4714],{},"The SoA gives leadership a high-level view of the organization's security posture. It shows which risks are being treated, what controls are in place, and where gaps exist. This makes it a valuable input for management reviews required by clause 9.3.",[560,4716,4718],{"id":4717},"for-operations","For Operations",[37,4720,4721],{},"Security and IT teams use the SoA as a reference to understand what controls they are responsible for maintaining. When linked to specific policies, procedures, and evidence, the SoA becomes an operational tool rather than just an audit artifact.",[32,4723,4725],{"id":4724},"how-to-create-a-statement-of-applicability","How to Create a Statement of Applicability",[560,4727,4729],{"id":4728},"step-1-complete-your-risk-assessment","Step 1: Complete Your Risk Assessment",[37,4731,4732,4733,4735],{},"The SoA cannot be created in isolation. It depends on the outputs of your ",[40,4734,880],{"href":240}," and risk treatment plan. You need to know which risks you are treating and which controls you have selected to mitigate those risks before you can build the SoA.",[560,4737,4739],{"id":4738},"step-2-list-all-annex-a-controls","Step 2: List All Annex A Controls",[37,4741,4742],{},"Start with the complete list of 93 controls from Annex A of ISO 27001:2022, organized under the four themes: organizational, people, physical, and technological.",[560,4744,4746],{"id":4745},"step-3-determine-applicability","Step 3: Determine Applicability",[37,4748,4749],{},"For each control, determine whether it is applicable to your organization based on:",[164,4751,4752,4758,4764,4770],{},[167,4753,4754,4757],{},[103,4755,4756],{},"Risk treatment decisions."," Controls selected to mitigate identified risks are applicable.",[167,4759,4760,4763],{},[103,4761,4762],{},"Legal and regulatory requirements."," Some controls may be required by law regardless of your risk assessment findings.",[167,4765,4766,4769],{},[103,4767,4768],{},"Contractual obligations."," Customer contracts or partner agreements may mandate specific controls.",[167,4771,4772,4775],{},[103,4773,4774],{},"Business requirements."," Some controls support business objectives beyond pure security.",[37,4777,4778],{},"A control can be applicable even if your risk assessment did not specifically call for it, for example if it is required by regulation or considered industry best practice.",[560,4780,4782],{"id":4781},"step-4-document-justifications","Step 4: Document Justifications",[37,4784,4785],{},"For each applicable control, document:",[164,4787,4788,4794,4800],{},[167,4789,4790,4793],{},[103,4791,4792],{},"Why it is included."," Link it to specific risks, legal requirements, or contractual obligations.",[167,4795,4796,4799],{},[103,4797,4798],{},"How it is implemented."," Describe the implementation approach at a summary level. This could reference a policy, a technical configuration, a process, or a combination.",[167,4801,4802,4805],{},[103,4803,4804],{},"Implementation status."," Indicate whether the control is fully implemented, partially implemented, or planned.",[37,4807,4808],{},"For each excluded control, document:",[164,4810,4811],{},[167,4812,4813,4816],{},[103,4814,4815],{},"Why it is excluded."," Provide a clear, defensible justification. Common reasons include the control being outside the ISMS scope, the associated risk being accepted, or the control being not relevant to the organization's context (for example, physical perimeter controls for a fully remote organization with no physical offices).",[560,4818,4820],{"id":4819},"step-5-review-and-approve","Step 5: Review and Approve",[37,4822,4823],{},"The SoA should be reviewed and approved by management as part of the ISMS governance process. It is a living document that reflects management's decisions about acceptable risk and control implementation.",[32,4825,4827],{"id":4826},"soa-structure-and-format","SoA Structure and Format",[37,4829,4830],{},"ISO 27001 does not prescribe a specific format, but a typical SoA includes the following columns for each control:",[1596,4832,4833,4843],{},[1599,4834,4835],{},[1602,4836,4837,4840],{},[1605,4838,4839],{},"Column",[1605,4841,4842],{},"Description",[1612,4844,4845,4853,4861,4869,4877,4885,4893,4901],{},[1602,4846,4847,4850],{},[1617,4848,4849],{},"Control reference",[1617,4851,4852],{},"The Annex A control number (e.g., A.5.1)",[1602,4854,4855,4858],{},[1617,4856,4857],{},"Control name",[1617,4859,4860],{},"The name of the control",[1602,4862,4863,4866],{},[1617,4864,4865],{},"Applicable (Yes\u002FNo)",[1617,4867,4868],{},"Whether the control applies",[1602,4870,4871,4874],{},[1617,4872,4873],{},"Justification for inclusion\u002Fexclusion",[1617,4875,4876],{},"Why the control is or is not applicable",[1602,4878,4879,4882],{},[1617,4880,4881],{},"Implementation status",[1617,4883,4884],{},"Fully implemented, partially implemented, planned, or not implemented",[1602,4886,4887,4890],{},[1617,4888,4889],{},"Implementation description",[1617,4891,4892],{},"Summary of how the control is implemented",[1602,4894,4895,4898],{},[1617,4896,4897],{},"Risk reference",[1617,4899,4900],{},"Link to the risk(s) in the risk register that this control addresses",[1602,4902,4903,4906],{},[1617,4904,4905],{},"Evidence reference",[1617,4907,4908],{},"Pointer to evidence artifacts (policies, configurations, logs)",[37,4910,4911],{},"Some organizations add columns for control owners, review dates, and notes. The level of detail should be proportionate to the complexity of your ISMS.",[32,4913,4915],{"id":4914},"relationship-to-annex-a","Relationship to Annex A",[37,4917,4918,4919,4921],{},"The SoA and Annex A are tightly coupled but serve different purposes. ",[40,4920,4417],{"href":130}," is the reference catalog of 93 controls provided by the standard. The SoA is your organization's declaration of which controls from that catalog you have adopted and how.",[37,4923,4924],{},"You are not limited to Annex A controls. If your risk assessment identifies a need for a control that is not in Annex A, you can and should implement it. The SoA should note any additional controls beyond Annex A that your organization has adopted.",[37,4926,4927],{},"Conversely, you cannot add controls to the SoA that are not implemented. The SoA must accurately reflect reality. If a control is listed as implemented, auditors will verify it.",[32,4929,4570],{"id":4569},[560,4931,4933],{"id":4932},"excluding-controls-without-justification","Excluding Controls Without Justification",[37,4935,4936],{},"Every exclusion needs a documented rationale. Simply stating \"not applicable\" without explanation will be flagged by auditors. The justification must be specific to your organization's context, not generic.",[560,4938,4940],{"id":4939},"copy-pasting-from-templates","Copy-Pasting from Templates",[37,4942,4943],{},"Using a template as a starting point is fine, but the SoA must reflect your actual environment. Generic descriptions copied from templates are immediately obvious to experienced auditors and indicate that the SoA was not developed through a genuine risk-based process.",[560,4945,4947],{"id":4946},"declaring-controls-implemented-when-they-are-not","Declaring Controls Implemented When They Are Not",[37,4949,4950],{},"Overstating implementation status is one of the most damaging mistakes. If an auditor finds that a control declared as \"fully implemented\" is only partially in place or not functioning, it results in a nonconformity. Be honest about implementation status. Listing a control as \"partially implemented\" or \"planned\" is perfectly acceptable, especially during initial certification.",[560,4952,4954],{"id":4953},"treating-the-soa-as-static","Treating the SoA as Static",[37,4956,4957,4958,242],{},"The SoA should be updated whenever your risk landscape changes, new controls are implemented, or existing controls are modified. A stale SoA that does not match your current control environment will cause problems during ",[40,4959,946],{"href":361},[560,4961,4963],{"id":4962},"disconnecting-from-the-risk-register","Disconnecting from the Risk Register",[37,4965,4966],{},"The SoA should have clear traceability to your risk register and risk treatment plan. Every applicable control should map to at least one risk, and every risk treatment decision that involves control implementation should be reflected in the SoA. Auditors specifically look for this linkage.",[560,4968,4970],{"id":4969},"making-it-too-detailed-or-too-vague","Making It Too Detailed or Too Vague",[37,4972,4973],{},"The SoA should provide enough detail for an auditor to understand what is in place and verify it, but it is not meant to be a comprehensive security architecture document. Strike a balance between brevity and completeness.",[32,4975,4977],{"id":4976},"maintaining-the-soa","Maintaining the SoA",[37,4979,4980],{},"Build the SoA into your regular ISMS review cycle:",[164,4982,4983,4989,4995,5001],{},[167,4984,4985,4988],{},[103,4986,4987],{},"After each risk assessment cycle",", review whether new controls are needed or existing applicability decisions have changed.",[167,4990,4991,4994],{},[103,4992,4993],{},"When implementing changes",", update the SoA to reflect new or modified controls.",[167,4996,4997,5000],{},[103,4998,4999],{},"Before surveillance audits",", verify that the SoA matches the current state of your control environment.",[167,5002,5003,5006],{},[103,5004,5005],{},"During management reviews",", present SoA changes as part of the ISMS status update.",[37,5008,5009,5010,5012],{},"Maintaining the SoA in a spreadsheet is common but error-prone. Platforms like episki generate the SoA directly from your control graph, ensuring that applicability decisions, implementation status, and evidence references stay synchronized automatically. Learn more about how this fits into the broader ",[40,5011,43],{"href":42}," compliance workflow.",{"title":427,"searchDepth":428,"depth":428,"links":5014},[5015,5016,5021,5028,5029,5030,5038],{"id":4669,"depth":428,"text":4670},{"id":4699,"depth":428,"text":4700,"children":5017},[5018,5019,5020],{"id":4703,"depth":963,"text":4704},{"id":4710,"depth":963,"text":4711},{"id":4717,"depth":963,"text":4718},{"id":4724,"depth":428,"text":4725,"children":5022},[5023,5024,5025,5026,5027],{"id":4728,"depth":963,"text":4729},{"id":4738,"depth":963,"text":4739},{"id":4745,"depth":963,"text":4746},{"id":4781,"depth":963,"text":4782},{"id":4819,"depth":963,"text":4820},{"id":4826,"depth":428,"text":4827},{"id":4914,"depth":428,"text":4915},{"id":4569,"depth":428,"text":4570,"children":5031},[5032,5033,5034,5035,5036,5037],{"id":4932,"depth":963,"text":4933},{"id":4939,"depth":963,"text":4940},{"id":4946,"depth":963,"text":4947},{"id":4953,"depth":963,"text":4954},{"id":4962,"depth":963,"text":4963},{"id":4969,"depth":963,"text":4970},{"id":4976,"depth":428,"text":4977},"Everything you need to know about the ISO 27001 Statement of Applicability, including what it contains, how to create one, its relationship to Annex A, and mistakes to avoid.",{},[515,982],[112,985,986,987,988],{"title":5044,"description":5045},"ISO 27001 Statement of Applicability (SoA) — Guide & Best Practices","Learn how to create an ISO 27001 Statement of Applicability. Covers SoA structure, Annex A mapping, common mistakes, and maintenance best practices.","5.frameworks\u002Fiso27001\u002Fstatement-of-applicability","FzA3uDdnLS792ODW33zk4W7ewvCCIJf18LzpLPzDdq4",{"id":5049,"title":5050,"body":5051,"description":5511,"extension":460,"faq":978,"frameworkSlug":515,"lastUpdated":979,"meta":5512,"navigation":497,"path":361,"relatedTerms":5513,"relatedTopics":5514,"seo":5515,"stem":5518,"__hash__":5519},"frameworkTopics\u002F5.frameworks\u002Fiso27001\u002Fsurveillance-audits.md","ISO 27001 Surveillance Audits",{"type":29,"value":5052,"toc":5490},[5053,5062,5066,5069,5098,5101,5104,5108,5111,5115,5118,5162,5166,5172,5175,5189,5193,5264,5267,5271,5274,5278,5285,5289,5292,5296,5299,5303,5309,5313,5316,5320,5323,5327,5330,5334,5337,5340,5354,5357,5360,5364,5367,5393,5396,5400,5403,5447,5451,5454,5480],[37,5054,5055,5056,5058,5059,5061],{},"Earning your ",[40,5057,43],{"href":498}," certificate is a significant achievement, but it marks the beginning of an ongoing commitment rather than the end of a project. The certification cycle spans three years, during which your certification body conducts surveillance audits to verify that your ",[40,5060,48],{"href":47}," continues to meet the standard's requirements. Understanding what these audits involve and how to prepare for them is essential to maintaining your certification.",[32,5063,5065],{"id":5064},"the-three-year-certification-cycle","The Three-Year Certification Cycle",[37,5067,5068],{},"ISO 27001 certification follows a predictable three-year rhythm:",[164,5070,5071,5080,5086,5092],{},[167,5072,5073,5076,5077,5079],{},[103,5074,5075],{},"Year 0:"," Initial certification audit (Stage 1 and Stage 2). See the ",[40,5078,619],{"href":84}," guide for details.",[167,5081,5082,5085],{},[103,5083,5084],{},"Year 1:"," First surveillance audit.",[167,5087,5088,5091],{},[103,5089,5090],{},"Year 2:"," Second surveillance audit.",[167,5093,5094,5097],{},[103,5095,5096],{},"Year 3:"," Recertification audit (full reassessment).",[37,5099,5100],{},"After recertification, the cycle repeats. The certificate issued at initial certification and at recertification is valid for three years, contingent on successful surveillance audits in the intervening years.",[37,5102,5103],{},"If a surveillance audit reveals significant issues that are not resolved, the certification body can suspend or withdraw your certificate.",[32,5105,5107],{"id":5106},"what-is-a-surveillance-audit","What Is a Surveillance Audit?",[37,5109,5110],{},"A surveillance audit is a smaller-scale audit conducted by your certification body to confirm that your ISMS is still operating effectively and in conformity with ISO 27001. Unlike the initial certification audit, surveillance audits do not assess every control and every clause. Instead, they sample specific areas while always covering certain mandatory elements.",[560,5112,5114],{"id":5113},"mandatory-elements","Mandatory Elements",[37,5116,5117],{},"Every surveillance audit must assess:",[164,5119,5120,5126,5132,5138,5144,5150,5156],{},[167,5121,5122,5125],{},[103,5123,5124],{},"Internal audit results."," The certification body reviews whether you have conducted internal audits as planned and whether findings have been addressed.",[167,5127,5128,5131],{},[103,5129,5130],{},"Management review results."," Evidence that top management has reviewed the ISMS and taken action on its outputs.",[167,5133,5134,5137],{},[103,5135,5136],{},"Corrective actions."," Status of any nonconformities raised in previous audits (both internal and external).",[167,5139,5140,5143],{},[103,5141,5142],{},"Handling of complaints."," How complaints related to information security have been managed.",[167,5145,5146,5149],{},[103,5147,5148],{},"ISMS effectiveness."," Whether the ISMS is achieving its intended outcomes and objectives.",[167,5151,5152,5155],{},[103,5153,5154],{},"Progress on planned improvements."," Actions identified in previous reviews or audits that were planned for implementation.",[167,5157,5158,5161],{},[103,5159,5160],{},"Use of marks and references to certification."," That the organization is using its certification status accurately and in accordance with the CB's rules.",[560,5163,5165],{"id":5164},"sampled-elements","Sampled Elements",[37,5167,5168,5169,5171],{},"In addition to the mandatory elements, the auditor selects a sample of ",[40,5170,113],{"href":130}," and ISMS processes to verify. The sampling is designed so that, across the two surveillance audits in a cycle, all significant areas of the ISMS are assessed at least once.",[37,5173,5174],{},"The auditor may choose areas based on:",[164,5176,5177,5180,5183,5186],{},[167,5178,5179],{},"Results of the previous audit",[167,5181,5182],{},"Known changes to the organization or its environment",[167,5184,5185],{},"Areas that were not covered in recent audits",[167,5187,5188],{},"Specific risk areas or controls that are inherently complex",[32,5190,5192],{"id":5191},"how-surveillance-audits-differ-from-certification-audits","How Surveillance Audits Differ from Certification Audits",[1596,5194,5195,5208],{},[1599,5196,5197],{},[1602,5198,5199,5202,5205],{},[1605,5200,5201],{},"Aspect",[1605,5203,5204],{},"Certification Audit",[1605,5206,5207],{},"Surveillance Audit",[1612,5209,5210,5221,5231,5242,5253],{},[1602,5211,5212,5215,5218],{},[1617,5213,5214],{},"Scope",[1617,5216,5217],{},"Full ISMS",[1617,5219,5220],{},"Sampled subset plus mandatory elements",[1602,5222,5223,5225,5228],{},[1617,5224,1610],{},[1617,5226,5227],{},"3-10 audit days",[1617,5229,5230],{},"1-3 audit days typically",[1602,5232,5233,5236,5239],{},[1617,5234,5235],{},"Frequency",[1617,5237,5238],{},"Every 3 years",[1617,5240,5241],{},"Annually (years 1 and 2)",[1602,5243,5244,5247,5250],{},[1617,5245,5246],{},"Output",[1617,5248,5249],{},"Certification decision",[1617,5251,5252],{},"Continued certification or findings",[1602,5254,5255,5258,5261],{},[1617,5256,5257],{},"Stage 1 required",[1617,5259,5260],{},"Yes",[1617,5262,5263],{},"No",[37,5265,5266],{},"Surveillance audits are shorter and less comprehensive, but they are not less serious. A major nonconformity found during surveillance carries the same weight as one found during initial certification and must be resolved within an agreed timeframe, usually 90 days, or the certificate may be suspended.",[32,5268,5270],{"id":5269},"preparing-for-surveillance-audits","Preparing for Surveillance Audits",[37,5272,5273],{},"The best preparation strategy is to maintain your ISMS as a living system rather than treating it as a certification artifact that gets dusted off before each audit. Here is what that looks like in practice.",[560,5275,5277],{"id":5276},"keep-the-risk-register-current","Keep the Risk Register Current",[37,5279,5280,5281,5284],{},"Your ",[40,5282,5283],{"href":240},"risk register"," should reflect current risks, not the risks that existed when you were first certified. Review and update it at planned intervals and whenever significant changes occur. Auditors will check that recent organizational or environmental changes have been reflected in your risk assessments.",[560,5286,5288],{"id":5287},"conduct-internal-audits-on-schedule","Conduct Internal Audits on Schedule",[37,5290,5291],{},"Plan your internal audit program to cover the full ISMS over the course of the three-year cycle. Ensure audits are actually conducted according to the plan, findings are documented, and corrective actions are tracked to closure. A common surveillance audit finding is that internal audits were not performed as planned.",[560,5293,5295],{"id":5294},"hold-management-reviews","Hold Management Reviews",[37,5297,5298],{},"Management reviews must happen at the frequency defined in your ISMS. Document the agenda, attendees, inputs reviewed, decisions made, and actions assigned. Auditors will ask to see management review records and will verify that actions from previous reviews have been completed.",[560,5300,5302],{"id":5301},"update-the-statement-of-applicability","Update the Statement of Applicability",[37,5304,5305,5306,5308],{},"If your control landscape has changed since the last audit (new controls implemented, controls modified, or controls that are no longer relevant), your ",[40,5307,143],{"href":153}," should reflect those changes. A stale SoA that does not match your actual control environment is a red flag.",[560,5310,5312],{"id":5311},"track-and-close-nonconformities","Track and Close Nonconformities",[37,5314,5315],{},"Any nonconformities from previous audits (internal or external) must have documented corrective actions. Auditors will verify that corrective actions were implemented, that root causes were addressed, and that the corrective actions were effective. Simply implementing a fix without confirming its effectiveness is a common gap.",[560,5317,5319],{"id":5318},"maintain-evidence","Maintain Evidence",[37,5321,5322],{},"Controls need ongoing evidence of operation. Access reviews should have records, training should have attendance logs, incidents should have response records, and backups should have test results. If the evidence trail goes cold between audits, it suggests the controls are not consistently operating.",[560,5324,5326],{"id":5325},"document-changes","Document Changes",[37,5328,5329],{},"Changes to the organization's structure, technology, processes, or external environment should be documented along with any impact assessment on the ISMS. Significant changes that were not reflected in updated risk assessments or control implementations are a frequent source of audit findings.",[32,5331,5333],{"id":5332},"the-recertification-audit","The Recertification Audit",[37,5335,5336],{},"In year three of the certification cycle, a full recertification audit replaces the surveillance audit. Recertification is essentially a repeat of the initial certification audit, though auditors will have the benefit of two years of surveillance audit history.",[37,5338,5339],{},"The recertification audit:",[164,5341,5342,5345,5348,5351],{},[167,5343,5344],{},"Covers the entire ISMS scope",[167,5346,5347],{},"Reassesses all clauses (4-10) and a comprehensive sample of Annex A controls",[167,5349,5350],{},"Evaluates the overall effectiveness and maturity of the ISMS over the previous cycle",[167,5352,5353],{},"Results in a new three-year certificate if successful",[37,5355,5356],{},"Recertification audits are longer than surveillance audits but typically shorter than the initial certification because the auditor already has a baseline understanding of the organization. Plan for roughly two-thirds of the initial audit duration.",[37,5358,5359],{},"It is critical to schedule recertification before your current certificate expires. If the certificate lapses, you may need to go through the full initial certification process again, including Stage 1.",[32,5361,5363],{"id":5362},"what-happens-if-you-fail","What Happens If You Fail",[37,5365,5366],{},"If a surveillance or recertification audit reveals a major nonconformity:",[1446,5368,5369,5375,5381,5387],{},[167,5370,5371,5374],{},[103,5372,5373],{},"Corrective action period."," You are given a defined window (typically 90 days) to implement corrective action and provide evidence of resolution.",[167,5376,5377,5380],{},[103,5378,5379],{},"Verification."," The auditor verifies the corrective action, either through documentation review or a follow-up visit.",[167,5382,5383,5386],{},[103,5384,5385],{},"Suspension."," If corrective action is not satisfactorily completed, the CB may suspend your certificate. Suspension means you cannot claim certification until the issue is resolved.",[167,5388,5389,5392],{},[103,5390,5391],{},"Withdrawal."," If suspension is not resolved within a defined period (typically six months), the certificate is withdrawn entirely.",[37,5394,5395],{},"Minor nonconformities follow a similar process but are less likely to result in suspension if addressed promptly.",[32,5397,5399],{"id":5398},"common-surveillance-audit-findings","Common Surveillance Audit Findings",[37,5401,5402],{},"Based on typical audit outcomes, the most frequent findings include:",[164,5404,5405,5411,5417,5423,5429,5435,5441],{},[167,5406,5407,5410],{},[103,5408,5409],{},"Incomplete internal audit coverage."," The internal audit program did not cover all planned areas.",[167,5412,5413,5416],{},[103,5414,5415],{},"Overdue corrective actions."," Nonconformities from previous audits remain open past their target dates.",[167,5418,5419,5422],{},[103,5420,5421],{},"Outdated risk assessments."," The risk register has not been updated to reflect organizational or environmental changes.",[167,5424,5425,5428],{},[103,5426,5427],{},"Missing management review records."," Management reviews were not conducted or were insufficiently documented.",[167,5430,5431,5434],{},[103,5432,5433],{},"Evidence gaps."," Controls are documented in the SoA but evidence of ongoing operation is insufficient.",[167,5436,5437,5440],{},[103,5438,5439],{},"Awareness shortfalls."," New employees have not received information security awareness training.",[167,5442,5443,5446],{},[103,5444,5445],{},"Change management gaps."," Significant changes to systems or processes were not assessed for security impact.",[32,5448,5450],{"id":5449},"staying-audit-ready-year-round","Staying Audit-Ready Year-Round",[37,5452,5453],{},"The organizations that find surveillance audits painless are the ones that operate their ISMS continuously rather than in audit preparation sprints. Key practices include:",[164,5455,5456,5462,5468,5474],{},[167,5457,5458,5461],{},[103,5459,5460],{},"Monthly or quarterly control reviews"," where control owners verify their controls are operating and evidence is current.",[167,5463,5464,5467],{},[103,5465,5466],{},"Integrated processes"," where security reviews are embedded into change management, project management, and vendor management rather than running as separate tracks.",[167,5469,5470,5473],{},[103,5471,5472],{},"Automated evidence collection"," that captures control operation artifacts without manual effort.",[167,5475,5476,5479],{},[103,5477,5478],{},"Dashboard visibility"," so management and ISMS owners can see the current state of compliance at any time.",[37,5481,5482,5483,5486,5487,5489],{},"Tools like episki keep your risk register, ",[40,5484,5485],{"href":153},"SoA",", control evidence, and review schedules connected and current, making surveillance audits a verification of ongoing practice rather than a scramble to reconstruct twelve months of activity. Explore the full ",[40,5488,43],{"href":42}," framework to understand how surveillance fits into the broader compliance lifecycle.",{"title":427,"searchDepth":428,"depth":428,"links":5491},[5492,5493,5497,5498,5507,5508,5509,5510],{"id":5064,"depth":428,"text":5065},{"id":5106,"depth":428,"text":5107,"children":5494},[5495,5496],{"id":5113,"depth":963,"text":5114},{"id":5164,"depth":963,"text":5165},{"id":5191,"depth":428,"text":5192},{"id":5269,"depth":428,"text":5270,"children":5499},[5500,5501,5502,5503,5504,5505,5506],{"id":5276,"depth":963,"text":5277},{"id":5287,"depth":963,"text":5288},{"id":5294,"depth":963,"text":5295},{"id":5301,"depth":963,"text":5302},{"id":5311,"depth":963,"text":5312},{"id":5318,"depth":963,"text":5319},{"id":5325,"depth":963,"text":5326},{"id":5332,"depth":428,"text":5333},{"id":5362,"depth":428,"text":5363},{"id":5398,"depth":428,"text":5399},{"id":5449,"depth":428,"text":5450},"What happens after ISO 27001 certification, including annual surveillance audits, the three-year certification cycle, recertification requirements, and how to stay audit-ready.",{},[515,982],[987,112,985,984,986],{"title":5516,"description":5517},"ISO 27001 Surveillance Audits — Annual Audits & Recertification Cycle","Understand ISO 27001 surveillance audits, the three-year certification cycle, recertification requirements, and strategies to stay audit-ready year-round.","5.frameworks\u002Fiso27001\u002Fsurveillance-audits","pzAi9DtvJ9EtuNmxMD1q_zg8FkmbFMwx7DY1ktDoK7I",[5521,6083,6234,6463,6705,6912,7157,7437,7655,7864,8093,8353,8551,8764,8895,9012,9133,9371,9516,9723,10308,10427,10972,11099,11625,11756,11876,11997,12130,12217,12364,12489,12774,13385,13593,13829,14043,14274,14498,15100,15280,15415],{"id":5522,"title":5523,"body":5524,"description":427,"extension":460,"lastUpdated":979,"meta":6066,"navigation":497,"path":6067,"relatedFrameworks":6068,"relatedTerms":6074,"seo":6077,"slug":6080,"stem":6081,"term":5529,"__hash__":6082},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":29,"value":5525,"toc":6052},[5526,5530,5533,5537,5540,5566,5570,5576,5582,5588,5594,5598,5601,5607,5624,5630,5644,5650,5661,5665,5668,5719,5723,5726,5740,5744,5747,5770,5774,5777,5826,5830,5833,5947,5950,5953,5982,5986,5992,5995,6032,6035,6038,6041,6045],[32,5527,5529],{"id":5528},"what-is-access-control","What is Access Control?",[37,5531,5532],{},"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.",[560,5534,5536],{"id":5535},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[37,5538,5539],{},"Access control is built on several foundational principles:",[164,5541,5542,5548,5554,5560],{},[167,5543,5544,5547],{},[103,5545,5546],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[167,5549,5550,5553],{},[103,5551,5552],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[167,5555,5556,5559],{},[103,5557,5558],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[167,5561,5562,5565],{},[103,5563,5564],{},"Default deny"," — access is denied by default unless explicitly granted",[560,5567,5569],{"id":5568},"what-are-the-types-of-access-control","What are the types of access control?",[37,5571,5572,5575],{},[103,5573,5574],{},"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,5577,5578,5581],{},[103,5579,5580],{},"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,5583,5584,5587],{},[103,5585,5586],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[37,5589,5590,5593],{},[103,5591,5592],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[560,5595,5597],{"id":5596},"what-are-access-control-components","What are access control components?",[37,5599,5600],{},"A complete access control program addresses:",[37,5602,5603,5606],{},[103,5604,5605],{},"Authentication"," — verifying the identity of users:",[164,5608,5609,5612,5615,5618,5621],{},[167,5610,5611],{},"Passwords and passphrases",[167,5613,5614],{},"Multi-factor authentication (MFA)",[167,5616,5617],{},"Single sign-on (SSO)",[167,5619,5620],{},"Biometric authentication",[167,5622,5623],{},"Certificate-based authentication",[37,5625,5626,5629],{},[103,5627,5628],{},"Authorization"," — determining what authenticated users can do:",[164,5631,5632,5635,5638,5641],{},[167,5633,5634],{},"Permission assignments",[167,5636,5637],{},"Role definitions",[167,5639,5640],{},"Access control lists",[167,5642,5643],{},"Policy enforcement points",[37,5645,5646,5649],{},[103,5647,5648],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[164,5651,5652,5655,5658],{},[167,5653,5654],{},"Provisioning (granting access when hired or role changes)",[167,5656,5657],{},"Review (periodic access certification)",[167,5659,5660],{},"Deprovisioning (revoking access upon termination or role change)",[560,5662,5664],{"id":5663},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[37,5666,5667],{},"Every major framework requires access control:",[164,5669,5670,5677,5687,5701,5710],{},[167,5671,5672,5676],{},[103,5673,5674],{},[40,5675,381],{"href":380}," — CC6.1 through CC6.8 cover logical and physical access controls",[167,5678,5679,5683,5684,5686],{},[103,5680,5681],{},[40,5682,43],{"href":498}," — ",[40,5685,4417],{"href":119}," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[167,5688,5689,5695,5696,5700],{},[103,5690,5691],{},[40,5692,5694],{"href":5693},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[40,5697,5699],{"href":5698},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[167,5702,5703,5709],{},[103,5704,5705],{},[40,5706,5708],{"href":5707},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[167,5711,5712,5718],{},[103,5713,5714],{},[40,5715,5717],{"href":5716},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," — PR.AC covers identity management, authentication, and access control",[560,5720,5722],{"id":5721},"what-are-access-reviews","What are access reviews?",[37,5724,5725],{},"Regular access reviews (also called access certifications) are a critical control:",[164,5727,5728,5731,5734,5737],{},[167,5729,5730],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[167,5732,5733],{},"Verify that access aligns with current job responsibilities",[167,5735,5736],{},"Identify and remove excessive or unnecessary access",[167,5738,5739],{},"Document review results and remediation actions",[560,5741,5743],{"id":5742},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[37,5745,5746],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[164,5748,5749,5752,5755,5758,5761,5764,5767],{},[167,5750,5751],{},"Excessive permissions that accumulate over time (privilege creep)",[167,5753,5754],{},"Shared or generic accounts that prevent individual accountability",[167,5756,5757],{},"Delayed deprovisioning when employees leave or change roles",[167,5759,5760],{},"Lack of MFA on critical systems and remote access paths",[167,5762,5763],{},"Inconsistent access review processes with no documented remediation",[167,5765,5766],{},"Service accounts with standing privileged access and no rotation schedule",[167,5768,5769],{},"Lack of visibility into SaaS application access outside the corporate IdP",[560,5771,5773],{"id":5772},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[37,5775,5776],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[1446,5778,5779,5785,5791,5797,5803,5809,5820],{},[167,5780,5781,5784],{},[103,5782,5783],{},"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.",[167,5786,5787,5790],{},[103,5788,5789],{},"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.",[167,5792,5793,5796],{},[103,5794,5795],{},"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.",[167,5798,5799,5802],{},[103,5800,5801],{},"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.",[167,5804,5805,5808],{},[103,5806,5807],{},"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.",[167,5810,5811,5814,5815,5819],{},[103,5812,5813],{},"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 ",[40,5816,5818],{"href":5817},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[167,5821,5822,5825],{},[103,5823,5824],{},"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.",[560,5827,5829],{"id":5828},"what-are-the-access-control-requirements","What are the access control requirements?",[37,5831,5832],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[1596,5834,5835,5852],{},[1599,5836,5837],{},[1602,5838,5839,5842,5844,5846,5848,5850],{},[1605,5840,5841],{},"Requirement",[1605,5843,381],{},[1605,5845,43],{},[1605,5847,5694],{},[1605,5849,5708],{},[1605,5851,5717],{},[1612,5853,5854,5874,5893,5913,5930],{},[1602,5855,5856,5859,5862,5865,5868,5871],{},[1617,5857,5858],{},"Unique user IDs",[1617,5860,5861],{},"CC6.1",[1617,5863,5864],{},"A.5.16",[1617,5866,5867],{},"§164.312(a)(2)(i)",[1617,5869,5870],{},"Req 8.2.1",[1617,5872,5873],{},"PR.AC-1",[1602,5875,5876,5879,5881,5884,5887,5890],{},[1617,5877,5878],{},"MFA",[1617,5880,5861],{},[1617,5882,5883],{},"A.8.5",[1617,5885,5886],{},"Addressable",[1617,5888,5889],{},"Req 8.4",[1617,5891,5892],{},"PR.AC-7",[1602,5894,5895,5898,5901,5904,5907,5910],{},[1617,5896,5897],{},"Access reviews",[1617,5899,5900],{},"CC6.2",[1617,5902,5903],{},"A.5.18",[1617,5905,5906],{},"§164.312(a)(1)",[1617,5908,5909],{},"Req 7.2",[1617,5911,5912],{},"PR.AC-4",[1602,5914,5915,5917,5920,5923,5925,5928],{},[1617,5916,5546],{},[1617,5918,5919],{},"CC6.3",[1617,5921,5922],{},"A.5.15",[1617,5924,5906],{},[1617,5926,5927],{},"Req 7.1",[1617,5929,5912],{},[1602,5931,5932,5935,5937,5939,5942,5945],{},[1617,5933,5934],{},"Deprovisioning",[1617,5936,5900],{},[1617,5938,5903],{},[1617,5940,5941],{},"§164.312(a)(2)(ii)",[1617,5943,5944],{},"Req 8.2.6",[1617,5946,5873],{},[37,5948,5949],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[37,5951,5952],{},"A few notes on framework-specific nuances:",[164,5954,5955,5960,5968,5975],{},[167,5956,5957,5959],{},[103,5958,5694],{}," 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.",[167,5961,5962,5967],{},[103,5963,5964,5966],{},[40,5965,5708],{"href":5707}," 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.",[167,5969,5970,5974],{},[103,5971,5972],{},[40,5973,381],{"href":380}," 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.",[167,5976,5977,5981],{},[103,5978,5979],{},[40,5980,5717],{"href":5716}," 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.",[560,5983,5985],{"id":5984},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[37,5987,5988,5989,242],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[103,5990,5991],{},"never trust, always verify",[37,5993,5994],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[164,5996,5997,6003,6009,6020,6026],{},[167,5998,5999,6002],{},[103,6000,6001],{},"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.",[167,6004,6005,6008],{},[103,6006,6007],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[167,6010,6011,6014,6015,6019],{},[103,6012,6013],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[40,6016,6018],{"href":6017},"\u002Fglossary\u002Fencryption","encryption",") is evaluated before access is granted.",[167,6021,6022,6025],{},[103,6023,6024],{},"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.",[167,6027,6028,6031],{},[103,6029,6030],{},"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,6033,6034],{},"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,6036,6037],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[37,6039,6040],{},"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.",[560,6042,6044],{"id":6043},"how-does-episki-help-with-access-control","How does episki help with access control?",[37,6046,6047,6048,242],{},"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 ",[40,6049,6051],{"href":6050},"\u002Fframeworks","compliance platform",{"title":427,"searchDepth":428,"depth":428,"links":6053},[6054],{"id":5528,"depth":428,"text":5529,"children":6055},[6056,6057,6058,6059,6060,6061,6062,6063,6064,6065],{"id":5535,"depth":963,"text":5536},{"id":5568,"depth":963,"text":5569},{"id":5596,"depth":963,"text":5597},{"id":5663,"depth":963,"text":5664},{"id":5721,"depth":963,"text":5722},{"id":5742,"depth":963,"text":5743},{"id":5772,"depth":963,"text":5773},{"id":5828,"depth":963,"text":5829},{"id":5984,"depth":963,"text":5985},{"id":6043,"depth":963,"text":6044},{},"\u002Fglossary\u002Faccess-control",[6069,6070,515,6071,6072,6073],"cmmc","soc2","hipaa","pci","nistcsf",[6075,2697,6018,6076],"minimum-necessary-rule","user-entity-controls",{"title":6078,"description":6079},"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.","access-control","8.glossary\u002Faccess-control","06FHtOe5hEs65vhNnMjZcNgPP9NXCQTnLD9llz_jEjM",{"id":6084,"title":4417,"body":6085,"description":427,"extension":460,"lastUpdated":979,"meta":6223,"navigation":497,"path":119,"relatedFrameworks":6224,"relatedTerms":6225,"seo":6228,"slug":6231,"stem":6232,"term":6090,"__hash__":6233},"glossary\u002F8.glossary\u002Fannex-a.md",{"type":29,"value":6086,"toc":6213},[6087,6091,6101,6105,6108,6134,6138,6141,6158,6161,6165,6168,6172,6175,6189,6192,6195,6203,6207],[32,6088,6090],{"id":6089},"what-is-iso-27001-annex-a","What is ISO 27001 Annex A?",[37,6092,6093,6094,6096,6097,6100],{},"ISO 27001 Annex A is the normative annex to the ",[40,6095,43],{"href":498}," standard that provides a reference list of information security controls. Organizations use Annex A as a checklist to ensure their ",[40,6098,6099],{"href":214},"Information Security Management System (ISMS)"," addresses a comprehensive range of security topics. As of the 2022 revision, Annex A contains 93 controls organized into four themes.",[560,6102,6104],{"id":6103},"what-are-the-four-themes","What are the four themes?",[37,6106,6107],{},"The 2022 revision reorganized controls from the previous 14 categories into four themes:",[164,6109,6110,6116,6122,6128],{},[167,6111,6112,6115],{},[103,6113,6114],{},"Organizational controls (37 controls)"," — policies, roles and responsibilities, threat intelligence, information security in project management, supplier relationships, and more",[167,6117,6118,6121],{},[103,6119,6120],{},"People controls (8 controls)"," — screening, terms and conditions of employment, security awareness training, disciplinary processes, and responsibilities after termination",[167,6123,6124,6127],{},[103,6125,6126],{},"Physical controls (14 controls)"," — physical security perimeters, entry controls, securing offices and facilities, equipment protection, and clear desk policies",[167,6129,6130,6133],{},[103,6131,6132],{},"Technological controls (34 controls)"," — user endpoint devices, privileged access management, access restrictions, secure authentication, malware protection, logging, encryption, and secure development",[560,6135,6137],{"id":6136},"how-does-annex-a-fit-into-iso-27001","How does Annex A fit into ISO 27001?",[37,6139,6140],{},"Annex A is not a standalone list of mandatory controls. Instead, it works in conjunction with the risk assessment process defined in clauses 6 and 8 of ISO 27001:",[1446,6142,6143,6146,6149,6152,6155],{},[167,6144,6145],{},"The organization performs a risk assessment to identify information security risks",[167,6147,6148],{},"The organization determines how to treat each risk (mitigate, accept, transfer, or avoid)",[167,6150,6151],{},"For risks being mitigated, the organization selects appropriate controls",[167,6153,6154],{},"The organization compares selected controls against Annex A to ensure nothing has been overlooked",[167,6156,6157],{},"The results are documented in the Statement of Applicability",[37,6159,6160],{},"This approach ensures that control selection is risk-driven rather than checkbox-driven. An organization may determine that certain Annex A controls are not applicable based on their specific risk profile, and this is acceptable as long as the justification is documented.",[560,6162,6164],{"id":6163},"how-does-annex-a-relate-to-iso-27002","How does Annex A relate to ISO 27002?",[37,6166,6167],{},"ISO 27002 provides detailed implementation guidance for each Annex A control. While Annex A lists the controls with brief descriptions, ISO 27002 explains the purpose, guidance, and other information for each control. Think of Annex A as the \"what\" and ISO 27002 as the \"how.\"",[560,6169,6171],{"id":6170},"what-changed-in-the-2022-revision-of-annex-a","What changed in the 2022 revision of Annex A?",[37,6173,6174],{},"The 2022 update introduced several changes from the 2013 version:",[164,6176,6177,6180,6183,6186],{},[167,6178,6179],{},"Controls were consolidated from 114 to 93",[167,6181,6182],{},"The 14 categories were replaced with 4 themes",[167,6184,6185],{},"11 new controls were added, including threat intelligence, information security for cloud services, ICT readiness for business continuity, and data masking",[167,6187,6188],{},"Each control now includes attributes (control type, cybersecurity concept, operational capability, and security domain) to aid in filtering and mapping",[37,6190,6191],{},"Organizations certified under the 2013 version had a transition period to update their ISMS to align with the 2022 revision.",[560,6193,6194],{"id":4669},"What is the Statement of Applicability?",[37,6196,139,6197,6199,6200,6202],{},[40,6198,136],{"href":153}," is the document where an organization records which Annex A controls are applicable, which are not, and the justification for each decision. The SoA is a mandatory document for ",[40,6201,4335],{"href":84}," and is a key artifact reviewed during certification audits.",[560,6204,6206],{"id":6205},"how-does-episki-help-with-annex-a","How does episki help with Annex A?",[37,6208,6209,6210,242],{},"episki includes all 93 Annex A controls with mappings to your risk treatment plan and Statement of Applicability. The platform helps you track implementation status, assign ownership, and collect evidence for each applicable control. Learn more on our ",[40,6211,6212],{"href":498},"ISO 27001 compliance page",{"title":427,"searchDepth":428,"depth":428,"links":6214},[6215],{"id":6089,"depth":428,"text":6090,"children":6216},[6217,6218,6219,6220,6221,6222],{"id":6103,"depth":963,"text":6104},{"id":6136,"depth":963,"text":6137},{"id":6163,"depth":963,"text":6164},{"id":6170,"depth":963,"text":6171},{"id":4669,"depth":963,"text":6194},{"id":6205,"depth":963,"text":6206},{},[515],[515,984,6226,6227,982],"iso-27002","control-objectives",{"title":6229,"description":6230},"ISO 27001 Annex A: All 93 Controls Explained (2022)","ISO 27001 Annex A lists 93 security controls in 4 themes. Learn each control category, how they map to your Statement of Applicability, and implementation tips.","annex-a","8.glossary\u002Fannex-a","7UuJknizYAej4wh0vgz3iQYe-_A9-r5bjizs222-Avw",{"id":6235,"title":6236,"body":6237,"description":427,"extension":460,"lastUpdated":979,"meta":6455,"navigation":497,"path":5817,"relatedFrameworks":6456,"relatedTerms":6457,"seo":6458,"slug":2697,"stem":6461,"term":6242,"__hash__":6462},"glossary\u002F8.glossary\u002Faudit-trail.md","Audit Trail",{"type":29,"value":6238,"toc":6445},[6239,6243,6246,6250,6253,6291,6294,6314,6318,6321,6343,6347,6350,6394,6398,6401,6415,6419,6436,6440],[32,6240,6242],{"id":6241},"what-is-an-audit-trail","What is an Audit Trail?",[37,6244,6245],{},"An audit trail is a chronological record of activities, events, and changes within a system or process that provides documentary evidence of the sequence of actions performed. Audit trails answer the fundamental questions: who did what, when did they do it, where did it happen, and what was the result. They are essential for security monitoring, incident investigation, compliance demonstration, and accountability.",[560,6247,6249],{"id":6248},"what-do-audit-trails-capture","What do audit trails capture?",[37,6251,6252],{},"Effective audit trails typically record:",[164,6254,6255,6261,6267,6273,6279,6285],{},[167,6256,6257,6260],{},[103,6258,6259],{},"User actions"," — logins, logouts, data access, data modifications, privilege changes",[167,6262,6263,6266],{},[103,6264,6265],{},"System events"," — configuration changes, service starts and stops, errors, failures",[167,6268,6269,6272],{},[103,6270,6271],{},"Administrative actions"," — user account creation and deletion, permission changes, policy updates",[167,6274,6275,6278],{},[103,6276,6277],{},"Data changes"," — creation, modification, and deletion of records, including before and after values where applicable",[167,6280,6281,6284],{},[103,6282,6283],{},"Access attempts"," — both successful and failed authentication and authorization attempts",[167,6286,6287,6290],{},[103,6288,6289],{},"Security events"," — firewall rule changes, intrusion detection alerts, malware detections",[37,6292,6293],{},"Each audit trail entry should include:",[164,6295,6296,6299,6302,6305,6308,6311],{},[167,6297,6298],{},"Timestamp (synchronized across systems)",[167,6300,6301],{},"User or system identity",[167,6303,6304],{},"Action performed",[167,6306,6307],{},"Target resource or data",[167,6309,6310],{},"Outcome (success or failure)",[167,6312,6313],{},"Source (IP address, device, or location)",[560,6315,6317],{"id":6316},"what-are-the-audit-trail-requirements","What are the audit trail requirements?",[37,6319,6320],{},"Multiple compliance frameworks require audit trails:",[164,6322,6323,6328,6333,6338],{},[167,6324,6325,6327],{},[103,6326,381],{}," — CC7.2 requires monitoring of system components for anomalies, and CC6.1 requires logical access controls with logging",[167,6329,6330,6332],{},[103,6331,43],{}," — control A.8.15 addresses logging, and A.8.17 addresses clock synchronization for accurate audit trails",[167,6334,6335,6337],{},[103,6336,5694],{}," — the Security Rule requires audit controls that record and examine activity in systems containing ePHI (45 CFR 164.312(b))",[167,6339,6340,6342],{},[103,6341,5708],{}," — Requirement 10 mandates logging and monitoring all access to network resources and cardholder data",[560,6344,6346],{"id":6345},"how-do-you-implement-audit-trails","How do you implement audit trails?",[37,6348,6349],{},"To implement effective audit trails:",[1446,6351,6352,6358,6364,6370,6376,6382,6388],{},[167,6353,6354,6357],{},[103,6355,6356],{},"Enable logging"," — activate audit logging on all in-scope systems including applications, databases, operating systems, and network devices",[167,6359,6360,6363],{},[103,6361,6362],{},"Centralize logs"," — aggregate logs into a central platform (SIEM) for correlation and analysis",[167,6365,6366,6369],{},[103,6367,6368],{},"Protect integrity"," — ensure logs cannot be modified or deleted by users, including administrators",[167,6371,6372,6375],{},[103,6373,6374],{},"Synchronize time"," — use NTP to ensure timestamps are consistent across all systems",[167,6377,6378,6381],{},[103,6379,6380],{},"Define retention"," — establish retention periods aligned with compliance and business requirements",[167,6383,6384,6387],{},[103,6385,6386],{},"Monitor actively"," — review audit trails for suspicious activity, not just for compliance evidence",[167,6389,6390,6393],{},[103,6391,6392],{},"Automate alerts"," — configure alerts for critical events such as failed login attempts, privilege escalation, and unauthorized access",[560,6395,6397],{"id":6396},"how-long-should-audit-trails-be-retained","How long should audit trails be retained?",[37,6399,6400],{},"Retention requirements vary by framework and jurisdiction:",[164,6402,6403,6406,6409,6412],{},[167,6404,6405],{},"PCI DSS requires at least 12 months of audit trail history, with the most recent 3 months immediately available",[167,6407,6408],{},"HIPAA requires documentation retention for 6 years",[167,6410,6411],{},"ISO 27001 does not specify a fixed period but requires organizations to define and follow their own retention policy",[167,6413,6414],{},"SOC 2 audit periods typically require evidence covering the observation period",[560,6416,6418],{"id":6417},"what-are-common-pitfalls-with-audit-trails","What are common pitfalls with audit trails?",[164,6420,6421,6424,6427,6430,6433],{},[167,6422,6423],{},"Insufficient logging — missing critical events or systems",[167,6425,6426],{},"Log overload — logging too much without meaningful analysis",[167,6428,6429],{},"No log protection — allowing administrators to modify or delete logs",[167,6431,6432],{},"Inconsistent timestamps — making it impossible to correlate events across systems",[167,6434,6435],{},"No review process — collecting logs but never analyzing them",[560,6437,6439],{"id":6438},"how-does-episki-help-with-audit-trails","How does episki help with audit trails?",[37,6441,6442,6443,242],{},"episki integrates with your logging infrastructure to track compliance-relevant events, maintain audit trail records, and demonstrate continuous monitoring to auditors. The platform maps audit trail capabilities to framework requirements and flags gaps in coverage. Learn more on our ",[40,6444,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":6446},[6447],{"id":6241,"depth":428,"text":6242,"children":6448},[6449,6450,6451,6452,6453,6454],{"id":6248,"depth":963,"text":6249},{"id":6316,"depth":963,"text":6317},{"id":6345,"depth":963,"text":6346},{"id":6396,"depth":963,"text":6397},{"id":6417,"depth":963,"text":6418},{"id":6438,"depth":963,"text":6439},{},[6070,515,6071,6072],[2698,6080,2386,4226],{"title":6459,"description":6460},"What is an Audit Trail? Definition & Compliance Guide","An audit trail is a chronological record of system activities that provides evidence of who did what, when, and where for security and compliance purposes.","8.glossary\u002Faudit-trail","wGJCFb9Xcb1bQvrLNHVniHH6roxZCmzstztRki0-h68",{"id":6464,"title":6465,"body":6466,"description":427,"extension":460,"lastUpdated":979,"meta":6692,"navigation":497,"path":6693,"relatedFrameworks":6694,"relatedTerms":6695,"seo":6699,"slug":6702,"stem":6703,"term":6471,"__hash__":6704},"glossary\u002F8.glossary\u002Fbusiness-continuity.md","Business Continuity",{"type":29,"value":6467,"toc":6682},[6468,6472,6475,6479,6482,6496,6499,6503,6509,6520,6526,6543,6549,6566,6572,6589,6593,6616,6620,6623,6649,6652,6656,6673,6677],[32,6469,6471],{"id":6470},"what-is-business-continuity","What is Business Continuity?",[37,6473,6474],{},"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.",[560,6476,6478],{"id":6477},"what-is-the-difference-between-business-continuity-and-disaster-recovery","What is the difference between business continuity and disaster recovery?",[37,6480,6481],{},"While often discussed together, business continuity and disaster recovery serve different purposes:",[164,6483,6484,6490],{},[167,6485,6486,6489],{},[103,6487,6488],{},"Business continuity"," focuses on maintaining overall business operations — it encompasses people, processes, facilities, and technology",[167,6491,6492,6495],{},[103,6493,6494],{},"Disaster recovery"," focuses specifically on restoring IT systems and data after a disruption",[37,6497,6498],{},"Disaster recovery is a subset of business continuity. A comprehensive business continuity program includes disaster recovery as one of its components.",[560,6500,6502],{"id":6501},"what-are-the-components-of-a-business-continuity-plan","What are the components of a business continuity plan?",[37,6504,6505,6508],{},[103,6506,6507],{},"Business Impact Analysis (BIA)"," — identifies critical business functions, the impact of disrupting them, and the maximum tolerable downtime:",[164,6510,6511,6514,6517],{},[167,6512,6513],{},"Recovery Time Objective (RTO) — the maximum acceptable time to restore a function",[167,6515,6516],{},"Recovery Point Objective (RPO) — the maximum acceptable data loss measured in time",[167,6518,6519],{},"Maximum Tolerable Period of Disruption (MTPD) — the longest the business can survive without the function",[37,6521,6522,6525],{},[103,6523,6524],{},"Risk assessment"," — identifies threats that could disrupt operations and evaluates their likelihood and impact:",[164,6527,6528,6531,6534,6537,6540],{},[167,6529,6530],{},"Natural disasters (earthquakes, floods, severe weather)",[167,6532,6533],{},"Technology failures (hardware failure, software bugs, network outages)",[167,6535,6536],{},"Cyber incidents (ransomware, DDoS attacks, data breaches)",[167,6538,6539],{},"Human factors (key personnel loss, labor disputes)",[167,6541,6542],{},"Supply chain disruptions (vendor failures, logistics breakdowns)",[37,6544,6545,6548],{},[103,6546,6547],{},"Recovery strategies"," — defines how critical functions will be maintained or restored:",[164,6550,6551,6554,6557,6560,6563],{},[167,6552,6553],{},"Alternative work locations or remote work capabilities",[167,6555,6556],{},"Redundant systems and infrastructure",[167,6558,6559],{},"Manual workaround procedures",[167,6561,6562],{},"Third-party recovery services",[167,6564,6565],{},"Communication plans for employees, customers, and stakeholders",[37,6567,6568,6571],{},[103,6569,6570],{},"Plan documentation"," — the written BCP includes:",[164,6573,6574,6577,6580,6583,6586],{},[167,6575,6576],{},"Roles and responsibilities",[167,6578,6579],{},"Contact information for key personnel and vendors",[167,6581,6582],{},"Step-by-step recovery procedures for each critical function",[167,6584,6585],{},"Resource requirements",[167,6587,6588],{},"Communication templates",[560,6590,6592],{"id":6591},"how-do-compliance-frameworks-address-business-continuity","How do compliance frameworks address business continuity?",[164,6594,6595,6600,6605,6610],{},[167,6596,6597,6599],{},[103,6598,43],{}," — control A.5.29 addresses information security during disruption, and A.5.30 addresses ICT readiness for business continuity",[167,6601,6602,6604],{},[103,6603,5717],{}," — the Recover function (RC) addresses recovery planning, improvements, and communications",[167,6606,6607,6609],{},[103,6608,381],{}," — the Availability criterion addresses system uptime and recovery capabilities",[167,6611,6612,6615],{},[103,6613,6614],{},"ISO 22301"," — the dedicated international standard for business continuity management systems",[560,6617,6619],{"id":6618},"how-do-you-test-a-business-continuity-plan","How do you test a business continuity plan?",[37,6621,6622],{},"A business continuity plan that has not been tested is unreliable. Testing approaches include:",[164,6624,6625,6631,6637,6643],{},[167,6626,6627,6630],{},[103,6628,6629],{},"Tabletop exercises"," — team discussions walking through scenarios",[167,6632,6633,6636],{},[103,6634,6635],{},"Structured walkthroughs"," — step-by-step review of procedures with assigned teams",[167,6638,6639,6642],{},[103,6640,6641],{},"Simulation tests"," — practicing response to a simulated disruption",[167,6644,6645,6648],{},[103,6646,6647],{},"Full interruption tests"," — actually activating recovery procedures (highest assurance but most disruptive)",[37,6650,6651],{},"Testing should occur at least annually and after significant changes to the business or infrastructure.",[560,6653,6655],{"id":6654},"what-are-common-pitfalls-with-business-continuity","What are common pitfalls with business continuity?",[164,6657,6658,6661,6664,6667,6670],{},[167,6659,6660],{},"BCP exists on paper but is never tested or updated",[167,6662,6663],{},"Critical dependencies on single points of failure are not identified",[167,6665,6666],{},"Communication plans do not account for the disruption itself (e.g., email is down)",[167,6668,6669],{},"Key personnel are not trained on their BCP responsibilities",[167,6671,6672],{},"The plan does not keep pace with business changes",[560,6674,6676],{"id":6675},"how-does-episki-help-with-business-continuity","How does episki help with business continuity?",[37,6678,6679,6680,242],{},"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 ",[40,6681,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":6683},[6684],{"id":6470,"depth":428,"text":6471,"children":6685},[6686,6687,6688,6689,6690,6691],{"id":6477,"depth":963,"text":6478},{"id":6501,"depth":963,"text":6502},{"id":6591,"depth":963,"text":6592},{"id":6618,"depth":963,"text":6619},{"id":6654,"depth":963,"text":6655},{"id":6675,"depth":963,"text":6676},{},"\u002Fglossary\u002Fbusiness-continuity",[515,6073],[6696,4226,6697,6698],"disaster-recovery","risk-register","risk-treatment-plan",{"title":6700,"description":6701},"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.","business-continuity","8.glossary\u002Fbusiness-continuity","dyPU67gMtqXpCCrubDS7MtzzpZM4MS8zudQDFFznv_U",{"id":6706,"title":6707,"body":6708,"description":427,"extension":460,"lastUpdated":979,"meta":6902,"navigation":497,"path":6903,"relatedFrameworks":6904,"relatedTerms":6905,"seo":6907,"slug":1362,"stem":6910,"term":6713,"__hash__":6911},"glossary\u002F8.glossary\u002Fcertification-body.md","Certification Body",{"type":29,"value":6709,"toc":6892},[6710,6714,6717,6721,6724,6764,6768,6771,6797,6800,6804,6807,6843,6847,6850,6853,6857,6860,6880,6883,6887],[32,6711,6713],{"id":6712},"what-is-a-certification-body","What is a Certification Body?",[37,6715,6716],{},"A certification body (CB), also called a registrar or conformity assessment body, is an independent organization accredited to perform audits and issue certifications against management system standards such as ISO 27001. When an organization achieves ISO 27001 certification, the certificate is issued by the certification body that conducted the audit.",[560,6718,6720],{"id":6719},"how-do-certification-bodies-work","How do certification bodies work?",[37,6722,6723],{},"Certification bodies operate under a structured process:",[1446,6725,6726,6732,6737,6742,6747,6752,6758],{},[167,6727,6728,6731],{},[103,6729,6730],{},"Application"," — the organization applies to the certification body, providing information about the scope of its ISMS",[167,6733,6734,6736],{},[103,6735,1642],{}," — the CB reviews documentation to confirm the ISMS is designed in accordance with ISO 27001 requirements",[167,6738,6739,6741],{},[103,6740,1658],{}," — the CB conducts an on-site or remote audit to verify that the ISMS is implemented and operating effectively",[167,6743,6744,6746],{},[103,6745,5249],{}," — based on audit findings, the CB decides whether to grant certification",[167,6748,6749,6751],{},[103,6750,1666],{}," — if successful, the CB issues a certificate valid for three years",[167,6753,6754,6757],{},[103,6755,6756],{},"Surveillance audits"," — the CB conducts annual surveillance audits to verify continued compliance",[167,6759,6760,6763],{},[103,6761,6762],{},"Recertification"," — at the end of the three-year cycle, a full recertification audit is performed",[560,6765,6767],{"id":6766},"how-are-certification-bodies-accredited","How are certification bodies accredited?",[37,6769,6770],{},"Certification bodies must themselves be accredited by a recognized accreditation body to ensure they operate competently and impartially. Key accreditation bodies include:",[164,6772,6773,6779,6785,6791],{},[167,6774,6775,6778],{},[103,6776,6777],{},"UKAS"," (United Kingdom Accreditation Service)",[167,6780,6781,6784],{},[103,6782,6783],{},"ANAB"," (ANSI National Accreditation Board) in the United States",[167,6786,6787,6790],{},[103,6788,6789],{},"DAkkS"," (Deutsche Akkreditierungsstelle) in Germany",[167,6792,6793,6796],{},[103,6794,6795],{},"JAS-ANZ"," (Joint Accreditation System of Australia and New Zealand)",[37,6798,6799],{},"Accreditation ensures that the certification body follows ISO 17021 (requirements for bodies providing audit and certification of management systems) and employs qualified auditors. Choosing a non-accredited certification body undermines the credibility of the certification.",[560,6801,6803],{"id":6802},"how-do-you-select-a-certification-body","How do you select a certification body?",[37,6805,6806],{},"When choosing a certification body, consider:",[164,6808,6809,6815,6821,6826,6832,6838],{},[167,6810,6811,6814],{},[103,6812,6813],{},"Accreditation"," — verify the CB is accredited by a recognized national accreditation body",[167,6816,6817,6820],{},[103,6818,6819],{},"Industry experience"," — some CBs specialize in certain industries (technology, healthcare, financial services) and understand sector-specific risks",[167,6822,6823,6825],{},[103,6824,1145],{}," — if your organization operates in multiple countries, ensure the CB can support international audits",[167,6827,6828,6831],{},[103,6829,6830],{},"Auditor expertise"," — the quality of the audit depends heavily on the auditor assigned to your engagement",[167,6833,6834,6837],{},[103,6835,6836],{},"Reputation"," — CBs recognized by your customers and partners carry more weight",[167,6839,6840,6842],{},[103,6841,297],{}," — audit fees and scheduling availability vary between CBs",[560,6844,6846],{"id":6845},"what-independence-requirements-apply-to-certification-bodies","What independence requirements apply to certification bodies?",[37,6848,6849],{},"Certification bodies must maintain independence from the organizations they certify. A CB cannot provide consulting services to design or implement the ISMS and then audit it. This separation ensures objectivity in the certification process.",[37,6851,6852],{},"Some organizations engage a consulting firm for ISMS implementation and a separate certification body for the audit to maintain clear boundaries.",[560,6854,6856],{"id":6855},"what-happens-when-nonconformities-are-found","What happens when nonconformities are found?",[37,6858,6859],{},"During an audit, the certification body may identify:",[164,6861,6862,6868,6874],{},[167,6863,6864,6867],{},[103,6865,6866],{},"Major nonconformities"," — significant failures that prevent certification until resolved",[167,6869,6870,6873],{},[103,6871,6872],{},"Minor nonconformities"," — less critical issues that must be addressed within a defined timeframe",[167,6875,6876,6879],{},[103,6877,6878],{},"Opportunities for improvement"," — suggestions that are not required but recommended",[37,6881,6882],{},"Major nonconformities must be resolved and verified before the certificate can be issued. Minor nonconformities typically must be addressed before the next surveillance audit.",[560,6884,6886],{"id":6885},"how-does-episki-help-with-certification-bodies","How does episki help with certification bodies?",[37,6888,6889,6890,242],{},"episki prepares your organization for certification body audits by organizing your ISMS documentation, Statement of Applicability, risk treatment plans, and evidence in a structured format that auditors can easily review. The platform tracks nonconformities and corrective actions to ensure timely resolution. Learn more on our ",[40,6891,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":6893},[6894],{"id":6712,"depth":428,"text":6713,"children":6895},[6896,6897,6898,6899,6900,6901],{"id":6719,"depth":963,"text":6720},{"id":6766,"depth":963,"text":6767},{"id":6802,"depth":963,"text":6803},{"id":6845,"depth":963,"text":6846},{"id":6855,"depth":963,"text":6856},{"id":6885,"depth":963,"text":6886},{},"\u002Fglossary\u002Fcertification-body",[515],[515,6906,984,982],"surveillance-audit",{"title":6908,"description":6909},"What is a Certification Body? Definition & Compliance Guide","A certification body is an accredited organization that audits and certifies companies against standards like ISO 27001. Learn how to choose the right one.","8.glossary\u002Fcertification-body","tGGQs2JaSNO2oRdpjvRKWMpEOGaOW9QFE2G22SZIPHk",{"id":6913,"title":6914,"body":6915,"description":427,"extension":460,"lastUpdated":979,"meta":7147,"navigation":497,"path":7148,"relatedFrameworks":7149,"relatedTerms":7150,"seo":7151,"slug":7154,"stem":7155,"term":6920,"__hash__":7156},"glossary\u002F8.glossary\u002Fchange-management.md","Change Management",{"type":29,"value":6916,"toc":7136},[6917,6921,6924,6928,6931,6948,6952,6955,6961,6980,6986,7000,7006,7017,7023,7034,7040,7051,7055,7072,7076,7096,7100,7103,7107,7110,7127,7131],[32,6918,6920],{"id":6919},"what-is-change-management","What is Change Management?",[37,6922,6923],{},"Change management is the structured process of planning, approving, implementing, and reviewing changes to an organization's information systems, infrastructure, and applications. The goal is to ensure that changes are made in a controlled manner, minimizing the risk of unintended disruptions, security vulnerabilities, or compliance violations.",[560,6925,6927],{"id":6926},"why-does-change-management-matter","Why does change management matter?",[37,6929,6930],{},"Uncontrolled changes are a leading cause of system outages, security incidents, and compliance failures. Without a formal change management process:",[164,6932,6933,6936,6939,6942,6945],{},[167,6934,6935],{},"Untested changes can introduce bugs or vulnerabilities",[167,6937,6938],{},"Unauthorized modifications can compromise security controls",[167,6940,6941],{},"Conflicting changes can cause system instability",[167,6943,6944],{},"Auditors cannot verify that changes were properly authorized and tested",[167,6946,6947],{},"Troubleshooting becomes difficult without a record of what changed",[560,6949,6951],{"id":6950},"what-are-the-components-of-a-change-management-process","What are the components of a change management process?",[37,6953,6954],{},"An effective change management program includes:",[37,6956,6957,6960],{},[103,6958,6959],{},"Change request"," — a formal submission describing the proposed change, including:",[164,6962,6963,6966,6969,6971,6974,6977],{},[167,6964,6965],{},"Description of the change",[167,6967,6968],{},"Business justification",[167,6970,6524],{},[167,6972,6973],{},"Rollback plan",[167,6975,6976],{},"Testing plan",[167,6978,6979],{},"Implementation timeline",[37,6981,6982,6985],{},[103,6983,6984],{},"Review and approval"," — changes are reviewed by appropriate stakeholders:",[164,6987,6988,6991,6994,6997],{},[167,6989,6990],{},"Technical review for feasibility and impact",[167,6992,6993],{},"Security review for potential risks",[167,6995,6996],{},"Management approval based on risk and priority",[167,6998,6999],{},"Change Advisory Board (CAB) review for significant changes",[37,7001,7002,7005],{},[103,7003,7004],{},"Testing"," — changes are tested in a non-production environment before deployment:",[164,7007,7008,7011,7014],{},[167,7009,7010],{},"Functional testing to verify the change works as intended",[167,7012,7013],{},"Regression testing to confirm existing functionality is not broken",[167,7015,7016],{},"Security testing when the change affects security-relevant systems",[37,7018,7019,7022],{},[103,7020,7021],{},"Implementation"," — changes are deployed following the approved plan:",[164,7024,7025,7028,7031],{},[167,7026,7027],{},"During designated maintenance windows when appropriate",[167,7029,7030],{},"With monitoring for unexpected issues",[167,7032,7033],{},"With rollback procedures ready if problems occur",[37,7035,7036,7039],{},[103,7037,7038],{},"Post-implementation review"," — after deployment, verify:",[164,7041,7042,7045,7048],{},[167,7043,7044],{},"The change achieved its intended outcome",[167,7046,7047],{},"No unintended side effects occurred",[167,7049,7050],{},"Documentation is updated to reflect the change",[560,7052,7054],{"id":7053},"how-do-compliance-frameworks-address-change-management","How do compliance frameworks address change management?",[164,7056,7057,7062,7067],{},[167,7058,7059,7061],{},[103,7060,381],{}," — CC8.1 requires that changes to infrastructure, data, software, and procedures are authorized, designed, developed, configured, documented, tested, approved, and implemented",[167,7063,7064,7066],{},[103,7065,43],{}," — control A.8.32 addresses change management, requiring that changes to information processing facilities and systems be subject to change management procedures",[167,7068,7069,7071],{},[103,7070,5708],{}," — Requirement 6.5 requires change control processes for all system components in the cardholder data environment",[560,7073,7075],{"id":7074},"what-are-the-types-of-changes-in-change-management","What are the types of changes in change management?",[164,7077,7078,7084,7090],{},[167,7079,7080,7083],{},[103,7081,7082],{},"Standard changes"," — pre-approved, low-risk, routine changes that follow a documented procedure (e.g., updating a standard software package)",[167,7085,7086,7089],{},[103,7087,7088],{},"Normal changes"," — changes that require the full change management process including review and approval",[167,7091,7092,7095],{},[103,7093,7094],{},"Emergency changes"," — urgent changes needed to resolve incidents or critical issues, typically with streamlined approval followed by retrospective documentation",[560,7097,7099],{"id":7098},"how-does-separation-of-duties-apply-to-change-management","How does separation of duties apply to change management?",[37,7101,7102],{},"A key control within change management is separation of duties — the person who develops a change should not be the same person who approves or deploys it to production. This prevents unauthorized or untested changes from reaching production systems.",[560,7104,7106],{"id":7105},"what-change-management-evidence-do-auditors-look-for","What change management evidence do auditors look for?",[37,7108,7109],{},"Auditors reviewing change management look for:",[164,7111,7112,7115,7118,7121,7124],{},[167,7113,7114],{},"Change request records with documented approvals",[167,7116,7117],{},"Evidence of testing before production deployment",[167,7119,7120],{},"Separation of duties between development, approval, and deployment",[167,7122,7123],{},"Rollback plans for significant changes",[167,7125,7126],{},"Post-implementation reviews",[560,7128,7130],{"id":7129},"how-does-episki-help-with-change-management","How does episki help with change management?",[37,7132,7133,7134,242],{},"episki tracks change management activities, integrates with ticketing and CI\u002FCD systems, and maintains audit-ready evidence of change approvals, testing, and deployment. The platform maps change management controls to SOC 2, ISO 27001, and PCI DSS requirements. Learn more on our ",[40,7135,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":7137},[7138],{"id":6919,"depth":428,"text":6920,"children":7139},[7140,7141,7142,7143,7144,7145,7146],{"id":6926,"depth":963,"text":6927},{"id":6950,"depth":963,"text":6951},{"id":7053,"depth":963,"text":7054},{"id":7074,"depth":963,"text":7075},{"id":7098,"depth":963,"text":7099},{"id":7105,"depth":963,"text":7106},{"id":7129,"depth":963,"text":7130},{},"\u002Fglossary\u002Fchange-management",[6069,6070,515,6072],[2697,6080,2698,6227],{"title":7152,"description":7153},"What is Change Management? Definition & Compliance Guide","Change management is the process of controlling modifications to systems and infrastructure to prevent unauthorized changes and maintain security and stability.","change-management","8.glossary\u002Fchange-management","xeecemxPeYwPVCVxeZ0eZXpmSOlKMkCLQoUsX4dbaQA",{"id":7158,"title":7159,"body":7160,"description":427,"extension":460,"lastUpdated":979,"meta":7426,"navigation":497,"path":7427,"relatedFrameworks":7428,"relatedTerms":7429,"seo":7432,"slug":2386,"stem":7435,"term":7165,"__hash__":7436},"glossary\u002F8.glossary\u002Fcontinuous-monitoring.md","Continuous Monitoring",{"type":29,"value":7161,"toc":7415},[7162,7166,7169,7173,7176,7196,7200,7203,7208,7222,7227,7241,7246,7257,7262,7276,7280,7303,7307,7362,7366,7369,7382,7385,7389,7406,7410],[32,7163,7165],{"id":7164},"what-is-continuous-monitoring","What is Continuous Monitoring?",[37,7167,7168],{},"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.",[560,7170,7172],{"id":7171},"why-does-continuous-monitoring-matter","Why does continuous monitoring matter?",[37,7174,7175],{},"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:",[164,7177,7178,7181,7184,7187,7190,7193],{},[167,7179,7180],{},"Detecting threats and vulnerabilities as they emerge, not months later",[167,7182,7183],{},"Verifying that controls remain effective on an ongoing basis",[167,7185,7186],{},"Identifying configuration drift and unauthorized changes",[167,7188,7189],{},"Providing evidence of sustained compliance for auditors",[167,7191,7192],{},"Enabling faster response to security incidents",[167,7194,7195],{},"Reducing the risk of surprises during audit cycles",[560,7197,7199],{"id":7198},"what-should-you-monitor-continuously","What should you monitor continuously?",[37,7201,7202],{},"Continuous monitoring spans multiple domains:",[37,7204,7205],{},[103,7206,7207],{},"Security controls:",[164,7209,7210,7213,7216,7219],{},[167,7211,7212],{},"Are access controls still properly configured?",[167,7214,7215],{},"Are encryption mechanisms active and using current standards?",[167,7217,7218],{},"Are security policies being followed?",[167,7220,7221],{},"Are patches being applied within defined timeframes?",[37,7223,7224],{},[103,7225,7226],{},"Systems and infrastructure:",[164,7228,7229,7232,7235,7238],{},[167,7230,7231],{},"Are systems operating normally?",[167,7233,7234],{},"Are there unauthorized configuration changes?",[167,7236,7237],{},"Are there new vulnerabilities affecting your environment?",[167,7239,7240],{},"Are all endpoints protected with current security agents?",[37,7242,7243],{},[103,7244,7245],{},"User activity:",[164,7247,7248,7251,7254],{},[167,7249,7250],{},"Are there unusual access patterns or privilege escalations?",[167,7252,7253],{},"Are terminated users' accounts being deactivated promptly?",[167,7255,7256],{},"Are there failed authentication attempts indicating brute-force attacks?",[37,7258,7259],{},[103,7260,7261],{},"Compliance status:",[164,7263,7264,7267,7270,7273],{},[167,7265,7266],{},"Are all required controls implemented and operating?",[167,7268,7269],{},"Is evidence being collected on schedule?",[167,7271,7272],{},"Are policy reviews and updates happening as planned?",[167,7274,7275],{},"Are vendor assessments current?",[560,7277,7279],{"id":7278},"how-do-compliance-frameworks-address-continuous-monitoring","How do compliance frameworks address continuous monitoring?",[164,7281,7282,7287,7292,7297],{},[167,7283,7284,7286],{},[103,7285,381],{}," — CC4.1 and CC4.2 require ongoing monitoring of the internal control system and evaluation of deficiencies",[167,7288,7289,7291],{},[103,7290,43],{}," — clause 9 (Performance evaluation) requires monitoring, measurement, analysis, and evaluation of the ISMS",[167,7293,7294,7296],{},[103,7295,5717],{}," — DE.CM (Continuous Monitoring) specifically addresses monitoring information systems and assets for cybersecurity events",[167,7298,7299,7302],{},[103,7300,7301],{},"NIST SP 800-137"," provides detailed guidance on Information Security Continuous Monitoring (ISCM)",[560,7304,7306],{"id":7305},"how-do-you-implement-continuous-monitoring","How do you implement continuous monitoring?",[1446,7308,7309,7315,7338,7344,7350,7356],{},[167,7310,7311,7314],{},[103,7312,7313],{},"Define monitoring objectives"," — determine what needs to be monitored based on risk assessment and compliance requirements",[167,7316,7317,7320,7321],{},[103,7318,7319],{},"Select monitoring tools"," — deploy appropriate technologies:\n",[164,7322,7323,7326,7329,7332,7335],{},[167,7324,7325],{},"SIEM (Security Information and Event Management) for log aggregation and correlation",[167,7327,7328],{},"EDR (Endpoint Detection and Response) for endpoint monitoring",[167,7330,7331],{},"Vulnerability scanners for continuous vulnerability assessment",[167,7333,7334],{},"Configuration management tools for drift detection",[167,7336,7337],{},"GRC platforms for compliance monitoring",[167,7339,7340,7343],{},[103,7341,7342],{},"Establish baselines"," — define normal operating parameters so deviations can be detected",[167,7345,7346,7349],{},[103,7347,7348],{},"Configure alerts"," — set meaningful alert thresholds to balance detection with alert fatigue",[167,7351,7352,7355],{},[103,7353,7354],{},"Define response procedures"," — establish processes for responding to monitoring alerts",[167,7357,7358,7361],{},[103,7359,7360],{},"Review and improve"," — regularly assess monitoring effectiveness and adjust as needed",[560,7363,7365],{"id":7364},"what-is-the-difference-between-continuous-monitoring-and-continuous-compliance","What is the difference between continuous monitoring and continuous compliance?",[37,7367,7368],{},"While related, these concepts differ:",[164,7370,7371,7377],{},[167,7372,7373,7376],{},[103,7374,7375],{},"Continuous monitoring"," focuses on security — detecting threats, vulnerabilities, and anomalies in real time",[167,7378,7379,7381],{},[103,7380,523],{}," focuses on maintaining compliance posture — ensuring controls remain effective and evidence stays current",[37,7383,7384],{},"An effective program addresses both. Security monitoring feeds compliance evidence, and compliance monitoring ensures security controls do not degrade.",[560,7386,7388],{"id":7387},"what-are-common-challenges-with-continuous-monitoring","What are common challenges with continuous monitoring?",[164,7390,7391,7394,7397,7400,7403],{},[167,7392,7393],{},"Alert fatigue from too many low-priority notifications",[167,7395,7396],{},"Gaps in monitoring coverage across all systems",[167,7398,7399],{},"Insufficient resources to investigate and respond to alerts",[167,7401,7402],{},"Monitoring tools that generate data but lack actionable insights",[167,7404,7405],{},"Difficulty correlating events across disparate systems",[560,7407,7409],{"id":7408},"how-does-episki-help-with-continuous-monitoring","How does episki help with continuous monitoring?",[37,7411,7412,7413,242],{},"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 ",[40,7414,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":7416},[7417],{"id":7164,"depth":428,"text":7165,"children":7418},[7419,7420,7421,7422,7423,7424,7425],{"id":7171,"depth":963,"text":7172},{"id":7198,"depth":963,"text":7199},{"id":7278,"depth":963,"text":7279},{"id":7305,"depth":963,"text":7306},{"id":7364,"depth":963,"text":7365},{"id":7387,"depth":963,"text":7388},{"id":7408,"depth":963,"text":7409},{},"\u002Fglossary\u002Fcontinuous-monitoring",[6069,6070,515,6073],[2698,2697,4226,7430,7431],"remediation","control-framework",{"title":7433,"description":7434},"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":7438,"title":7439,"body":7440,"description":427,"extension":460,"lastUpdated":979,"meta":7645,"navigation":497,"path":7646,"relatedFrameworks":7647,"relatedTerms":7648,"seo":7650,"slug":7431,"stem":7653,"term":7445,"__hash__":7654},"glossary\u002F8.glossary\u002Fcontrol-framework.md","Control Framework",{"type":29,"value":7441,"toc":7635},[7442,7446,7449,7453,7456,7488,7492,7495,7533,7537,7540,7572,7576,7579,7582,7586,7589,7626,7630],[32,7443,7445],{"id":7444},"what-is-a-control-framework","What is a Control Framework?",[37,7447,7448],{},"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.",[560,7450,7452],{"id":7451},"why-do-control-frameworks-matter","Why do control frameworks matter?",[37,7454,7455],{},"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:",[164,7457,7458,7464,7470,7476,7482],{},[167,7459,7460,7463],{},[103,7461,7462],{},"Comprehensiveness"," — a complete catalog of controls spanning all relevant security domains",[167,7465,7466,7469],{},[103,7467,7468],{},"Structure"," — logical organization of controls into categories and domains",[167,7471,7472,7475],{},[103,7473,7474],{},"Common language"," — standardized terminology for discussing security with auditors, customers, and partners",[167,7477,7478,7481],{},[103,7479,7480],{},"Benchmarking"," — a reference point for measuring maturity and identifying gaps",[167,7483,7484,7487],{},[103,7485,7486],{},"Compliance alignment"," — mapping to regulatory and contractual requirements",[560,7489,7491],{"id":7490},"what-are-common-control-frameworks","What are common control frameworks?",[37,7493,7494],{},"Several widely adopted control frameworks exist, each with a different focus:",[164,7496,7497,7503,7509,7515,7521,7527],{},[167,7498,7499,7502],{},[103,7500,7501],{},"SOC 2 Trust Services Criteria"," — evaluates controls across security, availability, processing integrity, confidentiality, and privacy for service organizations",[167,7504,7505,7508],{},[103,7506,7507],{},"ISO 27001 Annex A"," — provides 93 controls across organizational, people, physical, and technological themes for information security management",[167,7510,7511,7514],{},[103,7512,7513],{},"NIST Cybersecurity Framework (CSF)"," — organizes security activities into five functions: Identify, Protect, Detect, Respond, and Recover",[167,7516,7517,7520],{},[103,7518,7519],{},"NIST SP 800-53"," — a comprehensive catalog of security and privacy controls used primarily by US federal agencies and their contractors",[167,7522,7523,7526],{},[103,7524,7525],{},"CIS Controls"," — a prioritized set of actions (18 controls) that form a practical starting point for cybersecurity defense",[167,7528,7529,7532],{},[103,7530,7531],{},"COBIT"," — a framework for IT governance and management",[560,7534,7536],{"id":7535},"how-do-you-choose-a-control-framework","How do you choose a control framework?",[37,7538,7539],{},"The right framework depends on your organization's needs:",[164,7541,7542,7548,7554,7560,7566],{},[167,7543,7544,7547],{},[103,7545,7546],{},"Customer requirements"," — if customers require SOC 2 reports, the Trust Services Criteria will be your primary framework",[167,7549,7550,7553],{},[103,7551,7552],{},"Certification goals"," — if you need ISO 27001 certification, Annex A is the relevant control set",[167,7555,7556,7559],{},[103,7557,7558],{},"Industry"," — some industries have specific frameworks (HITRUST for healthcare, PCI DSS for payment cards)",[167,7561,7562,7565],{},[103,7563,7564],{},"Maturity level"," — organizations early in their security journey may start with CIS Controls, while more mature programs adopt NIST SP 800-53",[167,7567,7568,7571],{},[103,7569,7570],{},"Geography"," — ISO 27001 is globally recognized, while some frameworks are more region-specific",[560,7573,7575],{"id":7574},"how-do-you-map-controls-across-multiple-frameworks","How do you map controls across multiple frameworks?",[37,7577,7578],{},"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,7580,7581],{},"Effective multi-framework mapping reduces duplication and helps organizations manage compliance efficiently.",[560,7583,7585],{"id":7584},"how-do-you-implement-a-control-framework","How do you implement a control framework?",[37,7587,7588],{},"Implementation typically follows these phases:",[1446,7590,7591,7597,7603,7609,7614,7620],{},[167,7592,7593,7596],{},[103,7594,7595],{},"Gap assessment"," — compare current controls against the framework to identify gaps",[167,7598,7599,7602],{},[103,7600,7601],{},"Prioritization"," — rank gaps by risk impact and effort required",[167,7604,7605,7608],{},[103,7606,7607],{},"Control design"," — design controls to address identified gaps",[167,7610,7611,7613],{},[103,7612,7021],{}," — deploy controls through policies, processes, and technology",[167,7615,7616,7619],{},[103,7617,7618],{},"Evidence collection"," — establish processes to collect and maintain compliance evidence",[167,7621,7622,7625],{},[103,7623,7624],{},"Monitoring and review"," — continuously assess control effectiveness and address changes",[560,7627,7629],{"id":7628},"how-does-episki-help-with-control-frameworks","How does episki help with control frameworks?",[37,7631,7632,7633,242],{},"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 ",[40,7634,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":7636},[7637],{"id":7444,"depth":428,"text":7445,"children":7638},[7639,7640,7641,7642,7643,7644],{"id":7451,"depth":963,"text":7452},{"id":7490,"depth":963,"text":7491},{"id":7535,"depth":963,"text":7536},{"id":7574,"depth":963,"text":7575},{"id":7584,"depth":963,"text":7585},{"id":7628,"depth":963,"text":7629},{},"\u002Fglossary\u002Fcontrol-framework",[6070,515,6073],[6227,6697,3836,7649,6231],"trust-services-criteria",{"title":7651,"description":7652},"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":7656,"title":7657,"body":7658,"description":427,"extension":460,"lastUpdated":979,"meta":7855,"navigation":497,"path":7856,"relatedFrameworks":7857,"relatedTerms":7858,"seo":7859,"slug":6227,"stem":7862,"term":7663,"__hash__":7863},"glossary\u002F8.glossary\u002Fcontrol-objectives.md","Control Objectives",{"type":29,"value":7659,"toc":7844},[7660,7664,7667,7671,7674,7696,7700,7703,7717,7720,7724,7727,7759,7763,7766,7786,7790,7793,7825,7828,7832,7835,7839],[32,7661,7663],{"id":7662},"what-are-control-objectives","What are Control Objectives?",[37,7665,7666],{},"Control objectives are the specific goals or outcomes that a security control is designed to achieve. They define what a control should accomplish rather than how it should be implemented. Control objectives serve as the bridge between high-level security requirements and the specific controls an organization puts in place.",[560,7668,7670],{"id":7669},"what-role-do-control-objectives-play-in-compliance-frameworks","What role do control objectives play in compliance frameworks?",[37,7672,7673],{},"Control objectives appear across multiple compliance frameworks:",[164,7675,7676,7681,7686,7691],{},[167,7677,7678,7680],{},[103,7679,381],{}," — control objectives are aligned to Trust Services Criteria points. Each criterion defines an objective, and the organization implements controls to meet that objective.",[167,7682,7683,7685],{},[103,7684,43],{}," — Annex A contains control objectives organized into categories such as access control, cryptography, and operations security. Each objective has one or more associated controls.",[167,7687,7688,7690],{},[103,7689,5708],{}," — requirements are organized around objectives like protecting cardholder data, maintaining secure systems, and implementing access controls.",[167,7692,7693,7695],{},[103,7694,5717],{}," — functions (Identify, Protect, Detect, Respond, Recover) represent high-level objectives, with categories and subcategories providing more specific objectives.",[560,7697,7699],{"id":7698},"what-is-the-difference-between-control-objectives-and-controls","What is the difference between control objectives and controls?",[37,7701,7702],{},"It is important to distinguish between control objectives and the controls themselves:",[164,7704,7705,7711],{},[167,7706,4072,7707,7710],{},[103,7708,7709],{},"control objective"," states the desired outcome (e.g., \"ensure that access to systems is restricted to authorized users\")",[167,7712,4072,7713,7716],{},[103,7714,7715],{},"control"," is the specific mechanism that achieves the objective (e.g., \"multi-factor authentication is required for all user logins\")",[37,7718,7719],{},"Multiple controls may support a single objective, and a single control may contribute to multiple objectives. This many-to-many relationship is why control mapping is essential for compliance management.",[560,7721,7723],{"id":7722},"how-do-you-write-effective-control-objectives","How do you write effective control objectives?",[37,7725,7726],{},"Well-written control objectives share several characteristics:",[164,7728,7729,7735,7741,7747,7753],{},[167,7730,7731,7734],{},[103,7732,7733],{},"Specific"," — clearly state what should be achieved without ambiguity",[167,7736,7737,7740],{},[103,7738,7739],{},"Measurable"," — define success in terms that can be tested or verified",[167,7742,7743,7746],{},[103,7744,7745],{},"Aligned to risk"," — address identified risks and threats relevant to the organization",[167,7748,7749,7752],{},[103,7750,7751],{},"Framework-referenced"," — map to applicable regulatory or framework requirements",[167,7754,7755,7758],{},[103,7756,7757],{},"Outcome-focused"," — describe the desired state rather than prescribing implementation details",[560,7760,7762],{"id":7761},"what-are-examples-of-control-objectives","What are examples of control objectives?",[37,7764,7765],{},"Common control objectives include:",[164,7767,7768,7771,7774,7777,7780,7783],{},[167,7769,7770],{},"Access to production systems is restricted to authorized personnel based on job function",[167,7772,7773],{},"Changes to production systems follow an approved change management process",[167,7775,7776],{},"Security events are logged, monitored, and responded to in a timely manner",[167,7778,7779],{},"Sensitive data is encrypted in transit and at rest",[167,7781,7782],{},"Employees receive security awareness training upon hire and annually thereafter",[167,7784,7785],{},"Vendor security is assessed before engagement and periodically during the relationship",[560,7787,7789],{"id":7788},"how-do-you-map-controls-to-objectives","How do you map controls to objectives?",[37,7791,7792],{},"The process of mapping controls to objectives involves:",[1446,7794,7795,7801,7807,7813,7819],{},[167,7796,7797,7800],{},[103,7798,7799],{},"Identify applicable objectives"," — determine which control objectives are relevant based on your framework scope and risk assessment",[167,7802,7803,7806],{},[103,7804,7805],{},"Inventory existing controls"," — document current controls, processes, and tools",[167,7808,7809,7812],{},[103,7810,7811],{},"Map controls to objectives"," — link each control to the objectives it supports",[167,7814,7815,7818],{},[103,7816,7817],{},"Identify gaps"," — find objectives that lack sufficient supporting controls",[167,7820,7821,7824],{},[103,7822,7823],{},"Implement new controls"," — design and deploy controls to close identified gaps",[37,7826,7827],{},"This mapping exercise is fundamental to audit preparation and demonstrates to auditors that your control environment is comprehensive and well-organized.",[560,7829,7831],{"id":7830},"why-do-control-objectives-matter","Why do control objectives matter?",[37,7833,7834],{},"Control objectives provide structure and purpose to a compliance program. Without clear objectives, organizations risk implementing controls haphazardly — either missing critical areas or over-investing in low-risk areas. Well-defined objectives ensure that every control exists for a reason and contributes to the overall security posture.",[560,7836,7838],{"id":7837},"how-does-episki-help-with-control-objectives","How does episki help with control objectives?",[37,7840,7841,7842,242],{},"episki provides pre-defined control objectives mapped to SOC 2, ISO 27001, and other frameworks. The platform lets you link your controls to objectives, visualize coverage, and identify gaps. When auditors review your program, the objective-to-control mapping demonstrates a mature, structured approach. Learn more on our ",[40,7843,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":7845},[7846],{"id":7662,"depth":428,"text":7663,"children":7847},[7848,7849,7850,7851,7852,7853,7854],{"id":7669,"depth":963,"text":7670},{"id":7698,"depth":963,"text":7699},{"id":7722,"depth":963,"text":7723},{"id":7761,"depth":963,"text":7762},{"id":7788,"depth":963,"text":7789},{"id":7830,"depth":963,"text":7831},{"id":7837,"depth":963,"text":7838},{},"\u002Fglossary\u002Fcontrol-objectives",[6070,515],[7649,7431,6231,984],{"title":7860,"description":7861},"What are Control Objectives? Definition & Compliance Guide","Control objectives define the specific goals a security control is designed to achieve. Learn how they apply across SOC 2, ISO 27001, and other frameworks.","8.glossary\u002Fcontrol-objectives","SpnIlD6HDVFEkmxROjZuChf2JX-l2Yxt87Vg5QUxGAg",{"id":7865,"title":7866,"body":7867,"description":427,"extension":460,"lastUpdated":979,"meta":8081,"navigation":497,"path":8082,"relatedFrameworks":8083,"relatedTerms":8084,"seo":8087,"slug":8090,"stem":8091,"term":7872,"__hash__":8092},"glossary\u002F8.glossary\u002Fdata-classification.md","Data Classification",{"type":29,"value":7868,"toc":8071},[7869,7873,7876,7880,7883,7915,7919,7922,7952,7955,7959,7981,7985,8041,8045,8062,8066],[32,7870,7872],{"id":7871},"what-is-data-classification","What is Data Classification?",[37,7874,7875],{},"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.",[560,7877,7879],{"id":7878},"why-does-data-classification-matter","Why does data classification matter?",[37,7881,7882],{},"Data classification is foundational to an effective security program for several reasons:",[164,7884,7885,7891,7897,7903,7909],{},[167,7886,7887,7890],{},[103,7888,7889],{},"Proportional protection"," — sensitive data receives stronger controls while less sensitive data does not burden operations with unnecessary restrictions",[167,7892,7893,7896],{},[103,7894,7895],{},"Regulatory compliance"," — many regulations require specific handling of certain data types (PHI under HIPAA, PAN under PCI DSS, personal data under GDPR)",[167,7898,7899,7902],{},[103,7900,7901],{},"Access control"," — classification determines who should have access to what data",[167,7904,7905,7908],{},[103,7906,7907],{},"Incident response"," — knowing the classification of compromised data helps determine the severity of an incident and notification requirements",[167,7910,7911,7914],{},[103,7912,7913],{},"Data lifecycle management"," — classification informs retention, archival, and destruction decisions",[560,7916,7918],{"id":7917},"what-are-the-common-data-classification-levels","What are the common data classification levels?",[37,7920,7921],{},"Most organizations use three to five classification levels:",[164,7923,7924,7930,7936,7942],{},[167,7925,7926,7929],{},[103,7927,7928],{},"Public"," — information intended for public consumption with no restrictions (marketing materials, public website content)",[167,7931,7932,7935],{},[103,7933,7934],{},"Internal"," — information for internal use that is not sensitive but should not be shared externally without authorization (internal memos, non-sensitive policies)",[167,7937,7938,7941],{},[103,7939,7940],{},"Confidential"," — sensitive business information that could cause harm if disclosed (financial data, strategic plans, customer lists)",[167,7943,7944,7947,7948,7951],{},[103,7945,7946],{},"Restricted"," or ",[103,7949,7950],{},"Highly Confidential"," — the most sensitive data requiring the strongest protections (PHI, PAN, trade secrets, credentials, encryption keys)",[37,7953,7954],{},"Some organizations add additional levels or use different labels, but the principle remains: categorize data by the impact of unauthorized disclosure.",[560,7956,7958],{"id":7957},"how-do-compliance-frameworks-address-classification","How do compliance frameworks address classification?",[164,7960,7961,7966,7971,7976],{},[167,7962,7963,7965],{},[103,7964,43],{}," — 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.",[167,7967,7968,7970],{},[103,7969,5717],{}," — the Identify function (ID.AM-5) addresses classification of resources based on criticality and business value",[167,7972,7973,7975],{},[103,7974,5694],{}," — while HIPAA does not prescribe a classification scheme, PHI is inherently a \"restricted\" classification that requires specific safeguards",[167,7977,7978,7980],{},[103,7979,5708],{}," — cardholder data (particularly PAN) must be identified and protected with specific controls",[560,7982,7984],{"id":7983},"how-do-you-implement-data-classification","How do you implement data classification?",[1446,7986,7987,7993,7999,8005,8011,8017,8023,8029,8035],{},[167,7988,7989,7992],{},[103,7990,7991],{},"Define classification levels"," — establish clear, understandable categories with examples",[167,7994,7995,7998],{},[103,7996,7997],{},"Create a classification policy"," — document the scheme, responsibilities, and handling requirements for each level",[167,8000,8001,8004],{},[103,8002,8003],{},"Inventory data"," — identify what data the organization holds and where it resides",[167,8006,8007,8010],{},[103,8008,8009],{},"Classify data"," — assign classification levels to data based on sensitivity criteria",[167,8012,8013,8016],{},[103,8014,8015],{},"Label data"," — apply labels (metadata, headers, visual markings) to classified data",[167,8018,8019,8022],{},[103,8020,8021],{},"Define handling rules"," — specify how each classification level should be stored, transmitted, shared, and destroyed",[167,8024,8025,8028],{},[103,8026,8027],{},"Train employees"," — ensure all staff understand the classification scheme and their responsibilities",[167,8030,8031,8034],{},[103,8032,8033],{},"Enforce through controls"," — implement technical controls (DLP, access controls, encryption) aligned with classification levels",[167,8036,8037,8040],{},[103,8038,8039],{},"Review periodically"," — reassess classifications as data, regulations, and business needs change",[560,8042,8044],{"id":8043},"what-are-common-challenges-with-data-classification","What are common challenges with data classification?",[164,8046,8047,8050,8053,8056,8059],{},[167,8048,8049],{},"Data is distributed across many systems and formats, making classification difficult",[167,8051,8052],{},"Employees may not consistently apply classification labels",[167,8054,8055],{},"Automated classification tools have limitations, especially with unstructured data",[167,8057,8058],{},"Over-classification can reduce productivity while under-classification creates risk",[167,8060,8061],{},"Classification needs to be maintained as data evolves",[560,8063,8065],{"id":8064},"how-does-episki-help-with-data-classification","How does episki help with data classification?",[37,8067,8068,8069,242],{},"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 ",[40,8070,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8072},[8073],{"id":7871,"depth":428,"text":7872,"children":8074},[8075,8076,8077,8078,8079,8080],{"id":7878,"depth":963,"text":7879},{"id":7917,"depth":963,"text":7918},{"id":7957,"depth":963,"text":7958},{"id":7983,"depth":963,"text":7984},{"id":8043,"depth":963,"text":8044},{"id":8064,"depth":963,"text":8065},{},"\u002Fglossary\u002Fdata-classification",[6069,515,6073],[6018,6080,8085,8086,6697],"phi","pan",{"title":8088,"description":8089},"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.","data-classification","8.glossary\u002Fdata-classification","i7_WFqWjV-QN-2udK8JC1fF_Blw81yHdx6_cQyOh7lA",{"id":8094,"title":8095,"body":8096,"description":427,"extension":460,"lastUpdated":979,"meta":8344,"navigation":497,"path":8345,"relatedFrameworks":8346,"relatedTerms":8347,"seo":8348,"slug":6696,"stem":8351,"term":8101,"__hash__":8352},"glossary\u002F8.glossary\u002Fdisaster-recovery.md","Disaster Recovery",{"type":29,"value":8097,"toc":8333},[8098,8102,8105,8109,8115,8121,8127,8131,8134,8160,8163,8167,8170,8218,8222,8225,8263,8267,8289,8293,8296,8321,8324,8328],[32,8099,8101],{"id":8100},"what-is-disaster-recovery","What is Disaster Recovery?",[37,8103,8104],{},"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.",[560,8106,8108],{"id":8107},"what-are-the-key-disaster-recovery-concepts","What are the key disaster recovery concepts?",[37,8110,8111,8114],{},[103,8112,8113],{},"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,8116,8117,8120],{},[103,8118,8119],{},"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,8122,8123,8126],{},[103,8124,8125],{},"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.",[560,8128,8130],{"id":8129},"what-are-common-disaster-recovery-strategies","What are common disaster recovery strategies?",[37,8132,8133],{},"DR strategies vary in cost, complexity, and recovery speed:",[164,8135,8136,8142,8148,8154],{},[167,8137,8138,8141],{},[103,8139,8140],{},"Backup and restore"," — the simplest approach: maintain regular backups and restore them to new or repaired infrastructure when needed. Lowest cost but highest RTO.",[167,8143,8144,8147],{},[103,8145,8146],{},"Pilot light"," — maintain a minimal version of the production environment in a secondary location that can be scaled up quickly during a disaster.",[167,8149,8150,8153],{},[103,8151,8152],{},"Warm standby"," — run a scaled-down but fully functional copy of the production environment that can be scaled to full capacity during failover.",[167,8155,8156,8159],{},[103,8157,8158],{},"Hot standby \u002F active-active"," — run full production environments in multiple locations simultaneously. Provides near-zero RTO but at the highest cost.",[37,8161,8162],{},"The right strategy depends on the business's RTO and RPO requirements and budget.",[560,8164,8166],{"id":8165},"what-are-the-components-of-a-disaster-recovery-plan","What are the components of a disaster recovery plan?",[37,8168,8169],{},"A comprehensive DR plan includes:",[164,8171,8172,8177,8183,8188,8194,8200,8206,8212],{},[167,8173,8174,8176],{},[103,8175,5214],{}," — which systems and applications are covered",[167,8178,8179,8182],{},[103,8180,8181],{},"RTO and RPO targets"," — recovery objectives for each system",[167,8184,8185,8187],{},[103,8186,6576],{}," — who is responsible for each aspect of recovery",[167,8189,8190,8193],{},[103,8191,8192],{},"Recovery procedures"," — step-by-step instructions for restoring each system",[167,8195,8196,8199],{},[103,8197,8198],{},"Communication plan"," — how to notify stakeholders during a disaster",[167,8201,8202,8205],{},[103,8203,8204],{},"Vendor contacts"," — contact information for infrastructure and service providers",[167,8207,8208,8211],{},[103,8209,8210],{},"Dependencies"," — system interdependencies that affect recovery sequence",[167,8213,8214,8217],{},[103,8215,8216],{},"Testing schedule"," — how and when the plan will be tested",[560,8219,8221],{"id":8220},"how-do-you-manage-backups-for-disaster-recovery","How do you manage backups for disaster recovery?",[37,8223,8224],{},"Backups are the foundation of disaster recovery. Best practices include:",[164,8226,8227,8233,8239,8245,8251,8257],{},[167,8228,8229,8232],{},[103,8230,8231],{},"3-2-1 rule"," — maintain 3 copies of data, on 2 different types of media, with 1 copy offsite",[167,8234,8235,8238],{},[103,8236,8237],{},"Automated backups"," — schedule backups to run automatically at intervals aligned with RPO",[167,8240,8241,8244],{},[103,8242,8243],{},"Encryption"," — encrypt backups to protect data at rest",[167,8246,8247,8250],{},[103,8248,8249],{},"Regular testing"," — periodically restore from backups to verify they work",[167,8252,8253,8256],{},[103,8254,8255],{},"Monitoring"," — monitor backup jobs for failures and address issues immediately",[167,8258,8259,8262],{},[103,8260,8261],{},"Immutable backups"," — protect backups from ransomware by using immutable storage",[560,8264,8266],{"id":8265},"how-do-compliance-frameworks-address-disaster-recovery","How do compliance frameworks address disaster recovery?",[164,8268,8269,8274,8279,8284],{},[167,8270,8271,8273],{},[103,8272,43],{}," — control A.5.30 addresses ICT readiness for business continuity, including DR planning and testing",[167,8275,8276,8278],{},[103,8277,5717],{}," — RC.RP (Recovery Planning) addresses establishing and testing recovery processes",[167,8280,8281,8283],{},[103,8282,381],{}," — the Availability criterion covers system recovery capabilities",[167,8285,8286,8288],{},[103,8287,5708],{}," — while not explicitly requiring a DR plan, requirements around data protection and system availability support DR practices",[560,8290,8292],{"id":8291},"how-do-you-test-a-disaster-recovery-plan","How do you test a disaster recovery plan?",[37,8294,8295],{},"DR testing is essential and should include:",[164,8297,8298,8304,8310,8316],{},[167,8299,8300,8303],{},[103,8301,8302],{},"Backup restoration tests"," — regularly restore data from backups to verify integrity",[167,8305,8306,8309],{},[103,8307,8308],{},"Failover tests"," — practice switching to secondary systems",[167,8311,8312,8315],{},[103,8313,8314],{},"Full DR tests"," — simulate a complete disaster and execute the full recovery plan",[167,8317,8318,8320],{},[103,8319,6629],{}," — walk through DR scenarios with the team",[37,8322,8323],{},"Testing should occur at least annually, with backup restoration tests performed more frequently.",[560,8325,8327],{"id":8326},"how-does-episki-help-with-disaster-recovery","How does episki help with disaster recovery?",[37,8329,8330,8331,242],{},"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 ",[40,8332,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8334},[8335],{"id":8100,"depth":428,"text":8101,"children":8336},[8337,8338,8339,8340,8341,8342,8343],{"id":8107,"depth":963,"text":8108},{"id":8129,"depth":963,"text":8130},{"id":8165,"depth":963,"text":8166},{"id":8220,"depth":963,"text":8221},{"id":8265,"depth":963,"text":8266},{"id":8291,"depth":963,"text":8292},{"id":8326,"depth":963,"text":8327},{},"\u002Fglossary\u002Fdisaster-recovery",[6069,515,6073],[6702,4226,6697,6018],{"title":8349,"description":8350},"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":8354,"title":8243,"body":8355,"description":427,"extension":460,"lastUpdated":979,"meta":8542,"navigation":497,"path":6017,"relatedFrameworks":8543,"relatedTerms":8544,"seo":8546,"slug":6018,"stem":8549,"term":8360,"__hash__":8550},"glossary\u002F8.glossary\u002Fencryption.md",{"type":29,"value":8356,"toc":8531},[8357,8361,8364,8368,8374,8380,8386,8390,8393,8396,8410,8414,8417,8419,8436,8440,8443,8475,8479,8501,8505,8522,8526],[32,8358,8360],{"id":8359},"what-is-encryption","What is Encryption?",[37,8362,8363],{},"Encryption is the process of converting readable data (plaintext) into an unreadable format (ciphertext) using a cryptographic algorithm and a key. Only authorized parties with the correct decryption key can convert the ciphertext back to plaintext. Encryption is one of the most important technical controls for protecting the confidentiality of sensitive data and is required by virtually every compliance framework.",[560,8365,8367],{"id":8366},"what-are-the-types-of-encryption","What are the types of encryption?",[37,8369,8370,8373],{},[103,8371,8372],{},"Symmetric encryption"," — uses the same key for both encryption and decryption. It is fast and efficient for large volumes of data. Common algorithms include AES-256 (the current standard) and AES-128.",[37,8375,8376,8379],{},[103,8377,8378],{},"Asymmetric encryption"," — uses a pair of keys: a public key for encryption and a private key for decryption. It is used for key exchange, digital signatures, and scenarios where parties cannot share a secret key in advance. Common algorithms include RSA and elliptic curve cryptography (ECC).",[37,8381,8382,8385],{},[103,8383,8384],{},"Hashing"," — technically not encryption (it is one-way and cannot be reversed), but often discussed alongside encryption. Hashing produces a fixed-length output from any input, used for password storage and data integrity verification. Common algorithms include SHA-256 and bcrypt.",[560,8387,8389],{"id":8388},"what-is-encryption-at-rest","What is encryption at rest?",[37,8391,8392],{},"Encryption at rest protects data stored in databases, file systems, backups, and storage media. If a storage device is stolen or improperly decommissioned, encryption prevents unauthorized access to the data.",[37,8394,8395],{},"Common implementations include:",[164,8397,8398,8401,8404,8407],{},[167,8399,8400],{},"Full disk encryption (BitLocker, FileVault, LUKS)",[167,8402,8403],{},"Database encryption (Transparent Data Encryption)",[167,8405,8406],{},"File-level encryption",[167,8408,8409],{},"Cloud storage encryption (most cloud providers offer encryption at rest by default)",[560,8411,8413],{"id":8412},"what-is-encryption-in-transit","What is encryption in transit?",[37,8415,8416],{},"Encryption in transit protects data as it moves between systems over networks. It prevents eavesdropping, man-in-the-middle attacks, and data interception.",[37,8418,8395],{},[164,8420,8421,8424,8427,8430,8433],{},[167,8422,8423],{},"TLS 1.2 or 1.3 for web traffic (HTTPS)",[167,8425,8426],{},"TLS for email (SMTP with STARTTLS)",[167,8428,8429],{},"VPN tunnels for site-to-site or remote access connections",[167,8431,8432],{},"SSH for administrative access",[167,8434,8435],{},"IPsec for network-level encryption",[560,8437,8439],{"id":8438},"how-does-key-management-support-encryption","How does key management support encryption?",[37,8441,8442],{},"Encryption is only as strong as its key management. Poor key management undermines the protection encryption provides. Key management best practices include:",[164,8444,8445,8451,8457,8463,8469],{},[167,8446,8447,8450],{},[103,8448,8449],{},"Key generation"," — use cryptographically secure random number generators",[167,8452,8453,8456],{},[103,8454,8455],{},"Key storage"," — store keys separately from the data they protect, using hardware security modules (HSMs) or key management services",[167,8458,8459,8462],{},[103,8460,8461],{},"Key rotation"," — rotate keys periodically to limit exposure if a key is compromised",[167,8464,8465,8468],{},[103,8466,8467],{},"Key access control"," — restrict key access to authorized personnel and systems",[167,8470,8471,8474],{},[103,8472,8473],{},"Key destruction"," — securely destroy keys when no longer needed",[560,8476,8478],{"id":8477},"what-are-the-encryption-requirements","What are the encryption requirements?",[164,8480,8481,8486,8491,8496],{},[167,8482,8483,8485],{},[103,8484,381],{}," — CC6.1 and CC6.7 address protection of data through encryption and other mechanisms",[167,8487,8488,8490],{},[103,8489,43],{}," — control A.8.24 addresses use of cryptography",[167,8492,8493,8495],{},[103,8494,5694],{}," — encryption is an addressable implementation specification for ePHI at rest (45 CFR 164.312(a)(2)(iv)) and a requirement for ePHI in transit (45 CFR 164.312(e)(1))",[167,8497,8498,8500],{},[103,8499,5708],{}," — Requirement 3 requires encryption of stored PAN, and Requirement 4 requires encryption of PAN in transit over open networks",[560,8502,8504],{"id":8503},"what-are-common-mistakes-with-encryption","What are common mistakes with encryption?",[164,8506,8507,8510,8513,8516,8519],{},[167,8508,8509],{},"Using outdated algorithms (DES, 3DES, RC4, SSL, TLS 1.0\u002F1.1)",[167,8511,8512],{},"Storing encryption keys alongside encrypted data",[167,8514,8515],{},"Failing to encrypt backups",[167,8517,8518],{},"Not encrypting data in transit within internal networks",[167,8520,8521],{},"Hardcoding keys in application source code",[560,8523,8525],{"id":8524},"how-does-episki-help-with-encryption","How does episki help with encryption?",[37,8527,8528,8529,242],{},"episki tracks your encryption implementations across systems, monitors certificate expirations, and documents encryption policies and key management practices for audit evidence. Learn more on our ",[40,8530,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8532},[8533],{"id":8359,"depth":428,"text":8360,"children":8534},[8535,8536,8537,8538,8539,8540,8541],{"id":8366,"depth":963,"text":8367},{"id":8388,"depth":963,"text":8389},{"id":8412,"depth":963,"text":8413},{"id":8438,"depth":963,"text":8439},{"id":8477,"depth":963,"text":8478},{"id":8503,"depth":963,"text":8504},{"id":8524,"depth":963,"text":8525},{},[6069,6070,515,6071,6072],[8086,8085,8545,6080,8090],"tokenization",{"title":8547,"description":8548},"What is Encryption? Definition & Compliance Guide","Encryption transforms data into unreadable ciphertext to protect confidentiality. Learn about encryption at rest, in transit, and compliance requirements.","8.glossary\u002Fencryption","8HTAhzLPBjGJKnlguz6mBT1ob6J8h2KVZGzAJtWJEHM",{"id":8552,"title":8553,"body":8554,"description":427,"extension":460,"lastUpdated":979,"meta":8754,"navigation":497,"path":8755,"relatedFrameworks":8756,"relatedTerms":8757,"seo":8759,"slug":2698,"stem":8762,"term":8559,"__hash__":8763},"glossary\u002F8.glossary\u002Fevidence-collection.md","Evidence Collection",{"type":29,"value":8555,"toc":8744},[8556,8560,8563,8567,8570,8584,8588,8591,8641,8645,8648,8654,8660,8666,8670,8714,8718,8735,8739],[32,8557,8559],{"id":8558},"what-is-evidence-collection","What is Evidence Collection?",[37,8561,8562],{},"Evidence collection is the systematic process of gathering, organizing, and maintaining documentation that demonstrates security controls are implemented and operating effectively. It is a critical activity for any compliance program — without evidence, an organization cannot prove to auditors, customers, or regulators that its controls actually work.",[560,8564,8566],{"id":8565},"why-does-evidence-collection-matter","Why does evidence collection matter?",[37,8568,8569],{},"Controls that exist only in policy documents are insufficient. Auditors and assessors require proof that controls are executed consistently. Evidence collection bridges the gap between \"we have a policy\" and \"we follow the policy.\" Without organized evidence:",[164,8571,8572,8575,8578,8581],{},[167,8573,8574],{},"Audits take longer and cost more due to scrambling for documentation",[167,8576,8577],{},"Control gaps go undetected until audit time",[167,8579,8580],{},"Audit opinions may be qualified due to insufficient evidence",[167,8582,8583],{},"Customer trust erodes when security claims cannot be substantiated",[560,8585,8587],{"id":8586},"what-are-the-types-of-evidence-in-compliance-audits","What are the types of evidence in compliance audits?",[37,8589,8590],{},"Evidence takes many forms depending on the control being demonstrated:",[164,8592,8593,8599,8605,8611,8617,8623,8629,8635],{},[167,8594,8595,8598],{},[103,8596,8597],{},"Screenshots"," — system configurations, access control settings, dashboard views",[167,8600,8601,8604],{},[103,8602,8603],{},"Logs"," — audit logs, access logs, change management logs, security event logs",[167,8606,8607,8610],{},[103,8608,8609],{},"Documents"," — policies, procedures, meeting minutes, training records",[167,8612,8613,8616],{},[103,8614,8615],{},"Tickets"," — change management tickets, incident response tickets, access request tickets",[167,8618,8619,8622],{},[103,8620,8621],{},"Reports"," — vulnerability scan reports, penetration test reports, risk assessment reports",[167,8624,8625,8628],{},[103,8626,8627],{},"Certifications"," — employee training certificates, vendor SOC 2 reports, compliance attestations",[167,8630,8631,8634],{},[103,8632,8633],{},"Configurations"," — infrastructure-as-code files, system configuration exports",[167,8636,8637,8640],{},[103,8638,8639],{},"Interviews"," — auditor interviews with control owners (for live audits)",[560,8642,8644],{"id":8643},"what-are-common-evidence-collection-approaches","What are common evidence collection approaches?",[37,8646,8647],{},"Organizations typically use one of three approaches:",[37,8649,8650,8653],{},[103,8651,8652],{},"Manual collection"," — control owners manually gather screenshots, exports, and documents on a scheduled basis. This is the most common starting point but is labor-intensive and error-prone.",[37,8655,8656,8659],{},[103,8657,8658],{},"Semi-automated collection"," — integrations with key systems (cloud providers, identity providers, ticketing systems) automatically pull evidence, supplemented by manual collection for controls without integration support.",[37,8661,8662,8665],{},[103,8663,8664],{},"Continuous automated collection"," — deep integrations with infrastructure and applications automatically collect and organize evidence on an ongoing basis, with minimal manual intervention.",[560,8667,8669],{"id":8668},"what-are-best-practices-for-evidence-collection","What are best practices for evidence collection?",[164,8671,8672,8678,8684,8690,8696,8702,8708],{},[167,8673,8674,8677],{},[103,8675,8676],{},"Define evidence requirements upfront"," — for each control, specify what evidence is needed, how often it should be collected, and who is responsible",[167,8679,8680,8683],{},[103,8681,8682],{},"Collect continuously, not just before audits"," — evidence collected throughout the period is more credible than evidence gathered in a rush before the audit",[167,8685,8686,8689],{},[103,8687,8688],{},"Timestamp everything"," — evidence must demonstrate when the control was operating, not just that it exists",[167,8691,8692,8695],{},[103,8693,8694],{},"Organize by control"," — structure evidence so it maps directly to controls and framework requirements",[167,8697,8698,8701],{},[103,8699,8700],{},"Maintain chain of custody"," — ensure evidence cannot be tampered with after collection",[167,8703,8704,8707],{},[103,8705,8706],{},"Review evidence quality"," — periodically verify that collected evidence actually demonstrates the control is working",[167,8709,8710,8713],{},[103,8711,8712],{},"Retain evidence appropriately"," — keep evidence for the required retention period (typically matching the audit cycle plus any regulatory requirements)",[560,8715,8717],{"id":8716},"what-are-common-challenges-with-evidence-collection","What are common challenges with evidence collection?",[164,8719,8720,8723,8726,8729,8732],{},[167,8721,8722],{},"Evidence collection is distributed across many teams and systems",[167,8724,8725],{},"Control owners forget to collect on schedule",[167,8727,8728],{},"Evidence quality varies — screenshots may be unclear or incomplete",[167,8730,8731],{},"Evidence becomes stale if not collected at the right frequency",[167,8733,8734],{},"Storing and organizing large volumes of evidence is difficult without proper tooling",[560,8736,8738],{"id":8737},"how-does-episki-help-with-evidence-collection","How does episki help with evidence collection?",[37,8740,8741,8742,242],{},"episki automates evidence collection through integrations with cloud providers, identity systems, and development tools. The platform assigns collection tasks to control owners, sends reminders, validates evidence quality, and organizes everything by control and framework. When audit time arrives, evidence is already collected and organized. Learn more on our ",[40,8743,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8745},[8746],{"id":8558,"depth":428,"text":8559,"children":8747},[8748,8749,8750,8751,8752,8753],{"id":8565,"depth":963,"text":8566},{"id":8586,"depth":963,"text":8587},{"id":8643,"depth":963,"text":8644},{"id":8668,"depth":963,"text":8669},{"id":8716,"depth":963,"text":8717},{"id":8737,"depth":963,"text":8738},{},"\u002Fglossary\u002Fevidence-collection",[6070,515,6071,6072],[2697,8758,2386,6227],"soc2-type-2",{"title":8760,"description":8761},"What is Evidence Collection? Definition & Compliance Guide","Evidence collection is the process of gathering documentation that proves security controls are implemented and operating effectively for compliance audits.","8.glossary\u002Fevidence-collection","-4Die8_TxT3p7plrS5QfBm3mjx6_FZQa79Sl58zqSnw",{"id":8765,"title":8766,"body":8767,"description":427,"extension":460,"lastUpdated":979,"meta":8883,"navigation":497,"path":8884,"relatedFrameworks":8885,"relatedTerms":8886,"seo":8889,"slug":8892,"stem":8893,"term":8772,"__hash__":8894},"glossary\u002F8.glossary\u002Ffirewall.md","Firewall",{"type":29,"value":8768,"toc":8875},[8769,8773,8776,8780,8812,8816,8819,8841,8845,8866,8870],[32,8770,8772],{"id":8771},"what-is-a-firewall","What is a Firewall?",[37,8774,8775],{},"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.",[560,8777,8779],{"id":8778},"what-are-the-types-of-firewalls","What are the types of firewalls?",[164,8781,8782,8788,8794,8800,8806],{},[167,8783,8784,8787],{},[103,8785,8786],{},"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.",[167,8789,8790,8793],{},[103,8791,8792],{},"Stateful inspection firewalls"," — track the state of active connections and make decisions based on the context of traffic, not just individual packets.",[167,8795,8796,8799],{},[103,8797,8798],{},"Next-generation firewalls (NGFW)"," — combine traditional firewall capabilities with intrusion prevention, application awareness, and deep packet inspection.",[167,8801,8802,8805],{},[103,8803,8804],{},"Web application firewalls (WAF)"," — specifically protect web applications by filtering and monitoring HTTP traffic between the application and the internet.",[167,8807,8808,8811],{},[103,8809,8810],{},"Cloud firewalls"," — delivered as a service to protect cloud-based infrastructure and applications.",[560,8813,8815],{"id":8814},"how-do-compliance-frameworks-address-firewalls","How do compliance frameworks address firewalls?",[37,8817,8818],{},"Firewalls are a foundational control across compliance standards:",[164,8820,8821,8826,8831,8836],{},[167,8822,8823,8825],{},[103,8824,5708],{}," — Requirement 1 mandates installing and maintaining firewall configurations to protect cardholder data.",[167,8827,8828,8830],{},[103,8829,43],{}," — Network security controls (A.8.20, A.8.21) require network segmentation and filtering.",[167,8832,8833,8835],{},[103,8834,5717],{}," — PR.AC and PR.PT cover network protection and access enforcement.",[167,8837,8838,8840],{},[103,8839,381],{}," — CC6.6 requires restricting access through network security controls.",[560,8842,8844],{"id":8843},"what-are-best-practices-for-firewalls","What are best practices for firewalls?",[164,8846,8847,8850,8853,8856,8859],{},[167,8848,8849],{},"Define explicit allow and deny rules rather than relying on default configurations",[167,8851,8852],{},"Segment networks to limit lateral movement in the event of a breach",[167,8854,8855],{},"Review and update firewall rules regularly to remove stale or overly permissive entries",[167,8857,8858],{},"Log all firewall activity and monitor logs for anomalies",[167,8860,8861,8862],{},"Test firewall configurations as part of regular ",[40,8863,8865],{"href":8864},"\u002Fglossary\u002Fpenetration-testing","penetration testing",[560,8867,8869],{"id":8868},"how-does-episki-help-with-firewalls","How does episki help with firewalls?",[37,8871,8872,8873,242],{},"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 ",[40,8874,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8876},[8877],{"id":8771,"depth":428,"text":8772,"children":8878},[8879,8880,8881,8882],{"id":8778,"depth":963,"text":8779},{"id":8814,"depth":963,"text":8815},{"id":8843,"depth":963,"text":8844},{"id":8868,"depth":963,"text":8869},{},"\u002Fglossary\u002Ffirewall",[6069,6072,515,6073],[6080,8887,8888],"network-security","penetration-testing",{"title":8890,"description":8891},"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":8896,"title":8897,"body":8898,"description":427,"extension":460,"lastUpdated":979,"meta":9002,"navigation":497,"path":9003,"relatedFrameworks":9004,"relatedTerms":9005,"seo":9006,"slug":9009,"stem":9010,"term":8903,"__hash__":9011},"glossary\u002F8.glossary\u002Fframework.md","Framework",{"type":29,"value":8899,"toc":8994},[8900,8904,8907,8911,8938,8942,8945,8964,8968,8971,8985,8989],[32,8901,8903],{"id":8902},"what-is-a-framework","What is a Framework?",[37,8905,8906],{},"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.",[560,8908,8910],{"id":8909},"what-are-common-compliance-frameworks","What are common compliance frameworks?",[164,8912,8913,8918,8923,8928,8933],{},[167,8914,8915,8917],{},[103,8916,43],{}," — an international standard for information security management systems (ISMS) with a risk-based approach to protecting information assets.",[167,8919,8920,8922],{},[103,8921,381],{}," — a reporting framework developed by the AICPA based on five Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy.",[167,8924,8925,8927],{},[103,8926,5694],{}," — a US law that sets requirements for protecting health information, including the Security Rule and Privacy Rule.",[167,8929,8930,8932],{},[103,8931,5708],{}," — a set of security standards for organizations that handle payment card data.",[167,8934,8935,8937],{},[103,8936,5717],{}," — a voluntary framework published by the National Institute of Standards and Technology that provides a common taxonomy for managing cybersecurity risk.",[560,8939,8941],{"id":8940},"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,8943,8944],{},"These terms are often used interchangeably but have important distinctions:",[164,8946,8947,8952,8958],{},[167,8948,8949,8951],{},[103,8950,8897],{}," — a flexible structure of guidelines that can be adapted to an organization's context (e.g., NIST CSF).",[167,8953,8954,8957],{},[103,8955,8956],{},"Standard"," — a more prescriptive set of requirements that can be certified against (e.g., ISO 27001).",[167,8959,8960,8963],{},[103,8961,8962],{},"Regulation"," — a legally binding requirement enforced by a governing body (e.g., HIPAA, GDPR).",[560,8965,8967],{"id":8966},"how-do-you-choose-a-framework","How do you choose a framework?",[37,8969,8970],{},"When selecting a framework, consider:",[164,8972,8973,8976,8979,8982],{},[167,8974,8975],{},"Customer and market requirements — enterprise buyers often require SOC 2 or ISO 27001",[167,8977,8978],{},"Industry regulations — healthcare organizations must comply with HIPAA; payment processors with PCI DSS",[167,8980,8981],{},"Geographic scope — GDPR for organizations handling EU data",[167,8983,8984],{},"Organizational maturity — NIST CSF is often a good starting point for organizations new to formal security programs",[560,8986,8988],{"id":8987},"how-does-episki-help-with-compliance-frameworks","How does episki help with compliance frameworks?",[37,8990,8991,8992,242],{},"episki supports multiple frameworks in a single workspace, allowing organizations to map controls across standards and reuse evidence. Learn more on our ",[40,8993,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":8995},[8996],{"id":8902,"depth":428,"text":8903,"children":8997},[8998,8999,9000,9001],{"id":8909,"depth":963,"text":8910},{"id":8940,"depth":963,"text":8941},{"id":8966,"depth":963,"text":8967},{"id":8987,"depth":963,"text":8988},{},"\u002Fglossary\u002Fframework",[6070,515,6071,6072,6073],[7431,6227,3836],{"title":9007,"description":9008},"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":9013,"title":9014,"body":9015,"description":427,"extension":460,"lastUpdated":979,"meta":9124,"navigation":497,"path":9125,"relatedFrameworks":9126,"relatedTerms":9127,"seo":9128,"slug":3836,"stem":9131,"term":9020,"__hash__":9132},"glossary\u002F8.glossary\u002Fgrc.md","Grc",{"type":29,"value":9016,"toc":9115},[9017,9021,9028,9032,9035,9049,9053,9056,9070,9074,9087,9091,9094,9108,9112],[32,9018,9020],{"id":9019},"what-is-grc","What is GRC?",[37,9022,9023,9024,9027],{},"GRC stands for ",[103,9025,9026],{},"governance, risk, and compliance"," — a coordinated approach to aligning IT and security practices with business objectives, managing risk, and meeting regulatory requirements.",[560,9029,9031],{"id":9030},"what-is-governance-in-grc","What is governance in GRC?",[37,9033,9034],{},"Governance defines the policies, roles, and decision-making structures that guide how an organization operates. In a security context, governance includes:",[164,9036,9037,9040,9043,9046],{},[167,9038,9039],{},"Establishing security policies and standards",[167,9041,9042],{},"Assigning ownership for controls and programs",[167,9044,9045],{},"Setting risk appetite and tolerance levels",[167,9047,9048],{},"Board-level oversight of security posture",[560,9050,9052],{"id":9051},"what-is-risk-management-in-grc","What is risk management in GRC?",[37,9054,9055],{},"Risk management is the process of identifying, assessing, and treating threats that could affect the organization. Common activities include:",[164,9057,9058,9061,9064,9067],{},[167,9059,9060],{},"Maintaining a risk register with likelihood and impact scores",[167,9062,9063],{},"Prioritizing remediation based on business impact",[167,9065,9066],{},"Tracking treatment plans with owners and deadlines",[167,9068,9069],{},"Reviewing risk posture on a recurring schedule",[560,9071,9073],{"id":9072},"what-is-compliance-in-grc","What is compliance in GRC?",[37,9075,9076,9077,9079,9080,9079,9082,9084,9085,242],{},"Compliance means meeting the requirements of external standards, regulations, and contractual obligations. Common compliance frameworks include ",[40,9078,381],{"href":380},", ",[40,9081,43],{"href":498},[40,9083,5694],{"href":5693},", and ",[40,9086,5708],{"href":5707},[560,9088,9090],{"id":9089},"why-does-grc-matter","Why does GRC matter?",[37,9092,9093],{},"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:",[164,9095,9096,9099,9102,9105],{},[167,9097,9098],{},"Controls are mapped once and reused across frameworks",[167,9100,9101],{},"Risk decisions inform which controls get priority",[167,9103,9104],{},"Evidence is collected continuously rather than scrambled before audits",[167,9106,9107],{},"Leadership has visibility into security posture and compliance status",[560,9109,9111],{"id":9110},"what-is-grc-software","What is GRC software?",[37,9113,9114],{},"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":427,"searchDepth":428,"depth":428,"links":9116},[9117],{"id":9019,"depth":428,"text":9020,"children":9118},[9119,9120,9121,9122,9123],{"id":9030,"depth":963,"text":9031},{"id":9051,"depth":963,"text":9052},{"id":9072,"depth":963,"text":9073},{"id":9089,"depth":963,"text":9090},{"id":9110,"depth":963,"text":9111},{},"\u002Fglossary\u002Fgrc",[6070,515,6071,6072,6073],[6697,7431,2697,2698],{"title":9129,"description":9130},"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":9134,"title":9135,"body":9136,"description":427,"extension":460,"lastUpdated":979,"meta":9361,"navigation":497,"path":9362,"relatedFrameworks":9363,"relatedTerms":9364,"seo":9366,"slug":4226,"stem":9369,"term":9141,"__hash__":9370},"glossary\u002F8.glossary\u002Fincident-response.md","Incident Response",{"type":29,"value":9137,"toc":9351},[9138,9142,9145,9149,9152,9157,9177,9182,9199,9204,9221,9226,9243,9247,9250,9288,9292,9314,9318,9321,9325,9342,9346],[32,9139,9141],{"id":9140},"what-is-incident-response","What is Incident Response?",[37,9143,9144],{},"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.",[560,9146,9148],{"id":9147},"what-is-the-incident-response-lifecycle","What is the incident response lifecycle?",[37,9150,9151],{},"Most incident response programs follow the NIST SP 800-61 framework, which defines four phases:",[37,9153,9154],{},[103,9155,9156],{},"1. Preparation",[164,9158,9159,9162,9165,9168,9171,9174],{},[167,9160,9161],{},"Develop and document the incident response plan",[167,9163,9164],{},"Establish the incident response team and define roles",[167,9166,9167],{},"Deploy detection and monitoring tools",[167,9169,9170],{},"Conduct training and tabletop exercises",[167,9172,9173],{},"Establish communication channels and escalation procedures",[167,9175,9176],{},"Prepare forensic tools and evidence collection procedures",[37,9178,9179],{},[103,9180,9181],{},"2. Detection and analysis",[164,9183,9184,9187,9190,9193,9196],{},[167,9185,9186],{},"Monitor systems for indicators of compromise (IOCs)",[167,9188,9189],{},"Triage alerts to distinguish real incidents from false positives",[167,9191,9192],{},"Determine the scope, severity, and impact of the incident",[167,9194,9195],{},"Classify the incident (data breach, malware, unauthorized access, etc.)",[167,9197,9198],{},"Document findings and initial assessment",[37,9200,9201],{},[103,9202,9203],{},"3. Containment, eradication, and recovery",[164,9205,9206,9209,9212,9215,9218],{},[167,9207,9208],{},"Contain the incident to prevent further damage (short-term and long-term containment)",[167,9210,9211],{},"Eradicate the root cause (remove malware, close vulnerabilities, revoke compromised credentials)",[167,9213,9214],{},"Recover affected systems to normal operations",[167,9216,9217],{},"Verify that systems are clean and functioning properly",[167,9219,9220],{},"Monitor for signs of recurring activity",[37,9222,9223],{},[103,9224,9225],{},"4. Post-incident activity",[164,9227,9228,9231,9234,9237,9240],{},[167,9229,9230],{},"Conduct a lessons-learned review",[167,9232,9233],{},"Document the incident timeline, actions taken, and outcomes",[167,9235,9236],{},"Identify improvements to prevent similar incidents",[167,9238,9239],{},"Update the incident response plan based on lessons learned",[167,9241,9242],{},"Fulfill any regulatory notification requirements",[560,9244,9246],{"id":9245},"who-should-be-on-the-incident-response-team","Who should be on the incident response team?",[37,9248,9249],{},"An incident response team typically includes:",[164,9251,9252,9258,9264,9270,9276,9282],{},[167,9253,9254,9257],{},[103,9255,9256],{},"Incident commander"," — leads the response effort and makes key decisions",[167,9259,9260,9263],{},[103,9261,9262],{},"Security analysts"," — perform technical investigation and containment",[167,9265,9266,9269],{},[103,9267,9268],{},"IT operations"," — support system recovery and infrastructure changes",[167,9271,9272,9275],{},[103,9273,9274],{},"Legal counsel"," — advise on regulatory obligations and liability",[167,9277,9278,9281],{},[103,9279,9280],{},"Communications"," — manage internal and external communications",[167,9283,9284,9287],{},[103,9285,9286],{},"Executive sponsor"," — provides management authority and resources",[560,9289,9291],{"id":9290},"how-do-compliance-frameworks-address-incident-response","How do compliance frameworks address incident response?",[164,9293,9294,9299,9304,9309],{},[167,9295,9296,9298],{},[103,9297,381],{}," — CC7.3 and CC7.4 require procedures for responding to identified security events and recovering from incidents",[167,9300,9301,9303],{},[103,9302,43],{}," — controls A.5.24 through A.5.28 address incident management planning, assessment, response, and learning",[167,9305,9306,9308],{},[103,9307,5694],{}," — the Security Rule requires security incident procedures (45 CFR 164.308(a)(6)), and the Breach Notification Rule mandates notification following PHI breaches",[167,9310,9311,9313],{},[103,9312,5717],{}," — the Respond function (RS) addresses response planning, communications, analysis, mitigation, and improvements",[560,9315,9317],{"id":9316},"what-is-an-incident-response-tabletop-exercise","What is an incident response tabletop exercise?",[37,9319,9320],{},"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.",[560,9322,9324],{"id":9323},"what-are-common-pitfalls-with-incident-response","What are common pitfalls with incident response?",[164,9326,9327,9330,9333,9336,9339],{},[167,9328,9329],{},"No documented incident response plan",[167,9331,9332],{},"Team members unsure of their roles during an incident",[167,9334,9335],{},"Failure to preserve evidence for investigation",[167,9337,9338],{},"Delayed or incomplete regulatory notification",[167,9340,9341],{},"Not conducting post-incident reviews",[560,9343,9345],{"id":9344},"how-does-episki-help-with-incident-response","How does episki help with incident response?",[37,9347,9348,9349,242],{},"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 ",[40,9350,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":9352},[9353],{"id":9140,"depth":428,"text":9141,"children":9354},[9355,9356,9357,9358,9359,9360],{"id":9147,"depth":963,"text":9148},{"id":9245,"depth":963,"text":9246},{"id":9290,"depth":963,"text":9291},{"id":9316,"depth":963,"text":9317},{"id":9323,"depth":963,"text":9324},{"id":9344,"depth":963,"text":9345},{},"\u002Fglossary\u002Fincident-response",[6069,6070,515,6071,6073],[9365,2697,7430,6702,6696],"breach-notification",{"title":9367,"description":9368},"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":9372,"title":9373,"body":9374,"description":427,"extension":460,"lastUpdated":979,"meta":9508,"navigation":497,"path":47,"relatedFrameworks":9509,"relatedTerms":9510,"seo":9511,"slug":982,"stem":9514,"term":471,"__hash__":9515},"glossary\u002F8.glossary\u002Fisms.md","Isms",{"type":29,"value":9375,"toc":9499},[9376,9379,9385,9389,9392,9406,9410,9413,9449,9453,9456,9482,9486,9489,9493],[32,9377,471],{"id":9378},"what-is-an-isms",[37,9380,9381,9382,9384],{},"An ISMS (Information Security Management System) is a systematic framework of policies, processes, and controls that an organization uses to manage information security risks. It is the core requirement of ",[40,9383,43],{"href":498}," certification.",[560,9386,9388],{"id":9387},"what-is-the-purpose-of-an-isms","What is the purpose of an ISMS?",[37,9390,9391],{},"An ISMS provides a structured approach to:",[164,9393,9394,9397,9400,9403],{},[167,9395,9396],{},"Identifying information security risks and opportunities",[167,9398,9399],{},"Implementing controls proportionate to those risks",[167,9401,9402],{},"Monitoring and measuring security performance",[167,9404,9405],{},"Continually improving the security posture",[560,9407,9409],{"id":9408},"what-are-the-key-components-of-an-isms","What are the key components of an ISMS?",[37,9411,9412],{},"An effective ISMS typically includes:",[164,9414,9415,9421,9427,9433,9438,9444],{},[167,9416,9417,9420],{},[103,9418,9419],{},"Information security policy"," — top-level commitment from leadership",[167,9422,9423,9426],{},[103,9424,9425],{},"Risk assessment methodology"," — how the organization identifies, analyzes, and evaluates risks",[167,9428,9429,9432],{},[103,9430,9431],{},"Risk treatment plan"," — how identified risks are addressed (mitigate, accept, transfer, avoid)",[167,9434,9435,9437],{},[103,9436,143],{}," — which controls from Annex A apply and why",[167,9439,9440,9443],{},[103,9441,9442],{},"Internal audit program"," — regular reviews of ISMS effectiveness",[167,9445,9446,9448],{},[103,9447,3944],{}," — leadership evaluation of ISMS performance and direction",[560,9450,9452],{"id":9451},"what-is-the-isms-lifecycle","What is the ISMS lifecycle?",[37,9454,9455],{},"The ISMS follows a Plan-Do-Check-Act (PDCA) cycle:",[1446,9457,9458,9464,9470,9476],{},[167,9459,9460,9463],{},[103,9461,9462],{},"Plan"," — establish objectives, policies, and processes for managing risk",[167,9465,9466,9469],{},[103,9467,9468],{},"Do"," — implement and operate the ISMS",[167,9471,9472,9475],{},[103,9473,9474],{},"Check"," — monitor, measure, and review against objectives",[167,9477,9478,9481],{},[103,9479,9480],{},"Act"," — take corrective actions and improve",[560,9483,9485],{"id":9484},"what-is-the-difference-between-an-isms-and-individual-controls","What is the difference between an ISMS and individual controls?",[37,9487,9488],{},"An ISMS is not a list of controls — it is the management system that governs how controls are selected, implemented, monitored, and improved. Individual controls (like access management or encryption) operate within the ISMS framework.",[560,9490,9492],{"id":9491},"how-does-episki-support-your-isms","How does episki support your ISMS?",[37,9494,9495,9496,242],{},"episki provides the workspace for building and operating an ISMS: control libraries, risk registers, evidence tracking, ownership assignment, and review cadences. Learn more on our ",[40,9497,9498],{"href":498},"ISO 27001 page",{"title":427,"searchDepth":428,"depth":428,"links":9500},[9501],{"id":9378,"depth":428,"text":471,"children":9502},[9503,9504,9505,9506,9507],{"id":9387,"depth":963,"text":9388},{"id":9408,"depth":963,"text":9409},{"id":9451,"depth":963,"text":9452},{"id":9484,"depth":963,"text":9485},{"id":9491,"depth":963,"text":9492},{},[515],[515,6231,984,6698],{"title":9512,"description":9513},"What is an ISMS? Information Security Management System Explained","An ISMS is a systematic framework for managing information security risks. Learn how an ISMS works, its components, and how it relates to ISO 27001 certification.","8.glossary\u002Fisms","eFCKyr5T2onOha3nbKm5Esqc0WJorOxwE48XJvR0WXE",{"id":9517,"title":9518,"body":9519,"description":427,"extension":460,"lastUpdated":979,"meta":9714,"navigation":497,"path":9715,"relatedFrameworks":9716,"relatedTerms":9717,"seo":9718,"slug":6226,"stem":9721,"term":9524,"__hash__":9722},"glossary\u002F8.glossary\u002Fiso-27002.md","Iso 27002",{"type":29,"value":9520,"toc":9704},[9521,9525,9528,9532,9535,9548,9551,9555,9558,9584,9588,9591,9617,9620,9624,9627,9659,9662,9666,9669,9695,9699],[32,9522,9524],{"id":9523},"what-is-iso-27002","What is ISO 27002?",[37,9526,9527],{},"ISO 27002 is an international standard that provides implementation guidance for the information security controls referenced in ISO 27001 Annex A. While ISO 27001 specifies the requirements for an ISMS and lists controls in Annex A, ISO 27002 explains how to implement each control in practice. It is a guidance document, not a certification standard — organizations are certified against ISO 27001, not ISO 27002.",[560,9529,9531],{"id":9530},"how-does-iso-27002-relate-to-iso-27001","How does ISO 27002 relate to ISO 27001?",[37,9533,9534],{},"ISO 27001 and ISO 27002 work together as a pair:",[164,9536,9537,9542],{},[167,9538,9539,9541],{},[103,9540,43],{}," defines the management system requirements and lists controls in Annex A with brief descriptions",[167,9543,9544,9547],{},[103,9545,9546],{},"ISO 27002"," expands on each Annex A control with detailed guidance, purpose statements, and implementation considerations",[37,9549,9550],{},"Think of ISO 27001 Annex A as the \"what\" (which controls to consider) and ISO 27002 as the \"how\" (practical guidance for implementation). When an organization is deciding how to implement a particular Annex A control, ISO 27002 is the primary reference.",[560,9552,9554],{"id":9553},"how-is-iso-270022022-structured","How is ISO 27002:2022 structured?",[37,9556,9557],{},"The 2022 revision of ISO 27002 reorganized its structure to match the updated Annex A in ISO 27001:2022:",[164,9559,9560,9566,9572,9578],{},[167,9561,9562,9565],{},[103,9563,9564],{},"Clause 5: Organizational controls"," (37 controls) — covering policies, asset management, access control, supplier relationships, and more",[167,9567,9568,9571],{},[103,9569,9570],{},"Clause 6: People controls"," (8 controls) — covering hiring, training, awareness, and termination",[167,9573,9574,9577],{},[103,9575,9576],{},"Clause 7: Physical controls"," (14 controls) — covering physical security, equipment, and environmental protection",[167,9579,9580,9583],{},[103,9581,9582],{},"Clause 8: Technological controls"," (34 controls) — covering endpoint security, access management, cryptography, network security, and secure development",[560,9585,9587],{"id":9586},"what-does-each-iso-27002-control-entry-include","What does each ISO 27002 control entry include?",[37,9589,9590],{},"For each of the 93 controls, ISO 27002 provides:",[164,9592,9593,9599,9605,9611],{},[167,9594,9595,9598],{},[103,9596,9597],{},"Control statement"," — what the control requires",[167,9600,9601,9604],{},[103,9602,9603],{},"Purpose"," — why the control exists and what risk it addresses",[167,9606,9607,9610],{},[103,9608,9609],{},"Guidance"," — detailed recommendations for implementation",[167,9612,9613,9616],{},[103,9614,9615],{},"Other information"," — additional context, references, or considerations",[37,9618,9619],{},"This structure makes ISO 27002 a practical handbook for security teams tasked with designing and implementing controls.",[560,9621,9623],{"id":9622},"what-are-iso-27002-control-attributes","What are ISO 27002 control attributes?",[37,9625,9626],{},"ISO 27002:2022 introduced a new concept of control attributes, which allow organizations to filter and view controls from different perspectives:",[164,9628,9629,9635,9641,9647,9653],{},[167,9630,9631,9634],{},[103,9632,9633],{},"Control type"," — preventive, detective, or corrective",[167,9636,9637,9640],{},[103,9638,9639],{},"Information security properties"," — confidentiality, integrity, or availability",[167,9642,9643,9646],{},[103,9644,9645],{},"Cybersecurity concepts"," — mapped to identify, protect, detect, respond, or recover (aligned with NIST CSF)",[167,9648,9649,9652],{},[103,9650,9651],{},"Operational capabilities"," — such as governance, asset management, identity management, or threat management",[167,9654,9655,9658],{},[103,9656,9657],{},"Security domains"," — governance and ecosystem, protection, defense, or resilience",[37,9660,9661],{},"These attributes help organizations map ISO 27002 controls to other frameworks and organize their control environment by operational function.",[560,9663,9665],{"id":9664},"when-should-you-use-iso-27002","When should you use ISO 27002?",[37,9667,9668],{},"ISO 27002 is valuable in several scenarios:",[164,9670,9671,9677,9683,9689],{},[167,9672,9673,9676],{},[103,9674,9675],{},"Implementing ISO 27001"," — as the primary reference for how to implement Annex A controls",[167,9678,9679,9682],{},[103,9680,9681],{},"Designing a security program"," — even without pursuing certification, ISO 27002 provides a comprehensive set of best practices",[167,9684,9685,9688],{},[103,9686,9687],{},"Gap analysis"," — comparing current controls against ISO 27002 guidance to identify areas for improvement",[167,9690,9691,9694],{},[103,9692,9693],{},"Cross-framework mapping"," — the control attributes facilitate mapping to SOC 2, NIST CSF, and other frameworks",[560,9696,9698],{"id":9697},"how-does-episki-help-with-iso-27002","How does episki help with ISO 27002?",[37,9700,9701,9702,242],{},"episki incorporates ISO 27002 guidance directly into its control library, providing implementation recommendations alongside each Annex A control. This helps your team understand not just what controls are needed but how to implement them effectively. Learn more on our ",[40,9703,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":9705},[9706],{"id":9523,"depth":428,"text":9524,"children":9707},[9708,9709,9710,9711,9712,9713],{"id":9530,"depth":963,"text":9531},{"id":9553,"depth":963,"text":9554},{"id":9586,"depth":963,"text":9587},{"id":9622,"depth":963,"text":9623},{"id":9664,"depth":963,"text":9665},{"id":9697,"depth":963,"text":9698},{},"\u002Fglossary\u002Fiso-27002",[515],[515,6231,984,6227,982],{"title":9719,"description":9720},"What is ISO 27002? Definition & Compliance Guide","ISO 27002 provides detailed implementation guidance for the security controls listed in ISO 27001 Annex A. Learn how it complements your ISMS implementation.","8.glossary\u002Fiso-27002","ChRj7pOjrs_nqVHVnVVqR-k2uwPYJq5pHfejLLKm3AY",{"id":9724,"title":5,"body":9725,"description":427,"extension":460,"lastUpdated":979,"meta":10300,"navigation":497,"path":42,"relatedFrameworks":10301,"relatedTerms":10302,"seo":10303,"slug":515,"stem":10306,"term":35,"__hash__":10307},"glossary\u002F8.glossary\u002Fiso27001.md",{"type":29,"value":9726,"toc":10288},[9727,9729,9735,9742,9746,9768,9772,9775,9812,9816,9819,9845,9848,9851,9871,9874,9877,9932,9935,9939,9942,9947,9952,9957,9962,9968,9971,9975,9978,10062,10065,10068,10100,10103,10108,10122,10126,10129,10240,10243,10246,10249,10273,10279,10283],[32,9728,35],{"id":34},[37,9730,9731,9732,9734],{},"ISO 27001 is an international standard published by the International Organization for Standardization (ISO) that specifies requirements for establishing, implementing, maintaining, and continually improving an information security management system (",[40,9733,48],{"href":47},").",[37,9736,9737,9738,9741],{},"First published in 2005 and most recently revised in 2022, ISO 27001 is the world's most widely adopted information security framework. It takes a risk-based approach: rather than prescribing a fixed checklist, it requires organizations to identify their own security risks and select controls appropriate to their context. Certification is granted by accredited third-party ",[40,9739,9740],{"href":6903},"certification bodies"," after a formal audit process.",[560,9743,9745],{"id":9744},"what-are-the-key-components-of-iso-27001","What are the key components of ISO 27001?",[164,9747,9748,9753,9758,9763],{},[167,9749,9750,9752],{},[103,9751,48],{}," — a systematic approach to managing sensitive information through people, processes, and technology",[167,9754,9755,9757],{},[103,9756,113],{}," — a reference set of 93 controls (in the 2022 revision) organized into four themes: organizational, people, physical, and technological",[167,9759,9760,9762],{},[103,9761,136],{}," — a document listing which Annex A controls apply and justifying any exclusions",[167,9764,9765,9767],{},[103,9766,6524],{}," — a formal process for identifying and treating information security risks",[560,9769,9771],{"id":9770},"what-is-the-iso-27001-certification-process","What is the ISO 27001 certification process?",[37,9773,9774],{},"ISO 27001 certification involves:",[1446,9776,9777,9782,9787,9792,9797,9802,9807],{},[167,9778,9779,9781],{},[103,9780,9687],{}," — compare current practices against the standard",[167,9783,9784,9786],{},[103,9785,1251],{}," — build policies, controls, and processes",[167,9788,9789,9791],{},[103,9790,3911],{}," — verify the ISMS works as intended",[167,9793,9794,9796],{},[103,9795,1642],{}," — external auditor reviews documentation",[167,9798,9799,9801],{},[103,9800,1658],{}," — external auditor tests operational effectiveness",[167,9803,9804,9806],{},[103,9805,6756],{}," — annual reviews to maintain certification",[167,9808,9809,9811],{},[103,9810,6762],{}," — full audit every three years",[560,9813,9815],{"id":9814},"who-needs-iso-27001","Who needs ISO 27001?",[37,9817,9818],{},"ISO 27001 certification is voluntary — no law mandates it — but it is increasingly expected by enterprise buyers and procurement teams. Organizations that benefit most include:",[164,9820,9821,9827,9833,9839],{},[167,9822,9823,9826],{},[103,9824,9825],{},"Companies targeting international customers"," — ISO 27001 is the de facto security standard in Europe, APAC, and the Middle East. Without it, you may not make it past vendor questionnaires.",[167,9828,9829,9832],{},[103,9830,9831],{},"Regulated industries"," — Financial services, healthcare, and government contractors often require suppliers to hold ISO 27001 certification as a baseline.",[167,9834,9835,9838],{},[103,9836,9837],{},"SaaS and cloud providers"," — Enterprise buyers routinely ask for ISO 27001 during procurement. It signals that your security program is structured and externally validated.",[167,9840,9841,9844],{},[103,9842,9843],{},"Organizations scaling into new markets"," — If you already serve the US with a SOC 2, adding ISO 27001 opens doors globally without rebuilding your program from scratch.",[37,9846,9847],{},"Even when not contractually required, holding the certification reduces the time spent answering security questionnaires and builds trust with prospects before the first sales call.",[37,9849,9850],{},"ISO 27001 is especially valued in:",[164,9852,9853,9859,9865],{},[167,9854,9855,9858],{},[103,9856,9857],{},"Europe"," — GDPR-conscious buyers view it as evidence of mature data protection practices.",[167,9860,9861,9864],{},[103,9862,9863],{},"APAC"," — Markets like Japan, Australia, and Singapore treat it as a baseline requirement for technology vendors.",[167,9866,9867,9870],{},[103,9868,9869],{},"Global enterprises"," — Companies like Google, Microsoft, and Salesforce require ISO 27001 from critical suppliers in their vendor risk management programs.",[560,9872,9873],{"id":547},"What changed in ISO 27001:2022?",[37,9875,9876],{},"The 2022 revision of ISO 27001 (formally ISO\u002FIEC 27001:2022) brought the most significant structural changes since the standard's 2013 edition. The core ISMS requirements in clauses 4–10 received minor wording updates, but Annex A was overhauled:",[164,9878,9879,9885,9891],{},[167,9880,9881,9884],{},[103,9882,9883],{},"Restructured from 14 categories to 4 themes"," — The previous 14-domain layout was replaced with four broad themes: organizational, people, physical, and technological.",[167,9886,9887,9890],{},[103,9888,9889],{},"Consolidated from 114 controls to 93"," — Controls were merged and reorganized, not removed. The reduction reflects overlapping controls being combined into more coherent groupings.",[167,9892,9893,9896,9897],{},[103,9894,9895],{},"11 new controls added"," — The 2022 revision introduced controls that reflect the modern threat landscape, including:\n",[164,9898,9899,9902,9905,9908,9911,9914,9917,9920,9923,9926,9929],{},[167,9900,9901],{},"Threat intelligence",[167,9903,9904],{},"Information security for cloud services",[167,9906,9907],{},"ICT readiness for business continuity",[167,9909,9910],{},"Physical security monitoring",[167,9912,9913],{},"Configuration management",[167,9915,9916],{},"Information deletion",[167,9918,9919],{},"Data masking",[167,9921,9922],{},"Data leakage prevention",[167,9924,9925],{},"Monitoring activities",[167,9927,9928],{},"Web filtering",[167,9930,9931],{},"Secure coding",[37,9933,9934],{},"Organizations certified under the 2013 edition were required to transition to the 2022 revision by October 31, 2025. New certifications are issued exclusively against the 2022 standard.",[560,9936,9938],{"id":9937},"what-are-the-annex-a-control-themes","What are the Annex A control themes?",[37,9940,9941],{},"The four themes in Annex A group controls by domain rather than by the asset or process they protect. This makes it easier to assign ownership and track implementation progress.",[37,9943,9944,9946],{},[103,9945,6114],{},"\nThese cover governance, policies, and management-level activities. Examples include information security policies, defined roles and responsibilities, threat intelligence, asset management, access control policies, supplier security, and incident management.",[37,9948,9949,9951],{},[103,9950,6120],{},"\nFocused on the human side of security. Examples include pre-employment screening, information security awareness and training, disciplinary processes, responsibilities after termination, remote working arrangements, and confidentiality agreements.",[37,9953,9954,9956],{},[103,9955,6126],{},"\nAddress the protection of physical spaces and equipment. Examples include physical security perimeters, physical entry controls, securing offices and facilities, equipment maintenance, storage media handling, and supporting utility security.",[37,9958,9959,9961],{},[103,9960,6132],{},"\nCover technical safeguards applied to IT systems. Examples include user endpoint devices, privileged access rights, access restriction to information, secure authentication, capacity management, protection against malware, management of technical vulnerabilities, logging, network security, encryption, secure development lifecycle, and data masking.",[37,9963,9964,9965,9967],{},"Together, the 93 controls form the reference set from which you build your ",[40,9966,143],{"href":142},". Not every control will apply — the SoA documents which you selected and why you excluded the rest.",[37,9969,9970],{},"A common approach is to assign theme ownership: IT leads technological controls, HR owns people controls, facilities manages physical controls, and a GRC or security team coordinates organizational controls. This clear division of responsibility is one reason the 2022 restructuring was widely welcomed by practitioners.",[560,9972,9974],{"id":9973},"what-is-the-cost-and-timeline-of-iso-27001-certification","What is the cost and timeline of ISO 27001 certification?",[37,9976,9977],{},"ISO 27001 certification is a significant investment in both money and internal effort. Typical ranges depend on organization size, complexity, and existing maturity:",[1596,9979,9980,9996],{},[1599,9981,9982],{},[1602,9983,9984,9987,9990,9993],{},[1605,9985,9986],{},"Factor",[1605,9988,9989],{},"Small org (\u003C 50 employees)",[1605,9991,9992],{},"Mid-size org (50–500)",[1605,9994,9995],{},"Enterprise (500+)",[1612,9997,9998,10014,10030,10046],{},[1602,9999,10000,10005,10008,10011],{},[1617,10001,10002],{},[103,10003,10004],{},"Implementation cost",[1617,10006,10007],{},"$30K–$50K",[1617,10009,10010],{},"$50K–$100K",[1617,10012,10013],{},"$100K+",[1602,10015,10016,10021,10024,10027],{},[1617,10017,10018],{},[103,10019,10020],{},"Timeline to certification",[1617,10022,10023],{},"6–9 months",[1617,10025,10026],{},"9–12 months",[1617,10028,10029],{},"12–18 months",[1602,10031,10032,10037,10040,10043],{},[1617,10033,10034],{},[103,10035,10036],{},"Certification audit fees",[1617,10038,10039],{},"$10K–$20K",[1617,10041,10042],{},"$20K–$40K",[1617,10044,10045],{},"$40K–$80K",[1602,10047,10048,10053,10056,10059],{},[1617,10049,10050],{},[103,10051,10052],{},"Annual surveillance audits",[1617,10054,10055],{},"$5K–$15K",[1617,10057,10058],{},"$15K–$25K",[1617,10060,10061],{},"$25K–$50K",[37,10063,10064],{},"These figures include consulting, tooling, auditor fees, and remediation. They do not include the internal time your team spends building policies, gathering evidence, and running internal audits — which is often the largest hidden cost.",[37,10066,10067],{},"The implementation timeline typically breaks down as:",[1446,10069,10070,10076,10082,10088,10094],{},[167,10071,10072,10075],{},[103,10073,10074],{},"Months 1–2"," — Scoping, gap analysis, and risk assessment",[167,10077,10078,10081],{},[103,10079,10080],{},"Months 3–6"," — Policy development, control implementation, and staff training",[167,10083,10084,10087],{},[103,10085,10086],{},"Months 7–8"," — Internal audit and management review",[167,10089,10090,10093],{},[103,10091,10092],{},"Months 9–10"," — Stage 1 audit (documentation review)",[167,10095,10096,10099],{},[103,10097,10098],{},"Months 10–12"," — Remediation and Stage 2 audit (operational effectiveness)",[37,10101,10102],{},"After certification, expect ongoing costs for surveillance audits (annually) and a full recertification audit every three years.",[37,10104,10105],{},[103,10106,10107],{},"Tips for reducing cost and timeline:",[164,10109,10110,10113,10116,10119],{},[167,10111,10112],{},"Start with a gap analysis to avoid over-investing in areas you already cover.",[167,10114,10115],{},"Reuse existing policies and evidence from SOC 2 or NIST CSF if you have them.",[167,10117,10118],{},"Use a GRC platform to centralize evidence collection and automate control tracking.",[167,10120,10121],{},"Engage your certification body early for a pre-assessment to surface surprises before the formal audit.",[560,10123,10125],{"id":10124},"how-does-iso-27001-map-to-other-frameworks","How does ISO 27001 map to other frameworks?",[37,10127,10128],{},"If your organization already operates under another framework, ISO 27001 will share significant control overlap. Mapping controls across frameworks reduces duplicate work and accelerates certification timelines.",[1596,10130,10131,10145],{},[1599,10132,10133],{},[1602,10134,10135,10137,10139,10141,10143],{},[1605,10136],{},[1605,10138,43],{},[1605,10140,381],{},[1605,10142,5717],{},[1605,10144,5708],{},[1612,10146,10147,10166,10184,10202,10221],{},[1602,10148,10149,10154,10157,10160,10163],{},[1617,10150,10151],{},[103,10152,10153],{},"Type",[1617,10155,10156],{},"Certifiable standard",[1617,10158,10159],{},"Attestation report",[1617,10161,10162],{},"Voluntary framework",[1617,10164,10165],{},"Mandatory standard",[1602,10167,10168,10172,10175,10178,10181],{},[1617,10169,10170],{},[103,10171,5214],{},[1617,10173,10174],{},"Global",[1617,10176,10177],{},"Primarily North America",[1617,10179,10180],{},"US-originated, global adoption",[1617,10182,10183],{},"Any org handling cardholder data",[1602,10185,10186,10190,10193,10196,10199],{},[1617,10187,10188],{},[103,10189,7468],{},[1617,10191,10192],{},"ISMS + Annex A controls",[1617,10194,10195],{},"Trust Services Criteria",[1617,10197,10198],{},"6 functions, 22 categories",[1617,10200,10201],{},"12 requirements, 300+ sub-requirements",[1602,10203,10204,10209,10212,10215,10218],{},[1617,10205,10206],{},[103,10207,10208],{},"Validity",[1617,10210,10211],{},"3 years with surveillance",[1617,10213,10214],{},"Report covers observation period",[1617,10216,10217],{},"Self-assessed (no certification)",[1617,10219,10220],{},"Annual assessment",[1602,10222,10223,10228,10231,10234,10237],{},[1617,10224,10225],{},[103,10226,10227],{},"Control count",[1617,10229,10230],{},"93 (Annex A)",[1617,10232,10233],{},"~60 points of focus",[1617,10235,10236],{},"~100 subcategories",[1617,10238,10239],{},"300+",[37,10241,10242],{},"The overlap between ISO 27001 and SOC 2 is roughly 70–80% at the control level. NIST CSF aligns even more closely with ISO 27001 since both follow a risk-based approach. PCI DSS is more prescriptive but shares foundational controls around access management, logging, encryption, and incident response.",[37,10244,10245],{},"Organizations that already have one framework in place can typically achieve ISO 27001 certification 30–40% faster by reusing existing policies, evidence, and control implementations.",[37,10247,10248],{},"Key areas of overlap include:",[164,10250,10251,10256,10261,10267],{},[167,10252,10253,10255],{},[103,10254,7901],{}," — covered by all four frameworks, though PCI DSS is the most prescriptive about password complexity and multi-factor authentication.",[167,10257,10258,10260],{},[103,10259,7907],{}," — ISO 27001, NIST CSF, and PCI DSS all require documented incident response plans and regular testing.",[167,10262,10263,10266],{},[103,10264,10265],{},"Risk management"," — ISO 27001 and NIST CSF both center on risk-based decision-making; SOC 2 addresses it through the Common Criteria.",[167,10268,10269,10272],{},[103,10270,10271],{},"Logging and monitoring"," — a universal requirement, with PCI DSS specifying exact log retention periods and ISO 27001 leaving implementation details to the organization.",[37,10274,10275,10276,242],{},"For a detailed breakdown of how controls map across frameworks, see our ",[40,10277,10278],{"href":391},"framework mapping guide",[560,10280,10282],{"id":10281},"how-does-episki-help-with-iso-27001","How does episki help with ISO 27001?",[37,10284,10285,10286,242],{},"episki maps controls to Annex A, tracks your Statement of Applicability, and connects evidence across ISO 27001 and other frameworks. Learn more on our ",[40,10287,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":10289},[10290],{"id":34,"depth":428,"text":35,"children":10291},[10292,10293,10294,10295,10296,10297,10298,10299],{"id":9744,"depth":963,"text":9745},{"id":9770,"depth":963,"text":9771},{"id":9814,"depth":963,"text":9815},{"id":547,"depth":963,"text":9873},{"id":9937,"depth":963,"text":9938},{"id":9973,"depth":963,"text":9974},{"id":10124,"depth":963,"text":10125},{"id":10281,"depth":963,"text":10282},{},[515],[982,6231,1362,6906],{"title":10304,"description":10305},"What is ISO 27001? ISMS Certification Explained","ISO 27001 is the international standard for information security management systems (ISMS). Learn about certification requirements, Annex A controls, and how to prepare.","8.glossary\u002Fiso27001","9KWMfDsDTD7_JZ5rywuy0uGOWxwpgPDmm0DBaiUUC2U",{"id":10309,"title":10310,"body":10311,"description":427,"extension":460,"lastUpdated":979,"meta":10417,"navigation":497,"path":10418,"relatedFrameworks":10419,"relatedTerms":10420,"seo":10421,"slug":10424,"stem":10425,"term":10316,"__hash__":10426},"glossary\u002F8.glossary\u002Fjob-separation.md","Job Separation",{"type":29,"value":10312,"toc":10408},[10313,10317,10320,10324,10327,10331,10357,10361,10378,10382,10385,10399,10403],[32,10314,10316],{"id":10315},"what-is-job-separation","What is Job Separation?",[37,10318,10319],{},"Job separation, also known as segregation of duties (SoD), is the practice of dividing critical responsibilities among multiple people to reduce the risk of fraud, error, or abuse of privilege. The principle ensures that no single individual has end-to-end control over a sensitive process.",[560,10321,10323],{"id":10322},"why-does-job-separation-matter","Why does job separation matter?",[37,10325,10326],{},"When one person controls an entire workflow — such as approving and executing financial transactions, or deploying code and managing production access — the risk of undetected mistakes or intentional misuse increases significantly. Segregation of duties creates natural checkpoints where different individuals must independently verify or authorize actions.",[560,10328,10330],{"id":10329},"what-are-common-examples-of-job-separation","What are common examples of job separation?",[164,10332,10333,10339,10345,10351],{},[167,10334,10335,10338],{},[103,10336,10337],{},"Financial controls"," — the person who requests a purchase should not be the same person who approves payment",[167,10340,10341,10344],{},[103,10342,10343],{},"Change management"," — developers who write code should not be the same people who approve and deploy it to production",[167,10346,10347,10350],{},[103,10348,10349],{},"User access management"," — the person who requests access should not be the one who grants it",[167,10352,10353,10356],{},[103,10354,10355],{},"Audit and review"," — internal auditors should be independent of the processes they audit",[560,10358,10360],{"id":10359},"how-do-compliance-frameworks-address-job-separation","How do compliance frameworks address job separation?",[164,10362,10363,10368,10373],{},[167,10364,10365,10367],{},[103,10366,381],{}," — CC5.2 and CC6.1 address segregation of duties as part of control activities and access controls",[167,10369,10370,10372],{},[103,10371,43],{}," — A.5.3 requires segregation of duties to reduce opportunities for unauthorized modification or misuse",[167,10374,10375,10377],{},[103,10376,5708],{}," — Requirement 6.5.6 addresses separation of development, testing, and production environments",[560,10379,10381],{"id":10380},"what-compensating-controls-apply-when-job-separation-is-not-possible","What compensating controls apply when job separation is not possible?",[37,10383,10384],{},"In smaller organizations where strict separation is not always feasible, compensating controls can help:",[164,10386,10387,10390,10393,10396],{},[167,10388,10389],{},"Detailed audit logging of all actions",[167,10391,10392],{},"Regular management review of activity logs",[167,10394,10395],{},"Automated alerts for high-risk activities",[167,10397,10398],{},"Periodic access reviews to verify role appropriateness",[560,10400,10402],{"id":10401},"how-does-episki-help-with-job-separation","How does episki help with job separation?",[37,10404,10405,10406,242],{},"episki maps segregation of duties requirements across frameworks, tracks who has access to what, and provides evidence trails for auditors. Learn more on our ",[40,10407,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":10409},[10410],{"id":10315,"depth":428,"text":10316,"children":10411},[10412,10413,10414,10415,10416],{"id":10322,"depth":963,"text":10323},{"id":10329,"depth":963,"text":10330},{"id":10359,"depth":963,"text":10360},{"id":10380,"depth":963,"text":10381},{"id":10401,"depth":963,"text":10402},{},"\u002Fglossary\u002Fjob-separation",[6070,515,6072],[6080,6697,6227],{"title":10422,"description":10423},"What is Job Separation? Definition & Compliance Guide","Job separation (segregation of duties) is the practice of dividing critical responsibilities among multiple people to reduce the risk of fraud or error.","job-separation","8.glossary\u002Fjob-separation","NGlRTvMi7wGdE1a4aqRDvGWJqatS66pV0ZpUqXQPEGI",{"id":10428,"title":10429,"body":10430,"description":427,"extension":460,"lastUpdated":979,"meta":10962,"navigation":497,"path":10963,"relatedFrameworks":10964,"relatedTerms":10965,"seo":10966,"slug":10969,"stem":10970,"term":10435,"__hash__":10971},"glossary\u002F8.glossary\u002Fkey-management.md","Key Management",{"type":29,"value":10431,"toc":10950},[10432,10436,10439,10443,10481,10485,10488,10491,10517,10520,10524,10527,10532,10535,10561,10569,10572,10576,10579,10605,10608,10627,10630,10634,10637,10651,10654,10665,10672,10683,10687,10690,10785,10790,10817,10821,10824,10874,10878,10920,10924,10941,10945],[32,10433,10435],{"id":10434},"what-is-key-management","What is Key Management?",[37,10437,10438],{},"Key management is the process of creating, storing, distributing, rotating, and retiring cryptographic keys used to protect encrypted data. Effective key management ensures that encryption actually delivers the confidentiality and integrity it promises — poorly managed keys can render even strong encryption useless.",[560,10440,10442],{"id":10441},"what-are-the-stages-of-the-key-lifecycle","What are the stages of the key lifecycle?",[164,10444,10445,10451,10457,10463,10469,10475],{},[167,10446,10447,10450],{},[103,10448,10449],{},"Generation"," — creating keys using cryptographically secure methods with appropriate key lengths",[167,10452,10453,10456],{},[103,10454,10455],{},"Distribution"," — securely delivering keys to authorized systems or users",[167,10458,10459,10462],{},[103,10460,10461],{},"Storage"," — protecting keys at rest using hardware security modules (HSMs), key vaults, or other secure storage",[167,10464,10465,10468],{},[103,10466,10467],{},"Rotation"," — periodically replacing keys to limit the impact of a potential compromise",[167,10470,10471,10474],{},[103,10472,10473],{},"Revocation"," — disabling keys that are no longer trusted or have been compromised",[167,10476,10477,10480],{},[103,10478,10479],{},"Destruction"," — securely deleting keys that are no longer needed, ensuring they cannot be recovered",[560,10482,10484],{"id":10483},"why-does-key-management-matter-for-security","Why does key management matter for security?",[37,10486,10487],{},"Encryption is only as strong as the key management behind it. A 256-bit AES key offers no protection if it's stored in the same database as the data it encrypts — an attacker who compromises the database gets both the ciphertext and the key to decrypt it. This is not a theoretical concern; it's one of the most common encryption failures found in penetration tests and compliance assessments.",[37,10489,10490],{},"Key management failures create several categories of risk:",[164,10492,10493,10499,10505,10511],{},[167,10494,10495,10498],{},[103,10496,10497],{},"Exposure of historical data"," — Without regular key rotation, a single key compromise exposes every record encrypted with that key, potentially spanning years of sensitive data. Rotating keys limits the blast radius of any individual compromise.",[167,10500,10501,10504],{},[103,10502,10503],{},"Insider threats"," — If one administrator holds all key material with no split knowledge or dual control, that person can access every encrypted record in the organization. Proper key management distributes trust across multiple individuals.",[167,10506,10507,10510],{},[103,10508,10509],{},"Compliance failures"," — Auditors don't just check that encryption is enabled. They verify that keys are managed according to documented procedures, rotated on schedule, and protected with controls proportional to the sensitivity of the data they protect.",[167,10512,10513,10516],{},[103,10514,10515],{},"Incident response gaps"," — Organizations that lack documented key management procedures often cannot determine which data was exposed during a breach, which keys need emergency rotation, or how to restore encrypted backups after a key custodian leaves the company.",[37,10518,10519],{},"The bottom line: encryption without proper key management is security theater. It checks a box on a checklist without actually reducing risk. Organizations that invest in strong encryption algorithms but neglect key management are protecting data with a lock and then leaving the key under the doormat.",[560,10521,10523],{"id":10522},"what-are-common-key-management-architectures","What are common key management architectures?",[37,10525,10526],{},"There are three primary approaches to key management, each suited to different risk profiles, compliance requirements, and operational maturity levels. The right choice depends on what data you're protecting, which frameworks you're subject to, and how much operational complexity you can absorb.",[10528,10529,10531],"h4",{"id":10530},"cloud-kms","Cloud KMS",[37,10533,10534],{},"Cloud key management services — including AWS KMS, Azure Key Vault, and GCP Cloud KMS — are the most common starting point for organizations running workloads in the cloud. These services provide:",[164,10536,10537,10543,10549,10555],{},[167,10538,10539,10542],{},[103,10540,10541],{},"Envelope encryption"," — Data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a key encryption key (KEK) managed by the cloud provider. This limits the number of calls to the KMS while keeping the master key material protected.",[167,10544,10545,10548],{},[103,10546,10547],{},"Customer-managed keys (CMK)"," — You control key rotation schedules, access policies, and deletion. The cloud provider manages the underlying infrastructure but cannot use the key without your authorization.",[167,10550,10551,10554],{},[103,10552,10553],{},"Provider-managed keys"," — The cloud provider handles all key management automatically. Simpler to operate, but offers less control and may not satisfy compliance requirements that mandate customer-controlled keys.",[167,10556,10557,10560],{},[103,10558,10559],{},"Bring Your Own Key (BYOK)"," — You generate keys in your own environment (often an on-premises HSM) and import them into the cloud KMS. This satisfies requirements for key generation in a controlled environment while still leveraging cloud-native encryption integration.",[37,10562,10563,10564,7947,10566,10568],{},"Cloud KMS is appropriate for most SaaS applications, internal systems, and workloads where the cloud provider is already part of the trust boundary. For organizations subject to ",[40,10565,5708],{"href":5707},[40,10567,381],{"href":380},", cloud KMS with customer-managed keys typically satisfies key management requirements when combined with proper access policies and rotation schedules.",[37,10570,10571],{},"Most cloud KMS services also provide detailed audit logs of every key operation, which simplifies compliance evidence collection during assessments.",[10528,10573,10575],{"id":10574},"hardware-security-modules-hsms","Hardware Security Modules (HSMs)",[37,10577,10578],{},"HSMs are dedicated hardware devices designed to generate, store, and manage cryptographic keys in a tamper-resistant environment. They are validated against FIPS 140-2 or FIPS 140-3 standards at various levels:",[164,10580,10581,10587,10593,10599],{},[167,10582,10583,10586],{},[103,10584,10585],{},"Level 1"," — Basic security requirements, no physical tamper resistance",[167,10588,10589,10592],{},[103,10590,10591],{},"Level 2"," — Tamper-evident coatings or seals, role-based authentication",[167,10594,10595,10598],{},[103,10596,10597],{},"Level 3"," — Tamper-resistant with active response mechanisms (e.g., zeroization of keys upon detection of physical intrusion)",[167,10600,10601,10604],{},[103,10602,10603],{},"Level 4"," — Full physical security envelope with environmental failure protection",[37,10606,10607],{},"HSMs are required or strongly recommended in several contexts:",[164,10609,10610,10615,10621],{},[167,10611,10612,10614],{},[103,10613,5708],{}," — Strongly recommended for protecting cardholder data encryption keys, and effectively required for PIN-based transaction processing",[167,10616,10617,10620],{},[103,10618,10619],{},"Government and defense"," — CMMC, FedRAMP, and similar frameworks often require FIPS 140-2 Level 3 or higher for cryptographic key storage",[167,10622,10623,10626],{},[103,10624,10625],{},"Certificate authorities"," — Root and intermediate CA private keys must be stored in HSMs per industry standards",[37,10628,10629],{},"Cloud-based HSM options (AWS CloudHSM, Azure Dedicated HSM, GCP Cloud HSM) provide FIPS 140-2 Level 3 validated hardware in cloud data centers, bridging the gap between on-premises HSM security and cloud operational convenience.",[10528,10631,10633],{"id":10632},"software-based-key-stores","Software-based key stores",[37,10635,10636],{},"Software-based solutions like HashiCorp Vault, CyberArk Conjur, or application-level key management provide flexibility without dedicated hardware. These tools offer:",[164,10638,10639,10642,10645,10648],{},[167,10640,10641],{},"Centralized secret and key management across multiple applications and environments",[167,10643,10644],{},"Dynamic secrets that are generated on demand and automatically revoked after use",[167,10646,10647],{},"Audit logging of all key access and operations",[167,10649,10650],{},"Integration with identity providers for policy-based access control",[37,10652,10653],{},"Software key stores are appropriate when:",[164,10655,10656,10659,10662],{},[167,10657,10658],{},"Compliance requirements do not mandate HSMs",[167,10660,10661],{},"You need to manage secrets and keys across hybrid or multi-cloud environments",[167,10663,10664],{},"Your threat model does not include sophisticated physical or hardware-level attacks",[37,10666,10667,10668,10671],{},"They are ",[103,10669,10670],{},"not"," appropriate when:",[164,10673,10674,10677,10680],{},[167,10675,10676],{},"Regulations explicitly require hardware-based key protection (e.g., PCI PIN security, certain government classifications)",[167,10678,10679],{},"Your risk assessment identifies nation-state or advanced persistent threats targeting cryptographic material",[167,10681,10682],{},"You need to provide cryptographic proof that keys have never been exposed to software",[560,10684,10686],{"id":10685},"what-are-the-key-management-requirements","What are the key management requirements?",[37,10688,10689],{},"Different compliance frameworks impose different key management requirements. Understanding these differences is critical when an organization is subject to multiple frameworks simultaneously — which is increasingly common. The following table provides a practical comparison across five major frameworks:",[1596,10691,10692,10709],{},[1599,10693,10694],{},[1602,10695,10696,10698,10700,10702,10704,10706],{},[1605,10697,5841],{},[1605,10699,5708],{},[1605,10701,43],{},[1605,10703,5694],{},[1605,10705,381],{},[1605,10707,10708],{},"CMMC",[1612,10710,10711,10729,10748,10767],{},[1602,10712,10713,10716,10719,10722,10724,10726],{},[1617,10714,10715],{},"Documented key management procedures",[1617,10717,10718],{},"Req 3.6",[1617,10720,10721],{},"A.8.24",[1617,10723,5886],{},[1617,10725,5861],{},[1617,10727,10728],{},"SC.L2-3.13.10",[1602,10730,10731,10734,10737,10740,10743,10745],{},[1617,10732,10733],{},"Key rotation schedule",[1617,10735,10736],{},"Annual minimum",[1617,10738,10739],{},"Risk-based",[1617,10741,10742],{},"Not specified",[1617,10744,10739],{},[1617,10746,10747],{},"Per NIST 800-171",[1602,10749,10750,10753,10756,10759,10761,10764],{},[1617,10751,10752],{},"Split knowledge \u002F dual control",[1617,10754,10755],{},"Required for manual keys",[1617,10757,10758],{},"Recommended",[1617,10760,10742],{},[1617,10762,10763],{},"Expected",[1617,10765,10766],{},"Required",[1602,10768,10769,10772,10775,10777,10780,10782],{},[1617,10770,10771],{},"HSM or equivalent",[1617,10773,10774],{},"Strongly recommended",[1617,10776,10739],{},[1617,10778,10779],{},"Not required",[1617,10781,10739],{},[1617,10783,10784],{},"Varies by level",[37,10786,10787],{},[103,10788,10789],{},"Reading this table:",[164,10791,10792,10797,10802,10807,10812],{},[167,10793,10794,10796],{},[103,10795,5708],{}," is the most prescriptive. Requirement 3.6 specifies exactly what key management procedures must include, from key generation through destruction. Annual key rotation is a minimum baseline, and split knowledge\u002Fdual control is mandatory whenever keys are managed manually.",[167,10798,10799,10801],{},[103,10800,43],{}," takes a risk-based approach. Annex A control A.8.24 requires a policy on the use of cryptographic controls including key management, but the specific controls depend on your risk assessment and Statement of Applicability.",[167,10803,10804,10806],{},[103,10805,5694],{}," is the least prescriptive on key management specifically. Encryption of ePHI is an \"addressable\" implementation specification, meaning organizations must implement it or document why an equivalent alternative is appropriate. Key management requirements follow from the encryption decision.",[167,10808,10809,10811],{},[103,10810,381],{}," addresses key management through the Common Criteria, particularly CC6.1 (logical access) and CC6.7 (data transmission). The specific expectations depend on the trust services criteria in scope and the auditor's interpretation.",[167,10813,10814,10816],{},[103,10815,10708],{}," references NIST SP 800-171 for key management requirements. At Level 2, control SC.L2-3.13.10 requires establishing and managing cryptographic keys when cryptography is employed. Higher levels add additional requirements.",[560,10818,10820],{"id":10819},"what-are-common-key-management-mistakes","What are common key management mistakes?",[37,10822,10823],{},"Even organizations with mature security programs make key management errors. These mistakes are found repeatedly in audit findings, penetration test reports, and breach post-mortems. The most frequent include:",[164,10825,10826,10832,10838,10844,10850,10856,10862,10868],{},[167,10827,10828,10831],{},[103,10829,10830],{},"Storing keys alongside encrypted data"," — Placing encryption keys in the same database, file system, or backup as the data they protect. If an attacker gains access to the data store, they get the keys too. Keys must be stored in a separate system with independent access controls.",[167,10833,10834,10837],{},[103,10835,10836],{},"Hardcoding keys in source code"," — Embedding encryption keys, API keys, or other secrets directly in application code. These keys end up in version control history, CI\u002FCD logs, and developer laptops. Use a secrets manager or environment variable injection instead.",[167,10839,10840,10843],{},[103,10841,10842],{},"No key rotation policy"," — Using the same encryption keys indefinitely. Without rotation, a single compromise exposes all data ever encrypted with that key. Define rotation schedules based on data sensitivity and framework requirements.",[167,10845,10846,10849],{},[103,10847,10848],{},"Single person with all key access"," — Concentrating key custody in one individual with no split knowledge or dual control. This creates both a security risk (insider threat) and an operational risk (key unavailability if that person is unreachable).",[167,10851,10852,10855],{},[103,10853,10854],{},"No documented recovery procedures"," — Failing to plan for key loss, corruption, or custodian departure. Organizations discover this gap during an incident, when they cannot decrypt backups or rotate compromised keys because the procedure was never written down or tested.",[167,10857,10858,10861],{},[103,10859,10860],{},"Using weak or predictable key generation"," — Generating keys with insufficient entropy, predictable seeds, or non-cryptographic random number generators. Always use cryptographically secure random number generators (CSPRNGs) and key lengths appropriate for the algorithm and data sensitivity.",[167,10863,10864,10867],{},[103,10865,10866],{},"Ignoring key state tracking"," — Not maintaining an inventory of which keys are active, retired, or compromised. Without a key inventory, organizations cannot answer basic questions during an audit or incident: how many keys exist, who has access, and when they were last rotated.",[167,10869,10870,10873],{},[103,10871,10872],{},"Failing to test key recovery"," — Having a documented recovery procedure that has never been exercised. Recovery procedures degrade over time as infrastructure changes, personnel rotate, and backup systems are modified. Regular testing is the only way to ensure recovery will work when it matters.",[560,10875,10877],{"id":10876},"how-do-compliance-frameworks-address-key-management","How do compliance frameworks address key management?",[164,10879,10880,10891,10900,10910],{},[167,10881,10882,10886,10887],{},[103,10883,10884],{},[40,10885,5708],{"href":5707}," — Requirement 3.5 and 3.6 detail specific key management procedures for protecting ",[40,10888,10890],{"href":10889},"\u002Fglossary\u002Fpan","cardholder data (PAN)",[167,10892,10893,5683,10897,10899],{},[103,10894,10895],{},[40,10896,43],{"href":498},[40,10898,4417],{"href":119}," control A.8.24 covers the use of cryptography including key management policies",[167,10901,10902,10906,10907,10909],{},[103,10903,10904],{},[40,10905,5694],{"href":5693}," — the Security Rule requires ",[40,10908,6018],{"href":6017}," of ePHI, which implies proper key management",[167,10911,10912,10916,10917],{},[103,10913,10914],{},[40,10915,381],{"href":380}," — CC6.1 and CC6.7 address encryption and key management as part of logical ",[40,10918,10919],{"href":6067},"access controls",[560,10921,10923],{"id":10922},"what-are-best-practices-for-key-management","What are best practices for key management?",[164,10925,10926,10929,10932,10935,10938],{},[167,10927,10928],{},"Use hardware security modules (HSMs) or cloud key management services (AWS KMS, Azure Key Vault, GCP Cloud KMS) rather than storing keys in application code or configuration files",[167,10930,10931],{},"Enforce separation of duties so that key custodians cannot access the data those keys protect",[167,10933,10934],{},"Document key rotation schedules and automate rotation where possible",[167,10936,10937],{},"Maintain an inventory of all cryptographic keys, their owners, and their expiration dates",[167,10939,10940],{},"Test key recovery procedures regularly",[560,10942,10944],{"id":10943},"how-does-episki-help-with-key-management","How does episki help with key management?",[37,10946,10947,10948,242],{},"episki tracks key management policies, links them to encryption controls, and monitors rotation schedules to ensure cryptographic practices stay compliant. Learn more on our ",[40,10949,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":10951},[10952],{"id":10434,"depth":428,"text":10435,"children":10953},[10954,10955,10956,10957,10958,10959,10960,10961],{"id":10441,"depth":963,"text":10442},{"id":10483,"depth":963,"text":10484},{"id":10522,"depth":963,"text":10523},{"id":10685,"depth":963,"text":10686},{"id":10819,"depth":963,"text":10820},{"id":10876,"depth":963,"text":10877},{"id":10922,"depth":963,"text":10923},{"id":10943,"depth":963,"text":10944},{},"\u002Fglossary\u002Fkey-management",[6069,6070,515,6072,6071],[6018,8090,6080],{"title":10967,"description":10968},"Key Management: What It Is & Why Compliance Requires It","Key management covers creating, storing, rotating, and retiring cryptographic keys. Learn requirements across SOC 2, ISO 27001, HIPAA, and PCI DSS.","key-management","8.glossary\u002Fkey-management","1dvRJIXp6Ctc7SOVhg5O-XyVT22CTyhIb0o8RWTqqng",{"id":10973,"title":10974,"body":10975,"description":427,"extension":460,"lastUpdated":979,"meta":11089,"navigation":497,"path":11090,"relatedFrameworks":11091,"relatedTerms":11092,"seo":11093,"slug":11096,"stem":11097,"term":10980,"__hash__":11098},"glossary\u002F8.glossary\u002Fleast-privilege.md","Least Privilege",{"type":29,"value":10976,"toc":11081},[10977,10981,10984,10988,10991,11005,11009,11041,11045,11072,11076],[32,10978,10980],{"id":10979},"what-is-least-privilege","What is Least Privilege?",[37,10982,10983],{},"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.",[560,10985,10987],{"id":10986},"why-does-least-privilege-matter","Why does least privilege matter?",[37,10989,10990],{},"Excessive permissions are one of the most common security weaknesses. When users have more access than they need:",[164,10992,10993,10996,10999,11002],{},[167,10994,10995],{},"A compromised account gives attackers a wider attack surface",[167,10997,10998],{},"Accidental changes to sensitive systems become more likely",[167,11000,11001],{},"Insider threats are harder to detect and contain",[167,11003,11004],{},"Audit findings for excessive access are common compliance gaps",[560,11006,11008],{"id":11007},"how-do-you-implement-least-privilege","How do you implement least privilege?",[164,11010,11011,11017,11023,11029,11035],{},[167,11012,11013,11016],{},[103,11014,11015],{},"Start with zero access"," — new accounts should have no permissions by default, with access granted based on documented role requirements",[167,11018,11019,11022],{},[103,11020,11021],{},"Use role-based access control (RBAC)"," — define roles with specific permission sets rather than assigning permissions individually",[167,11024,11025,11028],{},[103,11026,11027],{},"Conduct regular access reviews"," — quarterly reviews of user permissions help identify and remove access that is no longer needed",[167,11030,11031,11034],{},[103,11032,11033],{},"Remove access promptly"," — revoke permissions immediately when employees change roles or leave the organization",[167,11036,11037,11040],{},[103,11038,11039],{},"Apply to systems and applications too"," — service accounts, APIs, and automated processes should also follow least privilege",[560,11042,11044],{"id":11043},"how-do-compliance-frameworks-address-least-privilege","How do compliance frameworks address least privilege?",[164,11046,11047,11052,11057,11062,11067],{},[167,11048,11049,11051],{},[103,11050,381],{}," — CC6.1 through CC6.3 require logical access controls based on least privilege",[167,11053,11054,11056],{},[103,11055,43],{}," — A.5.15 (access control) and A.8.2 (privileged access rights) explicitly reference least privilege",[167,11058,11059,11061],{},[103,11060,5694],{}," — the minimum necessary standard (45 CFR 164.502(b)) is the healthcare equivalent of least privilege",[167,11063,11064,11066],{},[103,11065,5708],{}," — Requirement 7 restricts access to cardholder data on a need-to-know basis",[167,11068,11069,11071],{},[103,11070,5717],{}," — PR.AC-4 addresses access permissions based on least privilege",[560,11073,11075],{"id":11074},"how-does-episki-help-with-least-privilege","How does episki help with least privilege?",[37,11077,11078,11079,242],{},"episki tracks access control policies, schedules periodic access reviews, and documents evidence of least privilege enforcement for auditors. Learn more on our ",[40,11080,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":11082},[11083],{"id":10979,"depth":428,"text":10980,"children":11084},[11085,11086,11087,11088],{"id":10986,"depth":963,"text":10987},{"id":11007,"depth":963,"text":11008},{"id":11043,"depth":963,"text":11044},{"id":11074,"depth":963,"text":11075},{},"\u002Fglossary\u002Fleast-privilege",[6069,6070,515,6071,6072,6073],[6080,10424,6076],{"title":11094,"description":11095},"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":11100,"title":11101,"body":11102,"description":427,"extension":460,"lastUpdated":979,"meta":11615,"navigation":497,"path":11616,"relatedFrameworks":11617,"relatedTerms":11618,"seo":11619,"slug":11622,"stem":11623,"term":11107,"__hash__":11624},"glossary\u002F8.glossary\u002Flog-management.md","Log Management",{"type":29,"value":11103,"toc":11603},[11104,11108,11111,11115,11118,11154,11158,11161,11165,11168,11206,11210,11213,11245,11249,11252,11278,11282,11285,11311,11315,11318,11383,11386,11390,11393,11397,11411,11415,11429,11433,11447,11451,11465,11469,11492,11496,11499,11543,11547,11573,11577,11594,11598],[32,11105,11107],{"id":11106},"what-is-log-management","What is Log Management?",[37,11109,11110],{},"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.",[560,11112,11114],{"id":11113},"what-gets-logged-in-a-log-management-program","What gets logged in a log management program?",[37,11116,11117],{},"Effective log management covers:",[164,11119,11120,11126,11132,11137,11143,11149],{},[167,11121,11122,11125],{},[103,11123,11124],{},"Authentication events"," — successful and failed login attempts, password changes, MFA challenges",[167,11127,11128,11131],{},[103,11129,11130],{},"Authorization events"," — access grants, denials, privilege escalations",[167,11133,11134,11136],{},[103,11135,6265],{}," — configuration changes, service starts and stops, errors",[167,11138,11139,11142],{},[103,11140,11141],{},"Network events"," — firewall decisions, DNS queries, connection attempts",[167,11144,11145,11148],{},[103,11146,11147],{},"Application events"," — user actions, API calls, data access patterns",[167,11150,11151,11153],{},[103,11152,6289],{}," — malware detections, vulnerability scan results, intrusion alerts",[560,11155,11157],{"id":11156},"what-is-log-management-architecture","What is log management architecture?",[37,11159,11160],{},"A mature log management program combines multiple components into a pipeline that moves raw event data from source to searchable, retained storage.",[10528,11162,11164],{"id":11163},"log-sources","Log sources",[37,11166,11167],{},"Logs originate from every layer of the technology stack:",[164,11169,11170,11176,11182,11188,11194,11200],{},[167,11171,11172,11175],{},[103,11173,11174],{},"Servers and operating systems"," — Linux auth logs, Windows Event Log, macOS Unified Log",[167,11177,11178,11181],{},[103,11179,11180],{},"Cloud platforms"," — AWS CloudTrail, Azure Activity Log, GCP Admin Activity audit logs",[167,11183,11184,11187],{},[103,11185,11186],{},"SaaS applications"," — Microsoft 365 Unified Audit Log, Google Workspace audit logs, Salesforce event monitoring",[167,11189,11190,11193],{},[103,11191,11192],{},"Endpoints"," — EDR telemetry, local application logs, mobile device management events",[167,11195,11196,11199],{},[103,11197,11198],{},"Network devices"," — firewalls, routers, switches, load balancers, VPN concentrators",[167,11201,11202,11205],{},[103,11203,11204],{},"Security tools"," — IDS\u002FIPS alerts, vulnerability scanners, DLP engines, email gateways",[10528,11207,11209],{"id":11208},"collection-methods","Collection methods",[37,11211,11212],{},"Getting logs from source to a central platform requires reliable collection mechanisms:",[164,11214,11215,11221,11227,11233,11239],{},[167,11216,11217,11220],{},[103,11218,11219],{},"Agents"," — lightweight forwarders installed on hosts (Fluentd, Filebeat, NXLog, Splunk Universal Forwarder) that ship logs in near real time",[167,11222,11223,11226],{},[103,11224,11225],{},"Syslog"," — the legacy standard (RFC 5424) still widely used by network devices; syslog-ng and rsyslog add filtering and reliable delivery",[167,11228,11229,11232],{},[103,11230,11231],{},"API polling"," — scheduled calls to SaaS and cloud provider APIs to pull audit logs (e.g., Microsoft Graph API, AWS CloudTrail Lake queries)",[167,11234,11235,11238],{},[103,11236,11237],{},"Cloud-native streams"," — managed pipelines like AWS Kinesis Data Firehose, Azure Event Hubs, or GCP Pub\u002FSub that deliver logs without managing agents",[167,11240,11241,11244],{},[103,11242,11243],{},"Webhooks"," — event-driven push from SaaS applications that support real-time notification (Slack audit API, GitHub audit log streaming)",[10528,11246,11248],{"id":11247},"centralization","Centralization",[37,11250,11251],{},"Logs are only useful when they are searchable in one place:",[164,11253,11254,11260,11266,11272],{},[167,11255,11256,11259],{},[103,11257,11258],{},"Commercial SIEM"," — Splunk Enterprise Security, Microsoft Sentinel, IBM QRadar provide correlation, detection rules, and case management",[167,11261,11262,11265],{},[103,11263,11264],{},"Cloud-native logging"," — AWS CloudWatch Logs, Azure Monitor, Google Cloud Logging offer tight integration with their respective platforms",[167,11267,11268,11271],{},[103,11269,11270],{},"Open-source stacks"," — the Elastic Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, and OpenSearch provide cost-effective alternatives with community-driven detection content",[167,11273,11274,11277],{},[103,11275,11276],{},"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",[10528,11279,11281],{"id":11280},"storage-tiers","Storage tiers",[37,11283,11284],{},"Log storage strategies balance search speed against cost and compliance retention:",[164,11286,11287,11293,11299,11305],{},[167,11288,11289,11292],{},[103,11290,11291],{},"Hot storage"," — fully indexed, real-time searchable data for active investigations and alerting (typically 30–90 days)",[167,11294,11295,11298],{},[103,11296,11297],{},"Warm storage"," — recent history available for on-demand search with slightly slower query times (typically 90 days to 12 months)",[167,11300,11301,11304],{},[103,11302,11303],{},"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)",[167,11306,11307,11310],{},[103,11308,11309],{},"Immutable storage"," — write-once, read-many storage that prevents tampering, critical for audit trail integrity and legal hold requirements",[560,11312,11314],{"id":11313},"what-are-the-log-retention-requirements","What are the log retention requirements?",[37,11316,11317],{},"Different compliance frameworks set varying expectations for how long logs must be kept. The table below summarizes key requirements:",[1596,11319,11320,11332],{},[1599,11321,11322],{},[1602,11323,11324,11326,11329],{},[1605,11325,8897],{},[1605,11327,11328],{},"Minimum retention",[1605,11330,11331],{},"Key requirements",[1612,11333,11334,11344,11354,11363,11373],{},[1602,11335,11336,11338,11341],{},[1617,11337,5708],{},[1617,11339,11340],{},"12 months (3 months immediately available)",[1617,11342,11343],{},"Req 10.7 — retain audit trail history",[1602,11345,11346,11348,11351],{},[1617,11347,381],{},[1617,11349,11350],{},"Based on risk assessment",[1617,11352,11353],{},"CC7.2 — monitor system components",[1602,11355,11356,11358,11360],{},[1617,11357,43],{},[1617,11359,11350],{},[1617,11361,11362],{},"A.8.15 — log retention policy required",[1602,11364,11365,11367,11370],{},[1617,11366,5694],{},[1617,11368,11369],{},"6 years for policies; log retention not specified but implied",[1617,11371,11372],{},"Audit controls for ePHI access",[1602,11374,11375,11377,11380],{},[1617,11376,5717],{},[1617,11378,11379],{},"Based on organizational needs",[1617,11381,11382],{},"DE.CM — continuous monitoring",[37,11384,11385],{},"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.",[560,11387,11389],{"id":11388},"what-should-you-alert-on-in-log-management","What should you alert on in log management?",[37,11391,11392],{},"Collecting logs without monitoring them defeats the purpose. Effective alerting focuses on high-fidelity signals across several categories:",[10528,11394,11396],{"id":11395},"authentication-anomalies","Authentication anomalies",[164,11398,11399,11402,11405,11408],{},[167,11400,11401],{},"Brute-force attempts — multiple failed logins against the same account within a short window",[167,11403,11404],{},"Impossible travel — successful logins from geographically distant locations within an implausible time frame",[167,11406,11407],{},"New device or location — first-time access from an unrecognized device, IP range, or country",[167,11409,11410],{},"Credential stuffing patterns — failed logins across many accounts from a small set of source IPs",[10528,11412,11414],{"id":11413},"privilege-escalation","Privilege escalation",[164,11416,11417,11420,11423,11426],{},[167,11418,11419],{},"Sudo or run-as usage outside of expected maintenance windows",[167,11421,11422],{},"Admin role assignments or membership changes in identity providers (Azure AD, Okta, Google Workspace)",[167,11424,11425],{},"Permission changes on sensitive resources — S3 bucket policies, database grants, file share ACLs",[167,11427,11428],{},"Service account creation or key generation",[10528,11430,11432],{"id":11431},"data-exfiltration-signals","Data exfiltration signals",[164,11434,11435,11438,11441,11444],{},[167,11436,11437],{},"Unusual download volumes — user downloading significantly more data than their baseline",[167,11439,11440],{},"Access outside business hours — especially to sensitive repositories, databases, or file shares",[167,11442,11443],{},"Mass file access — sequential reads across large numbers of records in short succession",[167,11445,11446],{},"Outbound data transfers to uncommon destinations — cloud storage services, personal email, file-sharing sites",[10528,11448,11450],{"id":11449},"configuration-changes","Configuration changes",[164,11452,11453,11456,11459,11462],{},[167,11454,11455],{},"Firewall rule modifications — new allow rules, disabled security groups, removed deny entries",[167,11457,11458],{},"Security group changes in cloud environments — opening ports, widening IP ranges",[167,11460,11461],{},"IAM policy changes — new inline policies, permission boundary modifications, role trust policy updates",[167,11463,11464],{},"DNS changes — new records, zone transfers, nameserver modifications",[10528,11466,11468],{"id":11467},"compliance-specific-events","Compliance-specific events",[164,11470,11471,11479,11486,11489],{},[167,11472,11473,11474,11478],{},"Access to ",[40,11475,11477],{"href":11476},"\u002Fglossary\u002Fpci-dss","cardholder data"," environments — any read, write, or copy operation",[167,11480,11481,11482,11485],{},"PHI access in ",[40,11483,5694],{"href":11484},"\u002Fglossary\u002Fhipaa","-regulated systems — views, exports, or modifications of protected health information",[167,11487,11488],{},"Encryption key operations — key creation, rotation, deletion, or export",[167,11490,11491],{},"Audit log access or modification attempts — anyone trying to read, delete, or alter the logs themselves",[560,11493,11495],{"id":11494},"what-are-common-log-management-mistakes","What are common log management mistakes?",[37,11497,11498],{},"Even organizations that invest in logging often fall into patterns that undermine the value of their program:",[1446,11500,11501,11507,11513,11519,11525,11531,11537],{},[167,11502,11503,11506],{},[103,11504,11505],{},"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.",[167,11508,11509,11512],{},[103,11510,11511],{},"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.",[167,11514,11515,11518],{},[103,11516,11517],{},"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.",[167,11520,11521,11524],{},[103,11522,11523],{},"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.",[167,11526,11527,11530],{},[103,11528,11529],{},"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.",[167,11532,11533,11536],{},[103,11534,11535],{},"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.",[167,11538,11539,11542],{},[103,11540,11541],{},"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.",[560,11544,11546],{"id":11545},"how-do-compliance-frameworks-address-log-management","How do compliance frameworks address log management?",[164,11548,11549,11554,11559,11564,11568],{},[167,11550,11551,11553],{},[103,11552,381],{}," — CC7.1 through CC7.4 require monitoring, detection, and response capabilities that depend on logging",[167,11555,11556,11558],{},[103,11557,43],{}," — A.8.15 (logging) and A.8.16 (monitoring activities) address log collection and analysis",[167,11560,11561,11563],{},[103,11562,5694],{}," — the Security Rule requires audit controls to record and examine activity in systems containing ePHI",[167,11565,11566,6342],{},[103,11567,5708],{},[167,11569,11570,11572],{},[103,11571,5717],{}," — DE.CM (continuous monitoring) and DE.AE (anomaly detection) rely on log data",[560,11574,11576],{"id":11575},"what-are-best-practices-for-log-management","What are best practices for log management?",[164,11578,11579,11582,11585,11588,11591],{},[167,11580,11581],{},"Centralize logs in a SIEM or log aggregation platform for correlation and analysis",[167,11583,11584],{},"Set retention periods that meet both compliance requirements and operational needs (typically 90 days to one year)",[167,11586,11587],{},"Protect log integrity with immutable storage or tamper-evident mechanisms",[167,11589,11590],{},"Establish alerting rules for high-risk events like failed authentication spikes or unauthorized access attempts",[167,11592,11593],{},"Regularly review and tune logging to ensure coverage without excessive noise",[560,11595,11597],{"id":11596},"how-does-episki-help-with-log-management","How does episki help with log management?",[37,11599,11600,11601,242],{},"episki documents log management policies, tracks retention schedules, and links logging controls to evidence for audit readiness. Learn more on our ",[40,11602,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":11604},[11605],{"id":11106,"depth":428,"text":11107,"children":11606},[11607,11608,11609,11610,11611,11612,11613,11614],{"id":11113,"depth":963,"text":11114},{"id":11156,"depth":963,"text":11157},{"id":11313,"depth":963,"text":11314},{"id":11388,"depth":963,"text":11389},{"id":11494,"depth":963,"text":11495},{"id":11545,"depth":963,"text":11546},{"id":11575,"depth":963,"text":11576},{"id":11596,"depth":963,"text":11597},{},"\u002Fglossary\u002Flog-management",[6069,6070,515,6071,6072,6073],[2697,2386,4226],{"title":11620,"description":11621},"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":11626,"title":11627,"body":11628,"description":427,"extension":460,"lastUpdated":979,"meta":11746,"navigation":497,"path":11747,"relatedFrameworks":11748,"relatedTerms":11749,"seo":11750,"slug":11753,"stem":11754,"term":11633,"__hash__":11755},"glossary\u002F8.glossary\u002Fmalware.md","Malware",{"type":29,"value":11629,"toc":11738},[11630,11634,11637,11641,11679,11683,11705,11709,11729,11733],[32,11631,11633],{"id":11632},"what-is-malware","What is Malware?",[37,11635,11636],{},"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.",[560,11638,11640],{"id":11639},"what-are-the-types-of-malware","What are the types of malware?",[164,11642,11643,11649,11655,11661,11667,11673],{},[167,11644,11645,11648],{},[103,11646,11647],{},"Viruses"," — attach to legitimate programs and spread when the infected program runs",[167,11650,11651,11654],{},[103,11652,11653],{},"Ransomware"," — encrypts data and demands payment for the decryption key",[167,11656,11657,11660],{},[103,11658,11659],{},"Trojans"," — disguise themselves as legitimate software to trick users into installation",[167,11662,11663,11666],{},[103,11664,11665],{},"Spyware"," — silently collects information about user activity and sends it to an attacker",[167,11668,11669,11672],{},[103,11670,11671],{},"Worms"," — self-replicate across networks without requiring user interaction",[167,11674,11675,11678],{},[103,11676,11677],{},"Rootkits"," — hide deep within the operating system to maintain persistent, undetected access",[560,11680,11682],{"id":11681},"how-do-compliance-frameworks-address-malware-protection","How do compliance frameworks address malware protection?",[164,11684,11685,11690,11695,11700],{},[167,11686,11687,11689],{},[103,11688,381],{}," — CC6.8 requires controls to prevent and detect malicious software",[167,11691,11692,11694],{},[103,11693,43],{}," — A.8.7 addresses protection against malware",[167,11696,11697,11699],{},[103,11698,5708],{}," — Requirement 5 mandates deploying anti-malware solutions on all commonly affected systems",[167,11701,11702,11704],{},[103,11703,5717],{}," — DE.CM-4 specifically addresses malicious code detection",[560,11706,11708],{"id":11707},"what-are-common-malware-defense-strategies","What are common malware defense strategies?",[164,11710,11711,11714,11717,11720,11723,11726],{},[167,11712,11713],{},"Deploy endpoint detection and response (EDR) tools across all endpoints",[167,11715,11716],{},"Keep operating systems and applications patched and up to date",[167,11718,11719],{},"Implement email filtering to block phishing and malicious attachments",[167,11721,11722],{},"Restrict administrative privileges to reduce malware installation risk",[167,11724,11725],{},"Train employees to recognize social engineering and phishing attempts",[167,11727,11728],{},"Maintain tested backup and recovery procedures to mitigate ransomware impact",[560,11730,11732],{"id":11731},"how-does-episki-help-with-malware","How does episki help with malware?",[37,11734,11735,11736,242],{},"episki tracks anti-malware controls, monitors policy compliance, and documents endpoint protection evidence for auditors. Learn more on our ",[40,11737,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":11739},[11740],{"id":11632,"depth":428,"text":11633,"children":11741},[11742,11743,11744,11745],{"id":11639,"depth":963,"text":11640},{"id":11681,"depth":963,"text":11682},{"id":11707,"depth":963,"text":11708},{"id":11731,"depth":963,"text":11732},{},"\u002Fglossary\u002Fmalware",[6069,6070,515,6072,6073],[4226,8888,2386],{"title":11751,"description":11752},"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":11757,"title":8255,"body":11758,"description":427,"extension":460,"lastUpdated":979,"meta":11867,"navigation":497,"path":11868,"relatedFrameworks":11869,"relatedTerms":11870,"seo":11871,"slug":2387,"stem":11874,"term":11763,"__hash__":11875},"glossary\u002F8.glossary\u002Fmonitoring.md",{"type":29,"value":11759,"toc":11859},[11760,11764,11767,11771,11803,11807,11829,11833,11850,11854],[32,11761,11763],{"id":11762},"what-is-monitoring","What is Monitoring?",[37,11765,11766],{},"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.",[560,11768,11770],{"id":11769},"what-are-the-types-of-monitoring","What are the types of monitoring?",[164,11772,11773,11779,11785,11791,11797],{},[167,11774,11775,11778],{},[103,11776,11777],{},"Security monitoring"," — detecting threats, intrusions, and malicious activity through SIEM tools, IDS\u002FIPS, and endpoint detection",[167,11780,11781,11784],{},[103,11782,11783],{},"Compliance monitoring"," — tracking whether controls are operating effectively and whether the organization remains aligned with framework requirements",[167,11786,11787,11790],{},[103,11788,11789],{},"Infrastructure monitoring"," — observing system health, performance, and availability across servers, networks, and cloud services",[167,11792,11793,11796],{},[103,11794,11795],{},"User activity monitoring"," — tracking user behavior to detect insider threats, policy violations, or compromised accounts",[167,11798,11799,11802],{},[103,11800,11801],{},"Vulnerability monitoring"," — continuously scanning for known vulnerabilities across the technology stack",[560,11804,11806],{"id":11805},"how-do-compliance-frameworks-address-monitoring","How do compliance frameworks address monitoring?",[164,11808,11809,11814,11819,11824],{},[167,11810,11811,11813],{},[103,11812,381],{}," — CC7.1 requires the use of detection and monitoring activities to identify anomalies",[167,11815,11816,11818],{},[103,11817,43],{}," — A.8.16 covers monitoring activities across networks and systems",[167,11820,11821,11823],{},[103,11822,5708],{}," — Requirement 10 and 11 address logging, monitoring, and regular security testing",[167,11825,11826,11828],{},[103,11827,5717],{}," — the Detect function (DE.CM, DE.AE) is entirely focused on continuous monitoring and anomaly detection",[560,11830,11832],{"id":11831},"what-are-best-practices-for-monitoring","What are best practices for monitoring?",[164,11834,11835,11838,11841,11844,11847],{},[167,11836,11837],{},"Define clear thresholds and alerting rules to minimize alert fatigue",[167,11839,11840],{},"Centralize monitoring data for correlation across systems",[167,11842,11843],{},"Establish escalation procedures so alerts lead to timely investigation",[167,11845,11846],{},"Review and tune monitoring rules regularly as the environment changes",[167,11848,11849],{},"Document monitoring coverage and gaps as part of risk assessments",[560,11851,11853],{"id":11852},"how-does-episki-help-with-monitoring","How does episki help with monitoring?",[37,11855,11856,11857,242],{},"episki tracks monitoring controls, documents coverage, and links monitoring evidence to framework requirements for continuous audit readiness. Learn more on our ",[40,11858,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":11860},[11861],{"id":11762,"depth":428,"text":11763,"children":11862},[11863,11864,11865,11866],{"id":11769,"depth":963,"text":11770},{"id":11805,"depth":963,"text":11806},{"id":11831,"depth":963,"text":11832},{"id":11852,"depth":963,"text":11853},{},"\u002Fglossary\u002Fmonitoring",[6069,6070,515,6072,6073],[2386,11622,4226],{"title":11872,"description":11873},"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.","8.glossary\u002Fmonitoring","QXZ4W_vuU7Y88VE8xwlReLlBVCa0cNFk0XPiqgd_4bc",{"id":11877,"title":11878,"body":11879,"description":427,"extension":460,"lastUpdated":979,"meta":11987,"navigation":497,"path":11988,"relatedFrameworks":11989,"relatedTerms":11990,"seo":11991,"slug":11994,"stem":11995,"term":11884,"__hash__":11996},"glossary\u002F8.glossary\u002Fmulti-factor-authentication.md","Multi Factor Authentication",{"type":29,"value":11880,"toc":11979},[11881,11885,11888,11892,11895,11915,11919,11922,11949,11953,11970,11974],[32,11882,11884],{"id":11883},"what-is-multi-factor-authentication","What is Multi-Factor Authentication?",[37,11886,11887],{},"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.",[560,11889,11891],{"id":11890},"what-are-the-authentication-factors-used-in-mfa","What are the authentication factors used in MFA?",[37,11893,11894],{},"MFA combines factors from different categories:",[164,11896,11897,11903,11909],{},[167,11898,11899,11902],{},[103,11900,11901],{},"Something you know"," — passwords, PINs, security questions",[167,11904,11905,11908],{},[103,11906,11907],{},"Something you have"," — mobile phones (SMS or authenticator apps), hardware tokens, smart cards",[167,11910,11911,11914],{},[103,11912,11913],{},"Something you are"," — biometrics such as fingerprints, facial recognition, or iris scans",[560,11916,11918],{"id":11917},"how-do-compliance-frameworks-address-mfa","How do compliance frameworks address MFA?",[37,11920,11921],{},"MFA is required or strongly recommended across all major frameworks:",[164,11923,11924,11929,11934,11939,11944],{},[167,11925,11926,11928],{},[103,11927,381],{}," — CC6.1 requires multi-factor authentication for access to sensitive systems",[167,11930,11931,11933],{},[103,11932,43],{}," — A.8.5 addresses secure authentication including multi-factor methods",[167,11935,11936,11938],{},[103,11937,5694],{}," — while not explicitly mandating MFA, the Security Rule requires access controls that effectively necessitate it for ePHI systems",[167,11940,11941,11943],{},[103,11942,5708],{}," — Requirement 8.3 mandates MFA for all remote access to the cardholder data environment",[167,11945,11946,11948],{},[103,11947,5717],{}," — PR.AC-7 recommends multi-factor authentication as part of identity management",[560,11950,11952],{"id":11951},"what-are-implementation-best-practices","What are implementation best practices?",[164,11954,11955,11958,11961,11964,11967],{},[167,11956,11957],{},"Require MFA for all user accounts, not just administrators",[167,11959,11960],{},"Prefer authenticator apps or hardware tokens over SMS-based codes (which are vulnerable to SIM swapping)",[167,11962,11963],{},"Implement MFA on VPN, cloud console, email, and any system containing sensitive data",[167,11965,11966],{},"Provide backup recovery methods (recovery codes, backup devices) to prevent lockouts",[167,11968,11969],{},"Monitor and alert on MFA bypass attempts or disabled MFA",[560,11971,11973],{"id":11972},"how-does-episki-help-with-mfa","How does episki help with MFA?",[37,11975,11976,11977,242],{},"episki tracks MFA policies, monitors enforcement across systems, and documents MFA evidence for compliance audits. Learn more on our ",[40,11978,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":11980},[11981],{"id":11883,"depth":428,"text":11884,"children":11982},[11983,11984,11985,11986],{"id":11890,"depth":963,"text":11891},{"id":11917,"depth":963,"text":11918},{"id":11951,"depth":963,"text":11952},{"id":11972,"depth":963,"text":11973},{},"\u002Fglossary\u002Fmulti-factor-authentication",[6069,6070,515,6071,6072,6073],[6080,11096,6018],{"title":11992,"description":11993},"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":11998,"title":11999,"body":12000,"description":427,"extension":460,"lastUpdated":979,"meta":12121,"navigation":497,"path":12122,"relatedFrameworks":12123,"relatedTerms":12124,"seo":12125,"slug":8887,"stem":12128,"term":12005,"__hash__":12129},"glossary\u002F8.glossary\u002Fnetwork-security.md","Network Security",{"type":29,"value":12001,"toc":12113},[12002,12006,12009,12013,12051,12055,12077,12081,12104,12108],[32,12003,12005],{"id":12004},"what-is-network-security","What is Network Security?",[37,12007,12008],{},"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.",[560,12010,12012],{"id":12011},"what-are-the-core-components-of-network-security","What are the core components of network security?",[164,12014,12015,12021,12027,12033,12039,12045],{},[167,12016,12017,12020],{},[103,12018,12019],{},"Firewalls"," — filter traffic between trusted and untrusted networks based on security rules",[167,12022,12023,12026],{},[103,12024,12025],{},"Intrusion detection and prevention systems (IDS\u002FIPS)"," — monitor network traffic for suspicious activity and can automatically block threats",[167,12028,12029,12032],{},[103,12030,12031],{},"Network segmentation"," — divides the network into isolated zones to contain breaches and limit lateral movement",[167,12034,12035,12038],{},[103,12036,12037],{},"Virtual private networks (VPN)"," — encrypt traffic between remote users and the corporate network",[167,12040,12041,12044],{},[103,12042,12043],{},"Network access control (NAC)"," — enforces policies about which devices and users can connect to the network",[167,12046,12047,12050],{},[103,12048,12049],{},"DNS security"," — protects against DNS-based attacks like spoofing and cache poisoning",[560,12052,12054],{"id":12053},"how-do-compliance-frameworks-address-network-security","How do compliance frameworks address network security?",[164,12056,12057,12062,12067,12072],{},[167,12058,12059,12061],{},[103,12060,5708],{}," — Requirements 1 and 2 address firewall configuration and secure network architecture",[167,12063,12064,12066],{},[103,12065,43],{}," — A.8.20 (network security), A.8.21 (security of network services), and A.8.22 (segregation of networks)",[167,12068,12069,12071],{},[103,12070,381],{}," — CC6.6 requires security controls for network boundaries",[167,12073,12074,12076],{},[103,12075,5717],{}," — PR.AC and PR.PT cover network access control and protective technology",[560,12078,12080],{"id":12079},"what-are-best-practices-for-network-security","What are best practices for network security?",[164,12082,12083,12086,12089,12092,12095,12098],{},[167,12084,12085],{},"Implement defense in depth with multiple layers of network controls",[167,12087,12088],{},"Regularly scan for open ports and unnecessary services",[167,12090,12091],{},"Encrypt data in transit using TLS\u002FSSL",[167,12093,12094],{},"Monitor network traffic for anomalies and potential intrusions",[167,12096,12097],{},"Document network architecture and maintain up-to-date network diagrams",[167,12099,12100,12101,12103],{},"Conduct regular ",[40,12102,8865],{"href":8864}," to identify network vulnerabilities",[560,12105,12107],{"id":12106},"how-does-episki-help-with-network-security","How does episki help with network security?",[37,12109,12110,12111,242],{},"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 ",[40,12112,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":12114},[12115],{"id":12004,"depth":428,"text":12005,"children":12116},[12117,12118,12119,12120],{"id":12011,"depth":963,"text":12012},{"id":12053,"depth":963,"text":12054},{"id":12079,"depth":963,"text":12080},{"id":12106,"depth":963,"text":12107},{},"\u002Fglossary\u002Fnetwork-security",[6069,6070,515,6072,6073],[8892,6080,6018,8888],{"title":12126,"description":12127},"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":12131,"title":12132,"body":12133,"description":427,"extension":460,"lastUpdated":979,"meta":12207,"navigation":497,"path":12208,"relatedFrameworks":12209,"relatedTerms":12210,"seo":12211,"slug":12214,"stem":12215,"term":12138,"__hash__":12216},"glossary\u002F8.glossary\u002Fnist.md","Nist",{"type":29,"value":12134,"toc":12200},[12135,12139,12142,12146,12170,12174,12177,12191,12195],[32,12136,12138],{"id":12137},"what-is-nist","What is NIST?",[37,12140,12141],{},"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.",[560,12143,12145],{"id":12144},"what-are-the-key-nist-publications","What are the key NIST publications?",[164,12147,12148,12153,12158,12164],{},[167,12149,12150,12152],{},[103,12151,7513],{}," — 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.",[167,12154,12155,12157],{},[103,12156,7519],{}," — a comprehensive catalog of security and privacy controls for federal information systems. Often used as a reference by private organizations building security programs.",[167,12159,12160,12163],{},[103,12161,12162],{},"NIST SP 800-171"," — security requirements for protecting Controlled Unclassified Information (CUI) in non-federal systems, required for defense contractors.",[167,12165,12166,12169],{},[103,12167,12168],{},"NIST SP 800-37"," — the Risk Management Framework (RMF) that guides organizations through a structured process for managing security risk.",[560,12171,12173],{"id":12172},"why-does-nist-matter-for-compliance","Why does NIST matter for compliance?",[37,12175,12176],{},"While NIST frameworks are voluntary for most private organizations, they serve as the foundation or reference point for many compliance requirements:",[164,12178,12179,12182,12185,12188],{},[167,12180,12181],{},"Federal agencies are required to follow NIST guidelines",[167,12183,12184],{},"Defense contractors must comply with NIST SP 800-171 (enforced through CMMC)",[167,12186,12187],{},"Many ISO 27001 and SOC 2 control mappings reference NIST publications",[167,12189,12190],{},"Cyber insurance providers increasingly reference NIST CSF alignment",[560,12192,12194],{"id":12193},"how-does-episki-help-with-nist","How does episki help with NIST?",[37,12196,12197,12198,242],{},"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 ",[40,12199,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":12201},[12202],{"id":12137,"depth":428,"text":12138,"children":12203},[12204,12205,12206],{"id":12144,"depth":963,"text":12145},{"id":12172,"depth":963,"text":12173},{"id":12193,"depth":963,"text":12194},{},"\u002Fglossary\u002Fnist",[6073,515],[9009,7431,6697],{"title":12212,"description":12213},"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":12218,"title":12219,"body":12220,"description":427,"extension":460,"lastUpdated":979,"meta":12354,"navigation":497,"path":12355,"relatedFrameworks":12356,"relatedTerms":12357,"seo":12358,"slug":12361,"stem":12362,"term":12225,"__hash__":12363},"glossary\u002F8.glossary\u002Foffboarding.md","Offboarding",{"type":29,"value":12221,"toc":12345},[12222,12226,12229,12233,12236,12250,12254,12292,12296,12318,12322,12336,12340],[32,12223,12225],{"id":12224},"what-is-offboarding","What is Offboarding?",[37,12227,12228],{},"Offboarding is the formal process of revoking an employee's or contractor's access to systems, applications, and data when they leave an organization or change roles. A well-executed offboarding process is critical for preventing unauthorized access after separation and is a key control auditors review during compliance assessments.",[560,12230,12232],{"id":12231},"why-does-offboarding-matter","Why does offboarding matter?",[37,12234,12235],{},"Delayed or incomplete offboarding creates significant security risks:",[164,12237,12238,12241,12244,12247],{},[167,12239,12240],{},"Former employees retaining access to sensitive systems and data",[167,12242,12243],{},"Orphaned accounts that attackers can discover and exploit",[167,12245,12246],{},"Shared credentials that remain active after a team member departs",[167,12248,12249],{},"Compliance findings for inadequate access termination procedures",[560,12251,12253],{"id":12252},"what-are-the-key-offboarding-activities","What are the key offboarding activities?",[164,12255,12256,12262,12268,12274,12280,12286],{},[167,12257,12258,12261],{},[103,12259,12260],{},"Disable user accounts"," — immediately deactivate accounts in identity providers (SSO, Active Directory) to cascade access revocation",[167,12263,12264,12267],{},[103,12265,12266],{},"Revoke application access"," — remove access to SaaS applications, cloud consoles, code repositories, and internal tools",[167,12269,12270,12273],{},[103,12271,12272],{},"Recover assets"," — collect laptops, mobile devices, badges, hardware tokens, and other company property",[167,12275,12276,12279],{},[103,12277,12278],{},"Transfer ownership"," — reassign shared resources, documents, and project ownership",[167,12281,12282,12285],{},[103,12283,12284],{},"Remove from communication channels"," — remove from email distribution lists, Slack channels, and shared drives",[167,12287,12288,12291],{},[103,12289,12290],{},"Review privileged access"," — ensure any administrative or elevated access is fully revoked",[560,12293,12295],{"id":12294},"how-do-compliance-frameworks-address-offboarding","How do compliance frameworks address offboarding?",[164,12297,12298,12303,12308,12313],{},[167,12299,12300,12302],{},[103,12301,381],{}," — CC6.2 requires timely revocation of access when personnel leave",[167,12304,12305,12307],{},[103,12306,43],{}," — A.6.5 covers responsibilities after termination or change of employment",[167,12309,12310,12312],{},[103,12311,5694],{}," — the Security Rule requires procedures for terminating access to ePHI when employment ends",[167,12314,12315,12317],{},[103,12316,5708],{}," — Requirement 8.1.3 mandates immediate revocation of access for terminated users",[560,12319,12321],{"id":12320},"what-are-best-practices-for-offboarding","What are best practices for offboarding?",[164,12323,12324,12327,12330,12333],{},[167,12325,12326],{},"Automate offboarding checklists triggered by HR termination events",[167,12328,12329],{},"Set a target of same-day access revocation for all departures",[167,12331,12332],{},"Conduct post-offboarding audits to verify no residual access remains",[167,12334,12335],{},"Document the offboarding process and retain evidence for audit review",[560,12337,12339],{"id":12338},"how-does-episki-help-with-offboarding","How does episki help with offboarding?",[37,12341,12342,12343,242],{},"episki tracks offboarding policies, links them to access control evidence, and provides checklists to ensure complete access revocation. Learn more on our ",[40,12344,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":12346},[12347],{"id":12224,"depth":428,"text":12225,"children":12348},[12349,12350,12351,12352,12353],{"id":12231,"depth":963,"text":12232},{"id":12252,"depth":963,"text":12253},{"id":12294,"depth":963,"text":12295},{"id":12320,"depth":963,"text":12321},{"id":12338,"depth":963,"text":12339},{},"\u002Fglossary\u002Foffboarding",[6070,515,6071,6072],[6080,11096,10424],{"title":12359,"description":12360},"What is Offboarding? Definition & Compliance Guide","Offboarding is the formal process of revoking an employee's or contractor's access to systems and data when they leave an organization.","offboarding","8.glossary\u002Foffboarding","Rz5QFRP5_SeeZAbasnNVFWLvYnrzwxu8rDWO1Kpf4lI",{"id":12365,"title":12366,"body":12367,"description":427,"extension":460,"lastUpdated":979,"meta":12479,"navigation":497,"path":12480,"relatedFrameworks":12481,"relatedTerms":12482,"seo":12483,"slug":12486,"stem":12487,"term":12372,"__hash__":12488},"glossary\u002F8.glossary\u002Foperational-risk.md","Operational Risk",{"type":29,"value":12368,"toc":12471},[12369,12373,12376,12380,12405,12409,12426,12430,12462,12466],[32,12370,12372],{"id":12371},"what-is-operational-risk","What is Operational Risk?",[37,12374,12375],{},"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.",[560,12377,12379],{"id":12378},"what-are-the-sources-of-operational-risk","What are the sources of operational risk?",[164,12381,12382,12387,12393,12399],{},[167,12383,12384,12386],{},[103,12385,2172],{}," — human error, insufficient training, insider threats, key person dependencies",[167,12388,12389,12392],{},[103,12390,12391],{},"Processes"," — poorly designed workflows, lack of documentation, inadequate controls",[167,12394,12395,12398],{},[103,12396,12397],{},"Systems"," — hardware failures, software bugs, cybersecurity incidents, integration breakdowns",[167,12400,12401,12404],{},[103,12402,12403],{},"External events"," — natural disasters, supply chain disruptions, regulatory changes, third-party failures",[560,12406,12408],{"id":12407},"how-do-compliance-frameworks-address-operational-risk","How do compliance frameworks address operational risk?",[164,12410,12411,12416,12421],{},[167,12412,12413,12415],{},[103,12414,381],{}," — CC3.1 through CC3.4 address risk assessment and management, including operational risks",[167,12417,12418,12420],{},[103,12419,43],{}," — clauses 6.1 and 8.2 require organizations to identify and treat information security risks, many of which are operational",[167,12422,12423,12425],{},[103,12424,5717],{}," — the Identify function (ID.RA) covers risk assessment including operational risk factors",[560,12427,12429],{"id":12428},"how-do-you-manage-operational-risk","How do you manage operational risk?",[164,12431,12432,12439,12446,12456,12459],{},[167,12433,12434,12435,12438],{},"Maintain a ",[40,12436,5283],{"href":12437},"\u002Fglossary\u002Frisk-register"," that captures identified operational risks with likelihood and impact ratings",[167,12440,12441,12442],{},"Implement controls proportional to the risk level and document them in a ",[40,12443,12445],{"href":12444},"\u002Fglossary\u002Frisk-treatment-plan","risk treatment plan",[167,12447,12448,12449,414,12452,12455],{},"Establish ",[40,12450,12451],{"href":6693},"business continuity",[40,12453,12454],{"href":8345},"disaster recovery"," plans for high-impact scenarios",[167,12457,12458],{},"Conduct regular risk assessments to identify new or changing risks",[167,12460,12461],{},"Monitor key risk indicators (KRIs) to detect emerging operational issues",[560,12463,12465],{"id":12464},"how-does-episki-help-with-operational-risk","How does episki help with operational risk?",[37,12467,12468,12469,242],{},"episki provides risk registers, links risks to controls, and tracks risk treatment plans to help organizations manage operational risk systematically. Learn more on our ",[40,12470,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":12472},[12473],{"id":12371,"depth":428,"text":12372,"children":12474},[12475,12476,12477,12478],{"id":12378,"depth":963,"text":12379},{"id":12407,"depth":963,"text":12408},{"id":12428,"depth":963,"text":12429},{"id":12464,"depth":963,"text":12465},{},"\u002Fglossary\u002Foperational-risk",[6070,515,6073],[6697,6698,6702,6696],{"title":12484,"description":12485},"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":12490,"title":12491,"body":12492,"description":427,"extension":460,"lastUpdated":979,"meta":12765,"navigation":497,"path":12766,"relatedFrameworks":12767,"relatedTerms":12768,"seo":12769,"slug":7430,"stem":12772,"term":12497,"__hash__":12773},"glossary\u002F8.glossary\u002Fremediation.md","Remediation",{"type":29,"value":12493,"toc":12754},[12494,12498,12501,12505,12508,12571,12575,12578,12626,12630,12633,12670,12674,12677,12697,12701,12704,12721,12724,12728,12745,12749],[32,12495,12497],{"id":12496},"what-is-remediation","What is Remediation?",[37,12499,12500],{},"Remediation is the process of identifying, prioritizing, and resolving security weaknesses, compliance gaps, audit findings, or vulnerabilities in an organization's systems and processes. It is a fundamental component of any security program — identifying risks and gaps is only valuable if the organization takes action to address them.",[560,12502,12504],{"id":12503},"where-do-remediation-items-come-from","Where do remediation items come from?",[37,12506,12507],{},"Remediation needs arise from multiple sources:",[164,12509,12510,12523,12533,12539,12547,12553,12559,12565],{},[167,12511,12512,12514,12515,9079,12517,12519,12520,12522],{},[103,12513,2020],{}," — gaps identified during ",[40,12516,381],{"href":380},[40,12518,43],{"href":498},", or ",[40,12521,5708],{"href":5707}," audits",[167,12524,12525,12528,12529],{},[103,12526,12527],{},"Vulnerability scans"," — technical vulnerabilities discovered by automated scanning tools or ",[40,12530,12532],{"href":12531},"\u002Fglossary\u002Fasv","approved scanning vendors (ASVs)",[167,12534,12535,12538],{},[103,12536,12537],{},"Penetration tests"," — weaknesses identified through manual security testing",[167,12540,12541,12546],{},[103,12542,12543],{},[40,12544,12545],{"href":12437},"Risk assessments"," — risks that require new or improved controls",[167,12548,12549,12552],{},[103,12550,12551],{},"Incident investigations"," — root cause analysis revealing underlying security weaknesses",[167,12554,12555,12558],{},[103,12556,12557],{},"Compliance gap assessments"," — differences between current controls and framework requirements",[167,12560,12561,12564],{},[103,12562,12563],{},"Customer security questionnaires"," — gaps exposed through vendor assessment processes",[167,12566,12567,12570],{},[103,12568,12569],{},"Regulatory changes"," — new requirements that existing controls do not address",[560,12572,12574],{"id":12573},"what-is-the-remediation-process","What is the remediation process?",[37,12576,12577],{},"An effective remediation process follows a structured approach:",[1446,12579,12580,12586,12592,12597,12603,12609,12614,12620],{},[167,12581,12582,12585],{},[103,12583,12584],{},"Identification"," — document the gap, vulnerability, or finding with sufficient detail to understand the issue",[167,12587,12588,12591],{},[103,12589,12590],{},"Assessment"," — evaluate the severity, risk, and potential impact of the issue",[167,12593,12594,12596],{},[103,12595,7601],{}," — rank remediation items based on risk severity, exploitability, and business impact",[167,12598,12599,12602],{},[103,12600,12601],{},"Assignment"," — designate a responsible owner for each remediation item",[167,12604,12605,12608],{},[103,12606,12607],{},"Planning"," — define the specific actions needed, required resources, and target completion date",[167,12610,12611,12613],{},[103,12612,7021],{}," — execute the remediation plan",[167,12615,12616,12619],{},[103,12617,12618],{},"Verification"," — confirm that the remediation effectively addresses the issue (through retesting, review, or evidence collection)",[167,12621,12622,12625],{},[103,12623,12624],{},"Documentation"," — record the remediation actions taken and their results",[560,12627,12629],{"id":12628},"how-do-you-prioritize-remediation-items","How do you prioritize remediation items?",[37,12631,12632],{},"Not all remediation items carry equal urgency. Common prioritization factors include:",[164,12634,12635,12641,12647,12653,12659,12665],{},[167,12636,12637,12640],{},[103,12638,12639],{},"Severity"," — how significant is the risk or vulnerability (e.g., CVSS score for technical vulnerabilities)",[167,12642,12643,12646],{},[103,12644,12645],{},"Exploitability"," — how easily could the weakness be exploited",[167,12648,12649,12652],{},[103,12650,12651],{},"Business impact"," — what would happen if the weakness were exploited",[167,12654,12655,12658],{},[103,12656,12657],{},"Compliance deadline"," — are there regulatory or contractual deadlines driving urgency",[167,12660,12661,12664],{},[103,12662,12663],{},"Effort required"," — how much work is needed to remediate",[167,12666,12667,12669],{},[103,12668,8210],{}," — does remediation depend on other work being completed first",[560,12671,12673],{"id":12672},"how-do-you-track-remediation","How do you track remediation?",[37,12675,12676],{},"Effective tracking ensures accountability and progress:",[164,12678,12679,12685,12688,12691,12694],{},[167,12680,12681,12682,12684],{},"Maintain a centralized remediation tracker (often integrated with the ",[40,12683,5283],{"href":12437}," or GRC platform)",[167,12686,12687],{},"Set clear deadlines and milestone dates",[167,12689,12690],{},"Send regular reminders to owners",[167,12692,12693],{},"Escalate overdue items to management",[167,12695,12696],{},"Report on remediation metrics (open items, aging, completion rates)",[560,12698,12700],{"id":12699},"how-does-remediation-work-in-audit-contexts","How does remediation work in audit contexts?",[37,12702,12703],{},"During compliance audits, auditors expect to see:",[164,12705,12706,12709,12712,12715,12718],{},[167,12707,12708],{},"A defined process for managing remediation items",[167,12710,12711],{},"Evidence of timely resolution",[167,12713,12714],{},"Follow-up verification that fixes are effective",[167,12716,12717],{},"Escalation procedures for items that miss deadlines",[167,12719,12720],{},"Management oversight of the remediation program",[37,12722,12723],{},"Auditors view an organization's ability to remediate findings as an indicator of program maturity. A long list of aging, unresolved findings suggests the compliance program is not being actively managed.",[560,12725,12727],{"id":12726},"what-are-common-challenges-with-remediation","What are common challenges with remediation?",[164,12729,12730,12733,12736,12739,12742],{},[167,12731,12732],{},"Competing priorities between security remediation and business initiatives",[167,12734,12735],{},"Insufficient resources to address all findings in a timely manner",[167,12737,12738],{},"Lack of clear ownership for remediation items",[167,12740,12741],{},"Remediation that addresses symptoms rather than root causes",[167,12743,12744],{},"No verification step to confirm effectiveness",[560,12746,12748],{"id":12747},"how-does-episki-help-with-remediation","How does episki help with remediation?",[37,12750,12751,12752,242],{},"episki provides remediation workflows that track findings from identification through verification. The platform assigns owners, sets deadlines, sends reminders, and reports on progress. Auditors can see the full remediation history for any finding. Learn more on our ",[40,12753,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":12755},[12756],{"id":12496,"depth":428,"text":12497,"children":12757},[12758,12759,12760,12761,12762,12763,12764],{"id":12503,"depth":963,"text":12504},{"id":12573,"depth":963,"text":12574},{"id":12628,"depth":963,"text":12629},{"id":12672,"depth":963,"text":12673},{"id":12699,"depth":963,"text":12700},{"id":12726,"depth":963,"text":12727},{"id":12747,"depth":963,"text":12748},{},"\u002Fglossary\u002Fremediation",[6070,515,6072],[6697,6698,2698,2386,8888],{"title":12770,"description":12771},"Remediation in Compliance: Definition, Process & Best Practices","Compliance remediation is the process of fixing security gaps and audit findings. Learn how to prioritize, track, and close remediation items efficiently.","8.glossary\u002Fremediation","gUhGasusB5qoXZyMJcWGEC3m1KU4Hcwyqjc-ZpOaaho",{"id":12775,"title":12776,"body":12777,"description":427,"extension":460,"lastUpdated":979,"meta":13376,"navigation":497,"path":12437,"relatedFrameworks":13377,"relatedTerms":13378,"seo":13380,"slug":6697,"stem":13383,"term":12782,"__hash__":13384},"glossary\u002F8.glossary\u002Frisk-register.md","Risk Register",{"type":29,"value":12778,"toc":13361},[12779,12783,12786,12790,12793,12867,12871,12874,12924,12928,12931,12963,12967,12970,12976,12982,12988,12995,12999,13002,13089,13092,13096,13102,13128,13131,13135,13138,13173,13177,13180,13282,13285,13289,13292,13322,13326,13329,13349,13352,13356],[32,12780,12782],{"id":12781},"what-is-a-risk-register","What is a Risk Register?",[37,12784,12785],{},"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.",[560,12787,12789],{"id":12788},"what-does-a-risk-register-contain","What does a risk register contain?",[37,12791,12792],{},"A well-structured risk register typically includes the following fields for each risk:",[164,12794,12795,12801,12807,12813,12819,12825,12831,12837,12843,12849,12855,12861],{},[167,12796,12797,12800],{},[103,12798,12799],{},"Risk ID"," — a unique identifier for tracking",[167,12802,12803,12806],{},[103,12804,12805],{},"Risk description"," — a clear statement of the risk, typically describing the threat, vulnerability, and potential impact",[167,12808,12809,12812],{},[103,12810,12811],{},"Risk category"," — classification such as operational, technical, compliance, strategic, or third-party",[167,12814,12815,12818],{},[103,12816,12817],{},"Likelihood"," — the probability of the risk materializing (often rated on a scale such as 1-5 or low\u002Fmedium\u002Fhigh)",[167,12820,12821,12824],{},[103,12822,12823],{},"Impact"," — the potential consequence if the risk materializes (rated similarly)",[167,12826,12827,12830],{},[103,12828,12829],{},"Risk score"," — calculated from likelihood and impact (e.g., likelihood x impact)",[167,12832,12833,12836],{},[103,12834,12835],{},"Risk owner"," — the person accountable for managing the risk",[167,12838,12839,12842],{},[103,12840,12841],{},"Treatment option"," — mitigate, accept, transfer, or avoid",[167,12844,12845,12848],{},[103,12846,12847],{},"Controls"," — the specific controls implemented to address the risk",[167,12850,12851,12854],{},[103,12852,12853],{},"Residual risk"," — the remaining risk level after treatment is applied",[167,12856,12857,12860],{},[103,12858,12859],{},"Status"," — current state (open, in treatment, accepted, closed)",[167,12862,12863,12866],{},[103,12864,12865],{},"Review date"," — when the risk was last reviewed or when the next review is due",[560,12868,12870],{"id":12869},"how-do-you-build-a-risk-register","How do you build a risk register?",[37,12872,12873],{},"Creating a risk register follows a systematic process:",[1446,12875,12876,12882,12888,12894,12900,12906,12912,12918],{},[167,12877,12878,12881],{},[103,12879,12880],{},"Identify risks"," — gather risks through workshops, interviews, threat modeling, vulnerability assessments, incident reviews, and industry threat intelligence",[167,12883,12884,12887],{},[103,12885,12886],{},"Assess each risk"," — evaluate the likelihood and impact of each risk to determine its severity",[167,12889,12890,12893],{},[103,12891,12892],{},"Prioritize"," — rank risks by their risk score to focus attention and resources on the most significant threats",[167,12895,12896,12899],{},[103,12897,12898],{},"Assign ownership"," — designate a responsible owner for each risk",[167,12901,12902,12905],{},[103,12903,12904],{},"Determine treatment"," — decide how each risk will be handled",[167,12907,12908,12911],{},[103,12909,12910],{},"Document controls"," — record the specific controls that address each risk",[167,12913,12914,12917],{},[103,12915,12916],{},"Calculate residual risk"," — assess the remaining risk after controls are applied",[167,12919,12920,12923],{},[103,12921,12922],{},"Review and approve"," — have management review and approve the register",[560,12925,12927],{"id":12926},"how-do-you-maintain-the-risk-register","How do you maintain the risk register?",[37,12929,12930],{},"A risk register is only valuable if it is kept current. Regular maintenance includes:",[164,12932,12933,12939,12945,12951,12957],{},[167,12934,12935,12938],{},[103,12936,12937],{},"Periodic reviews"," — review the full register at least quarterly, with management review at least annually",[167,12940,12941,12944],{},[103,12942,12943],{},"Triggered updates"," — update the register when significant changes occur (new systems, new services, organizational changes, incidents)",[167,12946,12947,12950],{},[103,12948,12949],{},"New risk identification"," — continuously identify and add new risks as the threat landscape evolves",[167,12952,12953,12956],{},[103,12954,12955],{},"Treatment progress tracking"," — monitor and update the status of risk treatment activities",[167,12958,12959,12962],{},[103,12960,12961],{},"Residual risk reassessment"," — re-evaluate residual risk as controls are implemented or change",[560,12964,12966],{"id":12965},"what-are-common-risk-scoring-methodologies","What are common risk scoring methodologies?",[37,12968,12969],{},"How you score risks determines how actionable the register is. The most common approaches:",[37,12971,12972,12975],{},[103,12973,12974],{},"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,12977,12978,12981],{},[103,12979,12980],{},"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,12983,12984,12987],{},[103,12985,12986],{},"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,12989,12990,12991,12994],{},"Most compliance programs start with a 5×5 matrix, then introduce quantitative methods for top-tier risks. Whichever scale you choose, ",[103,12992,12993],{},"document the definitions"," — what does \"likelihood 4\" actually mean in your organization? Without clear definitions, different raters produce wildly different scores.",[560,12996,12998],{"id":12997},"how-do-compliance-frameworks-address-risk-register","How do compliance frameworks address risk register?",[37,13000,13001],{},"Different frameworks require or recommend risk registers, often with specific expectations:",[1596,13003,13004,13015],{},[1599,13005,13006],{},[1602,13007,13008,13010,13012],{},[1605,13009,8897],{},[1605,13011,5841],{},[1605,13013,13014],{},"Specific reference",[1612,13016,13017,13029,13041,13053,13065,13077],{},[1602,13018,13019,13023,13026],{},[1617,13020,13021],{},[103,13022,43],{},[1617,13024,13025],{},"Documented risk assessment process with register as artifact",[1617,13027,13028],{},"Clause 6.1.2 and 8.2",[1602,13030,13031,13035,13038],{},[1617,13032,13033],{},[103,13034,381],{},[1617,13036,13037],{},"Risk identification, assessment, and response",[1617,13039,13040],{},"CC3.1–CC3.4",[1602,13042,13043,13047,13050],{},[1617,13044,13045],{},[103,13046,5717],{},[1617,13048,13049],{},"Risk assessment and risk management strategy",[1617,13051,13052],{},"ID.RA and GV.RM (new in 2.0)",[1602,13054,13055,13059,13062],{},[1617,13056,13057],{},[103,13058,5694],{},[1617,13060,13061],{},"Risk analysis for ePHI",[1617,13063,13064],{},"§164.308(a)(1)(ii)(A)",[1602,13066,13067,13071,13074],{},[1617,13068,13069],{},[103,13070,5708],{},[1617,13072,13073],{},"Targeted risk analyses for specific requirements",[1617,13075,13076],{},"PCI DSS v4.0 Req 12.3.1",[1602,13078,13079,13083,13086],{},[1617,13080,13081],{},[103,13082,10708],{},[1617,13084,13085],{},"Risk management practices",[1617,13087,13088],{},"RA.L2-3.11.1 through 3.11.3",[37,13090,13091],{},"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.",[560,13093,13095],{"id":13094},"what-are-the-risk-treatment-options","What are the risk treatment options?",[37,13097,13098,13099,13101],{},"For each risk, pick one of four treatment strategies (often documented in a parallel ",[40,13100,12445],{"href":12444},"):",[164,13103,13104,13110,13116,13122],{},[167,13105,13106,13109],{},[103,13107,13108],{},"Mitigate"," — implement controls to reduce likelihood or impact. Most common choice. Example: deploy MFA to reduce account takeover likelihood.",[167,13111,13112,13115],{},[103,13113,13114],{},"Accept"," — acknowledge the risk as within tolerance and proceed. Requires documented rationale and, for significant risks, executive sign-off.",[167,13117,13118,13121],{},[103,13119,13120],{},"Transfer"," — shift the risk to a third party via insurance, contract, or outsourcing. Cyber insurance is the canonical example.",[167,13123,13124,13127],{},[103,13125,13126],{},"Avoid"," — eliminate the activity causing the risk. Example: decide not to launch a feature in a high-risk jurisdiction.",[37,13129,13130],{},"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.",[560,13132,13134],{"id":13133},"how-do-you-connect-the-risk-register-to-operational-workflows","How do you connect the risk register to operational workflows?",[37,13136,13137],{},"A risk register that lives in isolation quickly goes stale. High-performing programs integrate it with:",[164,13139,13140,13149,13156,13161,13167],{},[167,13141,13142,13148],{},[103,13143,13144],{},[40,13145,13147],{"href":13146},"\u002Fglossary\u002Fvendor-risk-management","Vendor risk management"," — third-party risks from vendor assessments feed into the enterprise register",[167,13150,13151,13155],{},[103,13152,13153],{},[40,13154,7907],{"href":9362}," — post-incident reviews identify new risks or update likelihood scores for known ones",[167,13157,13158,13160],{},[103,13159,10343],{}," — significant system or business changes trigger a register update before deployment",[167,13162,13163,13166],{},[103,13164,13165],{},"Policy reviews"," — annual policy reviews check whether controls still address the risks they were designed for",[167,13168,13169,13172],{},[103,13170,13171],{},"Board reporting"," — top-tier risks roll up into executive dashboards showing trends, treatment progress, and heat maps",[560,13174,13176],{"id":13175},"what-does-an-example-risk-register-entry-look-like","What does an example risk register entry look like?",[37,13178,13179],{},"A concrete example makes the structure tangible. Consider a risk identified during an ISO 27001 internal audit:",[1596,13181,13182,13192],{},[1599,13183,13184],{},[1602,13185,13186,13189],{},[1605,13187,13188],{},"Field",[1605,13190,13191],{},"Value",[1612,13193,13194,13201,13208,13216,13223,13230,13238,13246,13253,13260,13268,13275],{},[1602,13195,13196,13198],{},[1617,13197,12799],{},[1617,13199,13200],{},"R-042",[1602,13202,13203,13205],{},[1617,13204,4842],{},[1617,13206,13207],{},"Unencrypted customer PII in database backups stored in S3",[1602,13209,13210,13213],{},[1617,13211,13212],{},"Category",[1617,13214,13215],{},"Data protection \u002F technical",[1602,13217,13218,13220],{},[1617,13219,12817],{},[1617,13221,13222],{},"3 (possible — we have access logs but no automated detection)",[1602,13224,13225,13227],{},[1617,13226,12823],{},[1617,13228,13229],{},"5 (severe — regulatory exposure under GDPR and state privacy laws)",[1602,13231,13232,13235],{},[1617,13233,13234],{},"Inherent score",[1617,13236,13237],{},"15 (high)",[1602,13239,13240,13243],{},[1617,13241,13242],{},"Owner",[1617,13244,13245],{},"CISO",[1602,13247,13248,13251],{},[1617,13249,13250],{},"Treatment",[1617,13252,13108],{},[1602,13254,13255,13257],{},[1617,13256,12847],{},[1617,13258,13259],{},"Enable S3 server-side encryption with KMS; rotate existing backups; add Macie scan",[1602,13261,13262,13265],{},[1617,13263,13264],{},"Residual score",[1617,13266,13267],{},"4 (low — automated encryption + detection materially reduces both)",[1602,13269,13270,13272],{},[1617,13271,12859],{},[1617,13273,13274],{},"In treatment — 60% complete",[1602,13276,13277,13279],{},[1617,13278,12865],{},[1617,13280,13281],{},"2026-06-01 (quarterly cadence)",[37,13283,13284],{},"This level of detail turns the register into a practical management tool rather than a compliance artifact.",[560,13286,13288],{"id":13287},"what-are-common-pitfalls-with-a-risk-register","What are common pitfalls with a risk register?",[37,13290,13291],{},"Organizations often struggle with risk registers due to:",[164,13293,13294,13297,13300,13303,13306,13309,13316,13319],{},[167,13295,13296],{},"Making the register too complex or too simple",[167,13298,13299],{},"Failing to review and update regularly",[167,13301,13302],{},"Not assigning clear ownership or clear treatment deadlines",[167,13304,13305],{},"Rating all risks as \"high\" without meaningful differentiation",[167,13307,13308],{},"Treating the register as a compliance checkbox rather than a management tool",[167,13310,13311,13312,13315],{},"Disconnecting the register from ",[40,13313,13314],{"href":9362},"incident response"," and vendor management workflows",[167,13317,13318],{},"Keeping risks open indefinitely without closure criteria or residual risk acceptance",[167,13320,13321],{},"Not versioning the register, making it impossible to demonstrate historical decisions to auditors",[560,13323,13325],{"id":13324},"what-risk-register-tools-and-templates-are-available","What risk register tools and templates are available?",[37,13327,13328],{},"Organizations use a range of tools to maintain a register:",[164,13330,13331,13337,13343],{},[167,13332,13333,13336],{},[103,13334,13335],{},"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.",[167,13338,13339,13342],{},[103,13340,13341],{},"GRC platforms"," — purpose-built tools (including episki) handle scoring, ownership, treatment workflows, and evidence links out of the box.",[167,13344,13345,13348],{},[103,13346,13347],{},"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,13350,13351],{},"Whatever tool you choose, exportability matters: auditors frequently ask for point-in-time snapshots, and regulators may request historical registers during an investigation.",[560,13353,13355],{"id":13354},"how-does-episki-help-with-a-risk-register","How does episki help with a risk register?",[37,13357,13358,13359,242],{},"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 ",[40,13360,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":13362},[13363],{"id":12781,"depth":428,"text":12782,"children":13364},[13365,13366,13367,13368,13369,13370,13371,13372,13373,13374,13375],{"id":12788,"depth":963,"text":12789},{"id":12869,"depth":963,"text":12870},{"id":12926,"depth":963,"text":12927},{"id":12965,"depth":963,"text":12966},{"id":12997,"depth":963,"text":12998},{"id":13094,"depth":963,"text":13095},{"id":13133,"depth":963,"text":13134},{"id":13175,"depth":963,"text":13176},{"id":13287,"depth":963,"text":13288},{"id":13324,"depth":963,"text":13325},{"id":13354,"depth":963,"text":13355},{},[6069,515,6073,6070],[6698,7430,7431,13379],"vendor-risk-management",{"title":13381,"description":13382},"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":13386,"title":13387,"body":13388,"description":427,"extension":460,"lastUpdated":979,"meta":13585,"navigation":497,"path":12444,"relatedFrameworks":13586,"relatedTerms":13587,"seo":13588,"slug":6698,"stem":13591,"term":13393,"__hash__":13592},"glossary\u002F8.glossary\u002Frisk-treatment-plan.md","Risk Treatment Plan",{"type":29,"value":13389,"toc":13575},[13390,13394,13397,13399,13402,13424,13427,13431,13434,13484,13488,13491,13511,13514,13518,13521,13525,13528,13566,13570],[32,13391,13393],{"id":13392},"what-is-a-risk-treatment-plan","What is a Risk Treatment Plan?",[37,13395,13396],{},"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.",[560,13398,13095],{"id":13094},[37,13400,13401],{},"For each identified risk, organizations typically choose one of four treatment options:",[164,13403,13404,13409,13414,13419],{},[167,13405,13406,13408],{},[103,13407,13108],{}," — implement controls to reduce the likelihood or impact of the risk to an acceptable level",[167,13410,13411,13413],{},[103,13412,13114],{}," — acknowledge the risk and decide not to take additional action, typically because the cost of treatment exceeds the potential impact",[167,13415,13416,13418],{},[103,13417,13120],{}," — shift the risk to a third party, such as through insurance or outsourcing to a specialized provider",[167,13420,13421,13423],{},[103,13422,13126],{}," — eliminate the risk entirely by discontinuing the activity or service that creates it",[37,13425,13426],{},"Most risks are treated through mitigation, with specific controls designed to address the identified threat.",[560,13428,13430],{"id":13429},"what-are-the-components-of-a-risk-treatment-plan","What are the components of a risk treatment plan?",[37,13432,13433],{},"A comprehensive risk treatment plan includes:",[164,13435,13436,13442,13447,13452,13457,13462,13468,13474,13479],{},[167,13437,13438,13441],{},[103,13439,13440],{},"Risk identifier"," — reference to the specific risk from the risk register",[167,13443,13444,13446],{},[103,13445,12805],{}," — a clear statement of the risk, including threat, vulnerability, and potential impact",[167,13448,13449,13451],{},[103,13450,12841],{}," — which of the four options has been selected",[167,13453,13454,13456],{},[103,13455,12847],{}," — the specific controls to be implemented for mitigated risks",[167,13458,13459,13461],{},[103,13460,13242],{}," — the person or team responsible for implementing the treatment",[167,13463,13464,13467],{},[103,13465,13466],{},"Timeline"," — target dates for implementation milestones",[167,13469,13470,13473],{},[103,13471,13472],{},"Resources required"," — budget, tools, or personnel needed",[167,13475,13476,13478],{},[103,13477,12853],{}," — the expected risk level after treatment is applied",[167,13480,13481,13483],{},[103,13482,12859],{}," — current implementation progress",[560,13485,13487],{"id":13486},"how-does-iso-27001-handle-risk-treatment","How does ISO 27001 handle risk treatment?",[37,13489,13490],{},"ISO 27001 clause 6.1.3 specifically requires organizations to formulate a risk treatment plan. The standard requires that:",[164,13492,13493,13496,13499,13502,13505,13508],{},[167,13494,13495],{},"Risk treatment options are determined for each assessed risk",[167,13497,13498],{},"Controls necessary to implement the treatment are identified",[167,13500,13501],{},"Selected controls are compared against Annex A to ensure completeness",[167,13503,13504],{},"A Statement of Applicability is produced",[167,13506,13507],{},"The risk treatment plan is approved by risk owners",[167,13509,13510],{},"Residual risk levels are accepted by management",[37,13512,13513],{},"The risk treatment plan is a key document reviewed during certification audits and surveillance audits.",[560,13515,13517],{"id":13516},"how-does-nist-csf-handle-risk-treatment","How does NIST CSF handle risk treatment?",[37,13519,13520],{},"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.",[560,13522,13524],{"id":13523},"how-do-you-build-an-effective-risk-treatment-plan","How do you build an effective risk treatment plan?",[37,13526,13527],{},"To create a practical and effective risk treatment plan:",[1446,13529,13530,13536,13542,13548,13554,13560],{},[167,13531,13532,13535],{},[103,13533,13534],{},"Prioritize risks"," — start with the highest-rated risks from your risk register",[167,13537,13538,13541],{},[103,13539,13540],{},"Select realistic treatments"," — choose options that are feasible given your budget, resources, and timeline",[167,13543,13544,13547],{},[103,13545,13546],{},"Assign clear ownership"," — every risk treatment must have a named owner accountable for implementation",[167,13549,13550,13553],{},[103,13551,13552],{},"Set measurable milestones"," — define specific, trackable milestones rather than vague commitments",[167,13555,13556,13559],{},[103,13557,13558],{},"Review regularly"," — update the plan as risks change, new threats emerge, or controls are implemented",[167,13561,13562,13565],{},[103,13563,13564],{},"Communicate status"," — report progress to management and stakeholders",[560,13567,13569],{"id":13568},"how-does-episki-help-with-a-risk-treatment-plan","How does episki help with a risk treatment plan?",[37,13571,13572,13573,242],{},"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 ",[40,13574,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":13576},[13577],{"id":13392,"depth":428,"text":13393,"children":13578},[13579,13580,13581,13582,13583,13584],{"id":13094,"depth":963,"text":13095},{"id":13429,"depth":963,"text":13430},{"id":13486,"depth":963,"text":13487},{"id":13516,"depth":963,"text":13517},{"id":13523,"depth":963,"text":13524},{"id":13568,"depth":963,"text":13569},{},[515,6073],[6697,984,515,7431,7430],{"title":13589,"description":13590},"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":13594,"title":13595,"body":13596,"description":427,"extension":460,"lastUpdated":979,"meta":13819,"navigation":497,"path":13820,"relatedFrameworks":13821,"relatedTerms":13822,"seo":13823,"slug":13826,"stem":13827,"term":13601,"__hash__":13828},"glossary\u002F8.glossary\u002Fsecurity-awareness-training.md","Security Awareness Training",{"type":29,"value":13597,"toc":13808},[13598,13602,13605,13609,13612,13629,13633,13636,13686,13690,13712,13716,13719,13751,13755,13758,13775,13779,13782,13799,13803],[32,13599,13601],{"id":13600},"what-is-security-awareness-training","What is Security Awareness Training?",[37,13603,13604],{},"Security awareness training is an educational program designed to teach employees about cybersecurity threats, security best practices, and their responsibilities for protecting organizational data and systems. Human error remains one of the leading causes of security incidents, making awareness training a critical control for reducing risk. Every major compliance framework requires or strongly recommends security awareness training.",[560,13606,13608],{"id":13607},"why-does-security-awareness-training-matter","Why does security awareness training matter?",[37,13610,13611],{},"Technology controls alone cannot prevent all security incidents. Employees interact with sensitive data, click links, open attachments, and make decisions that affect security every day. Effective training:",[164,13613,13614,13617,13620,13623,13626],{},[167,13615,13616],{},"Reduces the likelihood of successful phishing and social engineering attacks",[167,13618,13619],{},"Helps employees recognize and report suspicious activity",[167,13621,13622],{},"Builds a security-conscious culture throughout the organization",[167,13624,13625],{},"Meets compliance requirements across multiple frameworks",[167,13627,13628],{},"Reduces the frequency and impact of human-caused security incidents",[560,13630,13632],{"id":13631},"what-are-the-core-security-awareness-training-topics","What are the core security awareness training topics?",[37,13634,13635],{},"A comprehensive security awareness program typically covers:",[164,13637,13638,13644,13650,13656,13662,13668,13674,13680],{},[167,13639,13640,13643],{},[103,13641,13642],{},"Phishing and social engineering"," — how to identify and respond to phishing emails, phone-based pretexting, and other manipulation techniques",[167,13645,13646,13649],{},[103,13647,13648],{},"Password security"," — creating strong passwords, using password managers, and understanding multi-factor authentication",[167,13651,13652,13655],{},[103,13653,13654],{},"Data handling"," — proper classification, storage, transmission, and disposal of sensitive data",[167,13657,13658,13661],{},[103,13659,13660],{},"Physical security"," — securing workstations, preventing tailgating, and protecting physical access badges",[167,13663,13664,13667],{},[103,13665,13666],{},"Remote work security"," — securing home networks, using VPNs, and protecting devices outside the office",[167,13669,13670,13673],{},[103,13671,13672],{},"Incident reporting"," — how and when to report suspected security incidents",[167,13675,13676,13679],{},[103,13677,13678],{},"Acceptable use"," — organizational policies on technology use, internet access, and personal devices",[167,13681,13682,13685],{},[103,13683,13684],{},"Regulatory requirements"," — specific requirements based on the organization's compliance obligations (HIPAA for healthcare, PCI DSS for payment card handling)",[560,13687,13689],{"id":13688},"what-training-requirements-apply-by-framework","What training requirements apply by framework?",[164,13691,13692,13697,13702,13707],{},[167,13693,13694,13696],{},[103,13695,381],{}," — CC1.4 requires that the organization demonstrates a commitment to attract, develop, and retain competent individuals, including security training",[167,13698,13699,13701],{},[103,13700,43],{}," — control A.6.3 requires information security awareness, education, and training",[167,13703,13704,13706],{},[103,13705,5694],{}," — the Security Rule requires security awareness and training for all workforce members (45 CFR 164.308(a)(5))",[167,13708,13709,13711],{},[103,13710,5708],{}," — Requirement 12.6 requires security awareness training for all personnel upon hire and at least annually",[560,13713,13715],{"id":13714},"how-often-should-training-be-delivered-and-how","How often should training be delivered, and how?",[37,13717,13718],{},"Best practices for training delivery include:",[164,13720,13721,13727,13733,13739,13745],{},[167,13722,13723,13726],{},[103,13724,13725],{},"Upon hire"," — all new employees should complete security awareness training during onboarding",[167,13728,13729,13732],{},[103,13730,13731],{},"Annual refresher"," — all employees should complete refresher training at least annually",[167,13734,13735,13738],{},[103,13736,13737],{},"Role-specific training"," — employees in high-risk roles (developers, administrators, finance) should receive additional targeted training",[167,13740,13741,13744],{},[103,13742,13743],{},"Continuous reinforcement"," — supplement formal training with simulated phishing campaigns, security tips, and brief micro-learning modules throughout the year",[167,13746,13747,13750],{},[103,13748,13749],{},"Triggered training"," — require additional training when an employee fails a phishing simulation or is involved in a security incident",[560,13752,13754],{"id":13753},"how-do-you-measure-training-effectiveness","How do you measure training effectiveness?",[37,13756,13757],{},"Training effectiveness should be measured through:",[164,13759,13760,13763,13766,13769,13772],{},[167,13761,13762],{},"Phishing simulation click rates (tracked over time to show improvement)",[167,13764,13765],{},"Training completion rates",[167,13767,13768],{},"Security incident trends related to human factors",[167,13770,13771],{},"Employee knowledge assessments (quizzes or surveys)",[167,13773,13774],{},"Time to report suspicious activity",[560,13776,13778],{"id":13777},"what-training-evidence-do-auditors-look-for","What training evidence do auditors look for?",[37,13780,13781],{},"Auditors expect to see:",[164,13783,13784,13787,13790,13793,13796],{},[167,13785,13786],{},"Training policy documenting requirements and frequency",[167,13788,13789],{},"Records of training completion for all employees",[167,13791,13792],{},"Training content covering relevant topics",[167,13794,13795],{},"Phishing simulation results and trends",[167,13797,13798],{},"Evidence of new hire training",[560,13800,13802],{"id":13801},"how-does-episki-help-with-security-awareness-training","How does episki help with security awareness training?",[37,13804,13805,13806,242],{},"episki tracks security awareness training completion, sends reminders to employees and managers, and maintains training records as compliance evidence. The platform integrates with popular training providers and maps training requirements to framework controls. Learn more on our ",[40,13807,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":13809},[13810],{"id":13600,"depth":428,"text":13601,"children":13811},[13812,13813,13814,13815,13816,13817,13818],{"id":13607,"depth":963,"text":13608},{"id":13631,"depth":963,"text":13632},{"id":13688,"depth":963,"text":13689},{"id":13714,"depth":963,"text":13715},{"id":13753,"depth":963,"text":13754},{"id":13777,"depth":963,"text":13778},{"id":13801,"depth":963,"text":13802},{},"\u002Fglossary\u002Fsecurity-awareness-training",[6069,6070,515,6071,6072],[6080,4226,2698,8085],{"title":13824,"description":13825},"What is Security Awareness Training? Definition & Compliance Guide","Security awareness training educates employees about cybersecurity threats and best practices. Learn what to include and how it satisfies compliance requirements.","security-awareness-training","8.glossary\u002Fsecurity-awareness-training","xgD6bzRoOy6RZm_k9NAZRMfP5cKo0j-xLN3LeofSjwI",{"id":13830,"title":13831,"body":13832,"description":427,"extension":460,"lastUpdated":979,"meta":14035,"navigation":497,"path":142,"relatedFrameworks":14036,"relatedTerms":14037,"seo":14038,"slug":984,"stem":14041,"term":13837,"__hash__":14042},"glossary\u002F8.glossary\u002Fstatement-of-applicability.md","Statement Of Applicability",{"type":29,"value":13833,"toc":14025},[13834,13838,13841,13845,13848,13880,13884,13887,13929,13933,13936,13974,13978,13981,13992,13995,13999,14002,14016,14020],[32,13835,13837],{"id":13836},"what-is-a-statement-of-applicability","What is a Statement of Applicability?",[37,13839,13840],{},"The Statement of Applicability (SoA) is a mandatory document in ISO 27001 that records which Annex A controls are applicable to the organization, which are not applicable, and the justification for each decision. It serves as a central reference linking the organization's risk assessment results to its selected security controls.",[560,13842,13844],{"id":13843},"why-does-the-soa-matter","Why does the SoA matter?",[37,13846,13847],{},"The Statement of Applicability is one of the most important documents in an ISO 27001 ISMS. It serves multiple purposes:",[164,13849,13850,13856,13862,13868,13874],{},[167,13851,13852,13855],{},[103,13853,13854],{},"Demonstrates completeness"," — shows that the organization has considered every Annex A control and made deliberate decisions about each one",[167,13857,13858,13861],{},[103,13859,13860],{},"Links risk to controls"," — connects identified risks to the controls selected to mitigate them",[167,13863,13864,13867],{},[103,13865,13866],{},"Audit reference"," — certification auditors use the SoA as a primary reference when planning and conducting their audit",[167,13869,13870,13873],{},[103,13871,13872],{},"Scope definition"," — helps define the boundary of the ISMS by clarifying which controls apply and which do not",[167,13875,13876,13879],{},[103,13877,13878],{},"Communication tool"," — provides a clear summary of the organization's security control posture for management and stakeholders",[560,13881,13883],{"id":13882},"what-does-the-statement-of-applicability-contain","What does the Statement of Applicability contain?",[37,13885,13886],{},"A well-structured Statement of Applicability typically includes the following for each Annex A control:",[164,13888,13889,13895,13901,13907,13913,13918,13924],{},[167,13890,13891,13894],{},[103,13892,13893],{},"Control reference number"," — the Annex A control identifier (e.g., A.5.1, A.8.24)",[167,13896,13897,13900],{},[103,13898,13899],{},"Control description"," — a brief description of the control",[167,13902,13903,13906],{},[103,13904,13905],{},"Applicability status"," — whether the control is applicable or not applicable",[167,13908,13909,13912],{},[103,13910,13911],{},"Justification"," — the reason for inclusion or exclusion (referencing the risk assessment where relevant)",[167,13914,13915,13917],{},[103,13916,4881],{}," — whether the control is fully implemented, partially implemented, or planned",[167,13919,13920,13923],{},[103,13921,13922],{},"Implementation method"," — how the control is implemented (policy, technical measure, process, etc.)",[167,13925,13926,13928],{},[103,13927,4905],{}," — pointers to evidence demonstrating implementation",[560,13930,13932],{"id":13931},"how-do-you-build-the-soa","How do you build the SoA?",[37,13934,13935],{},"Creating the Statement of Applicability follows a logical sequence:",[1446,13937,13938,13944,13950,13956,13962,13968],{},[167,13939,13940,13943],{},[103,13941,13942],{},"Complete the risk assessment"," — identify and evaluate information security risks",[167,13945,13946,13949],{},[103,13947,13948],{},"Determine risk treatment"," — decide how each risk will be treated",[167,13951,13952,13955],{},[103,13953,13954],{},"Select controls"," — choose controls to mitigate identified risks",[167,13957,13958,13961],{},[103,13959,13960],{},"Cross-reference Annex A"," — compare selected controls against the full Annex A list to check for gaps",[167,13963,13964,13967],{},[103,13965,13966],{},"Document applicability"," — record which controls apply and which do not, with justifications",[167,13969,13970,13973],{},[103,13971,13972],{},"Track implementation"," — document the current status of each applicable control",[560,13975,13977],{"id":13976},"how-do-you-justify-excluding-controls-from-the-soa","How do you justify excluding controls from the SoA?",[37,13979,13980],{},"It is acceptable to exclude Annex A controls from the SoA, but each exclusion must be justified. Common justifications include:",[164,13982,13983,13986,13989],{},[167,13984,13985],{},"The risk associated with the control area has been assessed and is within acceptable tolerance",[167,13987,13988],{},"The control is not relevant to the organization's scope (e.g., physical security controls for a fully remote company with no physical offices)",[167,13990,13991],{},"The risk is transferred through insurance or contractual arrangements",[37,13993,13994],{},"Auditors will scrutinize exclusions, so justifications should be clear, specific, and tied to the risk assessment.",[560,13996,13998],{"id":13997},"how-do-you-maintain-the-soa","How do you maintain the SoA?",[37,14000,14001],{},"The SoA is not a one-time document. It should be reviewed and updated:",[164,14003,14004,14007,14010,14013],{},[167,14005,14006],{},"After changes to the risk assessment",[167,14008,14009],{},"When new Annex A controls are introduced (as in the 2022 revision)",[167,14011,14012],{},"When the organization's scope, services, or infrastructure changes",[167,14014,14015],{},"At least annually as part of the ISMS management review",[560,14017,14019],{"id":14018},"how-does-episki-help-with-the-soa","How does episki help with the SoA?",[37,14021,14022,14023,242],{},"episki generates and maintains your Statement of Applicability automatically based on your risk assessment results and control mappings. As your risk profile evolves, the SoA updates accordingly. The platform provides a clear view of applicability, implementation status, and evidence for each control. Learn more on our ",[40,14024,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":14026},[14027],{"id":13836,"depth":428,"text":13837,"children":14028},[14029,14030,14031,14032,14033,14034],{"id":13843,"depth":963,"text":13844},{"id":13882,"depth":963,"text":13883},{"id":13931,"depth":963,"text":13932},{"id":13976,"depth":963,"text":13977},{"id":13997,"depth":963,"text":13998},{"id":14018,"depth":963,"text":14019},{},[515],[515,6231,6698,982,1362],{"title":14039,"description":14040},"What is a Statement of Applicability? Definition & Compliance Guide","The Statement of Applicability (SoA) documents which ISO 27001 Annex A controls apply to your organization and why. Learn its role in certification audits.","8.glossary\u002Fstatement-of-applicability","JEWeJrex8SIN5Pb-0qR2PZ9smPxLhzDTy5T2yVTph8I",{"id":14044,"title":5207,"body":14045,"description":427,"extension":460,"lastUpdated":979,"meta":14265,"navigation":497,"path":14266,"relatedFrameworks":14267,"relatedTerms":14268,"seo":14269,"slug":6906,"stem":14272,"term":14049,"__hash__":14273},"glossary\u002F8.glossary\u002Fsurveillance-audit.md",{"type":29,"value":14046,"toc":14254},[14047,14050,14053,14057,14060,14092,14096,14099,14125,14128,14132,14135,14166,14169,14173,14176,14214,14218,14221,14238,14242,14245,14249],[32,14048,14049],{"id":5106},"What is a Surveillance Audit?",[37,14051,14052],{},"A surveillance audit is a periodic assessment conducted by a certification body to verify that a certified organization's management system continues to operate in accordance with the standard requirements. In the context of ISO 27001, surveillance audits occur annually between the initial certification and the three-year recertification cycle.",[560,14054,14056],{"id":14055},"what-is-the-purpose-of-surveillance-audits","What is the purpose of surveillance audits?",[37,14058,14059],{},"Surveillance audits serve several important purposes:",[164,14061,14062,14068,14074,14080,14086],{},[167,14063,14064,14067],{},[103,14065,14066],{},"Ongoing assurance"," — confirm that the ISMS has not degraded since the initial certification or last audit",[167,14069,14070,14073],{},[103,14071,14072],{},"Continuous improvement verification"," — check that the organization is actively improving its ISMS rather than letting it stagnate",[167,14075,14076,14079],{},[103,14077,14078],{},"Change assessment"," — evaluate how changes to the organization, its services, or its risk environment have been addressed",[167,14081,14082,14085],{},[103,14083,14084],{},"Corrective action follow-up"," — verify that nonconformities identified in previous audits have been resolved",[167,14087,14088,14091],{},[103,14089,14090],{},"Stakeholder confidence"," — maintain trust among customers, partners, and regulators that the certification remains valid",[560,14093,14095],{"id":14094},"what-is-the-surveillance-audit-schedule","What is the surveillance audit schedule?",[37,14097,14098],{},"ISO 27001 certification follows a three-year cycle:",[164,14100,14101,14107,14113,14119],{},[167,14102,14103,14106],{},[103,14104,14105],{},"Year 0"," — initial certification audit (Stage 1 and Stage 2)",[167,14108,14109,14112],{},[103,14110,14111],{},"Year 1"," — first surveillance audit",[167,14114,14115,14118],{},[103,14116,14117],{},"Year 2"," — second surveillance audit",[167,14120,14121,14124],{},[103,14122,14123],{},"Year 3"," — recertification audit (full audit to renew the certificate for another three years)",[37,14126,14127],{},"Surveillance audits are typically scheduled around the anniversary of the initial certification. Missing or failing a surveillance audit can result in suspension or withdrawal of the certificate.",[560,14129,14131],{"id":14130},"what-is-the-scope-of-surveillance-audits","What is the scope of surveillance audits?",[37,14133,14134],{},"Surveillance audits do not cover the entire ISMS in the same depth as the initial certification. Instead, the certification body samples a subset of controls and processes. However, certain elements are always reviewed:",[164,14136,14137,14143,14148,14154,14160],{},[167,14138,14139,14142],{},[103,14140,14141],{},"Internal audit results"," — evidence that the organization is conducting its own internal audits",[167,14144,14145,14147],{},[103,14146,3944],{}," — records showing that management regularly reviews ISMS performance",[167,14149,14150,14153],{},[103,14151,14152],{},"Corrective actions"," — status of previously identified nonconformities",[167,14155,14156,14159],{},[103,14157,14158],{},"Use of the certification mark"," — verification that the organization uses the ISO 27001 mark correctly",[167,14161,14162,14165],{},[103,14163,14164],{},"Changes to the ISMS"," — assessment of any significant changes since the last audit",[37,14167,14168],{},"The certification body plans the surveillance audits to ensure that, across the three-year cycle, all significant areas of the ISMS are examined.",[560,14170,14172],{"id":14171},"how-do-you-prepare-for-a-surveillance-audit","How do you prepare for a surveillance audit?",[37,14174,14175],{},"To prepare effectively:",[164,14177,14178,14184,14190,14196,14202,14208],{},[167,14179,14180,14183],{},[103,14181,14182],{},"Maintain your ISMS"," — do not treat certification as a one-time achievement; keep controls operating and evidence current",[167,14185,14186,14189],{},[103,14187,14188],{},"Conduct internal audits"," — perform regular internal audits and document findings and corrective actions",[167,14191,14192,14195],{},[103,14193,14194],{},"Hold management reviews"," — ensure management reviews occur at planned intervals with documented outcomes",[167,14197,14198,14201],{},[103,14199,14200],{},"Track corrective actions"," — close out any nonconformities from previous audits with evidence of resolution",[167,14203,14204,14207],{},[103,14205,14206],{},"Update documentation"," — keep policies, procedures, the risk register, and Statement of Applicability current",[167,14209,14210,14213],{},[103,14211,14212],{},"Brief your team"," — ensure control owners understand the surveillance process and can speak to their controls",[560,14215,14217],{"id":14216},"what-are-common-pitfalls-with-surveillance-audits","What are common pitfalls with surveillance audits?",[37,14219,14220],{},"Organizations frequently encounter issues during surveillance audits due to:",[164,14222,14223,14226,14229,14232,14235],{},[167,14224,14225],{},"Letting the ISMS become dormant between audits",[167,14227,14228],{},"Failing to conduct internal audits or management reviews",[167,14230,14231],{},"Not updating the risk assessment after significant changes",[167,14233,14234],{},"Incomplete corrective action records",[167,14236,14237],{},"Documentation that does not reflect current practices",[560,14239,14241],{"id":14240},"what-happens-if-you-fail-a-surveillance-audit","What happens if you fail a surveillance audit?",[37,14243,14244],{},"If the certification body identifies major nonconformities during a surveillance audit, the organization typically receives a defined period to resolve them. If nonconformities are not resolved, the CB may suspend or withdraw the certification.",[560,14246,14248],{"id":14247},"how-does-episki-help-with-surveillance-audits","How does episki help with surveillance audits?",[37,14250,14251,14252,242],{},"episki keeps your ISMS active year-round with automated evidence collection, internal audit tracking, and management review workflows. The platform ensures you are always surveillance-audit-ready rather than scrambling to prepare. Learn more on our ",[40,14253,6212],{"href":498},{"title":427,"searchDepth":428,"depth":428,"links":14255},[14256],{"id":5106,"depth":428,"text":14049,"children":14257},[14258,14259,14260,14261,14262,14263,14264],{"id":14055,"depth":963,"text":14056},{"id":14094,"depth":963,"text":14095},{"id":14130,"depth":963,"text":14131},{"id":14171,"depth":963,"text":14172},{"id":14216,"depth":963,"text":14217},{"id":14240,"depth":963,"text":14241},{"id":14247,"depth":963,"text":14248},{},"\u002Fglossary\u002Fsurveillance-audit",[515],[515,1362,982,984,6231],{"title":14270,"description":14271},"What is a Surveillance Audit? Definition & Compliance Guide","A surveillance audit is an annual check by a certification body to verify that your ISO 27001 ISMS continues to operate effectively. Learn what to expect.","8.glossary\u002Fsurveillance-audit","jJBmuftExlStO3zC0agQCzOIUDUgNonZM_tMXHozlAQ",{"id":14275,"title":14276,"body":14277,"description":427,"extension":460,"lastUpdated":979,"meta":14487,"navigation":497,"path":14488,"relatedFrameworks":14489,"relatedTerms":14490,"seo":14492,"slug":14495,"stem":14496,"term":14282,"__hash__":14497},"glossary\u002F8.glossary\u002Fthird-party-risk.md","Third Party Risk",{"type":29,"value":14278,"toc":14477},[14279,14283,14286,14290,14293,14337,14341,14344,14376,14380,14383,14410,14414,14417,14461,14465,14468,14472],[32,14280,14282],{"id":14281},"what-is-third-party-risk","What is Third-Party Risk?",[37,14284,14285],{},"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.",[560,14287,14289],{"id":14288},"what-are-the-types-of-third-party-risk","What are the types of third-party risk?",[37,14291,14292],{},"Third-party risk encompasses several categories:",[164,14294,14295,14301,14307,14313,14319,14325,14331],{},[167,14296,14297,14300],{},[103,14298,14299],{},"Security risk"," — the vendor's security weaknesses could lead to unauthorized access to your data or systems",[167,14302,14303,14306],{},[103,14304,14305],{},"Compliance risk"," — the vendor's practices may not meet regulatory requirements, creating liability for your organization",[167,14308,14309,14312],{},[103,14310,14311],{},"Operational risk"," — vendor outages, service failures, or business disruptions could impact your operations",[167,14314,14315,14318],{},[103,14316,14317],{},"Financial risk"," — vendor financial instability could threaten service continuity",[167,14320,14321,14324],{},[103,14322,14323],{},"Reputational risk"," — a vendor's public security incident or ethical violation could damage your brand",[167,14326,14327,14330],{},[103,14328,14329],{},"Strategic risk"," — over-reliance on a single vendor creates concentration risk",[167,14332,14333,14336],{},[103,14334,14335],{},"Data risk"," — the vendor may mishandle, lose, or improperly disclose your data",[560,14338,14340],{"id":14339},"why-is-third-party-risk-growing","Why is third-party risk growing?",[37,14342,14343],{},"Several trends are increasing third-party risk exposure:",[164,14345,14346,14352,14358,14364,14370],{},[167,14347,14348,14351],{},[103,14349,14350],{},"Cloud adoption"," — organizations store sensitive data with cloud providers and SaaS applications",[167,14353,14354,14357],{},[103,14355,14356],{},"Supply chain complexity"," — vendors use their own vendors (fourth parties), creating layers of risk",[167,14359,14360,14363],{},[103,14361,14362],{},"Data sharing"," — business processes increasingly require sharing data with external parties",[167,14365,14366,14369],{},[103,14367,14368],{},"Remote work"," — distributed workforces rely on more external tools and services",[167,14371,14372,14375],{},[103,14373,14374],{},"Regulatory expansion"," — regulators increasingly hold organizations accountable for their vendors' practices",[560,14377,14379],{"id":14378},"how-do-compliance-frameworks-address-third-party-risk","How do compliance frameworks address third-party risk?",[37,14381,14382],{},"Compliance frameworks address third-party risk explicitly:",[164,14384,14385,14390,14395,14400,14405],{},[167,14386,14387,14389],{},[103,14388,381],{}," — CC9.2 requires assessing risks from vendor relationships. The SSAE 18 standard also requires monitoring subservice organizations.",[167,14391,14392,14394],{},[103,14393,43],{}," — clauses A.5.19 through A.5.23 address supplier relationship security, including policies, assessment, and monitoring",[167,14396,14397,14399],{},[103,14398,5717],{}," — the Govern function includes supply chain risk management expectations",[167,14401,14402,14404],{},[103,14403,5694],{}," — requires BAAs with business associates and oversight of how they handle PHI",[167,14406,14407,14409],{},[103,14408,5708],{}," — Requirement 12.8 requires maintaining and monitoring service provider relationships",[560,14411,14413],{"id":14412},"how-do-you-manage-third-party-risk","How do you manage third-party risk?",[37,14415,14416],{},"Effective third-party risk management involves:",[1446,14418,14419,14425,14431,14437,14443,14449,14455],{},[167,14420,14421,14424],{},[103,14422,14423],{},"Inventory"," — know all your third parties and what data or systems they can access",[167,14426,14427,14430],{},[103,14428,14429],{},"Assess"," — evaluate each third party's security posture before and during the relationship",[167,14432,14433,14436],{},[103,14434,14435],{},"Tier"," — classify third parties by risk level to allocate assessment effort appropriately",[167,14438,14439,14442],{},[103,14440,14441],{},"Contract"," — include security requirements, breach notification clauses, and audit rights",[167,14444,14445,14448],{},[103,14446,14447],{},"Monitor"," — continuously track vendor security posture, not just at onboarding",[167,14450,14451,14454],{},[103,14452,14453],{},"Respond"," — have plans for responding to vendor incidents, including data breaches and service outages",[167,14456,14457,14460],{},[103,14458,14459],{},"Exit"," — plan for vendor transitions, ensuring data is returned or destroyed and access is revoked",[560,14462,14464],{"id":14463},"what-is-fourth-party-risk","What is fourth-party risk?",[37,14466,14467],{},"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.",[560,14469,14471],{"id":14470},"how-does-episki-help-with-third-party-risk","How does episki help with third-party risk?",[37,14473,14474,14475,242],{},"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 ",[40,14476,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":14478},[14479],{"id":14281,"depth":428,"text":14282,"children":14480},[14481,14482,14483,14484,14485,14486],{"id":14288,"depth":963,"text":14289},{"id":14339,"depth":963,"text":14340},{"id":14378,"depth":963,"text":14379},{"id":14412,"depth":963,"text":14413},{"id":14463,"depth":963,"text":14464},{"id":14470,"depth":963,"text":14471},{},"\u002Fglossary\u002Fthird-party-risk",[6070,515,6073],[13379,6697,6698,14491],"business-associate",{"title":14493,"description":14494},"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":14499,"title":14500,"body":14501,"description":427,"extension":460,"lastUpdated":979,"meta":15091,"navigation":497,"path":13146,"relatedFrameworks":15092,"relatedTerms":15093,"seo":15095,"slug":13379,"stem":15098,"term":14506,"__hash__":15099},"glossary\u002F8.glossary\u002Fvendor-risk-management.md","Vendor Risk Management",{"type":29,"value":14502,"toc":15078},[14503,14507,14510,14514,14517,14544,14548,14551,14557,14571,14576,14590,14596,14610,14616,14633,14639,14653,14657,14660,14709,14713,14730,14734,14737,14803,14808,14813,14828,14833,14842,14846,14849,14855,14872,14878,14895,14901,14915,14921,14932,14938,14942,14945,14951,14957,14963,14969,14983,14987,14990,14996,15031,15037,15066,15069,15073],[32,14504,14506],{"id":14505},"what-is-vendor-risk-management","What is Vendor Risk Management?",[37,14508,14509],{},"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.",[560,14511,14513],{"id":14512},"why-does-vendor-risk-management-matter","Why does vendor risk management matter?",[37,14515,14516],{},"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:",[164,14518,14519,14524,14529,14534,14539],{},[167,14520,14521,14523],{},[103,14522,381],{}," — CC9.2 requires organizations to assess and manage risks associated with vendors and business partners",[167,14525,14526,14528],{},[103,14527,43],{}," — controls A.5.19 through A.5.23 address information security in supplier relationships",[167,14530,14531,14533],{},[103,14532,5717],{}," — the Identify function includes supply chain risk management",[167,14535,14536,14538],{},[103,14537,5694],{}," — requires Business Associate Agreements with vendors handling PHI",[167,14540,14541,14543],{},[103,14542,5708],{}," — requires monitoring of service provider PCI DSS compliance",[560,14545,14547],{"id":14546},"what-are-the-components-of-a-vrm-program","What are the components of a VRM program?",[37,14549,14550],{},"An effective vendor risk management program includes:",[37,14552,14553,14556],{},[103,14554,14555],{},"Vendor inventory"," — maintain a complete list of all third-party vendors, including:",[164,14558,14559,14562,14565,14568],{},[167,14560,14561],{},"What services they provide",[167,14563,14564],{},"What data they can access",[167,14566,14567],{},"Their criticality to business operations",[167,14569,14570],{},"Contract terms and renewal dates",[37,14572,14573,14575],{},[103,14574,6524],{}," — evaluate each vendor's security posture through:",[164,14577,14578,14581,14584,14587],{},[167,14579,14580],{},"Security questionnaires (SIG, CAIQ, or custom)",[167,14582,14583],{},"Review of compliance reports (SOC 2, ISO 27001 certificates)",[167,14585,14586],{},"Technical assessments when appropriate",[167,14588,14589],{},"Review of publicly available security information",[37,14591,14592,14595],{},[103,14593,14594],{},"Risk tiering"," — classify vendors by risk level based on:",[164,14597,14598,14601,14604,14607],{},[167,14599,14600],{},"Sensitivity of data they access",[167,14602,14603],{},"Criticality of the service they provide",[167,14605,14606],{},"Volume of data handled",[167,14608,14609],{},"Regulatory requirements (e.g., HIPAA business associates)",[37,14611,14612,14615],{},[103,14613,14614],{},"Contractual protections"," — ensure vendor contracts include:",[164,14617,14618,14621,14624,14627,14630],{},[167,14619,14620],{},"Security requirements and responsibilities",[167,14622,14623],{},"Data protection obligations",[167,14625,14626],{},"Breach notification requirements",[167,14628,14629],{},"Right to audit",[167,14631,14632],{},"Compliance certifications",[37,14634,14635,14638],{},[103,14636,14637],{},"Ongoing monitoring"," — continuously monitor vendors through:",[164,14640,14641,14644,14647,14650],{},[167,14642,14643],{},"Annual or periodic reassessments",[167,14645,14646],{},"Review of updated compliance reports",[167,14648,14649],{},"Monitoring for security incidents or breaches",[167,14651,14652],{},"Tracking changes in the vendor's services or risk profile",[560,14654,14656],{"id":14655},"what-is-the-vendor-assessment-process","What is the vendor assessment process?",[37,14658,14659],{},"A typical vendor assessment follows these steps:",[1446,14661,14662,14668,14674,14680,14686,14691,14697,14703],{},[167,14663,14664,14667],{},[103,14665,14666],{},"Categorize the vendor"," — determine risk tier based on data access and service criticality",[167,14669,14670,14673],{},[103,14671,14672],{},"Send questionnaire"," — distribute a security questionnaire appropriate to the risk tier",[167,14675,14676,14679],{},[103,14677,14678],{},"Review responses"," — evaluate the vendor's security practices against your requirements",[167,14681,14682,14685],{},[103,14683,14684],{},"Request evidence"," — ask for supporting documentation (SOC 2 report, policies, certifications)",[167,14687,14688,14690],{},[103,14689,7817],{}," — document areas where the vendor does not meet your standards",[167,14692,14693,14696],{},[103,14694,14695],{},"Make decision"," — approve, approve with conditions, or reject the vendor",[167,14698,14699,14702],{},[103,14700,14701],{},"Document results"," — record the assessment findings and decision",[167,14704,14705,14708],{},[103,14706,14707],{},"Schedule reassessment"," — set a date for the next review based on risk tier",[560,14710,14712],{"id":14711},"what-are-common-challenges-with-vendor-risk-management","What are common challenges with vendor risk management?",[164,14714,14715,14718,14721,14724,14727],{},[167,14716,14717],{},"Managing assessments across dozens or hundreds of vendors",[167,14719,14720],{},"Getting timely responses to security questionnaires",[167,14722,14723],{},"Assessing vendors that lack formal compliance certifications",[167,14725,14726],{},"Monitoring vendor risk between assessment cycles",[167,14728,14729],{},"Balancing thoroughness with business velocity",[560,14731,14733],{"id":14732},"what-is-vrm-requirements-by-compliance-framework","What is VRM requirements by compliance framework?",[37,14735,14736],{},"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.",[1596,14738,14739,14750],{},[1599,14740,14741],{},[1602,14742,14743,14745,14747],{},[1605,14744,8897],{},[1605,14746,11331],{},[1605,14748,14749],{},"Specific controls",[1612,14751,14752,14762,14772,14782,14792],{},[1602,14753,14754,14756,14759],{},[1617,14755,381],{},[1617,14757,14758],{},"Vendor risk assessment, monitoring",[1617,14760,14761],{},"CC9.2, CC3.2",[1602,14763,14764,14766,14769],{},[1617,14765,43],{},[1617,14767,14768],{},"Supplier security policies, monitoring, change management",[1617,14770,14771],{},"A.5.19–A.5.23",[1602,14773,14774,14776,14779],{},[1617,14775,5694],{},[1617,14777,14778],{},"BAAs required for PHI-handling vendors",[1617,14780,14781],{},"§164.308(b), §164.314",[1602,14783,14784,14786,14789],{},[1617,14785,5708],{},[1617,14787,14788],{},"Service provider compliance validation",[1617,14790,14791],{},"Req 12.8, Req 12.9",[1602,14793,14794,14797,14800],{},[1617,14795,14796],{},"NIST CSF 2.0",[1617,14798,14799],{},"Dedicated supply chain governance",[1617,14801,14802],{},"GV.SC (expanded in 2.0)",[37,14804,14805,14807],{},[103,14806,381],{}," 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,14809,14810,14812],{},[103,14811,43],{}," 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,14814,14815,14817,14818,14822,14823,14827],{},[103,14816,5694],{}," takes a narrower but legally binding approach. Any vendor that creates, receives, maintains, or transmits ",[40,14819,14821],{"href":14820},"\u002Fglossary\u002Fphi","protected health information (PHI)"," on behalf of a covered entity must sign a ",[40,14824,14826],{"href":14825},"\u002Fglossary\u002Fbaa","Business Associate Agreement",". The BAA must specify permitted uses of PHI, breach notification obligations, and data return or destruction requirements.",[37,14829,14830,14832],{},[103,14831,5708],{}," 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,14834,14835,14837,14838,242],{},[103,14836,14796],{}," 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 ",[40,14839,14841],{"href":14840},"\u002Fframeworks\u002Fnistcsf\u002Fv2-changes","NIST CSF v2.0 changes",[560,14843,14845],{"id":14844},"how-do-you-build-a-vendor-risk-tiering-model","How do you build a vendor risk tiering model?",[37,14847,14848],{},"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,14850,14851,14854],{},[103,14852,14853],{},"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.",[164,14856,14857,14860,14863,14866,14869],{},[167,14858,14859],{},"Full security assessment with detailed questionnaire (SIG or equivalent)",[167,14861,14862],{},"Review of SOC 2 Type II report and\u002For ISO 27001 certificate",[167,14864,14865],{},"Annual reassessment at minimum, with continuous monitoring where feasible",[167,14867,14868],{},"Comprehensive contractual security requirements, including breach notification, audit rights, and data handling obligations",[167,14870,14871],{},"Executive-level relationship management and regular security review meetings",[37,14873,14874,14877],{},[103,14875,14876],{},"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.",[164,14879,14880,14883,14886,14889,14892],{},[167,14881,14882],{},"Standard security questionnaire",[167,14884,14885],{},"Review of available compliance certifications",[167,14887,14888],{},"Annual reassessment",[167,14890,14891],{},"Basic contractual protections including breach notification and data protection clauses",[167,14893,14894],{},"Periodic check-ins with vendor security contacts",[37,14896,14897,14900],{},[103,14898,14899],{},"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.",[164,14902,14903,14906,14909,14912],{},[167,14904,14905],{},"Abbreviated assessment or targeted questionnaire",[167,14907,14908],{},"Biennial reassessment (every two years)",[167,14910,14911],{},"Standard contract terms with security addendum",[167,14913,14914],{},"Reassess earlier if the vendor's scope of access changes",[37,14916,14917,14920],{},[103,14918,14919],{},"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.",[164,14922,14923,14926,14929],{},[167,14924,14925],{},"Self-attestation or security waiver",[167,14927,14928],{},"Reassess on contract renewal",[167,14930,14931],{},"Standard procurement terms, no additional security clauses required",[37,14933,14934,14935,14937],{},"The tiering decision should be documented in your ",[40,14936,5283],{"href":12437}," 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.",[560,14939,14941],{"id":14940},"what-vendor-assessment-tools-and-questionnaires-are-available","What vendor assessment tools and questionnaires are available?",[37,14943,14944],{},"Choosing the right assessment tool depends on the vendor's risk tier, your industry, and the depth of information you need.",[37,14946,14947,14950],{},[103,14948,14949],{},"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,14952,14953,14956],{},[103,14954,14955],{},"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,14958,14959,14962],{},[103,14960,14961],{},"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,14964,14965,14968],{},[103,14966,14967],{},"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,14970,14971,14974,14975,14979,14980,14982],{},[103,14972,14973],{},"Direct review of compliance reports"," — reviewing a vendor's ",[40,14976,14978],{"href":14977},"\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 ",[40,14981,43],{"href":42}," 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.",[560,14984,14986],{"id":14985},"how-do-you-handle-vendor-offboarding-and-incident-response","How do you handle vendor offboarding and incident response?",[37,14988,14989],{},"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,14991,14992,14995],{},[103,14993,14994],{},"Vendor offboarding"," — terminating a vendor relationship requires deliberate steps to protect your data and systems:",[164,14997,14998,15004,15010,15016,15025],{},[167,14999,15000,15003],{},[103,15001,15002],{},"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).",[167,15005,15006,15009],{},[103,15007,15008],{},"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.",[167,15011,15012,15015],{},[103,15013,15014],{},"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.",[167,15017,15018,15021,15022,15024],{},[103,15019,15020],{},"Risk register update"," — update your ",[40,15023,5283],{"href":12437}," to reflect the terminated relationship and document any residual risks, such as data that was processed during the engagement.",[167,15026,15027,15030],{},[103,15028,15029],{},"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,15032,15033,15036],{},[103,15034,15035],{},"Vendor-side breach response"," — your contracts and BAAs should establish clear expectations for what happens when a vendor experiences a security incident:",[164,15038,15039,15045,15054,15060],{},[167,15040,15041,15044],{},[103,15042,15043],{},"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.",[167,15046,15047,15050,15051,15053],{},[103,15048,15049],{},"Cooperation requirements"," — the vendor should be contractually obligated to cooperate with your ",[40,15052,13314],{"href":9362}," investigation, including providing forensic evidence, access logs, and impact assessments.",[167,15055,15056,15059],{},[103,15057,15058],{},"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.",[167,15061,15062,15065],{},[103,15063,15064],{},"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,15067,15068],{},"A well-defined vendor offboarding and incident response process reduces the risk of lingering access, orphaned data, and confused responsibilities when the unexpected happens.",[560,15070,15072],{"id":15071},"how-does-episki-help-with-vendor-risk-management","How does episki help with vendor risk management?",[37,15074,15075,15076,242],{},"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 ",[40,15077,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":15079},[15080],{"id":14505,"depth":428,"text":14506,"children":15081},[15082,15083,15084,15085,15086,15087,15088,15089,15090],{"id":14512,"depth":963,"text":14513},{"id":14546,"depth":963,"text":14547},{"id":14655,"depth":963,"text":14656},{"id":14711,"depth":963,"text":14712},{"id":14732,"depth":963,"text":14733},{"id":14844,"depth":963,"text":14845},{"id":14940,"depth":963,"text":14941},{"id":14985,"depth":963,"text":14986},{"id":15071,"depth":963,"text":15072},{},[6070,515,6073],[14495,6697,15094,2698],"baa",{"title":15096,"description":15097},"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":15101,"title":15102,"body":15103,"description":427,"extension":460,"lastUpdated":979,"meta":15269,"navigation":497,"path":15270,"relatedFrameworks":15271,"relatedTerms":15272,"seo":15274,"slug":15277,"stem":15278,"term":15108,"__hash__":15279},"glossary\u002F8.glossary\u002Fvulnerability-management.md","Vulnerability Management",{"type":29,"value":15104,"toc":15260},[15105,15109,15112,15116,15119,15154,15158,15161,15188,15192,15218,15222,15225,15251,15255],[32,15106,15108],{"id":15107},"what-is-vulnerability-management","What is Vulnerability Management?",[37,15110,15111],{},"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.",[560,15113,15115],{"id":15114},"what-is-the-vulnerability-management-lifecycle","What is the vulnerability management lifecycle?",[37,15117,15118],{},"An effective program follows a repeating cycle:",[1446,15120,15121,15127,15133,15138,15143,15148],{},[167,15122,15123,15126],{},[103,15124,15125],{},"Asset discovery"," — maintain an accurate inventory of all hardware, software, and cloud resources in scope",[167,15128,15129,15132],{},[103,15130,15131],{},"Vulnerability scanning"," — use automated tools to detect known vulnerabilities across your environment on a regular schedule",[167,15134,15135,15137],{},[103,15136,7601],{}," — rank findings by severity (CVSS score), exploitability, asset criticality, and business context — not every \"critical\" CVE is critical to your organization",[167,15139,15140,15142],{},[103,15141,12491],{}," — apply patches, configuration changes, or compensating controls to address vulnerabilities within defined SLAs",[167,15144,15145,15147],{},[103,15146,12618],{}," — rescan to confirm that remediation was effective and didn't introduce new issues",[167,15149,15150,15153],{},[103,15151,15152],{},"Reporting"," — track metrics like mean time to remediate (MTTR), vulnerability aging, and coverage rates",[560,15155,15157],{"id":15156},"how-do-compliance-frameworks-address-vulnerability-management","How do compliance frameworks address vulnerability management?",[37,15159,15160],{},"Most security frameworks require a formal vulnerability management program:",[164,15162,15163,15168,15173,15178,15183],{},[167,15164,15165,15167],{},[103,15166,5708],{}," — Requirement 6.3 requires patching critical vulnerabilities within defined timeframes; Requirement 11.3 requires internal and external vulnerability scanning",[167,15169,15170,15172],{},[103,15171,381],{}," — CC7.1 covers detection of vulnerabilities and CC8.1 addresses change management for remediation",[167,15174,15175,15177],{},[103,15176,43],{}," — A.8.8 (management of technical vulnerabilities) requires timely identification and remediation of vulnerabilities",[167,15179,15180,15182],{},[103,15181,5717],{}," — ID.RA (risk assessment) and PR.IP (information protection) directly relate to vulnerability identification and remediation",[167,15184,15185,15187],{},[103,15186,10708],{}," — RA.L2-3.11.2 requires remediation of vulnerabilities in accordance with risk assessments",[560,15189,15191],{"id":15190},"what-are-common-vulnerability-scanning-tools","What are common vulnerability scanning tools?",[164,15193,15194,15200,15206,15212],{},[167,15195,15196,15199],{},[103,15197,15198],{},"Infrastructure scanners"," — Nessus, Qualys, Rapid7 InsightVM for network and host-level vulnerabilities",[167,15201,15202,15205],{},[103,15203,15204],{},"Application scanners"," — OWASP ZAP, Burp Suite for web application vulnerabilities",[167,15207,15208,15211],{},[103,15209,15210],{},"Dependency scanners"," — Snyk, Dependabot, Trivy for software composition analysis (SCA)",[167,15213,15214,15217],{},[103,15215,15216],{},"Cloud security posture"," — AWS Inspector, Azure Defender, GCP Security Command Center for cloud misconfigurations",[560,15219,15221],{"id":15220},"what-are-sla-best-practices-for-vulnerability-management","What are SLA best practices for vulnerability management?",[37,15223,15224],{},"Define remediation timelines based on severity:",[164,15226,15227,15233,15239,15245],{},[167,15228,15229,15232],{},[103,15230,15231],{},"Critical"," — remediate within 24–72 hours",[167,15234,15235,15238],{},[103,15236,15237],{},"High"," — remediate within 7–14 days",[167,15240,15241,15244],{},[103,15242,15243],{},"Medium"," — remediate within 30 days",[167,15246,15247,15250],{},[103,15248,15249],{},"Low"," — remediate within 90 days or accept risk with documented justification",[560,15252,15254],{"id":15253},"how-does-episki-help-with-vulnerability-management","How does episki help with vulnerability management?",[37,15256,15257,15258,242],{},"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 ",[40,15259,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":15261},[15262],{"id":15107,"depth":428,"text":15108,"children":15263},[15264,15265,15266,15267,15268],{"id":15114,"depth":963,"text":15115},{"id":15156,"depth":963,"text":15157},{"id":15190,"depth":963,"text":15191},{"id":15220,"depth":963,"text":15221},{"id":15253,"depth":963,"text":15254},{},"\u002Fglossary\u002Fvulnerability-management",[6070,515,6072,6073,6069],[8888,7430,2386,15273],"web-application-security",{"title":15275,"description":15276},"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":15281,"title":15282,"body":15283,"description":427,"extension":460,"lastUpdated":979,"meta":15406,"navigation":497,"path":15407,"relatedFrameworks":15408,"relatedTerms":15409,"seo":15410,"slug":15273,"stem":15413,"term":15288,"__hash__":15414},"glossary\u002F8.glossary\u002Fweb-application-security.md","Web Application Security",{"type":29,"value":15284,"toc":15398},[15285,15289,15292,15296,15299,15337,15341,15363,15367,15389,15393],[32,15286,15288],{"id":15287},"what-is-web-application-security","What is Web Application Security?",[37,15290,15291],{},"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.",[560,15293,15295],{"id":15294},"what-are-common-web-application-threats","What are common web application threats?",[37,15297,15298],{},"The OWASP Top 10 provides a widely recognized list of the most critical web application security risks:",[164,15300,15301,15307,15313,15319,15325,15331],{},[167,15302,15303,15306],{},[103,15304,15305],{},"Injection attacks"," — including SQL injection, where attackers insert malicious code through input fields to manipulate databases",[167,15308,15309,15312],{},[103,15310,15311],{},"Cross-site scripting (XSS)"," — injecting malicious scripts into web pages viewed by other users",[167,15314,15315,15318],{},[103,15316,15317],{},"Broken authentication"," — weaknesses in authentication mechanisms that allow unauthorized access",[167,15320,15321,15324],{},[103,15322,15323],{},"Insecure direct object references"," — exposing internal implementation objects through URLs or parameters",[167,15326,15327,15330],{},[103,15328,15329],{},"Security misconfiguration"," — default credentials, unnecessary features enabled, or missing security headers",[167,15332,15333,15336],{},[103,15334,15335],{},"Cross-site request forgery (CSRF)"," — tricking authenticated users into performing unintended actions",[560,15338,15340],{"id":15339},"how-do-compliance-frameworks-address-web-application-security","How do compliance frameworks address web application security?",[164,15342,15343,15348,15353,15358],{},[167,15344,15345,15347],{},[103,15346,5708],{}," — Requirement 6 addresses secure development practices and web application firewalls for applications handling cardholder data",[167,15349,15350,15352],{},[103,15351,381],{}," — CC7.1 and CC8.1 cover vulnerability management and change management for applications",[167,15354,15355,15357],{},[103,15356,43],{}," — A.8.25 through A.8.28 address secure development lifecycle, testing, and application security",[167,15359,15360,15362],{},[103,15361,5717],{}," — PR.IP covers security in development and information protection processes",[560,15364,15366],{"id":15365},"what-are-web-application-defense-strategies","What are web application defense strategies?",[164,15368,15369,15372,15375,15378,15383,15386],{},[167,15370,15371],{},"Implement a secure development lifecycle (SDLC) with security reviews at each stage",[167,15373,15374],{},"Use static application security testing (SAST) and dynamic application security testing (DAST) in CI\u002FCD pipelines",[167,15376,15377],{},"Deploy a web application firewall (WAF) to filter malicious traffic",[167,15379,12100,15380,15382],{},[40,15381,8865],{"href":8864}," focused on application-layer vulnerabilities",[167,15384,15385],{},"Keep application frameworks and dependencies patched and up to date",[167,15387,15388],{},"Validate and sanitize all user input on the server side",[560,15390,15392],{"id":15391},"how-does-episki-help-with-web-application-security","How does episki help with web application security?",[37,15394,15395,15396,242],{},"episki tracks web application security controls, manages vulnerability remediation workflows, and documents security testing evidence for auditors. Learn more on our ",[40,15397,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":15399},[15400],{"id":15287,"depth":428,"text":15288,"children":15401},[15402,15403,15404,15405],{"id":15294,"depth":963,"text":15295},{"id":15339,"depth":963,"text":15340},{"id":15365,"depth":963,"text":15366},{"id":15391,"depth":963,"text":15392},{},"\u002Fglossary\u002Fweb-application-security",[6070,515,6072,6073],[8888,8892,6018,15277],{"title":15411,"description":15412},"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",{"id":15416,"title":15417,"body":15418,"description":427,"extension":460,"lastUpdated":979,"meta":15529,"navigation":497,"path":15530,"relatedFrameworks":15531,"relatedTerms":15532,"seo":15533,"slug":15536,"stem":15537,"term":15423,"__hash__":15538},"glossary\u002F8.glossary\u002Fworkforce-security.md","Workforce Security",{"type":29,"value":15419,"toc":15521},[15420,15424,15427,15431,15463,15467,15484,15488,15512,15516],[32,15421,15423],{"id":15422},"what-is-workforce-security","What is Workforce Security?",[37,15425,15426],{},"Workforce security refers to the policies, procedures, and controls that ensure employees, contractors, and other workforce members handle sensitive information responsibly and securely. It encompasses the full employment lifecycle — from hiring and onboarding through ongoing access management to termination and offboarding.",[560,15428,15430],{"id":15429},"what-are-the-key-components-of-workforce-security","What are the key components of workforce security?",[164,15432,15433,15439,15445,15451,15457],{},[167,15434,15435,15438],{},[103,15436,15437],{},"Background checks"," — verifying the identity, qualifications, and history of new hires before granting access to sensitive systems",[167,15440,15441,15444],{},[103,15442,15443],{},"Security awareness training"," — educating the workforce on security policies, threats, and their responsibilities",[167,15446,15447,15450],{},[103,15448,15449],{},"Access management"," — assigning appropriate access based on role and revoking it when no longer needed",[167,15452,15453,15456],{},[103,15454,15455],{},"Acceptable use policies"," — defining what constitutes proper use of organizational systems and data",[167,15458,15459,15462],{},[103,15460,15461],{},"Termination procedures"," — ensuring timely and complete access revocation when workforce members depart",[560,15464,15466],{"id":15465},"how-do-compliance-frameworks-address-workforce-security","How do compliance frameworks address workforce security?",[164,15468,15469,15474,15479],{},[167,15470,15471,15473],{},[103,15472,5694],{}," — the Security Rule (45 CFR 164.308(a)(3)) explicitly requires workforce security controls including authorization and supervision, clearance procedures, and termination procedures",[167,15475,15476,15478],{},[103,15477,381],{}," — CC1.4 and CC6.2 address human resource security including hiring, training, and termination",[167,15480,15481,15483],{},[103,15482,43],{}," — A.6.1 through A.6.5 cover screening, terms of employment, awareness training, disciplinary processes, and post-employment responsibilities",[560,15485,15487],{"id":15486},"what-are-best-practices-for-workforce-security","What are best practices for workforce security?",[164,15489,15490,15493,15496,15503,15509],{},[167,15491,15492],{},"Conduct background checks proportional to the sensitivity of the role",[167,15494,15495],{},"Require security awareness training at hire and annually thereafter",[167,15497,15498,15499,15502],{},"Implement role-based access that follows the ",[40,15500,15501],{"href":11090},"least privilege"," principle",[167,15504,15505,15506,15508],{},"Document and enforce termination and ",[40,15507,12361],{"href":12355}," checklists",[167,15510,15511],{},"Review workforce security policies annually and after significant organizational changes",[560,15513,15515],{"id":15514},"how-does-episki-help-with-workforce-security","How does episki help with workforce security?",[37,15517,15518,15519,242],{},"episki tracks workforce security controls, manages training completion records, and documents evidence of hiring and termination procedures for compliance audits. Learn more on our ",[40,15520,6051],{"href":6050},{"title":427,"searchDepth":428,"depth":428,"links":15522},[15523],{"id":15422,"depth":428,"text":15423,"children":15524},[15525,15526,15527,15528],{"id":15429,"depth":963,"text":15430},{"id":15465,"depth":963,"text":15466},{"id":15486,"depth":963,"text":15487},{"id":15514,"depth":963,"text":15515},{},"\u002Fglossary\u002Fworkforce-security",[6071,6070,515],[6080,13826,12361],{"title":15534,"description":15535},"What is Workforce Security? Definition & Compliance Guide","Workforce security refers to the policies and controls that ensure employees and contractors handle sensitive information responsibly and securely.","workforce-security","8.glossary\u002Fworkforce-security","na2bHZsChgoatdZZY7JsQpjSx5s4F6y3rTrEiRhd0js",[15540,16043,16621,16898,17516,18024],{"id":15541,"title":15542,"advantages":15543,"body":15565,"checklist":15975,"cta":15984,"description":427,"extension":460,"faq":15987,"hero":16005,"lastUpdated":495,"meta":16013,"name":10708,"navigation":497,"path":16014,"resources":16015,"seo":16028,"slug":6069,"stats":16031,"stem":16041,"__hash__":16042},"frameworks\u002F5.frameworks\u002Fcmmc.md","Cmmc",[15544,15551,15558],{"title":15545,"description":15546,"bullets":15547},"NIST 800-171 control mapping","Every CMMC Level 2 practice is linked to its NIST SP 800-171 source requirement with pre-written narratives.",[15548,15549,15550],"14 control families mapped to 110 security requirements","AI-drafted implementation narratives and testing procedures","Gap analysis highlights missing controls before your assessment",{"title":15552,"description":15553,"bullets":15554},"Assessment preparation workspace","Whether you self-assess or engage a C3PAO, episki organizes evidence and scoring in one place.",[15555,15556,15557],"POA&M tracking with 180-day close-out reminders","Scoring methodology aligned to DoD assessment guide","Assessor portal with scoped read-only access",{"title":15559,"description":15560,"bullets":15561},"Cross-framework reuse","Controls mapped to CMMC automatically satisfy overlapping NIST CSF, ISO 27001, and FedRAMP requirements.",[15562,15563,15564],"Unified control graph eliminates duplicate documentation","Evidence collected once, reused across every framework","Framework coverage dashboard shows gaps at a glance",{"type":29,"value":15566,"toc":15958},[15567,15571,15574,15577,15581,15588,15599,15610,15614,15622,15654,15657,15661,15672,15683,15687,15690,15707,15720,15723,15727,15730,15741,15748,15752,15766,15769,15773,15781,15807,15811,15838,15842,15850,15854,15862,15866,15874,15878,15881,15919,15923,15955],[32,15568,15570],{"id":15569},"what-is-cmmc","What is CMMC?",[37,15572,15573],{},"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,15575,15576],{},"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.",[560,15578,15580],{"id":15579},"cmmc-10-to-cmmc-20","CMMC 1.0 to CMMC 2.0",[37,15582,15583,15584,15587],{},"The first version of CMMC — sometimes called CMMC 1.0 — was announced in January 2020. It had ",[103,15585,15586],{},"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,15589,15590,15591,15594,15595,15598],{},"In November 2021 the DoD announced ",[103,15592,15593],{},"CMMC 2.0",", a streamlined successor. CMMC 2.0 collapsed the five levels into ",[103,15596,15597],{},"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,15600,15601,15602,15605,15606,15609],{},"The CMMC 2.0 program rule (32 CFR Part 170) was published in the Federal Register on October 15, 2024, and took effect on ",[103,15603,15604],{},"December 16, 2024",". The companion DFARS rule (48 CFR) was published on September 10, 2025, and took effect on ",[103,15607,15608],{},"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.",[560,15611,15613],{"id":15612},"the-three-cmmc-levels","The three CMMC levels",[37,15615,15616,15617,15621],{},"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. ",[40,15618,15620],{"href":15619},"\u002Fframeworks\u002Fcmmc\u002Flevels","See the full breakdown of CMMC levels"," for control counts, assessment types, and scoping rules.",[164,15623,15624,15634,15644],{},[167,15625,15626,15629,15630,15633],{},[103,15627,15628],{},"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 ",[103,15631,15632],{},"annual self-assessment"," with a senior official affirming the results in the Supplier Performance Risk System (SPRS).",[167,15635,15636,15639,15640,15643],{},[103,15637,15638],{},"Level 2 — Advanced."," Protects Controlled Unclassified Information (CUI). It requires all ",[103,15641,15642],{},"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.",[167,15645,15646,15649,15650,15653],{},[103,15647,15648],{},"Level 3 — Expert."," Reserved for the most sensitive DoD programs where advanced persistent threats are a credible risk. It includes every Level 2 requirement ",[103,15651,15652],{},"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,15655,15656],{},"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.",[560,15658,15660],{"id":15659},"nist-sp-800-171-is-the-heart-of-cmmc","NIST SP 800-171 is the heart of CMMC",[37,15662,15663,15664,15667,15668,15671],{},"CMMC Level 2 is a ",[103,15665,15666],{},"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 ",[40,15669,15670],{"href":12208},"NIST"," SP 800-171 compliance since 2017 did not have to start over.",[37,15673,15674,15675,15679,15680,15682],{},"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. ",[40,15676,15678],{"href":15677},"\u002Fframeworks\u002Fcmmc\u002Fnist-800-171-mapping","See the detailed NIST SP 800-171 mapping"," for the full control family breakdown and cross-framework overlap with ",[40,15681,5717],{"href":5716}," and ISO 27001.",[560,15684,15686],{"id":15685},"who-needs-cmmc","Who needs CMMC?",[37,15688,15689],{},"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:",[164,15691,15692,15695,15698,15701,15704],{},[167,15693,15694],{},"Prime contractors holding contracts directly with the DoD",[167,15696,15697],{},"Subcontractors at every tier in the supply chain",[167,15699,15700],{},"Cloud service providers hosting DoD contractor data",[167,15702,15703],{},"Managed service providers and IT vendors with access to FCI or CUI",[167,15705,15706],{},"Foreign suppliers in the defense industrial base handling covered information",[37,15708,15709,15710,15714,15715,15719],{},"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. ",[40,15711,15713],{"href":15712},"\u002Fframeworks\u002Fcmmc\u002Fwho-needs-cmmc","See who needs CMMC"," for detailed scoping guidance, and our ",[40,15716,15718],{"href":15717},"\u002Findustry\u002Fgovernment","government industry page"," for broader public-sector compliance context.",[37,15721,15722],{},"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.",[560,15724,15726],{"id":15725},"the-cmmc-assessment-process","The CMMC assessment process",[37,15728,15729],{},"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,15731,15732,15733,15736,15737,15740],{},"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 ",[103,15734,15735],{},"88 or above"," with remaining gaps documented in a Plan of Action and Milestones (POA&M) yields a ",[103,15738,15739],{},"conditional"," certification with a 180-day remediation window. A score below 88 yields no certification at all.",[37,15742,15743,15747],{},[40,15744,15746],{"href":15745},"\u002Fframeworks\u002Fcmmc\u002Fassessment-process","See the full CMMC assessment process"," for scoring details, POA&M rules, and what you can and cannot defer.",[560,15749,15751],{"id":15750},"c3paos-and-certified-assessors","C3PAOs and certified assessors",[37,15753,15754,15755,15758,15759,414,15762,15765],{},"Third-party CMMC assessments are conducted by ",[103,15756,15757],{},"CMMC Third-Party Assessment Organizations (C3PAOs)"," accredited by the Cyber AB (the Cyber Accreditation Body, formerly the CMMC Accreditation Body). C3PAOs employ ",[103,15760,15761],{},"Certified CMMC Assessors (CCAs)",[103,15763,15764],{},"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,15767,15768],{},"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.",[560,15770,15772],{"id":15771},"cmmc-implementation-timeline","CMMC implementation timeline",[37,15774,15775,15776,15780],{},"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. ",[40,15777,15779],{"href":15778},"\u002Fframeworks\u002Fcmmc\u002Fimplementation-timeline","See the full CMMC implementation timeline"," for dates and milestones.",[164,15782,15783,15789,15795,15801],{},[167,15784,15785,15788],{},[103,15786,15787],{},"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.",[167,15790,15791,15794],{},[103,15792,15793],{},"Phase 2 (November 2026 – November 2027)."," CMMC Level 2 C3PAO certification requirements expand significantly. Level 3 requirements begin appearing in select solicitations.",[167,15796,15797,15800],{},[103,15798,15799],{},"Phase 3 (November 2027 – November 2028)."," CMMC Level 2 and Level 3 requirements appear broadly across applicable DoD contracts.",[167,15802,15803,15806],{},[103,15804,15805],{},"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.",[560,15808,15810],{"id":15809},"cmmc-and-dfars","CMMC and DFARS",[37,15812,15813,15814,15817,15818,414,15821,15824,15825,15828,15829,15833,15834,242],{},"CMMC is the certification. DFARS is the contractual mechanism that makes the certification binding. ",[103,15815,15816],{},"DFARS 252.204-7012"," has required safeguarding of covered defense information and rapid incident reporting since 2017. ",[103,15819,15820],{},"DFARS 252.204-7019",[103,15822,15823],{},"-7020"," added the requirement to post NIST SP 800-171 assessment scores to SPRS. ",[103,15826,15827],{},"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. ",[40,15830,15832],{"href":15831},"\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 ",[40,15835,15837],{"href":15836},"\u002Fnow\u002Fcompliance-framework-comparison","compliance framework comparison",[560,15839,15841],{"id":15840},"self-assessment-vs-third-party-assessment","Self-assessment vs third-party assessment",[37,15843,15844,15845,15849],{},"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. ",[40,15846,15848],{"href":15847},"\u002Fframeworks\u002Fcmmc\u002Fself-assessment-vs-third-party","Compare CMMC self-assessment vs third-party"," to decide which applies to you and how to budget.",[560,15851,15853],{"id":15852},"handling-cui-the-cmmc-way","Handling CUI the CMMC way",[37,15855,15856,15857,15861],{},"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. ",[40,15858,15860],{"href":15859},"\u002Fframeworks\u002Fcmmc\u002Fcui-handling","See CUI handling under CMMC"," for marking rules, scoping guidance, and common mistakes.",[560,15863,15865],{"id":15864},"subcontractor-requirements","Subcontractor requirements",[37,15867,15868,15869,15873],{},"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. ",[40,15870,15872],{"href":15871},"\u002Fframeworks\u002Fcmmc\u002Fsubcontractor-requirements","See CMMC subcontractor requirements"," for the full flow-down model and how to reduce the burden.",[560,15875,15877],{"id":15876},"getting-cmmc-ready","Getting CMMC ready",[37,15879,15880],{},"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:",[1446,15882,15883,15889,15895,15901,15907,15913],{},[167,15884,15885,15888],{},[103,15886,15887],{},"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.",[167,15890,15891,15894],{},[103,15892,15893],{},"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.",[167,15896,15897,15900],{},[103,15898,15899],{},"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.",[167,15902,15903,15906],{},[103,15904,15905],{},"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.",[167,15908,15909,15912],{},[103,15910,15911],{},"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.",[167,15914,15915,15918],{},[103,15916,15917],{},"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.",[560,15920,15922],{"id":15921},"common-cmmc-challenges","Common CMMC challenges",[164,15924,15925,15931,15937,15943,15949],{},[167,15926,15927,15930],{},[103,15928,15929],{},"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.",[167,15932,15933,15936],{},[103,15934,15935],{},"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.",[167,15938,15939,15942],{},[103,15940,15941],{},"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.",[167,15944,15945,15948],{},[103,15946,15947],{},"Subcontractor flow-down."," Primes must verify subcontractor CMMC status continuously, not once at onboarding.",[167,15950,15951,15954],{},[103,15952,15953],{},"Evidence organization."," A CMMC assessment can touch hundreds of evidence artifacts. Without a single source of truth, assessors burn billable hours chasing documents.",[37,15956,15957],{},"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":427,"searchDepth":428,"depth":428,"links":15959},[15960],{"id":15569,"depth":428,"text":15570,"children":15961},[15962,15963,15964,15965,15966,15967,15968,15969,15970,15971,15972,15973,15974],{"id":15579,"depth":963,"text":15580},{"id":15612,"depth":963,"text":15613},{"id":15659,"depth":963,"text":15660},{"id":15685,"depth":963,"text":15686},{"id":15725,"depth":963,"text":15726},{"id":15750,"depth":963,"text":15751},{"id":15771,"depth":963,"text":15772},{"id":15809,"depth":963,"text":15810},{"id":15840,"depth":963,"text":15841},{"id":15852,"depth":963,"text":15853},{"id":15864,"depth":963,"text":15865},{"id":15876,"depth":963,"text":15877},{"id":15921,"depth":963,"text":15922},{"title":15976,"description":15977,"items":15978},"CMMC readiness checklist inside episki","Everything is preloaded in your free trial so you can start scoping your assessment and closing gaps immediately.",[15979,15980,15981,15982,15983],"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":15985,"description":15986},"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":15988,"items":15989},"CMMC frequently asked questions",[15990,15993,15996,15999,16002],{"label":15991,"content":15992},"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":15994,"content":15995},"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":15997,"content":15998},"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":16000,"content":16001},"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":16003,"content":16004},"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":16006,"title":16007,"description":16008,"links":16009},"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.",[16010,16012],{"label":16011,"icon":486,"to":487},"Start CMMC trial",{"label":489,"icon":490,"color":491,"variant":492,"to":493,"target":494},{},"\u002Fframeworks\u002Fcmmc",{"headline":16016,"title":16016,"description":16017,"items":16018},"CMMC acceleration resources","Give leadership and contracting officers visibility into your cybersecurity posture at every stage.",[16019,16022,16025],{"title":16020,"description":16021},"Executive scorecard","Translate control work into CMMC readiness percentages and contract eligibility status.",{"title":16023,"description":16024},"Assessment readiness kit","Pre-assessment checklist, evidence package review, and mock scoring aligned to DIBCAC methodology.",{"title":16026,"description":16027},"Subcontractor flow-down tracker","Monitor which subcontractors need their own CMMC certification and track their progress.",{"title":16029,"description":16030},"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.",[16032,16035,16038],{"value":16033,"description":16034},"3 maturity levels","Pre-mapped practices for Level 1, Level 2, and Level 3 with assessment-type guidance for each.",{"value":16036,"description":16037},"110 practices","Full NIST SP 800-171 Rev 2 control set mapped to CMMC Level 2 objectives out of the box.",{"value":16039,"description":16040},"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":16044,"title":16045,"advantages":16046,"body":16068,"checklist":16554,"cta":16563,"description":427,"extension":460,"faq":16566,"hero":16584,"lastUpdated":495,"meta":16592,"name":5694,"navigation":497,"path":5693,"resources":16593,"seo":16606,"slug":6071,"stats":16609,"stem":16619,"__hash__":16620},"frameworks\u002F5.frameworks\u002Fhipaa.md","Hipaa",[16047,16054,16061],{"title":16048,"description":16049,"bullets":16050},"Safeguards mapped to your stack","Every HIPAA standard comes with plain-language owners, SLAs, and tests.",[16051,16052,16053],"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":16055,"description":16056,"bullets":16057},"PHI-aware evidence locker","Secure uploads, access controls, and audit trails keep regulators satisfied.",[16058,16059,16060],"Granular permissions for internal and external reviewers","Automated retention and deletion policies","Download tracking and access audit trails",{"title":16062,"description":16063,"bullets":16064},"Vendor & incident workflows","Track BAAs, vendor attestations, and incidents from discovery to closure.",[16065,16066,16067],"BAA repository tied to vendor risk levels","Incident response runbooks with reminders","Post-incident reports aligned to HIPAA timelines",{"type":29,"value":16069,"toc":16527},[16070,16074,16077,16088,16091,16095,16098,16141,16145,16148,16153,16157,16160,16164,16171,16191,16194,16198,16205,16212,16216,16219,16223,16226,16229,16242,16246,16249,16252,16256,16274,16278,16290,16294,16297,16304,16308,16311,16314,16321,16325,16332,16335,16339,16346,16349,16372,16376,16379,16382,16388,16392,16395,16421,16424,16427,16431,16434,16452,16455,16459,16465,16469,16472,16501,16509,16513,16516,16524],[32,16071,16073],{"id":16072},"what-is-hipaa","What is HIPAA?",[37,16075,16076],{},"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,16078,16079,16080,16083,16084,16087],{},"At its core, the law establishes national standards that protect sensitive patient information — known as ",[40,16081,16082],{"href":14820},"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 ",[40,16085,16086],{"href":11484},"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,16089,16090],{},"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,16092,16094],{"id":16093},"a-brief-history-of-hipaa","A brief history of HIPAA",[37,16096,16097],{},"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.",[164,16099,16100,16106,16112,16118,16129,16135],{},[167,16101,16102,16105],{},[103,16103,16104],{},"1996"," — Congress passes HIPAA, directing HHS to issue regulations on privacy, security, and electronic transactions.",[167,16107,16108,16111],{},[103,16109,16110],{},"2000"," — The HIPAA Privacy Rule is published; it takes full effect in 2003.",[167,16113,16114,16117],{},[103,16115,16116],{},"2003"," — The HIPAA Security Rule is finalized, with compliance required by 2005 for most entities.",[167,16119,16120,16123,16124,16128],{},[103,16121,16122],{},"2009"," — The Health Information Technology for Economic and Clinical Health Act (",[40,16125,16127],{"href":16126},"\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.",[167,16130,16131,16134],{},[103,16132,16133],{},"2013"," — The HIPAA Omnibus Rule implements HITECH and further strengthens HIPAA enforcement, fines, and patient rights.",[167,16136,16137,16140],{},[103,16138,16139],{},"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.",[560,16142,16144],{"id":16143},"hitech-and-the-omnibus-rule","HITECH and the Omnibus Rule",[37,16146,16147],{},"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,16149,16150,16151,242],{},"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 ",[40,16152,16144],{"href":16126},[32,16154,16156],{"id":16155},"who-hipaa-applies-to","Who HIPAA applies to",[37,16158,16159],{},"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.",[560,16161,16163],{"id":16162},"covered-entities","Covered entities",[37,16165,4072,16166,16170],{},[40,16167,16169],{"href":16168},"\u002Fglossary\u002Fcovered-entity","covered entity"," is any of the following:",[164,16172,16173,16179,16185],{},[167,16174,16175,16178],{},[103,16176,16177],{},"Health plans"," — health insurance companies, HMOs, employer-sponsored group health plans, government programs like Medicare and Medicaid, and long-term care insurers.",[167,16180,16181,16184],{},[103,16182,16183],{},"Healthcare providers"," — hospitals, clinics, physician practices, dentists, pharmacies, psychologists, and any other provider that transmits health information electronically for billing or eligibility purposes.",[167,16186,16187,16190],{},[103,16188,16189],{},"Healthcare clearinghouses"," — entities that process nonstandard health information into standard formats (or vice versa), such as billing services and repricing companies.",[37,16192,16193],{},"If your organization directly delivers healthcare or finances it, you are almost certainly a covered entity.",[560,16195,16197],{"id":16196},"business-associates","Business associates",[37,16199,4072,16200,16204],{},[40,16201,16203],{"href":16202},"\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,16206,16207,16208,16211],{},"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 ",[40,16209,16210],{"href":14825},"business associate agreement"," with every upstream and downstream partner that touches PHI is non-negotiable.",[560,16213,16215],{"id":16214},"who-is-not-covered-by-hipaa","Who is not covered by HIPAA?",[37,16217,16218],{},"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,16220,16222],{"id":16221},"the-hipaa-privacy-rule","The HIPAA Privacy Rule",[37,16224,16225],{},"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,16227,16228],{},"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,16230,16231,16232,16236,16237,16241],{},"For a comprehensive walkthrough of the HIPAA Privacy Rule, permitted disclosures, and patient rights, read the dedicated ",[40,16233,16235],{"href":16234},"\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 ",[40,16238,16240],{"href":16239},"\u002Fframeworks\u002Fhipaa\u002Fminimum-necessary-rule","minimum necessary rule"," page.",[32,16243,16245],{"id":16244},"the-hipaa-security-rule","The HIPAA Security Rule",[37,16247,16248],{},"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,16250,16251],{},"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.",[560,16253,16255],{"id":16254},"administrative-safeguards","Administrative safeguards",[37,16257,16258,16259,16263,16264,16268,16269,16273],{},"Administrative safeguards are the policies, procedures, and organizational measures that govern your HIPAA program. They include security management processes, a designated security official, ",[40,16260,16262],{"href":16261},"\u002Fframeworks\u002Fhipaa\u002Fworkforce-training","workforce training",", a ",[40,16265,16267],{"href":16266},"\u002Fframeworks\u002Fhipaa\u002Fsanctions-policy","sanctions policy"," for workforce violations, access management, ",[40,16270,16272],{"href":16271},"\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.",[560,16275,16277],{"id":16276},"physical-safeguards","Physical safeguards",[37,16279,16280,16281,9079,16285,16289],{},"Physical safeguards protect the facilities, workstations, devices, and media that house ePHI. This category covers ",[40,16282,16284],{"href":16283},"\u002Fframeworks\u002Fhipaa\u002Ffacility-access-controls","facility access controls",[40,16286,16288],{"href":16287},"\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.",[560,16291,16293],{"id":16292},"technical-safeguards","Technical safeguards",[37,16295,16296],{},"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,16298,16299,16300,16303],{},"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 ",[40,16301,16302],{"href":5698},"HIPAA Security Rule"," guide.",[32,16305,16307],{"id":16306},"the-hipaa-breach-notification-rule","The HIPAA Breach Notification Rule",[37,16309,16310],{},"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,16312,16313],{},"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,16315,16316,16317,16303],{},"For full details on timelines, content requirements, and documentation expectations, see the ",[40,16318,16320],{"href":16319},"\u002Fframeworks\u002Fhipaa\u002Fbreach-notification","HIPAA Breach Notification Rule",[32,16322,16324],{"id":16323},"business-associate-agreements","Business associate agreements",[37,16326,16327,16328,16331],{},"No PHI should ever leave a covered entity — or a business associate — without a properly executed BAA in place. A ",[40,16329,16210],{"href":16330},"\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,16333,16334],{},"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,16336,16338],{"id":16337},"hipaa-compliance-checklist","HIPAA compliance checklist",[37,16340,16341,16342,16345],{},"Translating the regulatory language into day-to-day operations is where most programs struggle. The ",[40,16343,16338],{"href":16344},"\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,16347,16348],{},"At a high level, a complete HIPAA program includes:",[164,16350,16351,16354,16357,16360,16363,16366,16369],{},[167,16352,16353],{},"A current risk analysis and documented risk management plan.",[167,16355,16356],{},"Written policies and procedures covering Privacy, Security, and Breach Notification obligations.",[167,16358,16359],{},"A signed BAA with every vendor, subcontractor, and customer that exchanges PHI.",[167,16361,16362],{},"Workforce training at hire and at least annually thereafter, with documented completion.",[167,16364,16365],{},"Access control, audit logging, encryption, and contingency planning for every system that touches ePHI.",[167,16367,16368],{},"An incident response runbook aligned to the Breach Notification Rule.",[167,16370,16371],{},"Documentation retained for at least six years from creation or last effective date, whichever is later.",[32,16373,16375],{"id":16374},"hipaa-risk-analysis","HIPAA risk analysis",[37,16377,16378],{},"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,16380,16381],{},"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,16383,16384,16385,16303],{},"For a full breakdown of methodology, documentation requirements, and common pitfalls, read the ",[40,16386,16375],{"href":16387},"\u002Fframeworks\u002Fhipaa\u002Frisk-analysis",[32,16389,16391],{"id":16390},"penalties-and-enforcement","Penalties and enforcement",[37,16393,16394],{},"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.",[164,16396,16397,16403,16409,16415],{},[167,16398,16399,16402],{},[103,16400,16401],{},"Tier 1 — Unknowing violation"," — $100 to $50,000 per violation; annual cap $25,000 for identical violations.",[167,16404,16405,16408],{},[103,16406,16407],{},"Tier 2 — Reasonable cause"," — $1,000 to $50,000 per violation; annual cap $100,000.",[167,16410,16411,16414],{},[103,16412,16413],{},"Tier 3 — Willful neglect, corrected"," — $10,000 to $50,000 per violation; annual cap $250,000.",[167,16416,16417,16420],{},[103,16418,16419],{},"Tier 4 — Willful neglect, uncorrected"," — $50,000 per violation; annual cap $1.5 million per violation category.",[37,16422,16423],{},"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,16425,16426],{},"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,16428,16430],{"id":16429},"hipaa-vs-hitech-vs-hitrust","HIPAA vs HITECH vs HITRUST",[37,16432,16433],{},"These three acronyms sit close together in healthcare conversations and are often conflated. They are related but distinct.",[164,16435,16436,16441,16446],{},[167,16437,16438,16440],{},[103,16439,5694],{}," is the underlying federal law and its implementing regulations (Privacy, Security, Breach Notification, and Enforcement Rules). HIPAA defines the legal obligations.",[167,16442,16443,16445],{},[103,16444,16127],{}," 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.",[167,16447,16448,16451],{},[103,16449,16450],{},"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,16453,16454],{},"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.",[560,16456,16458],{"id":16457},"hipaa-and-soc-2","HIPAA and SOC 2",[37,16460,16461,16462,16464],{},"Many SaaS companies pursue ",[40,16463,381],{"href":380}," 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,16466,16468],{"id":16467},"getting-hipaa-compliant","Getting HIPAA compliant",[37,16470,16471],{},"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.",[1446,16473,16474,16477,16480,16483,16486,16489,16492,16495,16498],{},[167,16475,16476],{},"Confirm your status as a covered entity, business associate, or both, and inventory the PHI you handle today.",[167,16478,16479],{},"Appoint a security official and a privacy official (the same person may hold both roles at small companies).",[167,16481,16482],{},"Conduct a risk analysis scoped to every system that creates, receives, maintains, or transmits ePHI.",[167,16484,16485],{},"Implement the administrative, physical, and technical safeguards required by the Security Rule, informed by your risk analysis.",[167,16487,16488],{},"Draft and publish policies and procedures covering Privacy, Security, and Breach Notification obligations.",[167,16490,16491],{},"Execute BAAs with every vendor that touches PHI, and require a signed BAA before onboarding any new customer that qualifies as a covered entity.",[167,16493,16494],{},"Deliver workforce training at hire and annually thereafter, and document completion.",[167,16496,16497],{},"Stand up an incident response runbook aligned to the Breach Notification Rule.",[167,16499,16500],{},"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,16502,16503,16504,16508],{},"For companies operating in the broader ",[40,16505,16507],{"href":16506},"\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,16510,16512],{"id":16511},"how-episki-helps-with-hipaa-compliance","How episki helps with HIPAA compliance",[37,16514,16515],{},"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,16517,16518,16519,16523],{},"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 ",[40,16520,16522],{"href":16521},"\u002Fnow\u002Fhipaa-compliance-healthtech","HIPAA for healthtech"," playbook for a closer look at how modern SaaS companies operate HIPAA at startup speed.",[37,16525,16526],{},"Ready to tighten your HIPAA program? Start a free trial or book a demo from the top of this page.",{"title":427,"searchDepth":428,"depth":428,"links":16528},[16529,16530,16533,16538,16539,16544,16545,16546,16547,16548,16549,16552,16553],{"id":16072,"depth":428,"text":16073},{"id":16093,"depth":428,"text":16094,"children":16531},[16532],{"id":16143,"depth":963,"text":16144},{"id":16155,"depth":428,"text":16156,"children":16534},[16535,16536,16537],{"id":16162,"depth":963,"text":16163},{"id":16196,"depth":963,"text":16197},{"id":16214,"depth":963,"text":16215},{"id":16221,"depth":428,"text":16222},{"id":16244,"depth":428,"text":16245,"children":16540},[16541,16542,16543],{"id":16254,"depth":963,"text":16255},{"id":16276,"depth":963,"text":16277},{"id":16292,"depth":963,"text":16293},{"id":16306,"depth":428,"text":16307},{"id":16323,"depth":428,"text":16324},{"id":16337,"depth":428,"text":16338},{"id":16374,"depth":428,"text":16375},{"id":16390,"depth":428,"text":16391},{"id":16429,"depth":428,"text":16430,"children":16550},[16551],{"id":16457,"depth":963,"text":16458},{"id":16467,"depth":428,"text":16468},{"id":16511,"depth":428,"text":16512},{"title":16555,"description":16556,"items":16557},"HIPAA launch kit","Guided steps keep privacy, security, and ops in sync from day one.",[16558,16559,16560,16561,16562],"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":16564,"description":16565},"Launch HIPAA monitoring in minutes","Kick off the free trial and invite stakeholders before your next diligence call.",{"title":16567,"items":16568},"HIPAA compliance frequently asked questions",[16569,16572,16575,16578,16581],{"label":16570,"content":16571},"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":16573,"content":16574},"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":16576,"content":16577},"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":16579,"content":16580},"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":16582,"content":16583},"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":16585,"title":16586,"description":16587,"links":16588},"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.",[16589,16591],{"label":16590,"icon":486,"to":487},"Start HIPAA trial",{"label":489,"icon":490,"color":491,"variant":492,"to":493,"target":494},{},{"headline":16594,"title":16594,"description":16595,"items":16596},"HIPAA enablement","Keep leadership, customers, and partners aligned.",[16597,16600,16603],{"title":16598,"description":16599},"Board-ready posture report","Shows maturity score, risk trends, and upcoming audits.",{"title":16601,"description":16602},"Customer FAQ pack","Answers the most common HIPAA diligence questions.",{"title":16604,"description":16605},"Ops automation guide","Explains how to plug security tasks into existing tools.",{"title":16607,"description":16608},"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.",[16610,16613,16616],{"value":16611,"description":16612},"30-day rollout","Average time to production monitoring across safeguards.",{"value":16614,"description":16615},"PHI-safe sharing","Role-based portals keep sensitive documents organized and protected.",{"value":16617,"description":16618},"24\u002F7 alerts","Continuous monitoring for access, logging, and vendor risks.","5.frameworks\u002Fhipaa","9IldK-wXldOkZs8WFGmDWXYF8To1wETqwKkhsGGUW04",{"id":4,"title":5,"advantages":16622,"body":16629,"checklist":16873,"cta":16875,"description":427,"extension":460,"faq":16876,"hero":16883,"lastUpdated":495,"meta":16887,"name":43,"navigation":497,"path":498,"resources":16888,"seo":16893,"slug":515,"stats":16894,"stem":525,"__hash__":526},[16623,16625,16627],{"title":8,"description":9,"bullets":16624},[11,12,13],{"title":15,"description":16,"bullets":16626},[18,19,20],{"title":22,"description":23,"bullets":16628},[25,26,27],{"type":29,"value":16630,"toc":16855},[16631,16633,16639,16641,16643,16645,16647,16649,16651,16653,16655,16657,16663,16665,16667,16671,16673,16675,16679,16681,16685,16687,16691,16693,16697,16699,16701,16731,16735,16739,16741,16743,16745,16749,16751,16753,16755,16761,16763,16765,16769,16771,16773,16777,16779,16781,16799,16803,16805,16807,16811,16813,16815,16819,16821,16823,16837,16841,16843,16845,16851,16853],[32,16632,35],{"id":34},[37,16634,16635,44,16637,49],{},[40,16636,43],{"href":42},[40,16638,48],{"href":47},[37,16640,52],{},[37,16642,55],{},[37,16644,58],{},[32,16646,62],{"id":61},[37,16648,65],{},[37,16650,68],{},[37,16652,71],{},[32,16654,75],{"id":74},[37,16656,78],{},[37,16658,81,16659,86,16661,91],{},[40,16660,85],{"href":84},[40,16662,90],{"href":89},[32,16664,95],{"id":94},[37,16666,98],{},[37,16668,101,16669,106],{},[103,16670,105],{},[37,16672,109],{},[32,16674,113],{"id":112},[37,16676,116,16677,121],{},[40,16678,120],{"href":119},[37,16680,124],{},[37,16682,127,16683,132],{},[40,16684,131],{"href":130},[32,16686,136],{"id":135},[37,16688,139,16689,144],{},[40,16690,143],{"href":142},[37,16692,147],{},[37,16694,150,16695,155],{},[40,16696,154],{"href":153},[32,16698,159],{"id":158},[37,16700,162],{},[164,16702,16703,16707,16711,16715,16719,16723,16727],{},[167,16704,16705,172],{},[103,16706,171],{},[167,16708,16709,178],{},[103,16710,177],{},[167,16712,16713,184],{},[103,16714,183],{},[167,16716,16717,190],{},[103,16718,189],{},[167,16720,16721,196],{},[103,16722,195],{},[167,16724,16725,202],{},[103,16726,201],{},[167,16728,16729,208],{},[103,16730,207],{},[37,16732,211,16733,216],{},[40,16734,215],{"href":214},[37,16736,219,16737,224],{},[40,16738,223],{"href":222},[32,16740,228],{"id":227},[37,16742,231],{},[37,16744,234],{},[37,16746,237,16747,242],{},[40,16748,241],{"href":240},[32,16750,246],{"id":245},[37,16752,249],{},[37,16754,252],{},[37,16756,255,16757,260,16759,242],{},[40,16758,259],{"href":258},[40,16760,264],{"href":263},[32,16762,268],{"id":267},[37,16764,271],{},[37,16766,274,16767,279],{},[40,16768,278],{"href":277},[32,16770,283],{"id":282},[37,16772,286],{},[37,16774,289,16775,242],{},[40,16776,293],{"href":292},[32,16778,297],{"id":296},[37,16780,300],{},[164,16782,16783,16787,16791,16795],{},[167,16784,16785,308],{},[103,16786,307],{},[167,16788,16789,314],{},[103,16790,313],{},[167,16792,16793,320],{},[103,16794,319],{},[167,16796,16797,326],{},[103,16798,325],{},[37,16800,329,16801,333],{},[40,16802,332],{"href":84},[32,16804,337],{"id":336},[37,16806,340],{},[37,16808,343,16809,348],{},[40,16810,347],{"href":346},[32,16812,352],{"id":351},[37,16814,355],{},[37,16816,358,16817,363],{},[40,16818,362],{"href":361},[32,16820,367],{"id":366},[37,16822,370],{},[164,16824,16825,16831],{},[167,16826,16827,382],{},[103,16828,377,16829,242],{},[40,16830,381],{"href":380},[167,16832,16833,388,16835,393],{},[103,16834,387],{},[40,16836,392],{"href":391},[37,16838,396,16839,399],{},[40,16840,90],{"href":89},[32,16842,403],{"id":402},[37,16844,406],{},[37,16846,409,16847,414,16849,419],{},[40,16848,413],{"href":412},[40,16850,418],{"href":417},[37,16852,422],{},[37,16854,425],{},{"title":427,"searchDepth":428,"depth":428,"links":16856},[16857,16858,16859,16860,16861,16862,16863,16864,16865,16866,16867,16868,16869,16870,16871,16872],{"id":34,"depth":428,"text":35},{"id":61,"depth":428,"text":62},{"id":74,"depth":428,"text":75},{"id":94,"depth":428,"text":95},{"id":112,"depth":428,"text":113},{"id":135,"depth":428,"text":136},{"id":158,"depth":428,"text":159},{"id":227,"depth":428,"text":228},{"id":245,"depth":428,"text":246},{"id":267,"depth":428,"text":268},{"id":282,"depth":428,"text":283},{"id":296,"depth":428,"text":297},{"id":336,"depth":428,"text":337},{"id":351,"depth":428,"text":352},{"id":366,"depth":428,"text":367},{"id":402,"depth":428,"text":403},{"title":447,"description":448,"items":16874},[450,451,452,453,454,455,456],{"title":458,"description":459},{"title":462,"items":16877},[16878,16879,16880,16881,16882],{"label":465,"content":466},{"label":468,"content":469},{"label":471,"content":472},{"label":474,"content":475},{"label":477,"content":478},{"headline":480,"title":481,"description":482,"links":16884},[16885,16886],{"label":485,"icon":486,"to":487},{"label":489,"icon":490,"color":491,"variant":492,"to":493,"target":494},{},{"headline":500,"title":500,"description":501,"items":16889},[16890,16891,16892],{"title":504,"description":505},{"title":507,"description":508},{"title":510,"description":511},{"title":513,"description":514},[16895,16896,16897],{"value":120,"description":518},{"value":520,"description":521},{"value":523,"description":524},{"id":16899,"title":16900,"advantages":16901,"body":16923,"checklist":17449,"cta":17458,"description":427,"extension":460,"faq":17461,"hero":17478,"lastUpdated":495,"meta":17487,"name":5717,"navigation":497,"path":5716,"resources":17488,"seo":17501,"slug":6073,"stats":17504,"stem":17514,"__hash__":17515},"frameworks\u002F5.frameworks\u002Fnistcsf.md","Nistcsf",[16902,16909,16916],{"title":16903,"description":16904,"bullets":16905},"Tailored CSF roadmap","Start with opinionated baseline controls, then layer your own.",[16906,16907,16908],"Gap analysis highlights missing outcomes","Auto-generated improvement initiatives","Budget impact estimates for leadership",{"title":16910,"description":16911,"bullets":16912},"Continuous monitoring and AI ops","Stream alerts, detections, and incidents into CSF context.",[16913,16914,16915],"Connect SIEM, EDR, and cloud posture tools","AI summarizes incidents for exec updates","Workflows escalate unreviewed alerts",{"title":16917,"description":16918,"bullets":16919},"Board and customer alignment","Share progress externally with confidence.",[16920,16921,16922],"Customizable scorecards for customers or partners","Trend lines show quarter-over-quarter improvements","Trust room access with expiring links",{"type":29,"value":16924,"toc":17427},[16925,16929,16936,16939,16943,16950,16953,16957,16960,16970,16974,16977,16980,17018,17023,17027,17030,17033,17037,17046,17050,17060,17064,17074,17078,17088,17092,17101,17105,17115,17118,17122,17129,17155,17161,17165,17171,17174,17188,17191,17201,17205,17215,17232,17239,17243,17251,17257,17268,17272,17275,17322,17325,17329,17332,17364,17367,17370,17374,17377,17421,17424],[32,16926,16928],{"id":16927},"what-is-nist-csf","What is NIST CSF?",[37,16930,16931,16932,16935],{},"The NIST Cybersecurity Framework (NIST CSF) is a voluntary, outcome-based set of cybersecurity guidelines published by the ",[40,16933,16934],{"href":12208},"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,16937,16938],{},"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.",[560,16940,16942],{"id":16941},"nist-origin-and-executive-order-13636","NIST origin and Executive Order 13636",[37,16944,16945,16946,16949],{},"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 ",[103,16947,16948],{},"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,16951,16952],{},"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.",[560,16954,16956],{"id":16955},"the-evolution-of-nist-csf","The evolution of NIST CSF",[37,16958,16959],{},"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,16961,16962,16963,16965,16966,16969],{},"In February 2024, NIST published ",[103,16964,14796],{}," — 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 ",[103,16967,16968],{},"Govern",", reorganized several categories, and introduced a richer set of implementation resources including quick-start guides, informative references, and community profiles.",[32,16971,16973],{"id":16972},"nist-csf-20-changes","NIST CSF 2.0 changes",[37,16975,16976],{},"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,16978,16979],{},"Highlights of NIST CSF 2.0:",[164,16981,16982,16988,16994,17000,17012],{},[167,16983,16984,16987],{},[103,16985,16986],{},"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.",[167,16989,16990,16993],{},[103,16991,16992],{},"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.",[167,16995,16996,16999],{},[103,16997,16998],{},"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.",[167,17001,17002,17005,17006,17008,17009,17011],{},[103,17003,17004],{},"Improved implementation guidance"," — NIST CSF 2.0 ships with a companion CSF Reference Tool, searchable informative references mapping NIST CSF subcategories to ",[40,17007,7519],{"href":12208},", ISO 27001, CIS Controls, ",[40,17010,381],{"href":380},", and more.",[167,17013,17014,17017],{},[103,17015,17016],{},"Refreshed implementation tiers"," — the four-tier maturity model (Partial, Risk-Informed, Repeatable, Adaptive) now explicitly incorporates governance and supply chain considerations.",[37,17019,17020,17021,16303],{},"For a deep dive into every structural and categorical change between NIST CSF 1.1 and NIST CSF 2.0, see our ",[40,17022,16973],{"href":14840},[32,17024,17026],{"id":17025},"the-six-core-functions-of-nist-csf-20","The six core functions of NIST CSF 2.0",[37,17028,17029],{},"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,17031,17032],{},"The six NIST CSF 2.0 functions are:",[560,17034,17036],{"id":17035},"govern-gv","Govern (GV)",[37,17038,139,17039,17041,17042,242],{},[103,17040,16968],{}," 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: ",[40,17043,17045],{"href":17044},"\u002Fframeworks\u002Fnistcsf\u002Fgovern-function","NIST CSF Govern function",[560,17047,17049],{"id":17048},"identify-id","Identify (ID)",[37,17051,139,17052,17055,17056,242],{},[103,17053,17054],{},"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: ",[40,17057,17059],{"href":17058},"\u002Fframeworks\u002Fnistcsf\u002Fidentify-function","NIST CSF Identify function",[560,17061,17063],{"id":17062},"protect-pr","Protect (PR)",[37,17065,139,17066,17069,17070,242],{},[103,17067,17068],{},"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: ",[40,17071,17073],{"href":17072},"\u002Fframeworks\u002Fnistcsf\u002Fprotect-function","NIST CSF Protect function",[560,17075,17077],{"id":17076},"detect-de","Detect (DE)",[37,17079,139,17080,17083,17084,242],{},[103,17081,17082],{},"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: ",[40,17085,17087],{"href":17086},"\u002Fframeworks\u002Fnistcsf\u002Fdetect-function","NIST CSF Detect function",[560,17089,17091],{"id":17090},"respond-rs","Respond (RS)",[37,17093,139,17094,17096,17097,242],{},[103,17095,14453],{}," 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: ",[40,17098,17100],{"href":17099},"\u002Fframeworks\u002Fnistcsf\u002Frespond-function","NIST CSF Respond function",[560,17102,17104],{"id":17103},"recover-rc","Recover (RC)",[37,17106,139,17107,17110,17111,242],{},[103,17108,17109],{},"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: ",[40,17112,17114],{"href":17113},"\u002Fframeworks\u002Fnistcsf\u002Frecover-function","NIST CSF Recover function",[37,17116,17117],{},"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,17119,17121],{"id":17120},"nist-csf-implementation-tiers","NIST CSF implementation tiers",[37,17123,17124,17125,17128],{},"NIST CSF uses ",[103,17126,17127],{},"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.",[164,17130,17131,17137,17143,17149],{},[167,17132,17133,17136],{},[103,17134,17135],{},"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.",[167,17138,17139,17142],{},[103,17140,17141],{},"Tier 2 — Risk-Informed",": Risk management practices are approved by management but may not be established organization-wide. Cybersecurity activities consider organizational risk objectives.",[167,17144,17145,17148],{},[103,17146,17147],{},"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.",[167,17150,17151,17154],{},[103,17152,17153],{},"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,17156,17157,17158,16303],{},"For a complete walkthrough of each tier, including how to select a target tier and move between tiers, see our ",[40,17159,17121],{"href":17160},"\u002Fframeworks\u002Fnistcsf\u002Fimplementation-tiers",[32,17162,17164],{"id":17163},"nist-csf-framework-profiles","NIST CSF framework profiles",[37,17166,4072,17167,17170],{},[103,17168,17169],{},"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,17172,17173],{},"NIST CSF supports two kinds of profiles:",[164,17175,17176,17182],{},[167,17177,4072,17178,17181],{},[103,17179,17180],{},"Current Profile"," describes the cybersecurity outcomes the organization is achieving today.",[167,17183,4072,17184,17187],{},[103,17185,17186],{},"Target Profile"," describes the cybersecurity outcomes the organization wants to achieve.",[37,17189,17190],{},"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,17192,17193,17194,17197,17198,242],{},"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 ",[40,17195,17196],{"href":7646},"control framework"," — see ",[40,17199,17164],{"href":17200},"\u002Fframeworks\u002Fnistcsf\u002Fframework-profiles",[32,17202,17204],{"id":17203},"nist-csf-categories-and-subcategories","NIST CSF categories and subcategories",[37,17206,17207,17208,414,17211,17214],{},"Below the function layer, NIST CSF decomposes cybersecurity activity into ",[103,17209,17210],{},"categories",[103,17212,17213],{},"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.",[164,17216,17217,17227],{},[167,17218,17219,17222,17223,17226],{},[103,17220,17221],{},"NIST CSF 1.1"," defined 23 categories and ",[103,17224,17225],{},"108 subcategories"," across the five original functions.",[167,17228,17229,17231],{},[103,17230,14796],{}," 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,17233,17234,17235,17238],{},"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 ",[103,17236,17237],{},"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,17240,17242],{"id":17241},"mapping-nist-csf-to-other-frameworks","Mapping NIST CSF to other frameworks",[37,17244,17245,17246,9079,17248,17250],{},"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 ",[40,17247,381],{"href":380},[40,17249,43],{"href":498},", 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,17252,17253,17254,17256],{},"For federal contractors in particular, NIST CSF acts as the governance umbrella above NIST SP 800-171 and ",[40,17255,10708],{"href":15677},", 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,17258,17259,17260,17262,17263,17267],{},"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 ",[40,17261,17242],{"href":391},". If you are actively building that mapping into a live compliance program, our ",[40,17264,17266],{"href":17265},"\u002Fnow\u002Fnist-csf-mapping-compliance","NIST CSF mapping compliance"," guide walks through the operational mechanics.",[32,17269,17271],{"id":17270},"who-uses-nist-csf","Who uses NIST CSF?",[37,17273,17274],{},"The NIST Cybersecurity Framework started as a voluntary framework for United States critical infrastructure. A decade later, NIST CSF is used by:",[164,17276,17277,17283,17292,17298,17304,17310,17316],{},[167,17278,17279,17282],{},[103,17280,17281],{},"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.",[167,17284,17285,17288,17289,242],{},[103,17286,17287],{},"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 ",[40,17290,17291],{"href":15677},"NIST SP 800-171 and the CMMC program",[167,17293,17294,17297],{},[103,17295,17296],{},"State, local, tribal, and territorial (SLTT) governments"," — many states have adopted NIST CSF as the baseline cybersecurity model for agencies and municipal systems.",[167,17299,17300,17303],{},[103,17301,17302],{},"Large enterprises"," — Fortune 500 companies use NIST CSF to communicate cybersecurity risk to boards, investors, insurers, and regulators.",[167,17305,17306,17309],{},[103,17307,17308],{},"Small and mid-sized businesses (SMBs)"," — especially after NIST CSF 2.0, which ships with SMB-specific quick-start guides and community profiles.",[167,17311,17312,17315],{},[103,17313,17314],{},"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.",[167,17317,17318,17321],{},[103,17319,17320],{},"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,17323,17324],{},"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,17326,17328],{"id":17327},"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,17330,17331],{},"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.",[164,17333,17334,17344,17354],{},[167,17335,17336,17339,17340,17343],{},[103,17337,17338],{},"NIST CSF (Cybersecurity Framework)"," is an ",[103,17341,17342],{},"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.",[167,17345,17346,17349,17350,17353],{},[103,17347,17348],{},"NIST SP 800-53 (Security and Privacy Controls for Information Systems and Organizations)"," is a comprehensive ",[103,17351,17352],{},"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).",[167,17355,17356,17359,17360,17363],{},[103,17357,17358],{},"NIST SP 800-171 (Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations)"," is a ",[103,17361,17362],{},"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,17365,17366],{},"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,17368,17369],{},"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,17371,17373],{"id":17372},"getting-started-with-nist-csf","Getting started with NIST CSF",[37,17375,17376],{},"Implementing the NIST Cybersecurity Framework does not require a multi-year consulting engagement. A typical first NIST CSF implementation follows a repeatable pattern:",[1446,17378,17379,17385,17391,17397,17403,17409,17415],{},[167,17380,17381,17384],{},[103,17382,17383],{},"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.",[167,17386,17387,17390],{},[103,17388,17389],{},"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.",[167,17392,17393,17396],{},[103,17394,17395],{},"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.",[167,17398,17399,17402],{},[103,17400,17401],{},"Perform a gap analysis"," — the delta between Current and Target is your NIST CSF roadmap. Prioritize by business impact, risk, and cost.",[167,17404,17405,17408],{},[103,17406,17407],{},"Select implementation tiers"," — match each part of the program to an appropriate tier. Not every subcategory needs to be Tier 4.",[167,17410,17411,17414],{},[103,17412,17413],{},"Execute and measure"," — track initiatives, re-score the NIST CSF profile quarterly, and report progress to leadership.",[167,17416,17417,17420],{},[103,17418,17419],{},"Map to other frameworks"," — reuse the NIST CSF profile as the source of truth for SOC 2, ISO 27001, HIPAA, and CMMC evidence.",[37,17422,17423],{},"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,17425,17426],{},"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":427,"searchDepth":428,"depth":428,"links":17428},[17429,17433,17434,17442,17443,17444,17445,17446,17447,17448],{"id":16927,"depth":428,"text":16928,"children":17430},[17431,17432],{"id":16941,"depth":963,"text":16942},{"id":16955,"depth":963,"text":16956},{"id":16972,"depth":428,"text":16973},{"id":17025,"depth":428,"text":17026,"children":17435},[17436,17437,17438,17439,17440,17441],{"id":17035,"depth":963,"text":17036},{"id":17048,"depth":963,"text":17049},{"id":17062,"depth":963,"text":17063},{"id":17076,"depth":963,"text":17077},{"id":17090,"depth":963,"text":17091},{"id":17103,"depth":963,"text":17104},{"id":17120,"depth":428,"text":17121},{"id":17163,"depth":428,"text":17164},{"id":17203,"depth":428,"text":17204},{"id":17241,"depth":428,"text":17242},{"id":17270,"depth":428,"text":17271},{"id":17327,"depth":428,"text":17328},{"id":17372,"depth":428,"text":17373},{"title":17450,"description":17451,"items":17452},"NIST CSF launch guide","Use episki’s free trial to benchmark, prioritize, and communicate fast.",[17453,17454,17455,17456,17457],"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":17459,"description":17460},"See your NIST CSF score in episki","Start the trial, import controls, and share a scorecard the same day.",{"title":17462,"items":17463},"NIST CSF frequently asked questions",[17464,17466,17469,17472,17475],{"label":16928,"content":17465},"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":17467,"content":17468},"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":17470,"content":17471},"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":17473,"content":17474},"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":17476,"content":17477},"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":17479,"title":17480,"description":17481,"links":17482},"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.",[17483,17485],{"label":17484,"icon":486,"to":487},"Start NIST CSF trial",{"label":489,"icon":17486,"color":491,"variant":492,"to":493,"target":494},"i-lucide-presentation",{},{"headline":17489,"title":17489,"description":17490,"items":17491},"NIST CSF toolset","Everything you need to show measurable progress.",[17492,17495,17498],{"title":17493,"description":17494},"Quarterly business review pack","Slides with KPIs, upcoming initiatives, and resource needs.",{"title":17496,"description":17497},"Customer assurance brief","Explains how NIST CSF maps to their requirements.",{"title":17499,"description":17500},"Automation cookbook","Step-by-step instructions for connecting your tooling.",{"title":17502,"description":17503},"NIST CSF Framework Software","Operationalize NIST CSF with live maturity scoring, risk registers, and executive dashboards. Benchmark and improve your cybersecurity posture with episki.",[17505,17508,17511],{"value":17506,"description":17507},"Live maturity score","Automated scoring by category, tier, and business unit.",{"value":17509,"description":17510},"Unified risk register","Link risks to CSF categories with AI-prioritized remediation.",{"value":17512,"description":17513},"Executive-ready","Dashboards turn security work into business milestones.","5.frameworks\u002Fnistcsf","Doz-LVyeK9ESsWNopGw7Kjfzq0igBKQBgD_u17qdUwk",{"id":17517,"title":17518,"advantages":17519,"body":17541,"checklist":17956,"cta":17965,"description":427,"extension":460,"faq":17968,"hero":17986,"lastUpdated":495,"meta":17995,"name":5708,"navigation":497,"path":5707,"resources":17996,"seo":18009,"slug":6072,"stats":18012,"stem":18022,"__hash__":18023},"frameworks\u002F5.frameworks\u002Fpci.md","Pci",[17520,17527,17534],{"title":17521,"description":17522,"bullets":17523},"Cardholder data mapped","Visualize systems, networks, and data flows tied to each DSS requirement.",[17524,17525,17526],"Track segmentation documentation and approvals","Connect SIEM and log tools for retention evidence","Link vulnerability scans and pen tests to controls",{"title":17528,"description":17529,"bullets":17530},"Task orchestration for engineering","Send prioritized remediation tasks to Jira or Linear with context.",[17531,17532,17533],"Auto-created tickets with required evidence","SLA tracking ensures high-risk remediations close on time","Change management logs sync back automatically",{"title":17535,"description":17536,"bullets":17537},"QSA-ready collaboration","Centralize requests, walkthroughs, and findings with secure file sharing.",[17538,17539,17540],"QSA comments resolve next to each control","Expiring links for sensitive diagrams","Exportable ROC narrative drafts",{"type":29,"value":17542,"toc":17943},[17543,17547,17553,17556,17559,17563,17571,17657,17660,17664,17671,17675,17688,17692,17700,17753,17765,17769,17780,17783,17786,17790,17807,17811,17814,17851,17859,17863,17866,17870,17883,17887,17890,17940],[32,17544,17546],{"id":17545},"what-is-pci-dss","What is PCI DSS?",[37,17548,17549,17550,17552],{},"The Payment Card Industry Data Security Standard -- universally known as ",[40,17551,5708],{"href":11476}," -- 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,17554,17555],{},"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,17557,17558],{},"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,17560,17562],{"id":17561},"the-12-pci-dss-requirements","The 12 PCI DSS requirements",[37,17564,17565,17566,17570],{},"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 ",[40,17567,17569],{"href":17568},"\u002Fframeworks\u002Fpci\u002Frequirements","PCI DSS requirements page","; at a glance they are:",[1446,17572,17573,17583,17589,17603,17609,17615,17621,17627,17633,17639,17645,17651],{},[167,17574,17575,17578,17579,242],{},[103,17576,17577],{},"Install and maintain network security controls"," -- firewalls and equivalent controls around the ",[40,17580,17582],{"href":17581},"\u002Fglossary\u002Fcardholder-data-environment","cardholder data environment",[167,17584,17585,17588],{},[103,17586,17587],{},"Apply secure configurations to all system components"," -- hardening standards, default credential elimination, and secure build baselines.",[167,17590,17591,17594,17595,17598,17599,17602],{},[103,17592,17593],{},"Protect stored account data"," -- encryption, truncation, hashing, or ",[40,17596,8545],{"href":17597},"\u002Fglossary\u002Ftokenization"," of the ",[40,17600,17601],{"href":10889},"PAN"," and prohibition on storing sensitive authentication data.",[167,17604,17605,17608],{},[103,17606,17607],{},"Protect cardholder data with strong cryptography during transmission"," over open, public networks.",[167,17610,17611,17614],{},[103,17612,17613],{},"Protect all systems and networks from malicious software"," -- anti-malware on in-scope systems and defenses against script-based threats.",[167,17616,17617,17620],{},[103,17618,17619],{},"Develop and maintain secure systems and software"," -- secure SDLC, patching, and vulnerability management for in-scope systems.",[167,17622,17623,17626],{},[103,17624,17625],{},"Restrict access to system components and cardholder data by business need to know"," -- least-privilege role design.",[167,17628,17629,17632],{},[103,17630,17631],{},"Identify users and authenticate access to system components"," -- unique IDs, strong authentication, and phishing-resistant MFA.",[167,17634,17635,17638],{},[103,17636,17637],{},"Restrict physical access to cardholder data"," -- physical security for facilities, media, and devices.",[167,17640,17641,17644],{},[103,17642,17643],{},"Log and monitor all access to system components and cardholder data"," -- centralized logging, daily review, and tamper protection.",[167,17646,17647,17650],{},[103,17648,17649],{},"Test security of systems and networks regularly"," -- ASV scans, internal scans, pen tests, and segmentation validation.",[167,17652,17653,17656],{},[103,17654,17655],{},"Support information security with organizational policies and programs"," -- governance, awareness, incident response, and third-party oversight.",[37,17658,17659],{},"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,17661,17663],{"id":17662},"pci-dss-v40-changes","PCI DSS v4.0 changes",[37,17665,17666,17667,242],{},"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 ",[40,17668,17670],{"href":17669},"\u002Fframeworks\u002Fpci\u002Fv4-changes","PCI DSS v4.0 changes guide",[32,17672,17674],{"id":17673},"merchant-compliance-levels-1-4","Merchant compliance levels 1-4",[37,17676,17677,17678,17682,17683,17687],{},"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 ",[40,17679,17681],{"href":17680},"\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 ",[40,17684,17686],{"href":17685},"\u002Fframeworks\u002Fpci\u002Fcompliance-levels","PCI DSS compliance levels page"," breaks down every threshold by card brand and the validation path each level owes.",[32,17689,17691],{"id":17690},"self-assessment-questionnaires-saqs","Self-Assessment Questionnaires (SAQs)",[37,17693,17694,17695,17699],{},"Merchants and service providers that are not required to complete a full PCI DSS Report on Compliance validate using a ",[40,17696,17698],{"href":17697},"\u002Fglossary\u002Fsaq","Self-Assessment Questionnaire",", or SAQ. The PCI SSC publishes nine SAQ types, each tailored to a specific acceptance channel and technology profile:",[164,17701,17702,17708,17714,17720,17726,17732,17738,17744],{},[167,17703,17704,17707],{},[103,17705,17706],{},"SAQ A"," -- card-not-present merchants that fully outsource all cardholder data functions.",[167,17709,17710,17713],{},[103,17711,17712],{},"SAQ A-EP"," -- e-commerce merchants that partially outsource payment processing but host pages that could affect payment page security.",[167,17715,17716,17719],{},[103,17717,17718],{},"SAQ B"," -- merchants using only imprint machines or standalone dial-out terminals.",[167,17721,17722,17725],{},[103,17723,17724],{},"SAQ B-IP"," -- merchants using only standalone IP-connected POI devices.",[167,17727,17728,17731],{},[103,17729,17730],{},"SAQ C-VT"," -- merchants entering transactions into a virtual payment terminal.",[167,17733,17734,17737],{},[103,17735,17736],{},"SAQ C"," -- merchants with payment application systems connected to the internet.",[167,17739,17740,17743],{},[103,17741,17742],{},"SAQ P2PE"," -- merchants using PCI-listed point-to-point encryption solutions.",[167,17745,17746,414,17749,17752],{},[103,17747,17748],{},"SAQ D for Merchants",[103,17750,17751],{},"SAQ D for Service Providers"," -- the catch-all SAQs for entities that store cardholder data or do not qualify for a simpler SAQ.",[37,17754,17755,17756,260,17760,17764],{},"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 ",[40,17757,17759],{"href":17758},"\u002Fframeworks\u002Fpci\u002Fself-assessment-questionnaire","SAQ reference",[40,17761,17763],{"href":17762},"\u002Fframeworks\u002Fpci\u002Fsaq-types-explained","SAQ types explained"," page walk through each SAQ's eligibility, question count, and typical pitfalls.",[32,17766,17768],{"id":17767},"cardholder-data-environment-cde-and-scoping","Cardholder data environment (CDE) and scoping",[37,17770,17771,17772,17774,17775,17779],{},"Every PCI DSS program begins with scoping. The ",[40,17773,17582],{"href":17581},", 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 ",[40,17776,17778],{"href":17777},"\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,17781,17782],{},"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,17784,17785],{},"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,17787,17789],{"id":17788},"scope-reduction-strategies","Scope reduction strategies",[37,17791,17792,17793,17797,17798,17802,17803,17806],{},"Because PCI DSS obligations scale with the CDE, shrinking the CDE is the fastest way to cut PCI DSS cost and risk. Effective ",[40,17794,17796],{"href":17795},"\u002Fframeworks\u002Fpci\u002Fscope-reduction","PCI DSS scope reduction"," typically combines four levers: strong ",[40,17799,17801],{"href":17800},"\u002Fframeworks\u002Fpci\u002Fnetwork-segmentation","network segmentation"," that isolates the CDE onto dedicated VLANs with tightly controlled firewall rules; ",[40,17804,8545],{"href":17805},"\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,17808,17810],{"id":17809},"key-pci-dss-roles-qsas-asvs-and-isas","Key PCI DSS roles: QSAs, ASVs, and ISAs",[37,17812,17813],{},"Three accredited roles support every PCI DSS program:",[164,17815,17816,17831,17845],{},[167,17817,17818,17825,17826,17830],{},[103,17819,17820,17821,17824],{},"Qualified Security Assessors (",[40,17822,17823],{"href":17680},"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 ",[40,17827,17829],{"href":17828},"\u002Fframeworks\u002Fpci\u002Fqsa-selection","QSA selection guide"," covers how to evaluate firms, cost drivers, and red flags.",[167,17832,17833,17839,17840,17844],{},[103,17834,17835,17836,17824],{},"Approved Scanning Vendors (",[40,17837,17838],{"href":12531},"ASVs"," -- PCI SSC-approved firms that run the quarterly external vulnerability scans required by PCI DSS Requirement 11.3.2. The ",[40,17841,17843],{"href":17842},"\u002Fframeworks\u002Fpci\u002Fasv-program","ASV program guide"," covers vendor selection, scanning cadence, passing thresholds, and remediation workflows.",[167,17846,17847,17850],{},[103,17848,17849],{},"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,17852,17853,17854,17858],{},"Penetration testing (Requirement 11.4) sits alongside ASV scanning and is a frequent source of PCI DSS findings. The ",[40,17855,17857],{"href":17856},"\u002Fframeworks\u002Fpci\u002Fpenetration-testing","PCI DSS penetration testing guide"," covers internal vs external scope, segmentation testing, and frequency.",[32,17860,17862],{"id":17861},"penalties-for-non-compliance","Penalties for non-compliance",[37,17864,17865],{},"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,17867,17869],{"id":17868},"pci-dss-vs-other-frameworks","PCI DSS vs other frameworks",[37,17871,17872,17873,17877,17878,17882],{},"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 ",[40,17874,17876],{"href":17875},"\u002Findustry\u002Ffinance","finance industry"," or running ",[40,17879,17881],{"href":17880},"\u002Findustry\u002Fecommerce","e-commerce"," platforms, PCI DSS almost always becomes the binding constraint that the rest of the security program organizes around.",[32,17884,17886],{"id":17885},"getting-pci-compliant","Getting PCI compliant",[37,17888,17889],{},"A typical path to PCI DSS compliance looks like this:",[1446,17891,17892,17898,17904,17910,17916,17922,17928,17934],{},[167,17893,17894,17897],{},[103,17895,17896],{},"Define scope"," -- inventory every place card data lives, moves, or could move. Produce annotated network and data-flow diagrams.",[167,17899,17900,17903],{},[103,17901,17902],{},"Reduce scope"," -- apply segmentation, tokenization, P2PE, and outsourcing to shrink the CDE before assessment.",[167,17905,17906,17909],{},[103,17907,17908],{},"Select your validation path"," -- confirm your PCI DSS level with your acquirer and determine whether you owe a ROC or an SAQ.",[167,17911,17912,17915],{},[103,17913,17914],{},"Gap assess"," -- map your current controls to every applicable PCI DSS requirement and prioritize remediation.",[167,17917,17918,17921],{},[103,17919,17920],{},"Remediate and document"," -- close gaps, write the policies and procedures PCI DSS expects, and stand up the logging, monitoring, scanning, and testing programs.",[167,17923,17924,17927],{},[103,17925,17926],{},"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.",[167,17929,17930,17933],{},[103,17931,17932],{},"Validate and attest"," -- produce the ROC or SAQ plus Attestation of Compliance, and submit to your acquirer on the required cadence.",[167,17935,17936,17939],{},[103,17937,17938],{},"Operate continuously"," -- PCI DSS v4.0 expects continuous monitoring, targeted risk analyses, and evidence that controls stay effective between assessments.",[37,17941,17942],{},"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":427,"searchDepth":428,"depth":428,"links":17944},[17945,17946,17947,17948,17949,17950,17951,17952,17953,17954,17955],{"id":17545,"depth":428,"text":17546},{"id":17561,"depth":428,"text":17562},{"id":17662,"depth":428,"text":17663},{"id":17673,"depth":428,"text":17674},{"id":17690,"depth":428,"text":17691},{"id":17767,"depth":428,"text":17768},{"id":17788,"depth":428,"text":17789},{"id":17809,"depth":428,"text":17810},{"id":17861,"depth":428,"text":17862},{"id":17868,"depth":428,"text":17869},{"id":17885,"depth":428,"text":17886},{"title":17957,"description":17958,"items":17959},"PCI DSS playbook","Follow structured milestones from scoping through ROC submission.",[17960,17961,17962,17963,17964],"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":17966,"description":17967},"Keep PCI DSS audit-ready around the clock","Spin up your trial, sync evidence, and invite your QSA in a single day.",{"title":17969,"items":17970},"PCI DSS frequently asked questions",[17971,17974,17977,17980,17983],{"label":17972,"content":17973},"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":17975,"content":17976},"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":17978,"content":17979},"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":17981,"content":17982},"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":17984,"content":17985},"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":17987,"title":17988,"description":17989,"links":17990},"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.",[17991,17993],{"label":17992,"icon":486,"to":487},"Start PCI trial",{"label":489,"icon":17994,"color":491,"variant":492,"to":493,"target":494},"i-lucide-calendar",{},{"headline":17997,"title":17997,"description":17998,"items":17999},"PCI enablement kit","Give leadership, ops, and QSAs a single source of truth.",[18000,18003,18006],{"title":18001,"description":18002},"CDE architecture report","Share sanitized diagrams and segmentation notes with prospects.",{"title":18004,"description":18005},"Risk and remediation digest","Weekly summary of open items, owners, and due dates.",{"title":18007,"description":18008},"Assessor workspace","Prebuilt template keeps every requirement, artifact, and note aligned.",{"title":18010,"description":18011},"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.",[18013,18016,18019],{"value":18014,"description":18015},"90% automation","Evidence coverage across access, logging, segmentation, and monitoring.",{"value":18017,"description":18018},"QSA portal","Scoped access keeps your assessor in sync without endless spreadsheets.",{"value":18020,"description":18021},"Weekly drift checks","Automated alerts highlight misconfigurations before audits.","5.frameworks\u002Fpci","wxvQHRYeBHEsDrDF1QZg43Nio6AvwX3DWW21RftBG2c",{"id":18025,"title":18026,"advantages":18027,"body":18049,"checklist":18553,"cta":18562,"description":427,"extension":460,"faq":18565,"hero":18582,"lastUpdated":495,"meta":18590,"name":18591,"navigation":497,"path":380,"resources":18592,"seo":18604,"slug":6070,"stats":18607,"stem":18617,"__hash__":18618},"frameworks\u002F5.frameworks\u002Fsoc2.md","Soc2",[18028,18035,18042],{"title":18029,"description":18030,"bullets":18031},"Mapped once, reused forever","Applies Trust Service Criteria to your existing controls and keeps overlaps synced.",[18032,18033,18034],"Control graph highlights reuse across security, availability, and confidentiality","AI suggests narratives and testing procedures","Version history shows every update for auditors",{"title":18036,"description":18037,"bullets":18038},"Evidence organized by control","Upload and track screenshots, configs, and exports in a structured evidence locker.",[18039,18040,18041],"Organized screenshots, configs, and test exports","Alerting when evidence expires or SLAs slip","Immutable locker with reviewer threads",{"title":18043,"description":18044,"bullets":18045},"Auditor collaboration hub","Invite your auditor with scoped access and keep Q&A right next to each control.",[18046,18047,18048],"Bulk requests & fulfillment tracking","Redacted file sharing with access controls","One-click SOC 2 summaries for customers",{"type":29,"value":18050,"toc":18535},[18051,18055,18058,18066,18073,18079,18083,18086,18092,18097,18111,18115,18120,18124,18127,18131,18139,18143,18146,18150,18158,18162,18169,18173,18176,18179,18196,18204,18208,18215,18257,18260,18264,18267,18270,18308,18316,18320,18323,18378,18381,18385,18388,18395,18402,18409,18420,18428,18432,18440,18472,18475,18479,18482,18485,18523],[32,18052,18054],{"id":18053},"what-is-soc-2","What is SOC 2?",[37,18056,18057],{},"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,18059,18060,18061,18065],{},"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 ",[40,18062,18064],{"href":18063},"\u002Fglossary\u002Fssae-18","SSAE 18"," framework.",[37,18067,18068,18069,18072],{},"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 ",[40,18070,10195],{"href":18071},"\u002Fframeworks\u002Fsoc2\u002Ftrust-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,18074,18075,18076,18078],{},"SOC 2 is built on five ",[103,18077,10195],{},": 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,18080,18082],{"id":18081},"soc-2-type-i-vs-type-ii","SOC 2 Type I vs Type II",[37,18084,18085],{},"Every SOC 2 engagement is either Type I or Type II, and the difference matters.",[37,18087,4072,18088,18091],{},[103,18089,18090],{},"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,18093,4072,18094,18096],{},[103,18095,14978],{}," 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,18098,18099,18100,18104,18105,414,18108,242],{},"For a full comparison including cost benchmarks, observation period tradeoffs, and decision frameworks, see ",[40,18101,18103],{"href":18102},"\u002Fframeworks\u002Fsoc2\u002Ftype-1-vs-type-2","SOC 2 Type 1 vs Type 2",". Related glossary terms: ",[40,18106,18107],{"href":14977},"SOC 2 Type 2",[40,18109,10195],{"href":18110},"\u002Fglossary\u002Ftrust-services-criteria",[32,18112,18114],{"id":18113},"the-five-trust-services-criteria","The five Trust Services Criteria",[37,18116,139,18117,18119],{},[40,18118,10195],{"href":18071}," define the principles your controls must satisfy. Each criterion addresses a different aspect of how a service organization protects and manages customer data.",[560,18121,18123],{"id":18122},"security-common-criteria-required","Security (Common Criteria) — required",[37,18125,18126],{},"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.",[560,18128,18130],{"id":18129},"availability","Availability",[37,18132,18133,18134,18138],{},"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 ",[40,18135,18137],{"href":18136},"\u002Fframeworks\u002Fsoc2\u002Favailability-criteria","availability criteria deep dive"," for common controls and implementation patterns.",[560,18140,18142],{"id":18141},"processing-integrity","Processing integrity",[37,18144,18145],{},"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.",[560,18147,18149],{"id":18148},"confidentiality","Confidentiality",[37,18151,18152,18153,18157],{},"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 ",[40,18154,18156],{"href":18155},"\u002Fframeworks\u002Fsoc2\u002Fconfidentiality-criteria","confidentiality criteria deep dive"," for details.",[560,18159,18161],{"id":18160},"privacy","Privacy",[37,18163,18164,18165,242],{},"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 ",[40,18166,18168],{"href":18167},"\u002Fframeworks\u002Fsoc2\u002Fprivacy-criteria","privacy criteria deep dive",[32,18170,18172],{"id":18171},"who-needs-soc-2-compliance","Who needs SOC 2 compliance?",[37,18174,18175],{},"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,18177,18178],{},"Companies typically pursue SOC 2 when one or more of the following is true:",[164,18180,18181,18184,18187,18190,18193],{},[167,18182,18183],{},"Enterprise prospects are asking for a report during procurement or vendor reviews.",[167,18185,18186],{},"Sales cycles are slowing because buyers are blocking deals on security questionnaires.",[167,18188,18189],{},"Existing customers are requesting a current SOC 2 report during annual reviews.",[167,18191,18192],{},"Investors or partners are asking about the company's security posture.",[167,18194,18195],{},"The business is entering regulated verticals like financial services, healthcare, or government.",[37,18197,18198,18199,18203],{},"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 ",[40,18200,18202],{"href":18201},"\u002Fnow\u002Fsoc2-for-saas","SOC 2 for SaaS"," for a deeper discussion.",[32,18205,18207],{"id":18206},"the-soc-2-audit-process-overview","The SOC 2 audit process overview",[37,18209,139,18210,18214],{},[40,18211,18213],{"href":18212},"\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.",[1446,18216,18217,18233,18239,18245,18251],{},[167,18218,18219,18222,18223,18227,18228,18232],{},[103,18220,18221],{},"Scoping and readiness assessment."," Define what systems and Trust Services Criteria are in scope, then perform a ",[40,18224,18226],{"href":18225},"\u002Fframeworks\u002Fsoc2\u002Freadiness-assessment","readiness assessment"," to compare current controls against ",[40,18229,18231],{"href":18230},"\u002Fframeworks\u002Fsoc2\u002Frequirements","SOC 2 requirements",". The output is a prioritized remediation plan.",[167,18234,18235,18238],{},[103,18236,18237],{},"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.",[167,18240,18241,18244],{},[103,18242,18243],{},"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.",[167,18246,18247,18250],{},[103,18248,18249],{},"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.",[167,18252,18253,18256],{},[103,18254,18255],{},"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,18258,18259],{},"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,18261,18263],{"id":18262},"what-does-soc-2-cost","What does SOC 2 cost?",[37,18265,18266],{},"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,18268,18269],{},"Typical benchmarks for a first-time SOC 2 engagement:",[164,18271,18272,18278,18284,18290,18296,18302],{},[167,18273,18274,18277],{},[103,18275,18276],{},"Type I auditor fees",": $15,000 to $40,000",[167,18279,18280,18283],{},[103,18281,18282],{},"Type II auditor fees",": $25,000 to $80,000",[167,18285,18286,18289],{},[103,18287,18288],{},"Readiness consulting"," (optional): $10,000 to $40,000",[167,18291,18292,18295],{},[103,18293,18294],{},"Compliance platform",": $6,000 to $60,000 annually depending on vendor",[167,18297,18298,18301],{},[103,18299,18300],{},"Penetration testing",": $8,000 to $30,000 per test",[167,18303,18304,18307],{},[103,18305,18306],{},"Internal staff time",": 200 to 600 hours across the first cycle",[37,18309,18310,18311,18315],{},"Total first-year cost for most growth-stage SaaS companies lands between $40,000 and $200,000. See the full ",[40,18312,18314],{"href":18313},"\u002Fframeworks\u002Fsoc2\u002Fcost","SOC 2 cost breakdown"," for detailed ranges and cost-reduction strategies.",[32,18317,18319],{"id":18318},"common-soc-2-challenges","Common SOC 2 challenges",[37,18321,18322],{},"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.",[164,18324,18325,18331,18336,18342,18348,18359,18369],{},[167,18326,18327,18330],{},[103,18328,18329],{},"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.",[167,18332,18333,18335],{},[103,18334,5433],{}," Screenshots expire. Configurations change. Ownership drifts between quarters. By the time the auditor asks, the evidence trail is broken.",[167,18337,18338,18341],{},[103,18339,18340],{},"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.",[167,18343,18344,18347],{},[103,18345,18346],{},"Policy drift."," Policies written for the audit do not match how the team actually operates. Auditors detect this quickly during interviews and walkthroughs.",[167,18349,18350,18353,18354,18358],{},[103,18351,18352],{},"Vendor oversight."," Third-party vendors handle critical data but are rarely monitored with the same rigor as internal systems. See ",[40,18355,18357],{"href":18356},"\u002Fframeworks\u002Fsoc2\u002Fvendor-management","vendor management"," for how to close this gap.",[167,18360,18361,18364,18365,18368],{},[103,18362,18363],{},"Change management."," Production changes bypass approval workflows, leaving no audit trail. ",[40,18366,10343],{"href":18367},"\u002Fframeworks\u002Fsoc2\u002Fchange-management"," is a frequent source of Type II exceptions.",[167,18370,18371,18374,18375,242],{},[103,18372,18373],{},"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 ",[40,18376,13314],{"href":18377},"\u002Fframeworks\u002Fsoc2\u002Fincident-response",[37,18379,18380],{},"A structured approach — mapping controls, evidence, and owners from day one — removes most of these friction points before they become audit findings.",[32,18382,18384],{"id":18383},"how-soc-2-compares-to-other-frameworks","How SOC 2 compares to other frameworks",[37,18386,18387],{},"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,18389,18390,18394],{},[103,18391,18392],{},[40,18393,43],{"href":498}," 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,18396,18397,18401],{},[103,18398,18399],{},[40,18400,5694],{"href":5693}," 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,18403,18404,18408],{},[103,18405,18406],{},[40,18407,5708],{"href":5707}," 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,18410,18411,9079,18414,9084,18417,18419],{},[103,18412,18413],{},"NIST Cybersecurity Framework",[103,18415,18416],{},"FedRAMP",[103,18418,10708],{}," 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,18421,18422,18423,18427],{},"If you are comparing SOC 2 tooling options, our ",[40,18424,18426],{"href":18425},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata comparison"," covers the leading compliance automation platforms.",[32,18429,18431],{"id":18430},"soc-2-readiness-checklist","SOC 2 readiness checklist",[37,18433,18434,18435,18439],{},"A readiness checklist keeps your team focused during the months before the audit begins. The ",[40,18436,18438],{"href":18437},"\u002Fframeworks\u002Fsoc2\u002Fchecklist","full SOC 2 checklist"," covers every category, but at a high level expect to address:",[164,18441,18442,18445,18448,18451,18454,18457,18460,18463,18466,18469],{},[167,18443,18444],{},"Governance and policies (information security policy, acceptable use, code of conduct)",[167,18446,18447],{},"Access control (SSO, MFA, role-based access, quarterly access reviews)",[167,18449,18450],{},"Change management (code review, deployment approvals, production change logs)",[167,18452,18453],{},"Vendor risk management (inventory, assessments, monitoring)",[167,18455,18456],{},"Incident response (documented plan, tested at least annually)",[167,18458,18459],{},"Business continuity and disaster recovery (plan with defined RPO\u002FRTO, tested)",[167,18461,18462],{},"Logging and monitoring (centralized logs, alerting, incident tickets)",[167,18464,18465],{},"Security awareness training (annual minimum, tracked completion)",[167,18467,18468],{},"HR controls (background checks, onboarding, offboarding, confidentiality agreements)",[167,18470,18471],{},"Risk assessment (annual risk review, risk register, treatment plans)",[37,18473,18474],{},"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,18476,18478],{"id":18477},"getting-started-with-soc-2","Getting started with SOC 2",[37,18480,18481],{},"The best time to start a SOC 2 program is before the first buyer demands it. The second best time is now.",[37,18483,18484],{},"A reasonable starting sequence:",[1446,18486,18487,18493,18499,18505,18511,18517],{},[167,18488,18489,18492],{},[103,18490,18491],{},"Pick your Trust Services Criteria."," Security is required. Add others only if you have customer commitments that map to them.",[167,18494,18495,18498],{},[103,18496,18497],{},"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.",[167,18500,18501,18504],{},[103,18502,18503],{},"Run a readiness assessment."," Either internally or with a consultant. The goal is a prioritized remediation list, not a polished report.",[167,18506,18507,18510],{},[103,18508,18509],{},"Remediate in priority order."," Address policy gaps, access control weaknesses, and logging first — these are the most common sources of findings.",[167,18512,18513,18516],{},[103,18514,18515],{},"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.",[167,18518,18519,18522],{},[103,18520,18521],{},"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,18524,18525,18526,7947,18531,18534],{},"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. ",[40,18527,18530],{"href":487,"rel":18528},[18529],"nofollow","Start a free trial",[40,18532,18533],{"href":493},"book a demo"," to see how SOC 2 looks with the scramble removed.",{"title":427,"searchDepth":428,"depth":428,"links":18536},[18537,18538,18539,18546,18547,18548,18549,18550,18551,18552],{"id":18053,"depth":428,"text":18054},{"id":18081,"depth":428,"text":18082},{"id":18113,"depth":428,"text":18114,"children":18540},[18541,18542,18543,18544,18545],{"id":18122,"depth":963,"text":18123},{"id":18129,"depth":963,"text":18130},{"id":18141,"depth":963,"text":18142},{"id":18148,"depth":963,"text":18149},{"id":18160,"depth":963,"text":18161},{"id":18171,"depth":428,"text":18172},{"id":18206,"depth":428,"text":18207},{"id":18262,"depth":428,"text":18263},{"id":18318,"depth":428,"text":18319},{"id":18383,"depth":428,"text":18384},{"id":18430,"depth":428,"text":18431},{"id":18477,"depth":428,"text":18478},{"title":18554,"description":18555,"items":18556},"SOC 2 readiness checklist inside episki","Everything is preloaded in your free trial so you can start assigning ownership and collecting proof immediately.",[18557,18558,18559,18560,18561],"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":18563,"description":18564},"Launch your SOC 2 workspace today","Import your controls, connect evidence, and invite your auditor in under an hour.",{"title":18566,"items":18567},"SOC 2 frequently asked questions",[18568,18571,18574,18577,18579],{"label":18569,"content":18570},"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":18572,"content":18573},"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":18575,"content":18576},"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":18172,"content":18578},"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":18580,"content":18581},"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":18583,"title":18584,"description":18585,"links":18586},"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.",[18587,18589],{"label":18588,"icon":486,"to":487},"Start SOC 2 trial",{"label":489,"icon":490,"color":491,"variant":492,"to":493,"target":494},{},"SOC 2 Type I\u002FII",{"headline":18593,"title":18593,"description":18594,"items":18595},"SOC 2 acceleration resources","Give execs and customers visibility into progress at every stage.",[18596,18598,18601],{"title":16020,"description":18597},"Summaries translate control work into risk reduction and deals unlocked.",{"title":18599,"description":18600},"Sales enablement kit","SOC 2 FAQ answers and trust collateral ready for GTM teams.",{"title":18602,"description":18603},"Audit retro template","Capture what worked, track remediations, and prep the next period.",{"title":18605,"description":18606},"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.",[18608,18611,18614],{"value":18609,"description":18610},"45 days faster","Average time saved reaching Type II readiness with episki’s automation.",{"value":18612,"description":18613},"120+ controls","Pre-mapped control narratives with owners, evidence, and review cadences.",{"value":18615,"description":18616},"100% coverage","Auditor portal with control health dashboards and SOC 2 exports.","5.frameworks\u002Fsoc2","bJbRF5XSL9ALksj1QWkHTg9lO2E2kfmot3QsCAz1naE",1778494662428]