{"id":2463,"date":"2026-11-12T05:31:53","date_gmt":"2026-11-12T05:31:53","guid":{"rendered":"https:\/\/www.epw.com\/blog\/?p=2463"},"modified":"2026-11-12T18:38:25","modified_gmt":"2026-11-12T18:38:25","slug":"cobit-framework-information-systems-auditing","status":"publish","type":"post","link":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing","title":{"rendered":"The COBIT Framework for Information Systems Auditing Explained"},"content":{"rendered":"<p class=\"epw-featured-image-caption\"><em>AI-generated illustration created to represent the article\u2019s subject. It does not depict an actual EPW course, trainer, participant, client, event or venue.<\/em><\/p>\n<p><strong>The COBIT framework gives information systems auditors a structured way to assess whether enterprise information and technology are governed and managed in support of business objectives.<\/strong> It helps an audit team translate broad concerns\u2014such as cyber exposure, unreliable systems, uncontrolled change or weak supplier oversight\u2014into defined governance and management objectives, control criteria, evidence requirements and meaningful findings.<\/p>\n<p>COBIT is maintained by ISACA and is designed for the governance and management of enterprise information and technology. It is not a prescriptive audit checklist, a cybersecurity standard or a substitute for professional judgement. Used well, it provides a common language that connects boards, management, technology teams, risk specialists and auditors.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd0808;color:#dd0808\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd0808;color:#dd0808\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Key_takeaways\" >Key takeaways<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Contents\" >Contents<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#What_is_the_COBIT_framework\" >What is the COBIT framework?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#How_is_COBIT_structured\" >How is COBIT structured?<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#The_five_COBIT_domains\" >The five COBIT domains<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Governance-system_components\" >Governance-system components<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Goals_and_design_factors\" >Goals and design factors<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#How_to_use_COBIT_in_an_information_systems_audit\" >How to use COBIT in an information systems audit<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#1_Define_the_business_objective_and_decision_context\" >1. Define the business objective and decision context<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#2_Identify_relevant_technology_risks\" >2. Identify relevant technology risks<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#3_Select_relevant_COBIT_objectives\" >3. Select relevant COBIT objectives<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#4_Convert_practices_into_audit_criteria\" >4. Convert practices into audit criteria<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#5_Assess_design_before_operating_effectiveness\" >5. Assess design before operating effectiveness<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#6_Test_operation_using_sufficient_reliable_evidence\" >6. Test operation using sufficient, reliable evidence<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#7_Report_the_condition_cause_consequence_and_action\" >7. Report the condition, cause, consequence and action<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#COBIT_objectives_commonly_relevant_to_IS_audits\" >COBIT objectives commonly relevant to IS audits<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#What_evidence_should_a_COBIT-informed_audit_obtain\" >What evidence should a COBIT-informed audit obtain?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#How_COBIT_relates_to_NIST_CSF_20\" >How COBIT relates to NIST CSF 2.0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#What_COBIT_does_not_do\" >What COBIT does not do<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#A_practical_COBIT_audit_checklist\" >A practical COBIT audit checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Build_practical_information_systems_audit_capability\" >Build practical information systems audit capability<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Frequently_asked_questions\" >Frequently asked questions<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Is_COBIT_an_audit_standard\" >Is COBIT an audit standard?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Does_an_organisation_need_to_implement_all_40_COBIT_objectives\" >Does an organisation need to implement all 40 COBIT objectives?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#Can_COBIT_be_used_for_cyber-risk_audits\" >Can COBIT be used for cyber-risk audits?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\/#References\" >References<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Key_takeaways\"><\/span>Key takeaways<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>COBIT starts with stakeholder needs and enterprise objectives, not with a generic list of technical controls.<\/li>\n<li>Its core model contains 40 governance and management objectives across five domains.<\/li>\n<li>Auditors can use COBIT to define criteria, map risks, assess control design and communicate findings in business terms.<\/li>\n<li>COBIT should be tailored through context and design factors; applying every objective to every audit would be inefficient.<\/li>\n<li>Cybersecurity and technical testing may require complementary sources such as NIST guidance, architecture standards and system-specific evidence.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Contents\"><\/span>Contents<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><a href=\"#what-is-cobit\">What COBIT is<\/a><\/li>\n<li><a href=\"#structure\">COBIT\u2019s structure and domains<\/a><\/li>\n<li><a href=\"#audit-use\">How auditors use COBIT<\/a><\/li>\n<li><a href=\"#objectives\">Objectives commonly used in IS audits<\/a><\/li>\n<li><a href=\"#evidence\">Evidence and testing<\/a><\/li>\n<li><a href=\"#limitations\">COBIT\u2019s boundaries<\/a><\/li>\n<li><a href=\"#course\">Build practical IS audit capability<\/a><\/li>\n<\/ul>\n<h2 id=\"what-is-cobit\"><span class=\"ez-toc-section\" id=\"What_is_the_COBIT_framework\"><\/span>What is the COBIT framework?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>COBIT is a framework for establishing and improving a governance system for enterprise information and technology. ISACA explains that the <a href=\"https:\/\/www.isaca.org\/resources\/cobit\">COBIT core model<\/a> contains 40 governance and management objectives, each connected to enterprise and alignment goals. The framework allows organisations to select and tailor practices according to their strategy, risk profile, compliance obligations, sourcing model, technology adoption and other design factors.<\/p>\n<p>The important phrase is <em>enterprise information and technology<\/em>. COBIT is wider than the IT department. Digital services, automated decisions, information quality, cloud dependencies, privacy, cyber resilience and technology investment affect operations, customers, finance and strategy. An information systems audit should therefore test how technology supports organisational objectives and how associated risks are governed.<\/p>\n<p>COBIT also distinguishes governance from management:<\/p>\n<ul>\n<li><strong>Governance<\/strong> evaluates stakeholder needs and conditions, directs priorities and monitors performance and conformance.<\/li>\n<li><strong>Management<\/strong> plans, builds, runs and monitors activities in line with the direction established by the governing body.<\/li>\n<\/ul>\n<p>This distinction helps auditors identify the correct accountable party. A board may oversee technology risk and approve direction, while executives and process owners design and operate the management system.<\/p>\n<h2 id=\"structure\"><span class=\"ez-toc-section\" id=\"How_is_COBIT_structured\"><\/span>How is COBIT structured?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"The_five_COBIT_domains\"><\/span>The five COBIT domains<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<table>\n<thead>\n<tr>\n<th>Domain<\/th>\n<th>Purpose<\/th>\n<th>Typical audit focus<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>EDM: Evaluate, Direct and Monitor<\/td>\n<td>Governance objectives<\/td>\n<td>Board oversight, benefits, risk and resources<\/td>\n<\/tr>\n<tr>\n<td>APO: Align, Plan and Organise<\/td>\n<td>Strategy, architecture, people, risk and security<\/td>\n<td>Accountability, plans, policies and capabilities<\/td>\n<\/tr>\n<tr>\n<td>BAI: Build, Acquire and Implement<\/td>\n<td>Programmes, solutions, change and assets<\/td>\n<td>Projects, requirements, releases and configuration<\/td>\n<\/tr>\n<tr>\n<td>DSS: Deliver, Service and Support<\/td>\n<td>Operations, services, continuity and security<\/td>\n<td>Service delivery, incidents, access and resilience<\/td>\n<\/tr>\n<tr>\n<td>MEA: Monitor, Evaluate and Assess<\/td>\n<td>Performance, internal control and compliance<\/td>\n<td>Monitoring, assurance, control evaluation and obligations<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12051355\/epw-cobit-governance-management-domains.webp\" alt=\"COBIT governance and management domains for information systems auditing\" width=\"1200\" height=\"800\" loading=\"lazy\" style=\"max-width:100%;height:auto\" \/><figcaption>COBIT separates governance from management while linking both to enterprise goals.<\/figcaption><\/figure>\n<h3><span class=\"ez-toc-section\" id=\"Governance-system_components\"><\/span>Governance-system components<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A reliable governance system depends on more than processes. COBIT\u2019s components include processes; organisational structures; principles, policies and procedures; information; culture, ethics and behaviour; people, skills and competencies; and services, infrastructure and applications. This breadth is useful in an audit because a formally correct process may still fail when accountability is unclear, information is unreliable or behaviour rewards circumvention.<\/p>\n<p>For example, an audit of privileged access should not stop after reading the access policy. It may need to assess decision authority, administrator competence, account data, approval workflow, monitoring technology, exception culture and management response. The components encourage a more complete causal analysis.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Goals_and_design_factors\"><\/span>Goals and design factors<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>COBIT uses a goals cascade to link stakeholder drivers and enterprise goals to technology-related alignment goals and relevant governance or management objectives. It also recognises that governance systems must be tailored. A regulated financial institution, a public body and a fast-growing digital company may require different priorities even when they use similar technology.<\/p>\n<p>For auditors, tailoring improves scope discipline. The audit universe, risk assessment and engagement objectives should reflect material business services, obligations, threat conditions, technology dependencies and change\u2014not an assumption that every COBIT objective deserves equal testing.<\/p>\n<h2 id=\"audit-use\"><span class=\"ez-toc-section\" id=\"How_to_use_COBIT_in_an_information_systems_audit\"><\/span>How to use COBIT in an information systems audit<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"1_Define_the_business_objective_and_decision_context\"><\/span>1. Define the business objective and decision context<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Begin with the service, process or outcome that technology supports. Identify stakeholders, critical information, tolerance for disruption, legal obligations and dependencies. An audit objective such as \u201cassess change management\u201d becomes stronger when connected to the risk that unauthorised or poorly tested change could interrupt a critical service or corrupt financial information.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Identify_relevant_technology_risks\"><\/span>2. Identify relevant technology risks<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Describe plausible events and their causes, consequences and velocity. Consider unauthorised access, data error, cyberattack, unavailable services, uncontrolled change, supplier failure, weak recovery, obsolete technology and ineffective oversight. Risk scenarios prevent the framework from becoming a compliance exercise.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Select_relevant_COBIT_objectives\"><\/span>3. Select relevant COBIT objectives<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Map the engagement objective and risks to a focused set of COBIT governance and management objectives. Use the mapping as a reasoned starting point, then confirm it against the actual organisation, architecture and obligations. Record why objectives were included or excluded.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"4_Convert_practices_into_audit_criteria\"><\/span>4. Convert practices into audit criteria<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Audit criteria state the reasonable condition against which evidence will be evaluated. COBIT can inform criteria, but auditors should combine it with approved policies, contracts, regulation, recognised security standards and system requirements. Criteria need to be relevant, reliable, understandable and agreed early enough to avoid disputes after testing.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"5_Assess_design_before_operating_effectiveness\"><\/span>5. Assess design before operating effectiveness<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Determine whether responsibilities, procedures, technology and information could reasonably achieve the control objective. A control cannot operate effectively if its design omits a material population, permits incompatible access or lacks escalation. Design assessment prevents extensive testing of a fundamentally unsuitable control.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"6_Test_operation_using_sufficient_reliable_evidence\"><\/span>6. Test operation using sufficient, reliable evidence<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use enquiry only as context. Corroborate it with configuration, logs, tickets, approvals, reconciliations, monitoring records, observation, reperformance or data analysis. Consider completeness and accuracy of system-generated information before relying on it. Sample selection should reflect frequency, population, risk and possible management override.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"7_Report_the_condition_cause_consequence_and_action\"><\/span>7. Report the condition, cause, consequence and action<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Connect findings to the governance or management objective and the affected enterprise outcome. Explain the actual condition, credible root cause, risk exposure and agreed action. Avoid implying that a COBIT practice is mandatory unless law, contract or policy makes it so. Follow up until action is implemented or the responsible authority formally accepts the residual risk.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12051357\/epw-cobit-is-audit-workflow.webp\" alt=\"Seven-stage COBIT information systems audit workflow\" width=\"1200\" height=\"800\" loading=\"lazy\" style=\"max-width:100%;height:auto\" \/><figcaption>Auditors can use COBIT to move from business context to defensible findings and follow-up.<\/figcaption><\/figure>\n<h2 id=\"objectives\"><span class=\"ez-toc-section\" id=\"COBIT_objectives_commonly_relevant_to_IS_audits\"><\/span>COBIT objectives commonly relevant to IS audits<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<table>\n<thead>\n<tr>\n<th>COBIT objective<\/th>\n<th>Example audit questions<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>EDM03 Ensured Risk Optimisation<\/td>\n<td>Does governing-body direction reflect material technology risk and appetite?<\/td>\n<\/tr>\n<tr>\n<td>APO12 Managed Risk<\/td>\n<td>Are technology risks identified, analysed, owned and integrated with enterprise risk?<\/td>\n<\/tr>\n<tr>\n<td>APO13 Managed Security<\/td>\n<td>Is information security governed through an appropriate management system?<\/td>\n<\/tr>\n<tr>\n<td>BAI06 Managed IT Changes<\/td>\n<td>Are changes authorised, tested, segregated, documented and reviewed?<\/td>\n<\/tr>\n<tr>\n<td>DSS04 Managed Continuity<\/td>\n<td>Can critical technology services recover within business requirements?<\/td>\n<\/tr>\n<tr>\n<td>DSS05 Managed Security Services<\/td>\n<td>Are security operations, access, monitoring and response controlled?<\/td>\n<\/tr>\n<tr>\n<td>MEA02 Managed System of Internal Control<\/td>\n<td>Does management monitor control design, performance, deficiencies and remediation?<\/td>\n<\/tr>\n<tr>\n<td>MEA03 Managed Compliance With External Requirements<\/td>\n<td>Are applicable technology obligations identified, assigned and monitored?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The selection is illustrative, not universal. An application audit may emphasise requirements, data integrity and change; a cloud audit may focus on architecture, suppliers, security services and continuity; and a governance audit may concentrate on EDM and APO objectives.<\/p>\n<h2 id=\"evidence\"><span class=\"ez-toc-section\" id=\"What_evidence_should_a_COBIT-informed_audit_obtain\"><\/span>What evidence should a COBIT-informed audit obtain?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><strong>Governance evidence:<\/strong> approved strategies, committee mandates, decisions, risk appetite, investment criteria and oversight reports.<\/li>\n<li><strong>Process evidence:<\/strong> procedures, workflows, tickets, approvals, exceptions and performance measures.<\/li>\n<li><strong>Technical evidence:<\/strong> configuration extracts, identity records, logs, vulnerability results, backup records and recovery tests.<\/li>\n<li><strong>Information evidence:<\/strong> data definitions, ownership, lineage, quality controls and reconciliation.<\/li>\n<li><strong>People and culture evidence:<\/strong> role profiles, competence records, interviews, escalation behaviour and consequence management.<\/li>\n<li><strong>Third-party evidence:<\/strong> contracts, service levels, assurance reports, incident notifications and exit provisions.<\/li>\n<\/ul>\n<p>The audit team should validate evidence provenance, period and completeness. Screenshots selected by the control owner may illustrate configuration but rarely prove that it operated across the audit period. Where possible, obtain evidence directly from authoritative systems and reconcile populations before sampling.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_COBIT_relates_to_NIST_CSF_20\"><\/span>How COBIT relates to NIST CSF 2.0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>COBIT and the NIST Cybersecurity Framework are complementary. COBIT provides an enterprise governance and management system; <a href=\"https:\/\/www.nist.gov\/cyberframework\">NIST CSF 2.0<\/a> organises cybersecurity outcomes around Govern, Identify, Protect, Detect, Respond and Recover. NIST\u2019s addition of the Govern function strengthens the connection between cybersecurity, enterprise risk, policy and accountability.<\/p>\n<p>An auditor might use COBIT to assess governance, accountability and management processes, then use NIST CSF outcomes and more detailed technical criteria for security testing. Cross-mapping is helpful, but it does not make the frameworks interchangeable. The audit must retain a clear line from objective to risk, criterion, evidence and conclusion.<\/p>\n<h2 id=\"limitations\"><span class=\"ez-toc-section\" id=\"What_COBIT_does_not_do\"><\/span>What COBIT does not do<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>It does not automatically define an audit scope or replace risk assessment.<\/li>\n<li>It does not prove that a control operated; evidence and testing remain essential.<\/li>\n<li>It is not a detailed penetration-testing, configuration or forensic method.<\/li>\n<li>It does not make every practice mandatory for every organisation.<\/li>\n<li>It does not remove the need to consider regulation, contracts, internal policy and other authoritative criteria.<\/li>\n<\/ul>\n<p>Common mistakes include copying a maturity questionnaire without verifying evidence, applying too many objectives, rating capability without a sound method, and reporting framework gaps without explaining business consequences. The best use of COBIT is selective, transparent and anchored in the organisation\u2019s objectives.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_practical_COBIT_audit_checklist\"><\/span>A practical COBIT audit checklist<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ol>\n<li>State the business service or objective in scope.<\/li>\n<li>Document material technology and cyber-risk scenarios.<\/li>\n<li>Identify accountable governance and management roles.<\/li>\n<li>Select relevant COBIT objectives and components.<\/li>\n<li>Agree suitable criteria and evidence requirements.<\/li>\n<li>Assess control design before sampling operation.<\/li>\n<li>Validate system-generated populations and technical evidence.<\/li>\n<li>Relate findings to consequences, root causes and residual risk.<\/li>\n<li>Assign actions, owners and target dates.<\/li>\n<li>Monitor completion and confirm sustainable improvement.<\/li>\n<\/ol>\n<p>Readers seeking a broader governance context can also review EPW\u2019s explanation of <a href=\"https:\/\/www.epw.com\/blog\/courses\/what-is-governance-risk-and-compliance\">governance, risk and compliance<\/a> and the <a href=\"https:\/\/www.epw.com\/courses\/auditing-governance-and-risk-compliance\">Auditing, Governance, and Risk Compliance training portfolio<\/a>.<\/p>\n<h2 id=\"course\"><span class=\"ez-toc-section\" id=\"Build_practical_information_systems_audit_capability\"><\/span>Build practical information systems audit capability<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>EPW\u2019s five-day <a href=\"https:\/\/www.epw.com\/training\/information-systems-auditing-and-cyber-risk-awareness\"><strong>Information Systems Auditing and Cyber Risk Awareness Course<\/strong><\/a> equips internal auditors, risk professionals and control managers to conduct risk-based technology assurance. It covers COBIT and NIST concepts, IT governance, general IT controls, applications, data, cloud services, cyber-risk scenarios, resilience, audit evidence, analytics and technology-risk reporting. Participants practise scoping, control testing and evidence evaluation in workshops and a capstone IS audit case.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Frequently_asked_questions\"><\/span>Frequently asked questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Is_COBIT_an_audit_standard\"><\/span>Is COBIT an audit standard?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. COBIT is a governance and management framework. Auditors can use it as a source of criteria and structure, while following applicable professional audit standards and considering legal, regulatory, contractual and internal requirements.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Does_an_organisation_need_to_implement_all_40_COBIT_objectives\"><\/span>Does an organisation need to implement all 40 COBIT objectives?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. COBIT is designed to be tailored. The relevant objectives depend on enterprise goals, risks, obligations, sourcing, technology and other design factors.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_COBIT_be_used_for_cyber-risk_audits\"><\/span>Can COBIT be used for cyber-risk audits?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Yes, particularly for governance, accountability and management processes. Detailed cybersecurity testing should also use suitable security frameworks, technical standards and system-specific criteria.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"References\"><\/span>References<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><a href=\"https:\/\/www.isaca.org\/resources\/cobit\">ISACA, COBIT resources and COBIT 2019 framework publications<\/a>.<\/li>\n<li><a href=\"https:\/\/support.isaca.org\/s\/article\/How-does-COBIT-relate-to-my-business-or-similar-standards\">ISACA, How COBIT relates to business and other standards<\/a>.<\/li>\n<li><a href=\"https:\/\/www.nist.gov\/cyberframework\">US National Institute of Standards and Technology, Cybersecurity Framework 2.0<\/a>.<\/li>\n<li><a href=\"https:\/\/www.theiia.org\/en\/standards\/2024-standards\/global-internal-audit-standards\/\">The Institute of Internal Auditors, Global Internal Audit Standards<\/a>.<\/li>\n<li><a href=\"https:\/\/csrc.nist.gov\/pubs\/sp\/800\/53\/r5\/upd1\/final\">NIST, Security and Privacy Controls for Information Systems and Organizations, SP 800-53 Rev. 5<\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>A practical explanation of how information systems auditors use COBIT to connect enterprise objectives, technology risks, governance controls, evidence and findings.<\/p>\n","protected":false},"author":1,"featured_media":4122,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-2463","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-auditing-governance-and-risk-compliance-articles"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.7 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>COBIT Framework for Information Systems Auditing | EPW<\/title>\n<meta name=\"description\" content=\"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"COBIT Framework for Information Systems Auditing | EPW\" \/>\n<meta property=\"og:description\" content=\"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\" \/>\n<meta property=\"og:site_name\" content=\"Blog Categories - EPW Training\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-12T05:31:53+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-12T18:38:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"576\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"EPW Training Blog\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"EPW Training Blog\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\"},\"author\":{\"@type\":\"Organization\",\"name\":\"EPW Training Blog\",\"url\":\"https:\/\/www.epw.com\/blog\/\",\"@id\":\"https:\/\/www.epw.com\/blog\/#organization\"},\"headline\":\"The COBIT Framework for Information Systems Auditing Explained\",\"datePublished\":\"2026-11-12T05:31:53+00:00\",\"dateModified\":\"2026-11-12T18:38:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\"},\"wordCount\":1916,\"publisher\":{\"@id\":\"https:\/\/www.epw.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage\"},\"thumbnailUrl\":\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp\",\"articleSection\":[\"Auditing, Governance, and Risk Compliance Articles\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\",\"url\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\",\"name\":\"COBIT Framework for Information Systems Auditing | EPW\",\"isPartOf\":{\"@id\":\"https:\/\/www.epw.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage\"},\"thumbnailUrl\":\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp\",\"datePublished\":\"2026-11-12T05:31:53+00:00\",\"dateModified\":\"2026-11-12T18:38:25+00:00\",\"description\":\"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage\",\"url\":\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp\",\"contentUrl\":\"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp\",\"width\":1024,\"height\":576,\"caption\":\"Auditors and risk managers reviewing information systems controls on laptops and printed charts\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.epw.com\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The COBIT Framework for Information Systems Auditing Explained\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.epw.com\/blog\/#website\",\"url\":\"https:\/\/www.epw.com\/blog\/\",\"name\":\"Blog Categories - EPW Training\",\"description\":\"Expert Insights and Updates in Professional Training\",\"publisher\":{\"@id\":\"https:\/\/www.epw.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.epw.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.epw.com\/blog\/#organization\",\"name\":\"Blog Categories - EPW Training\",\"url\":\"https:\/\/www.epw.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.epw.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.epw.com\/blog\/wp-content\/uploads\/2025\/08\/epw-training-blog-logo.png\",\"contentUrl\":\"https:\/\/www.epw.com\/blog\/wp-content\/uploads\/2025\/08\/epw-training-blog-logo.png\",\"width\":746,\"height\":256,\"caption\":\"Blog Categories - EPW Training\"},\"image\":{\"@id\":\"https:\/\/www.epw.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.epw.com\/blog\/#person\",\"name\":\"EPW Training Blog\",\"sameAs\":[\"https:\/\/www.epw.com\/blog\/\"],\"url\":\"https:\/\/www.epw.com\/blog\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"COBIT Framework for Information Systems Auditing | EPW","description":"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing","og_locale":"en_US","og_type":"article","og_title":"COBIT Framework for Information Systems Auditing | EPW","og_description":"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.","og_url":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing","og_site_name":"Blog Categories - EPW Training","article_published_time":"2026-11-12T05:31:53+00:00","article_modified_time":"2026-11-12T18:38:25+00:00","og_image":[{"width":1024,"height":576,"url":"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp","type":"image\/webp"}],"author":"EPW Training Blog","twitter_card":"summary_large_image","twitter_misc":{"Written by":"EPW Training Blog","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#article","isPartOf":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing"},"author":{"@type":"Organization","name":"EPW Training Blog","url":"https:\/\/www.epw.com\/blog\/","@id":"https:\/\/www.epw.com\/blog\/#organization"},"headline":"The COBIT Framework for Information Systems Auditing Explained","datePublished":"2026-11-12T05:31:53+00:00","dateModified":"2026-11-12T18:38:25+00:00","mainEntityOfPage":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing"},"wordCount":1916,"publisher":{"@id":"https:\/\/www.epw.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage"},"thumbnailUrl":"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp","articleSection":["Auditing, Governance, and Risk Compliance Articles"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing","url":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing","name":"COBIT Framework for Information Systems Auditing | EPW","isPartOf":{"@id":"https:\/\/www.epw.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage"},"image":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage"},"thumbnailUrl":"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp","datePublished":"2026-11-12T05:31:53+00:00","dateModified":"2026-11-12T18:38:25+00:00","description":"Learn how the COBIT framework supports information systems auditing, from scoping and control criteria to evidence, findings and cyber-risk assurance.","breadcrumb":{"@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#primaryimage","url":"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp","contentUrl":"https:\/\/assets.epw.com\/blog\/wp-content\/uploads\/2026\/11\/12183748\/cobit-framework-information-systems-auditing-featured.webp","width":1024,"height":576,"caption":"Auditors and risk managers reviewing information systems controls on laptops and printed charts"},{"@type":"BreadcrumbList","@id":"https:\/\/www.epw.com\/blog\/auditing-governance-and-risk-compliance-articles\/cobit-framework-information-systems-auditing#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.epw.com\/blog"},{"@type":"ListItem","position":2,"name":"The COBIT Framework for Information Systems Auditing Explained"}]},{"@type":"WebSite","@id":"https:\/\/www.epw.com\/blog\/#website","url":"https:\/\/www.epw.com\/blog\/","name":"Blog Categories - EPW Training","description":"Expert Insights and Updates in Professional Training","publisher":{"@id":"https:\/\/www.epw.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.epw.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.epw.com\/blog\/#organization","name":"Blog Categories - EPW Training","url":"https:\/\/www.epw.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.epw.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.epw.com\/blog\/wp-content\/uploads\/2025\/08\/epw-training-blog-logo.png","contentUrl":"https:\/\/www.epw.com\/blog\/wp-content\/uploads\/2025\/08\/epw-training-blog-logo.png","width":746,"height":256,"caption":"Blog Categories - EPW Training"},"image":{"@id":"https:\/\/www.epw.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.epw.com\/blog\/#person","name":"EPW Training Blog","sameAs":["https:\/\/www.epw.com\/blog\/"],"url":"https:\/\/www.epw.com\/blog\/"}]}},"_links":{"self":[{"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/posts\/2463","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/comments?post=2463"}],"version-history":[{"count":3,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/posts\/2463\/revisions"}],"predecessor-version":[{"id":4124,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/posts\/2463\/revisions\/4124"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/media\/4122"}],"wp:attachment":[{"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/media?parent=2463"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/categories?post=2463"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.epw.com\/blog\/wp-json\/wp\/v2\/tags?post=2463"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}