\n> **_\u201cThe art of communication is the language of leadership.\u201d_** \u2014 James Humes, former Presidential speechwriter and author. <\/p>\n
Cybersecurity teams face adversaries who thrive in chaos. Attackers move fast, automate, and strike where defenses are weakest. In a borderless digital world, disruption is constant, driven by innovation, complexity, and the pressure to move faster, often at the cost of safety. <\/p>\n
To withstand that pressure, teams need leadership and effective, confident communication. <\/p>\n
Industry studies, including the Verizon DBIR, consistently find that the majority of major incidents are worsened by poor communication and a lack of coordinated responses. The tactics of effective cybersecurity leadership rely on continuous improvement, clarity, structure, and agility. With the right priorities and proper coordination, leaders can build systems that support swift, unified action, even under relentless pressure. However, as we\u2019ve seen throughout this series, success hinges on information, available resources, and clear mission priorities. Without structure, even the strongest plans can collapse under pressure.<\/p>\n
A global shipping and logistics company experienced this firsthand during the NotPetya attack. Despite strong tools and sound practices, ransomware spread unchecked, crippling critical operations and paralyzing logistics networks around the world. <\/p>\n
* Systems locked up across regions. <\/p>\n
* Communication and coordination collapsed. <\/p>\n
* Schedules, systems, and asset visibility gone. <\/p>\n
* Shipments halted; global operations disrupted. <\/p>\n
It took almost two weeks to recover to basic operating levels. (Recovery could have taken far longer if not for a fortunate offline backup of a key domain controller.)<\/p>\n
The financial toll reached hundreds of millions, but the real exposure was strategic: the incident revealed just how fragile operations are without a structured link between technical action and business needs.<\/p>\n
**The most glaring lesson: technology and talent alone weren\u2019t enough.**<\/p>\n
In the aftermath, the company began mapping and building foundational systems it had never fully established. Business Continuity and Disaster Recovery plans were rewritten. Asset inventories were created and validated. And for the first time, risk-based decision-making was integrated into every critical function. With surprising agility, teams shifted from simply reacting to executing with a streamlined, prioritized posture. Leadership gained real-time visibility into risks, assets, and threats, finally aligning technical insight with business impact.<\/p>\n
Today, security and technical teams understand what disaster and success look like. They know which systems matter most. Leadership experienced far less friction when requesting metrics and communicating them to various decision-makers.<\/p>\n
As we have covered throughout this series, technology alone will never be enough. Cybersecurity teams must build systems that ensure clear, confident communication, especially when everything is on the line.<\/p>\n
## An Orchestrated Response – Prioritized and Sharply Tuned<\/p>\n
> **_” All the squadrons in the world are of no use if they cannot be brought into action at the right moment, at the right spot, and in sufficient numbers.”_**__ \u2013 Air Chief Marshal Hugh Dowding<\/p>\n
Victory in Cybersecurity isn\u2019t determined by raw resources, but by how effectively they\u2019re deployed. For leaders to be effective, threat awareness must drive and empower decisive action.<\/p>\n
In Step 3, we introduced the British defensive pivot after the fall of France in the spring of 1940. Facing invasion, Britain\u2019s survival would not simply depend on brute force but clarity of mission, methodical deployments, and a bit of innovation.<\/p>\n
That summer, Germany poured effort and resources into securing radio transmissions for the next push. However, rather than simply focusing on intercepting enemy messages, Britain built a system to _see_ attacks before they struck. For the first time in history, coastal radar towers were used to reflect signals and triangulate the position of incoming aircraft. This innovation enabled unparalleled early detection and gave defenders the critical seconds needed to respond rapidly.<\/p>\n
Germany, meanwhile, concentrated on encrypting communications and bombing airfields, underestimating the value of Britain\u2019s radar network. This early miscalculation allowed Britain to preserve its early warning capabilities, enabling faster, more effective responses to incoming raids.<\/p>\n
__Chain Home Radar Towers | Picture Source: Imperial War Museums UK website__<\/p>\n
This breakthrough, known as \u201cChain Home,\u201d gave defenders the eyes and foresight they needed to act. Integrated into the Dowding System framework, it funneled intelligence to command centers, which coordinated real-time air defensive deployments.<\/p>\n
_Dowding System Flow | Picture Source: Imperial War Museums UK website_<\/p>\n
The innovative Dowding System brought order to mountains of intelligence and data, enabling maximum impact of limited resources. Agile communication, clear roles, and rapid execution gave Britain an edge.<\/p>\n
_RAF Sector \u2018G\u2019 Operations Room | Picture Source: Imperial War Museums UK website_<\/p>\n
Despite standing alone and facing overwhelming odds, the system held; the attacks were repelled, and for the first time, the tide began to turn.<\/p>\n
This wasn\u2019t just technological ingenuity, but an innovative, repeatable system, for an agile _and_ orchestrated response. It turned scattered inputs into decisive action and gave leadership the visibility to make well-informed calls at the speed of conflict. It also inspired other nations who witnessed the first defeat of a force thought to be unbeatable.<\/p>\n
Every day brought new attacks, often without warning, targeting airfields, radar stations, cities, and supply lines. There was no pause, just the constant pressure to intercept, adapt, and survive.<\/p>\n
Modern cybersecurity teams face a similar battle. The digital homeland is constantly under attack. Adversaries move fast, looking for every weakness, thriving on slow, disjointed responses. The Dowding System stitched together radar, ground observers, and command centers into a live operational picture. This enabled rapid identification, vectoring of fighter squadrons, and centralized decision-making under pressure. In the end, the right tools and talent mean little without a structure that translates information into swift, confident action.<\/p>\n
Good news: Security teams don\u2019t have to build their own Dowding and Chain Home systems from scratch.<\/p>\n
## A Template for Resilience \u2013 Leveraging NIST Frameworks<\/p>\n
**_” All the great struggles of history, whether in war or peace, turn on effective organization, on bringing superior force to bear at the right time, and place.”_** \u2014 Winston Churchill<\/p>\n
It bears repeating that there is no need for cybersecurity teams to build their risk-reduction strategies from the ground up. Established risk management frameworks (RMF) offer a proven playbook for maturing security posture and turning intelligence into prioritized action. These frameworks move organizations beyond reactive responses to scalable, repeatable risk reduction aligned with business goals. NIST\u2019s strategic runbooks embed cybersecurity risk management into everyday business operations, ensuring risk is measured, communicated, and acted on across the organization.<\/p>\n
We\u2019ll focus on two essential frameworks that help teams integrate cybersecurity into business operations with clarity and confidence: 1) NIST 800-39 and 2) 800-37.<\/p>\n
* NIST 800-39 RMF focuses on _organization-wide risk management_. It aligns cybersecurity with mission objectives, assigns clear ownership, and embeds risk directly into business decision-making. Leadership should start here to **communicate** accountability and drive a top-down, business-first approach to managing risk.<\/p>\n
<\/p>\n
**RMF Implementation \u2013 Simplified:**<\/p>\n
1. **Categorize:** Identify the impact level of assets to prioritize security needs.
2. **Select & Implement Controls:** Tailor and deploy security measures based on the identified risks.
3. **Assess & Monitor:** Continuously assess and refine controls to keep up with emerging threats.<\/p>\n
* NIST 800-37 revision 2 lays out the Risk Management Framework (RMF), a repeatable process for selecting, implementing, assessing, and continuously monitoring security controls.This is where teams **measure** effectiveness, **eliminate** blind spots, and keep defenses relevant through day-to-day execution.<\/p>\n
<\/p>\n
**Key principles from NIST 800-37 Rev. 2:**<\/p>\n
1. **Cybersecurity as a Business Function:**
Risk is not isolated, and cybersecurity is integral to business objectives. Aligning risk management with business functions reduces the chance of overlooked threats and strengthens operational resilience.
2. **Continuous Monitoring:**
Risk management isn\u2019t a one-and-done exercise. Ongoing assessment ensures defenses stay effective and responsive as the threat landscape shifts.
3. **Preparation and Planning:**
Effective risk management starts with a solid foundation. Proactive preparation ensures smoother RMF execution and faster response to real-world risks.
4. **Lifecycle Approach to Security:**
Risk management must span the entire system lifecycle, from design through deployment, to ensure systems are protected from the start.<\/p>\n
By embedding security from the beginning and continuously reassessing controls, organizations align cybersecurity with broader business strategies, boosting resilience, reducing downtime, and ensuring that defenses adapt to risk.<\/p>\n
Think of NIST 800-39 and 800-37, combined with the Enterprise TruRisk Platform, as today\u2019s Dowding System. A unified command-and-control structure where intelligence flows freely, decisions are informed, and responses are swift. By applying these frameworks, cybersecurity leaders aren\u2019t just protecting systems but embedding resilience into the DNA of the business. And with solutions like Qualys’ Enterprise TruRisk Platform, leaders have the tools to seamlessly integrate risk management, streamline operations, and continuously fortify defenses, ensuring their business stays ahead of the ever-evolving threat landscape.<\/p>\n
## Informed, Prioritized, Aligned – Enterprise TruRisk Management<\/p>\n
Qualys Enterprise TruRisk  Management (ETM) unifies vulnerability, threat, and asset data, _regardless of source_ , into a single, business-aligned view. It enables ownership assignment, enrichment, and deduplicated data, while connecting tooling to _real_ financial impact. With native connectors and open integrations, organizations pull in data from across their ecosystem: Threat intel, third-party data, and CMDBs, in one shared platform. (See built-in connectors)<\/p>\n
Teams gain cockpit-level visibility into risk, with search tokens, dynamic report tools, or automated continuous monitoring response rules, all from the same interface.<\/p>\n
The business context drives every decision. ETM enables customized Business Entity creation, assignment of risk tolerance, and tracking exposure. That’s how you see where risk lives, how it trends, and where to act first based on _what_ matters to the business.<\/p>\n
<\/p>\n
**See top risky groups, their value, and trends:**<\/p>\n
<\/p>\n
**Customized Risk Reduction priority building:**<\/p>\n
<\/p>\n
With Qualys ETM, organizations operate from a single source of truth. Risk is measured, communicated, and acted on confidently across teams. With fewer clicks and fewer silos, a single agent delivers greater clarity, speed, and time, enabling more informed decisions that align cyber risk with business priorities.<\/p>\n
## From Measurement to Leadership: Communicating & Executing with Purpose<\/p>\n
Steps 1 through 4 to TruRisk laid the groundwork: mapping assets, understanding threats, prioritizing what truly matters, and communicating risk. With this foundation, you\u2019ve moved beyond the fog of digital war.<\/p>\n
Step 5 is where leadership turns into action, strategy becomes execution, and risk is tackled, not just tracked. This is when teams shift from identifying to addressing risk. Step 5 is about executing with authority, marshaling the right resources, aligning teams, and closing gaps that matter most to your business.<\/p>\n
Every step has led to this: It\u2019s time to de-risk the business. <\/p>\n
**Stay tuned for the next and final chapter of this series**!\n<\/p><\/div>\n
View Advisory Details<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Security Update News Update Information Title How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 Update ID QUALYSBLOG:6C8D3EDFD5E5127FC8BB1DD0AD0C3D38 Type qualysblog Published 2025-06-25T15:00:00 Last…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,34,12,13,33,120,7,11,5],"class_list":["post-7341","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-cvss-00","tag-exploit","tag-news","tag-none","tag-qualysblog","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n
How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/zero.redgem.net\/?p=7341\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem\" \/>\n<meta property=\"og:description\" content=\"Security Update News Update Information Title How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 Update ID QUALYSBLOG:6C8D3EDFD5E5127FC8BB1DD0AD0C3D38 Type qualysblog Published 2025-06-25T15:00:00 Last...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/zero.redgem.net\/?p=7341\" \/>\n<meta property=\"og:site_name\" content=\"zero redgem\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-29T10:46:01+00:00\" \/>\n<meta name=\"author\" content=\"invoker\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"invoker\" \/>\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\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341\"},\"author\":{\"name\":\"invoker\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#\\\/schema\\\/person\\\/fbfeae8dfad117ac08a7621bee1a1dca\"},\"headline\":\"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122\",\"datePublished\":\"2025-06-29T10:46:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341\"},\"wordCount\":1891,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#organization\"},\"keywords\":[\"CVE\",\"CVSS\",\"CVSS-0.0\",\"exploit\",\"news\",\"NONE\",\"qualysblog\",\"Security\",\"tapic\",\"Vulnerability\"],\"articleSection\":[\"category_news\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/zero.redgem.net\\\/?p=7341#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341\",\"url\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341\",\"name\":\"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#website\"},\"datePublished\":\"2025-06-29T10:46:01+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/zero.redgem.net\\\/?p=7341\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/?p=7341#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/zero.redgem.net\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#website\",\"url\":\"https:\\\/\\\/zero.redgem.net\\\/\",\"name\":\"zero redgem\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/zero.redgem.net\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#organization\",\"name\":\"zero redgem\",\"url\":\"https:\\\/\\\/zero.redgem.net\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"\",\"contentUrl\":\"\",\"width\":191,\"height\":188,\"caption\":\"zero redgem\"},\"image\":{\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/zero.redgem.net\\\/#\\\/schema\\\/person\\\/fbfeae8dfad117ac08a7621bee1a1dca\",\"name\":\"invoker\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g\",\"caption\":\"invoker\"},\"sameAs\":[\"https:\\\/\\\/zero.redgem.net\"],\"url\":\"https:\\\/\\\/zero.redgem.net\\\/?author=1\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem","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:\/\/zero.redgem.net\/?p=7341","og_locale":"en_US","og_type":"article","og_title":"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem","og_description":"Security Update News Update Information Title How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 Update ID QUALYSBLOG:6C8D3EDFD5E5127FC8BB1DD0AD0C3D38 Type qualysblog Published 2025-06-25T15:00:00 Last...","og_url":"https:\/\/zero.redgem.net\/?p=7341","og_site_name":"zero redgem","article_published_time":"2025-06-29T10:46:01+00:00","author":"invoker","twitter_card":"summary_large_image","twitter_misc":{"Written by":"invoker","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/zero.redgem.net\/?p=7341#article","isPartOf":{"@id":"https:\/\/zero.redgem.net\/?p=7341"},"author":{"name":"invoker","@id":"https:\/\/zero.redgem.net\/#\/schema\/person\/fbfeae8dfad117ac08a7621bee1a1dca"},"headline":"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122","datePublished":"2025-06-29T10:46:01+00:00","mainEntityOfPage":{"@id":"https:\/\/zero.redgem.net\/?p=7341"},"wordCount":1891,"commentCount":0,"publisher":{"@id":"https:\/\/zero.redgem.net\/#organization"},"keywords":["CVE","CVSS","CVSS-0.0","exploit","news","NONE","qualysblog","Security","tapic","Vulnerability"],"articleSection":["category_news"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/zero.redgem.net\/?p=7341#respond"]}]},{"@type":"WebPage","@id":"https:\/\/zero.redgem.net\/?p=7341","url":"https:\/\/zero.redgem.net\/?p=7341","name":"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122 - zero redgem","isPartOf":{"@id":"https:\/\/zero.redgem.net\/#website"},"datePublished":"2025-06-29T10:46:01+00:00","breadcrumb":{"@id":"https:\/\/zero.redgem.net\/?p=7341#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/zero.redgem.net\/?p=7341"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/zero.redgem.net\/?p=7341#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/zero.redgem.net\/"},{"@type":"ListItem","position":2,"name":"How to Quantify Risk and Communicate Effectively: Step 4 to TruRisk\u2122"}]},{"@type":"WebSite","@id":"https:\/\/zero.redgem.net\/#website","url":"https:\/\/zero.redgem.net\/","name":"zero redgem","description":"","publisher":{"@id":"https:\/\/zero.redgem.net\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/zero.redgem.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/zero.redgem.net\/#organization","name":"zero redgem","url":"https:\/\/zero.redgem.net\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/zero.redgem.net\/#\/schema\/logo\/image\/","url":"","contentUrl":"","width":191,"height":188,"caption":"zero redgem"},"image":{"@id":"https:\/\/zero.redgem.net\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/zero.redgem.net\/#\/schema\/person\/fbfeae8dfad117ac08a7621bee1a1dca","name":"invoker","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f17c01d7338e6932bcde121cf83569393df3374625d25afd62677cfb528f2e3e?s=96&d=mm&r=g","caption":"invoker"},"sameAs":["https:\/\/zero.redgem.net"],"url":"https:\/\/zero.redgem.net\/?author=1"}]}},"_links":{"self":[{"href":"https:\/\/zero.redgem.net\/index.php?rest_route=\/wp\/v2\/posts\/7341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zero.redgem.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zero.redgem.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zero.redgem.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zero.redgem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7341"}],"version-history":[{"count":0,"href":"https:\/\/zero.redgem.net\/index.php?rest_route=\/wp\/v2\/posts\/7341\/revisions"}],"wp:attachment":[{"href":"https:\/\/zero.redgem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zero.redgem.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zero.redgem.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}