{"id":13357,"date":"2026-10-01T00:00:00","date_gmt":"2026-10-01T00:00:00","guid":{"rendered":"https:\/\/formatourinc.com\/en\/what-is-a-statement-of-applicability-the-executive-guide-to-iso-270012022\/"},"modified":"2026-10-08T19:01:24","modified_gmt":"2026-10-08T19:01:24","slug":"what-is-a-statement-of-applicability-the-executive-guide-to-iso-270012022","status":"publish","type":"post","link":"https:\/\/formatourinc.com\/en\/what-is-a-statement-of-applicability-the-executive-guide-to-iso-270012022\/","title":{"rendered":"What is a Statement of Applicability? The Executive Guide to ISO 27001:2022"},"content":{"rendered":"<p>The Statement of Applicability isn\u2019t just a compliance hurdle. It connects your security risks to operational decisions. If you\u2019re asking what is a statement of applicability, it\u2019s the document that records which ISO 27001 controls your organization applies, which it excludes, and why.<\/p>\n<p>It\u2019s understandable to feel uncertain. ISO\/IEC 27001:2022 reduced Annex A from 114 controls to 93, introduced 11 new controls, and reorganized them into four themes. The transition deadline has passed, so organizations with a 2013-version certification need to understand what the updated standard requires. Auditors also use the SoA to assess whether control decisions are grounded in risk, making clear documentation important.<\/p>\n<p>This guide explains the SoA\u2019s requirements and how to document control decisions with sound, risk-based justifications. You\u2019ll learn how to connect the 2022 control set to your risk assessment, business priorities, and implementation status. You\u2019ll also see how a well-maintained SoA can support day-to-day security management as well as audit preparation.<\/p>\n<div class=\"key-takeaways\">\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<ul>\n<li>Understand what is a statement of applicability and how it connects your organization\u2019s risk assessment to its security decisions.<\/li>\n<li>Learn how to structure an SoA around the ISO 27001:2022 control set and maintain clear, useful documentation.<\/li>\n<li>Build evidence-based justifications for including or excluding controls, so your decisions are easier to explain during an audit.<\/li>\n<li>Follow a practical sequence for developing an SoA, starting with risk assessment and treatment planning.<\/li>\n<li>Use the SoA as a management tool to support resilience and give your organization a clear record of its security decisions.<\/li>\n<\/ul>\n<\/div>\n<div class=\"table-of-contents\" role=\"navigation\" aria-label=\"Table of Contents\">\n<h2 id=\"table-of-contents\">Table of Contents<\/h2>\n<ul>\n<li><a href=\"#defining-the-statement-of-applicability-soa-in-the-2026-regulatory-landscape\">Defining the Statement of Applicability (SoA) in the 2026 Regulatory Landscape<\/a><\/li>\n<li><a href=\"#the-architecture-of-an-effective-soa-mapping-iso-270012022-controls\">The Architecture of an Effective SoA: Mapping ISO 27001:2022 Controls<\/a><\/li>\n<li><a href=\"#strategic-justification-navigating-inclusions-and-exclusions\">Strategic Justification: Navigating Inclusions and Exclusions<\/a><\/li>\n<li><a href=\"#how-to-create-a-statement-of-applicability-a-methodical-implementation\">How to Create a Statement of Applicability: A Methodical Implementation<\/a><\/li>\n<li><a href=\"#beyond-compliance-leveraging-the-soa-for-organizational-resilience\">Beyond Compliance: Leveraging the SoA for Organizational Resilience<\/a><\/li>\n<\/ul>\n<\/div>\n<h2 id=\"defining-the-statement-of-applicability-soa-in-the-2026-regulatory-landscape\">Defining the Statement of Applicability (SoA) in the 2026 Regulatory Landscape<\/h2>\n<p>If you\u2019re asking <strong>what is a statement of applicability<\/strong>, think of it as a record of your organization\u2019s information security control decisions. It identifies the controls selected for the ISMS, explains why they were selected, and records their implementation status. Under ISO\/IEC 27001:2022, the SoA is mandatory and connects risk assessment and treatment decisions to the measures an organization puts in place.<\/p>\n<p>The SoA gives leaders, stakeholders, and auditors a structured view of how the organization addresses information security risks. It identifies applicable controls and records why controls are included or excluded. That makes it more than a checklist: it shows how security decisions relate to business needs and the defined ISMS scope. The <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO\/IEC_27001\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">Statement of Applicability<\/a> is also a central reference during certification audits, helping auditors review whether control choices and implementation status are documented coherently.<\/p>\n<p>The SoA should be grounded in a risk assessment, but risk isn\u2019t the only consideration. ISO 27001\u2019s planning requirements also account for applicable legal and contractual requirements. A control may therefore be necessary even if the risk assessment alone doesn\u2019t identify it. Recording that rationale helps ensure important obligations aren\u2019t missed during a risk-only review.<\/p>\n<h3>The Core Purpose: Why the SoA is Mandatory<\/h3>\n<p>ISO 27001 clause 6.1.3 requires the organization to produce an SoA as part of planning information security risk treatment. The document summarizes which controls are necessary, why they were selected, whether they\u2019re implemented, and why Annex A controls were excluded. For executives, it provides a consistent view of security decisions. For auditors, it makes those decisions easier to assess. It also gives internal audits and continual improvement a documented baseline.<\/p>\n<h3>SoA vs. Risk Treatment Plan: Understanding the Difference<\/h3>\n<p>The SoA and Risk Treatment Plan (RTP) serve related but distinct purposes. The SoA identifies <em>what<\/em> controls the organization has selected and records their status and rationale. The RTP describes <em>how<\/em> the organization will address risks, including the actions, responsibilities, and timing needed to implement risk treatment decisions.<\/p>\n<p>For example, if an assessment identifies a risk that requires an additional access control, the SoA records the relevant control and its implementation status. The RTP sets out the work needed to address the risk. Read together, the documents show the path from risk to decision to action. This distinction makes the SoA a practical governance tool, not simply another audit file.<\/p>\n<h2 id=\"the-architecture-of-an-effective-soa-mapping-iso-270012022-controls\">The Architecture of an Effective SoA: Mapping ISO 27001:2022 Controls<\/h2>\n<p>To understand <strong>what is a statement of applicability<\/strong> in practice, look at how it organizes control decisions. ISO\/IEC 27001:2022 reduced Annex A from 114 controls to 93 and regrouped them into four themes. An effective SoA references every Annex A control, records whether it applies to the organization, and explains the reasoning. The goal isn\u2019t to adopt every control automatically. It\u2019s to show that each one has been considered in relation to risk, business context, and applicable requirements.<\/p>\n<p>This structure also makes the SoA useful beyond certification. As <a href=\"https:\/\/www.isaca.org\/resources\/isaca-journal\/issues\/2017\/volume-3\/the-benefits-of-the-statement-of-applicability-in-isms-projects\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">ISACA\u2019s discussion of the Statement of Applicability<\/a> explains, it connects risk assessment to risk treatment. The 2022 control themes help teams organize that connection, while a well-considered SoA can make gaps, responsibilities, and implementation priorities easier to review.<\/p>\n<h3>The Four Pillars of the 2022 Control Set<\/h3>\n<p>The themes group controls by their primary focus, helping teams see how information security responsibilities extend across the organization. The counts are useful for orientation, not targets for how many controls a business should select.<\/p>\n<ul>\n<li><strong>Organizational (37):<\/strong> Policies, cloud services, and supplier relationships establish governance and oversight.<\/li>\n<li><strong>People (8):<\/strong> Controls address responsibilities such as screening, remote work, and confidentiality agreements.<\/li>\n<li><strong>Physical (14):<\/strong> Secure areas, equipment maintenance, and monitoring help manage physical information-security risks.<\/li>\n<li><strong>Technological (34):<\/strong> Controls cover areas including encryption, secure coding, and network security.<\/li>\n<\/ul>\n<h3>What to Record for Each Control<\/h3>\n<p>Apply the same logic to each of the 93 entries. Record the Annex A identifier and control name, then distinguish applicability from implementation. An \u201cIn\u201d or \u201cOut\u201d label can show whether a control is selected, but it doesn\u2019t replace the rationale. If a selected control is planned rather than active, record that status clearly. For an exclusion, state the evidence-based reason.<\/p>\n<p>Some SoAs also use control attributes, such as control type, operational capability, or security domain. These attributes can help teams group controls and map them to frameworks such as NIST CSF or SOC 2. They\u2019re an optional management aid, not a substitute for the required control decisions and justifications. Use them when they improve oversight, and keep the SoA readable for the people who maintain and audit it.<\/p>\n<h2 id=\"strategic-justification-navigating-inclusions-and-exclusions\">Strategic Justification: Navigating Inclusions and Exclusions<\/h2>\n<p>The value of an SoA lies not only in the controls it lists, but also in the reasoning behind each decision. Auditors review justifications to understand whether control choices follow from the organization\u2019s risk assessment, ISMS scope, and relevant obligations. A complete rationale helps show that the ISMS is managed deliberately rather than assembled as a checklist.<\/p>\n<h3>How to Justify Exclusions Correctly<\/h3>\n<p>An exclusion needs a precise explanation that fits the organization\u2019s actual environment. If the organization doesn\u2019t develop software, for example, it may be reasonable to exclude a control focused on secure coding. The rationale should explain that software development isn\u2019t performed within the ISMS scope, rather than simply saying the control is irrelevant. \u201cNot applicable\u201d isn\u2019t sufficient without context.<\/p>\n<p>Check that the reason is supported by the defined ISMS scope and current operations. If development is outsourced, consider whether supplier or other applicable controls address the associated risks before excluding a control. A scope statement that includes development activity would also conflict with an unsupported claim that secure coding has no relevance.<\/p>\n<p>Cost alone is a weak basis for exclusion. If a risk requires treatment but a preferred measure is difficult to implement, document the decision through the organization\u2019s risk treatment and risk acceptance processes, with appropriate authority and rationale. Risk acceptance isn\u2019t a shortcut for removing a necessary control from consideration. The SoA still needs to reflect the organization\u2019s considered decision.<\/p>\n<h3>Linking Controls to Business Objectives<\/h3>\n<p>Justifications are stronger when they explain how controls support business outcomes as well as reduce risk. A control that safeguards access to critical information, for example, may help an organization maintain reliable operations as it adopts new digital processes. Document the relevant risk or objective, the selected control, and where its implementation is evidenced.<\/p>\n<p>This makes the SoA useful in project governance and stakeholder discussions. Clients and partners can see that security measures are deliberate choices aligned with the organization\u2019s priorities. For organizations seeking structured support to connect control decisions with implementation, explore <a href=\"https:\/\/formatourinc.com\/en\/\">ISO 27001 guidance from Formatour<\/a>.<\/p>\n<p><!-- autoseo-infographic --><\/p>\n<div class=\"autoseo-infographic-container\"><img fetchpriority=\"high\" decoding=\"async\" width=\"528\" height=\"1920\" src=\"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/What-is-a-Statement-of-Applicability-The-Executive-Guide-to-ISO-270012022-Infographic-3.webp\" class=\"autoseo-infographic-image skip-lazy no-lazy\" alt=\"What is a Statement of Applicability? The Executive Guide to ISO 27001:2022\" loading=\"eager\" data-no-lazy=\"1\" data-skip-lazy=\"1\" \/><\/div>\n<p><!-- \/autoseo-infographic --><\/p>\n<h2 id=\"how-to-create-a-statement-of-applicability-a-methodical-implementation\">How to Create a Statement of Applicability: A Methodical Implementation<\/h2>\n<p>A dependable SoA is built from evidence, not copied from a generic template. For every control, the process should produce a traceable decision, a clear status, and a connection to the organization\u2019s ISMS. Use these steps to create a document your team can maintain and explain.<\/p>\n<ol>\n<li><strong>Finalize the risk assessment and Risk Treatment Plan.<\/strong> Confirm the relevant risks, planned responses, and any applicable legal or contractual requirements. These provide the rationale for control decisions.<\/li>\n<li><strong>Review all 93 Annex A controls.<\/strong> Work through the ISO 27001:2022 control set individually. Consider each control against your ISMS scope, risk assessment, obligations, and business context. Don\u2019t assume a control is irrelevant just because it\u2019s unfamiliar.<\/li>\n<li><strong>Record the decision and status.<\/strong> Mark each control as selected or not selected, then state whether selected controls are active or planned. A selected control that hasn\u2019t been implemented shouldn\u2019t appear complete.<\/li>\n<li><strong>Document a specific justification.<\/strong> Explain why the control is included or excluded, and reference supporting evidence where practical, such as a risk record, policy, or process document.<\/li>\n<li><strong>Review and approve the SoA.<\/strong> Have the appropriate management authority confirm that the decisions reflect the organization\u2019s accepted risks and priorities. Record the approval and document version so teams know which SoA is current.<\/li>\n<\/ol>\n<h3>Common Pitfalls in SoA Development<\/h3>\n<h3>Preparing for the Certification Audit<\/h3>\n<p>Auditors use the SoA to review control decisions and implementation evidence. Treat it as a navigation document, not a substitute for underlying records. Check that policies, processes, and actual practices align with the status shown. Be ready to explain exclusions with evidence and confirm that each decision fits the ISMS scope. These points may be reviewed during the Stage 1 audit.<\/p>\n<p>Internal teams can build confidence by strengthening their understanding of the standard and audit process. If you\u2019re assessing <a href=\"https:\/\/formatourinc.com\/en\/\">ISO 27001 lead auditor training<\/a>, consider how the learning will help staff evaluate evidence and explain control decisions. For support with ISO 27001 implementation and auditing, <a href=\"https:\/\/formatourinc.com\/en\/contact\/\">contact Formatour to discuss your organization\u2019s needs<\/a>.<\/p>\n<h2 id=\"beyond-compliance-leveraging-the-soa-for-organizational-resilience\">Beyond Compliance: Leveraging the SoA for Organizational Resilience<\/h2>\n<h3>The SoA as a Competitive Advantage<\/h3>\n<p>A clear SoA can support trust with clients and partners by showing how the organization has considered its information security controls. Procurement requirements vary, so ISO 27001 certification or specific security evidence may be requested for some government and enterprise opportunities, but shouldn\u2019t be assumed to be a universal prerequisite. A well-organized record can help teams respond more consistently to vendor risk questionnaires and security due diligence.<\/p>\n<p>Think of the SoA as a structured \u201csecurity menu,\u201d not a document to circulate without review. Share appropriate, approved information about selected controls and their status, while considering whether detailed internal evidence should remain confidential. Internally, clear ownership and documented decisions help departments understand their responsibilities and how their work contributes to the organization\u2019s security framework.<\/p>\n<h3>Partnering for Strategic Success<\/h3>\n<p>Turning an SoA into a useful management tool takes executive direction and practical understanding of day-to-day operations. The document should reflect the organization\u2019s actual context, not off-the-shelf assumptions. Formatour is a Canadian advisory firm specializing in ISO 27001 implementation and auditing, with a multidisciplinary approach to strategic transformation and organizational resilience.<\/p>\n<p>For organizations aligning security with a broader <a href=\"https:\/\/formatourinc.com\/en\/\">digital transformation strategy<\/a>, the SoA can help surface dependencies and inform decisions about control priorities. Use it to identify resilience gaps, assign follow-up actions, and revisit investment choices as business needs evolve. To discuss how ISO 27001 implementation can support your organization\u2019s strategic objectives, connect with Formatour Incorporated.<\/p>\n<h2 id=\"turn-your-soa-into-a-strategic-asset\">Turn Your SoA Into a Strategic Asset<\/h2>\n<p>Knowing <strong>what is a statement of applicability<\/strong> is the first step. Its value comes from using it to connect risk decisions with selected controls, documented evidence, and business priorities. A well-maintained SoA makes control choices easier to review, helps teams identify gaps, and gives leaders a practical reference as risks and operations change.<\/p>\n<p>Build it from a current risk assessment, consider every Annex A control, and make each inclusion or exclusion traceable to a clear rationale. Keep implementation status accurate, involve management in approval, and revisit the document as your organization evolves. These practices strengthen audit readiness and help security support organizational resilience and strategic transformation.<\/p>\n<p>Formatour is a Canadian multidisciplinary advisory firm specializing in ISO 27001 implementation and auditing, with a focus on strategic transformation and organizational resilience. If your team is ready to develop an SoA that supports sound governance and business objectives, <a href=\"https:\/\/formatourinc.com\/en\/contact\/\">discuss ISO 27001 implementation with Formatour<\/a>.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<h3>Is the Statement of Applicability mandatory for ISO 27001 certification?<\/h3>\n<p>Yes. For anyone asking what is a statement of applicability, it\u2019s a required ISO 27001 document that records the controls selected for the ISMS, their implementation status, and the rationale for including or excluding controls. Clause 6.1.3 requires organizations to produce it as part of information security risk treatment planning. Auditors use the SoA to understand the organization\u2019s control decisions and assess whether they\u2019re supported by its risk management process.<\/p>\n<h3>How often should the Statement of Applicability be updated?<\/h3>\n<p>Update the SoA when changes to risks, technology, suppliers, business activities, or ISMS scope affect control decisions or implementation status. ISO 27001 doesn\u2019t prescribe one universal review interval for the document, so establish an approach that fits your organization\u2019s change and governance processes. For example, a major system change may prompt a review of relevant controls. Internal audits and management reviews can also help identify when updates are needed.<\/p>\n<h3>Can I exclude any of the Annex A controls from my SoA?<\/h3>\n<p>Yes. An organization can exclude an Annex A control if it determines the control isn\u2019t necessary for its ISMS, but it must document a clear, evidence-based justification. The decision should align with the organization\u2019s scope, risks, and applicable requirements. For example, a control focused on secure coding may not apply if software development isn\u2019t performed within the ISMS scope. A bare statement such as \u201cnot applicable\u201d doesn\u2019t explain the decision.<\/p>\n<h3>What is the difference between ISO 27001:2013 and ISO 27001:2022 SoA requirements?<\/h3>\n<p>The SoA\u2019s core purpose remains the same, but the 2022 version references an updated Annex A control set: 93 controls organized into four themes, rather than the 114 controls in the 2013 version. The 2022 set includes 11 new controls and consolidates others. Organizations should use the version matching their certification. The transition deadline has passed; as of October 2026, 2013-version certifications are expired and no longer valid.<\/p>\n<h3>Who is responsible for signing off on the Statement of Applicability?<\/h3>\n<p>ISO 27001 requires the organization to maintain the SoA, but it doesn\u2019t prescribe one universal job title for the person who must sign it. The organization should assign approval to an appropriate management authority under its governance arrangements. In practice, the approver should have the authority to confirm that control choices, exclusions, and risk treatment decisions reflect organizational priorities. Record approval and version information so teams can identify the current document.<\/p>\n<h3>Do I need to include controls that are not in Annex A in my SoA?<\/h3>\n<p>The SoA must address the Annex A controls and identify which are necessary, including reasons for exclusions. It may also include controls selected from other sources or developed by the organization when they\u2019re necessary to treat identified risks or meet relevant requirements. For example, an organization might document an additional internal control in its broader control framework. Keep it clearly distinguished from Annex A controls and link it to the reason it\u2019s required.<\/p>\n<h3>How detailed should the justifications in the SoA be for an auditor?<\/h3>\n<p>Provide enough detail for a reviewer to understand the reason behind each inclusion or exclusion and trace it to supporting evidence. Connect the decision to relevant risk assessment findings, ISMS scope, or applicable legal and contractual requirements. For an exclusion, explain why the control doesn\u2019t apply in the organization\u2019s actual environment. Reference supporting records, such as a risk entry or policy, where useful. Avoid generic wording that doesn\u2019t explain the organization\u2019s specific rationale.<\/p>\n<h3>Can I use an SoA template for my ISO 27001 implementation?<\/h3>\n<p>Yes. A template can provide a useful structure for listing controls, decisions, justifications, status, and evidence references. It can\u2019t replace a risk-based review or determine which controls apply to your organization. Tailor every entry to your ISMS scope, risks, and requirements, and verify that the template reflects ISO 27001:2022 if that\u2019s your certification version. Treat the completed SoA as a controlled, living document, not a one-time form to file away.<\/p>","protected":false},"excerpt":{"rendered":"<p>The Statement of Applicability isn\u2019t just a compliance hurdle. It connects your security risks to operational decisions. If you\u2019re asking what is a&#8230;<\/p>","protected":false},"author":4,"featured_media":13358,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"What is a Statement of Applicability? The Executive Guide to ISO 27001:2022","_seopress_titles_desc":"Wondering what is a statement of applicability? Learn how to structure your ISO 27001:2022 SoA, justify controls, and prepare for your audit in this guide.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"What is a Statement of Applicability? The Executive Guide to ISO 27001:2022","_seopress_social_fb_desc":"Wondering what is a statement of applicability? Learn how to structure your ISO 27001:2022 SoA, justify controls, and prepare for your audit in this guide.","_seopress_social_fb_img":"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/what-is-a-statement-of-applicability-the-executive-guide-to-iso-270012022.webp","_seopress_social_fb_img_attachment_id":13358,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"What is a Statement of Applicability? The Executive Guide to ISO 27001:2022","_seopress_social_twitter_desc":"Wondering what is a statement of applicability? Learn how to structure your ISO 27001:2022 SoA, justify controls, and prepare for your audit in this guide.","_seopress_social_twitter_img":"https:\/\/formatourinc.com\/wp-content\/uploads\/2026\/10\/what-is-a-statement-of-applicability-the-executive-guide-to-iso-270012022.webp","_seopress_social_twitter_img_attachment_id":13358,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"what is a statement of applicability","iawp_total_views":1,"footnotes":""},"categories":[13],"tags":[448,186,167,153,151,157,155,447],"class_list":["post-13357","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-annex-a-controls","tag-audit-preparation","tag-compliance","tag-information-security","tag-iso-27001","tag-iso-270012022","tag-risk-management","tag-statement-of-applicability"],"acf":[],"_links":{"self":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts\/13357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/comments?post=13357"}],"version-history":[{"count":0,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/posts\/13357\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/media\/13358"}],"wp:attachment":[{"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/media?parent=13357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/categories?post=13357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formatourinc.com\/en\/wp-json\/wp\/v2\/tags?post=13357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}