{"id":8985,"date":"2026-08-28T13:38:41","date_gmt":"2026-08-28T08:08:41","guid":{"rendered":"https:\/\/www.anakage.com\/blog\/?p=8985"},"modified":"2026-08-28T13:38:41","modified_gmt":"2026-08-28T08:08:41","slug":"how-anakage-coexists-with-edr-the-security-guard-protects-the-door-anakage-keeps-the-building-running","status":"publish","type":"post","link":"https:\/\/www.anakage.com\/blog\/how-anakage-coexists-with-edr-the-security-guard-protects-the-door-anakage-keeps-the-building-running\/","title":{"rendered":"How Anakage Coexists with EDR: The Security Guard Protects the Door. Anakage Keeps the Building Running."},"content":{"rendered":"

There is a question that increasingly comes up in modern enterprise IT environments:<\/span>\u00a0<\/span><\/p>\n

\u201cWe already have an EDR. Why would we need another agent on the endpoint?\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

It is a fair question.<\/span>\u00a0<\/span><\/p>\n

Enterprise endpoints are already crowded with security, management, monitoring, and productivity tools. No IT leader wants another overlapping layer, another console, or another agent competing for resources.<\/span>\u00a0<\/span><\/p>\n

But there is an important distinction that often gets lost in the conversation:<\/span>\u00a0<\/span><\/p>\n

Security and endpoint operations may share the same device, but they are solving different problems.<\/span><\/b>\u00a0<\/span><\/p>\n

That is where the relationship between EDR and\u00a0Anakage\u00a0becomes interesting.<\/span>\u00a0<\/span><\/p>\n

The easiest way to understand it is to stop thinking of\u00a0Anakage\u00a0as another security gate.<\/span>\u00a0<\/span><\/p>\n

Think of it as the team\u00a0working\u00a0<\/span>inside the building<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

The endpoint is under pressure every second<\/span>\u00a0<\/span><\/p>\n

The modern enterprise endpoint is no longer a quiet workplace asset. It is one of the most active points of interaction between employees, applications, identities,\u00a0networks\u00a0and external services.<\/span>\u00a0<\/span><\/p>\n

Palo Alto Networks\u2019 Unit 42 found that\u00a0<\/span>endpoints were involved in 72% of the incidents in its 2025 incident-response dataset<\/span><\/b>. More strikingly, attackers\u00a0operated\u00a0across multiple fronts in\u00a0<\/span>84% of incidents<\/span><\/b>, showing that modern attacks rarely stay confined to a single security layer.<\/span>\u00a0<\/span><\/p>\n

The scale of activity is also enormous.<\/span>\u00a0<\/span><\/p>\n

In India\u2019s 2025 cyber threat report,\u00a0Seqrite\u00a0reported more than\u00a0<\/span>369 million security incidents across 8.44 million endpoints<\/span><\/b>\u00a0during its observation period\u2014an average of\u00a0roughly\u00a0<\/span>702\u00a0incidents per minute, or about 11 per second<\/span><\/b>. Importantly, these figures\u00a0represent\u00a0detected security incidents rather than 11 unique successful attacks every second.<\/span>\u00a0<\/span><\/p>\n

That distinction matters.<\/span>\u00a0<\/span><\/p>\n

Because the job of the enterprise security stack is not to make the endpoint perfectly quiet.<\/span>\u00a0<\/span><\/p>\n

Its job is to make the endpoint\u00a0<\/span>defensible<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

And this is exactly where EDR plays its role.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

EDR is the door guard\u2014and a very capable one<\/span>\u00a0<\/span><\/p>\n

Modern Endpoint Detection and Response platforms continuously\u00a0monitor\u00a0endpoint activity,\u00a0identify\u00a0suspicious behavior, investigate\u00a0threats\u00a0and enable response actions. Microsoft describes EDR as a technology that\u00a0monitors\u00a0endpoint activity, detects suspicious\u00a0behavior\u00a0and helps security teams investigate and respond to threats in real time.<\/span>\u00a0<\/span><\/p>\n

Modern EDR platforms can go much further than simply raising an alert.<\/span>\u00a0<\/span><\/p>\n

They can use behavioral analytics, threat\u00a0intelligence\u00a0and automated response to detect malicious activity and, in some scenarios, isolate a compromised endpoint or\u00a0contain\u00a0an attack.<\/span>\u00a0<\/span><\/p>\n

So\u00a0imagine the endpoint as a building.<\/span>\u00a0<\/span><\/p>\n

EDR is\u00a0the\u00a0sophisticated security system at the door.<\/span>\u00a0<\/span><\/p>\n

It watches who\u00a0is\u00a0entering.<\/span>\u00a0<\/span><\/p>\n

It\u00a0identifies\u00a0suspicious behavior.<\/span>\u00a0<\/span><\/p>\n

It can stop a threat.<\/span>\u00a0<\/span><\/p>\n

It can isolate a compromised device.<\/span>\u00a0<\/span><\/p>\n

It can investigate what happened.<\/span>\u00a0<\/span><\/p>\n

It can help security teams understand whether someone has crossed the line from normal activity into malicious activity.<\/span>\u00a0<\/span><\/p>\n

That is an essential job.<\/span><\/b>\u00a0<\/span><\/p>\n

But now consider what happens inside the building.<\/span>\u00a0<\/span><\/p>\n

A printer\u00a0stops working.<\/span>\u00a0<\/span><\/p>\n

The VPN configuration is broken.<\/span>\u00a0<\/span><\/p>\n

Disk space falls below a healthy threshold.<\/span>\u00a0<\/span><\/p>\n

An application crashes repeatedly.<\/span>\u00a0<\/span><\/p>\n

A required\u00a0service stops.<\/span>\u00a0<\/span><\/p>\n

A patch is missing.<\/span>\u00a0<\/span><\/p>\n

A security\u00a0control becomes inactive.<\/span>\u00a0<\/span><\/p>\n

A user\u00a0encounters\u00a0a recurring issue and raises a ticket.<\/span>\u00a0<\/span><\/p>\n

None of these problems necessarily\u00a0represent\u00a0a malicious actor.<\/span>\u00a0<\/span><\/p>\n

But they can still bring the employee\u2019s work to a halt.<\/span>\u00a0<\/span><\/p>\n

And this is where another capability is\u00a0required.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Not every endpoint problem is a security incident<\/span>\u00a0<\/span><\/p>\n

This is the fundamental difference.<\/span>\u00a0<\/span><\/p>\n

EDR asks:<\/span><\/b>\u00a0<\/span><\/p>\n

\u201cIs this endpoint exhibiting behavior that could indicate a threat?\u201d<\/span>\u00a0<\/span><\/p>\n

Endpoint operations\u00a0asks:<\/span><\/b>\u00a0<\/span><\/p>\n

\u201cIs this endpoint healthy, compliant, usable and able to support the employee?\u201d<\/span>\u00a0<\/span><\/p>\n

Those questions can exist on the same machine at the same time.<\/span>\u00a0<\/span><\/p>\n

They are not\u00a0competing\u00a0questions.<\/span>\u00a0<\/span><\/p>\n

They are\u00a0complementary ones.<\/span>\u00a0<\/span><\/p>\n

In fact, enterprise endpoint environments increasingly need both.<\/span>\u00a0<\/span><\/p>\n

An EDR platform provides security visibility and response.<\/span>\u00a0<\/span><\/p>\n

An endpoint automation platform can provide operational visibility, remediation, self-healing, guided\u00a0assistance, software automation, compliance\u00a0actions\u00a0and ITSM integration.<\/span>\u00a0<\/span><\/p>\n

Anakage\u00a0is built around this second problem.<\/span>\u00a0<\/span><\/p>\n

Its platform combines endpoint telemetry, digital employee experience, proactive remediation, self-healing, automation, software deployment, ITSM\u00a0integration\u00a0and service delivery capabilities.<\/span>\u00a0<\/span><\/p>\n

That means\u00a0Anakage\u00a0does not need to replace the security system.<\/span>\u00a0<\/span><\/p>\n

It can work alongside it.<\/span><\/b>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

The overlooked space between \u201csecure\u201d and \u201cworking\u201d<\/span>\u00a0<\/span><\/p>\n

This is where\u00a0the coexistence story becomes\u00a0especially important.<\/span>\u00a0<\/span><\/p>\n

An endpoint can be\u00a0<\/span>secure enough to pass a security check and still be a terrible employee experience.<\/span><\/b>\u00a0<\/span><\/p>\n

Consider a few examples.<\/span>\u00a0<\/span><\/p>\n

A laptop has its EDR agent running correctly, but the device is running critically low on disk space.<\/span>\u00a0<\/span><\/p>\n

An EDR may correctly see nothing malicious happening.<\/span>\u00a0<\/span><\/p>\n

The employee, meanwhile, cannot install an application, save a\u00a0file\u00a0or complete a software update.<\/span>\u00a0<\/span><\/p>\n

Or consider an application that repeatedly crashes because of a configuration or dependency issue.<\/span>\u00a0<\/span><\/p>\n

Again, there may be no security\u00a0incident.<\/span>\u00a0<\/span><\/p>\n

There is simply an employee who cannot work.<\/span>\u00a0<\/span><\/p>\n

Or take compliance.<\/span>\u00a0<\/span><\/p>\n

A security platform may\u00a0identify\u00a0that a control is\u00a0inactive\u00a0or that a configuration needs attention. The security team now knows that something requires remediation.<\/span>\u00a0<\/span><\/p>\n

But someone still\u00a0has to\u00a0perform\u00a0the operational\u00a0action.<\/span>\u00a0<\/span><\/p>\n

This is where endpoint automation can become the bridge between\u00a0<\/span>detection and action<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

Anakage\u2019s\u00a0event-driven automation capabilities, for example, can use endpoint telemetry and configurable conditions to trigger targeted actions. A documented example is automatically\u00a0initiating\u00a0remediation when a threshold such as low disk space is reached; the platform can also trigger actions when security-relevant conditions such as antivirus inactivity are detected.<\/span>\u00a0<\/span><\/p>\n

The key point is not that\u00a0Anakage\u00a0is \u201cbetter security\u201d than an EDR.<\/span>\u00a0<\/span><\/p>\n

It\u00a0isn\u2019t\u00a0trying to be.<\/span>\u00a0<\/span><\/p>\n

The point is:<\/span>\u00a0<\/span><\/p>\n

Once the security platform\u00a0identifies\u00a0a condition, the endpoint still needs to be managed.<\/span><\/b>\u00a0<\/span><\/p>\n

That is where the two can complement each other.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Think of EDR as the guard. Think of\u00a0Anakage\u00a0as the response crew.<\/span>\u00a0<\/span><\/p>\n

The best enterprise environments do not ask one system to do every job.<\/span>\u00a0<\/span><\/p>\n

A sophisticated building has a security system.<\/span>\u00a0<\/span><\/p>\n

It also has facilities management.<\/span>\u00a0<\/span><\/p>\n

Security cameras do not repair a broken elevator.<\/span>\u00a0<\/span><\/p>\n

Access-control systems do not refill the fire extinguisher.<\/span>\u00a0<\/span><\/p>\n

A security alarm does not fix an air-conditioning failure.<\/span>\u00a0<\/span><\/p>\n

They coexist because they\u00a0operate\u00a0at\u00a0different layers of the same environment.<\/span>\u00a0<\/span><\/p>\n

The same principle applies to the endpoint.<\/span>\u00a0<\/span><\/p>\n

EDR<\/span>\u00a0<\/span><\/p>\n

Protects the endpoint from threats.<\/span><\/b>\u00a0<\/span><\/p>\n

It\u00a0monitors\u00a0behavior,\u00a0identifies\u00a0suspicious activity, investigates\u00a0incidents\u00a0and supports containment and response.<\/span>\u00a0<\/span><\/p>\n

Anakage<\/span>\u00a0<\/span><\/p>\n

Keeps the endpoint operational and the employee productive.<\/span><\/b>\u00a0<\/span><\/p>\n

It can\u00a0observe\u00a0endpoint health and experience, proactively remediate common issues, automate endpoint actions, support self-service\u00a0and integrate with ITSM workflows.<\/span>\u00a0<\/span><\/p>\n

Together, the model becomes much more powerful:<\/span>\u00a0<\/span><\/p>\n

EDR detects and protects.<\/span><\/b>
\nAnakage observes,\u00a0fixes\u00a0and automates.<\/span><\/b>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

And the most important part: coexistence does not mean duplication<\/span>\u00a0<\/span><\/p>\n

The concern about two agents is legitimate.<\/span>\u00a0<\/span><\/p>\n

Enterprises need to know:<\/span>\u00a0<\/span><\/p>\n

Will they interfere with each other?<\/span>\u00a0<\/span><\/p>\n

Will both try to\u00a0modify\u00a0the same endpoint configuration?<\/span>\u00a0<\/span><\/p>\n

Will one create noise for the other?<\/span>\u00a0<\/span><\/p>\n

Will IT teams end up managing two disconnected systems?<\/span>\u00a0<\/span><\/p>\n

This is where architecture and governance matter more than the mere presence of two agents.<\/span>\u00a0<\/span><\/p>\n

Anakage\u2019s own platform positioning explicitly supports keeping existing investments and using\u00a0Anakage\u00a0as an\u00a0<\/span>automation layer<\/span><\/b>\u00a0across an existing enterprise tool landscape rather than forcing a rip-and-replace approach. Its current platform also emphasizes integrations across ITSM,\u00a0UEM\u00a0and security tooling.<\/span>\u00a0<\/span><\/p>\n

In other words, coexistence should not mean:<\/span>\u00a0<\/span><\/p>\n

\u201cLet\u2019s install another tool and hope the two agents behave.\u201d<\/span>\u00a0<\/span><\/p>\n

It should mean:<\/span>\u00a0<\/span><\/p>\n

\u201cLet\u2019s give each system a clearly defined job.\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

The security platform owns threat detection and security\u00a0response.<\/span>\u00a0<\/span><\/p>\n

The endpoint automation layer owns operational remediation and employee-facing resolution.<\/span>\u00a0<\/span><\/p>\n

The ITSM platform\u00a0remains\u00a0the system of record for incidents and requests.<\/span>\u00a0<\/span><\/p>\n

And integration connects the three.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

What does this look like in the real world?<\/span>\u00a0<\/span><\/p>\n

Imagine an employee\u2019s laptop suddenly\u00a0develops\u00a0a problem.<\/span>\u00a0<\/span><\/p>\n

Scenario 1: A real security threat<\/span>\u00a0<\/span><\/p>\n

EDR detects suspicious behavior.<\/span>\u00a0<\/span><\/p>\n

The security platform investigates the activity and can take containment or remediation action according to the organization\u2019s security policies.<\/span>\u00a0<\/span><\/p>\n

This is EDR\u2019s territory.<\/span><\/b>\u00a0<\/span><\/p>\n

Anakage\u00a0does not need to interfere.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Scenario 2: A routine endpoint problem<\/span>\u00a0<\/span><\/p>\n

The laptop\u2019s disk falls below a defined threshold.<\/span>\u00a0<\/span><\/p>\n

There is no malicious activity.<\/span>\u00a0<\/span><\/p>\n

Anakage\u00a0detects the condition through endpoint telemetry and can trigger an approved cleanup or remediation workflow.<\/span>\u00a0<\/span><\/p>\n

The employee gets back to work without turning a small issue into a service-desk interaction.<\/span><\/b>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Scenario 3: A security-related operational condition<\/span>\u00a0<\/span><\/p>\n

A security\u00a0control becomes inactive.<\/span>\u00a0<\/span><\/p>\n

The EDR or security stack can surface the condition.<\/span>\u00a0<\/span><\/p>\n

Anakage\u00a0can then\u00a0participate\u00a0in the operational remediation workflow\u2014subject, of course, to the organization\u2019s security policies and approvals.<\/span>\u00a0<\/span><\/p>\n

The distinction is important:<\/span>\u00a0<\/span><\/p>\n

EDR\u00a0identifies\u00a0the security condition.<\/span><\/b>
\nAnakage can help execute the operational fix.<\/span><\/b>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Scenario 4: The employee raises a ticket anyway<\/span>\u00a0<\/span><\/p>\n

This is where the relationship becomes even more interesting.<\/span>\u00a0<\/span><\/p>\n

Anakage\u00a0has long supported ITSM-integrated endpoint automation, where a user-created ticket can be\u00a0analyzed\u00a0and a relevant endpoint solution can be triggered automatically rather than waiting for a service-desk engineer to manually intervene.<\/span>\u00a0<\/span><\/p>\n

The ticket\u00a0remains\u00a0part of the\u00a0service-management\u00a0process.<\/span>\u00a0<\/span><\/p>\n

But the endpoint action does not necessarily have to wait for a human.<\/span>\u00a0<\/span><\/p>\n

The result is a different operating model:<\/span>\u00a0<\/span><\/p>\n

Detect \u2192 Decide \u2192 Automate \u2192 Resolve \u2192 Record<\/span><\/b>\u00a0<\/span><\/p>\n

rather than:<\/span>\u00a0<\/span><\/p>\n

Detect \u2192 Ticket \u2192 Queue \u2192 Engineer \u2192 Remote session \u2192 Resolve<\/span><\/b>\u00a0<\/span><\/p>\n

That distinction becomes significant at\u00a0enterprise\u00a0scale.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

The real\u00a0objective\u00a0is not \u201cmore tools\u201d<\/span>\u00a0<\/span><\/p>\n

This is\u00a0probably the\u00a0most\u00a0important point\u00a0in the entire discussion.<\/span>\u00a0<\/span><\/p>\n

The goal should never be to give IT another dashboard.<\/span>\u00a0<\/span><\/p>\n

It should be to reduce the amount of work that humans have to perform manually.<\/span>\u00a0<\/span><\/p>\n

Security teams should be able to focus on security.<\/span>\u00a0<\/span><\/p>\n

Service-desk teams should be able to focus on issues that genuinely require human judgment.<\/span>\u00a0<\/span><\/p>\n

Employees should not have to wait for an engineer to fix problems that automation can safely resolve.<\/span>\u00a0<\/span><\/p>\n

And endpoint teams should have enough telemetry and control to move from reactive support to proactive operations.<\/span>\u00a0<\/span><\/p>\n

This is also why the conversation about EDR and\u00a0Anakage\u00a0should not be framed as\u00a0<\/span>\u201cEDR versus\u00a0Anakage.\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

It is a false choice.<\/span>\u00a0<\/span><\/p>\n

The more useful question is:<\/span>\u00a0<\/span><\/p>\n

\u201cWhat happens after the endpoint tells us that something needs attention?\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

Because an alert is not the same thing as a resolution.<\/span>\u00a0<\/span><\/p>\n

A detection\u00a0is not the same thing as remediation.<\/span>\u00a0<\/span><\/p>\n

And a secure endpoint is not automatically a healthy endpoint.<\/span>\u00a0<\/span><\/p>\n

\u00a0<\/span><\/p>\n

The enterprise endpoint needs both defense and resilience<\/span>\u00a0<\/span><\/p>\n

The modern endpoint has become too important to manage through a single lens.<\/span>\u00a0<\/span><\/p>\n

It\u00a0has to\u00a0be:<\/span>\u00a0<\/span><\/p>\n

Secure enough to resist threats.<\/span><\/b>
\nHealthy enough to perform.<\/span><\/b>
\nCompliant enough to meet policy.<\/span><\/b>
\nAutomated enough to recover.<\/span><\/b>
\nSimple enough for employees to use.<\/span><\/b>\u00a0<\/span><\/p>\n

EDR is a critical part of the first\u00a0objective.<\/span>\u00a0<\/span><\/p>\n

Anakage\u00a0can help address the others.<\/span>\u00a0<\/span><\/p>\n

And that is why coexistence makes sense.<\/span>\u00a0<\/span><\/p>\n

Not because an enterprise needs more software.<\/span>\u00a0<\/span><\/p>\n

But because\u00a0<\/span>different problems deserve different capabilities.<\/span><\/b>\u00a0<\/span><\/p>\n

The security guard should remain focused on keeping threats out.<\/span>\u00a0<\/span><\/p>\n

The team inside should keep the building functioning.<\/span>\u00a0<\/span><\/p>\n

And when those two teams communicate well, the organization gets something more valuable than either one alone:<\/span>\u00a0<\/span><\/p>\n

an endpoint that is not only protected\u2014but continuously operational.<\/span><\/b>\u00a0<\/span><\/p>\n

 <\/p>\n

The Coexistence Series<\/span>\u00a0<\/span><\/p>\n

The EDR conversation is only one example of a broader question enterprise IT leaders are asking:<\/span>\u00a0<\/span><\/p>\n

\u201cWhere does\u00a0Anakage\u00a0fit when we already have a tool for that?\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

That question deserves a better answer than \u201creplace it.\u201d<\/span>\u00a0<\/span><\/p>\n

The more interesting answer is often:<\/span>\u00a0<\/span><\/p>\n

\u201cKeep what already works. Add automation where the operational gap\u00a0remains.\u201d<\/span><\/b>\u00a0<\/span><\/p>\n

That opens the door to a wider coexistence series\u2014looking at how\u00a0Anakage\u00a0can complement existing investments across security, endpoint management, ITSM, patching, employee\u00a0experience\u00a0and automation.<\/span>\u00a0<\/span><\/p>\n

Because in a mature enterprise environment, the winning strategy is rarely about having one tool\u00a0do\u00a0everything.<\/span>\u00a0<\/span><\/p>\n

It is about making the tools you already have\u00a0work\u00a0harder\u2014together.<\/span><\/b>\u00a0<\/span><\/p>\n

Sources: Microsoft Security on EDR capabilities and endpoint detection\/response; Palo Alto Networks Unit 42 2025 Incident Response Report;\u00a0Seqrite\u00a0India Cyber Threat Report 2025;\u00a0Anakage\u00a0platform and endpoint automation documentation.<\/span><\/i>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

There is a question that increasingly comes up in modern enterprise IT environments:\u00a0 \u201cWe already have an EDR. Why would […]<\/p>\n","protected":false},"author":1,"featured_media":8986,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[1],"tags":[],"coauthors":[88],"class_list":["post-8985","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"views":30,"_links":{"self":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/8985","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/comments?post=8985"}],"version-history":[{"count":1,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/8985\/revisions"}],"predecessor-version":[{"id":8987,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/8985\/revisions\/8987"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media\/8986"}],"wp:attachment":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media?parent=8985"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/categories?post=8985"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/tags?post=8985"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/coauthors?post=8985"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}