{"id":18008,"date":"2026-06-24T15:54:53","date_gmt":"2026-06-24T15:54:53","guid":{"rendered":"https:\/\/www.securitytoday.de\/?p=18008"},"modified":"2026-07-09T16:13:54","modified_gmt":"2026-07-09T16:13:54","slug":"protective-dns-the-layer-that-many-overlook","status":"publish","type":"post","link":"https:\/\/www.securitytoday.de\/en\/2026\/06\/24\/protective-dns-the-layer-that-many-overlook\/","title":{"rendered":"Protective DNS: the layer that many overlook"},"content":{"rendered":"<div>\n<p style=\"color:#69d8ed;font-size:0.9em;margin:0 0 16px;padding:0;\">7 min read<\/p>\n<p style=\"line-height:1.8;\"><strong>Before malware reaches its command-and-control server, it makes a DNS query. Before an employee lands on a fake login page, their device resolves its domain. Almost every attack stalls at a point most companies never inspect: at the DNS layer. Protective DNS plugs that gap-and it\u2019s one of the cheapest security layers you can add.<\/strong><\/p>\n<div style=\"background:#003340;color:#fff;padding:32px 36px;margin:32px 0;border-radius:8px;\">\n<p style=\"margin:0 0 18px 0;font-size:0.95em;font-weight:800;text-transform:uppercase;letter-spacing:0.2em;color:#69d8ed;border-bottom:2px solid rgba(105,216,237,0.25);padding-bottom:12px;\">Key Takeaways<\/p>\n<ul style=\"margin:0;padding-left:22px;color:rgba(255,255,255,0.92);line-height:1.6;\">\n<li style=\"margin-bottom:12px;\"><strong style=\"color:#69d8ed;\">DNS is the common denominator:<\/strong> Malware control, phishing and data exfiltration nearly always start with a name lookup. If you don\u2019t filter DNS, you\u2019re ignoring the earliest detection stage.<\/li>\n<li style=\"margin-bottom:12px;\"><strong style=\"color:#69d8ed;\">Protective DNS blocks at the root:<\/strong> A hardened resolver checks every request against threat intelligence and stops known C2 servers, newly registered domains and phishing pages before the connection is ever established.<\/li>\n<li><strong style=\"color:#69d8ed;\">Encrypted DNS is the weak spot:<\/strong> DNS over HTTPS bypasses the corporate resolver-and the filter. If you don\u2019t control this channel, you\u2019re undermining your own protection.<\/li>\n<\/ul>\n<\/div>\n<p style=\"font-size:0.88em;color:#b8c5ce;margin:20px 0 32px 0;border-top:1px solid rgba(230,227,218,0.12);border-bottom:1px solid rgba(230,227,218,0.12);padding:10px 0;\"><span style=\"color:#69d8ed;font-weight:700;text-transform:uppercase;font-size:0.72em;letter-spacing:0.14em;margin-right:14px;\">Related:<\/span><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/04\/26\/itdr-joins-siem-and-edr-detection-architecture-2026\/\" style=\"color:#333;text-decoration:underline;\">ITDR alongside SIEM and EDR: Detection architecture 2026<\/a>&nbsp;&nbsp;<span style=\"color:#ccc;\">\/<\/span>&nbsp;&nbsp;<a href=\"https:\/\/www.securitytoday.de\/en\/2026\/05\/29\/the-edge-device-as-a-ransomware-gateway-why-mfa-at-the-vpn-is-not-enough\/\" style=\"color:#333;text-decoration:underline;\">Edge device as ransomware gateway: why MFA on VPN isn\u2019t enough<\/a><\/p>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">Why attackers route through DNS<\/h2>\n<p style=\"line-height:1.8;\">DNS is the internet\u2019s address book. Every connection starts with a name being translated into an address-whether you\u2019re visiting a website or malware reaching out to its command server. That\u2019s why DNS is the one point almost every attack chain touches, whether it\u2019s phishing, secondary payload delivery or covert data exfiltration.<\/p>\n<p style=\"line-height:1.8;\">Most defenses kick in later. Antivirus scans the file, the firewall inspects traffic, EDR watches endpoint behavior. The DNS request that came before often slips through unfiltered, often straight to a public resolver. That means missing the chance to stop an attack before it even establishes a connection.<\/p>\n<p style=\"line-height:1.8;\">This detection stage isn\u2019t just early-it\u2019s also inexpensive. If you already run DNS, which every business does, you can usually retrofit the protection with existing infrastructure. That makes Protective DNS one of the few security layers with an outstanding cost-to-benefit ratio.<\/p>\n<p style=\"line-height:1.8;\"><strong>What is Protective DNS?<\/strong> Protective DNS is a DNS resolver that checks every name lookup against threat intelligence and blocks or redirects requests to known malicious domains. Instead of returning a dangerous address, it serves a block page. Authorities like Germany\u2019s BSI and security services in several countries explicitly recommend the approach.<\/p>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">What a hardened resolver blocks<\/h2>\n<p style=\"line-height:1.8;\">A protective DNS service operates with blocklists fed by continuously updated threat data. Technically, it often implements this via Response Policy Zones-rules that refuse to resolve specific domains from the outset. The practical benefit lies in the categories it covers and the blind spots it deliberately leaves open.<\/p>\n<div class=\"evm-pros-cons\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(280px,1fr));gap:16px;margin:28px 0;\">\n<div style=\"background:#fafafa;border-top:3px solid #2d7a3e;padding:18px 20px;border-radius:4px;\">\n<p style=\"margin:0 0 10px 0;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.12em;color:#2d7a3e;\">What protective DNS delivers<\/p>\n<ul style=\"margin:0;padding-left:18px;color:#333;line-height:1.55;font-size:0.95em;\">\n<li style=\"margin-bottom:6px;\">Blocks known command-and-control servers used by malware<\/li>\n<li style=\"margin-bottom:6px;\">Stops phishing and typosquatting domains<\/li>\n<li style=\"margin-bottom:6px;\">Acts early on freshly registered domains<\/li>\n<li>Provides valuable logs for detecting compromised hosts<\/li>\n<\/ul><\/div>\n<div style=\"background:#fafafa;border-top:3px solid #c0392b;padding:18px 20px;border-radius:4px;\">\n<p style=\"margin:0 0 10px 0;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.12em;color:#c0392b;\">Where the limits lie<\/p>\n<ul style=\"margin:0;padding-left:18px;color:#333;line-height:1.55;font-size:0.95em;\">\n<li style=\"margin-bottom:6px;\">Unknown, brand-new domains slip through<\/li>\n<li style=\"margin-bottom:6px;\">Direct IP-based connections bypass DNS entirely<\/li>\n<li style=\"margin-bottom:6px;\">Encrypted DNS undermines the filter<\/li>\n<li>No substitute for EDR, patching, and segmentation<\/li>\n<\/ul><\/div>\n<\/div>\n<p style=\"line-height:1.8;\">Protective DNS is therefore no silver bullet, but one layer in the stack. It removes a lot of early-stage load cheaply, yet it doesn\u2019t replace later stages. Precisely this understanding determines whether its rollout ends as a genuine security gain or as a false sense of security.<\/p>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">The gap encrypted DNS opens up<\/h2>\n<p style=\"line-height:1.8;\">The biggest practical stumbling block has an unassuming name: DNS over HTTPS. Modern browsers and many applications can send their DNS queries encrypted and straight to an external provider, bypassing the corporate resolver. From a privacy standpoint, this is intentional. From a defense standpoint, it\u2019s a hole-because your own protective DNS filter never sees those requests.<\/p>\n<p style=\"line-height:1.8;\">Malware increasingly exploits this route, especially to evade filters. If you deploy protective DNS without controlling encrypted DNS, you lock the front door while leaving the window wide open. This is where I\u2019ve seen setups that looked pristine on paper and failed completely in practice.<\/p>\n<p style=\"line-height:1.8;\">Countermeasures are known, but require discipline: enforce your resolver as the only permitted DNS path, block external encrypted DNS at the firewall, and grant exceptions deliberately and with documentation. Without this step, even the most polished filter remains powerless.<\/p>\n<h2 style=\"margin-top:48px;margin-bottom:18px;\">How to Implement Protective DNS<\/h2>\n<p style=\"line-height:1.8;\">Implementation is straightforward if you follow the sequence. Starting to block domains before understanding what\u2019s normal in your network mostly creates disruptions and erodes acceptance.<\/p>\n<div class=\"evm-timeline\" style=\"margin:28px 0;border:1px solid rgba(230,227,218,0.12);border-radius:6px;overflow:hidden;\">\n<div style=\"background:#003340;color:#fff;padding:12px 18px;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.14em;\">Four-step introduction<\/div>\n<div style=\"padding:8px 0;\">\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#69d8ed;\">Step 1<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Start in observation mode.<\/strong> Let the hardened resolver log only-do not block yet. You\u2019ll see which domains your network actually queries and avoid nasty surprises.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#69d8ed;\">Step 2<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Block gradually.<\/strong> Begin with clearly malicious categories, then refine. From day one, maintain a short exception list for legitimate edge cases.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#69d8ed;\">Step 3<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Close encrypted DNS.<\/strong> Block external DNS over HTTPS at the firewall and enforce your own resolver as the sole path. Without this step, the filter can be bypassed.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;\">\n<div style=\"min-width:90px;font-weight:700;color:#69d8ed;\">Step 4<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Feed logs into detection.<\/strong> Ingest the query logs into your SIEM. A host repeatedly querying blocked domains is a reliable early indicator of compromise.<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n<h2 style=\"padding-top:64px;margin-bottom:20px;\">Frequently Asked Questions<\/h2>\n<p class=\"st-faq-hint\">Every question is locked. A tap unlocks the answer.<\/p>\n<details>\n<summary><strong>Does Protective DNS replace my firewall or EDR?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">No. Protective DNS is an early, low-cost layer that stops many attacks before a connection is ever established. Firewalls, EDR, patching, and segmentation remain essential. Protective DNS simply lightens the load for those layers by intercepting threats before the handshake.<\/p>\n<\/details>\n<details>\n<summary><strong>What\u2019s the difference between Protective DNS and a normal DNS resolver?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">A normal resolver resolves every request, even to malicious domains. A Protective DNS resolver checks each query against threat intelligence and refuses to resolve dangerous addresses-often via Response Policy Zones.<\/p>\n<\/details>\n<details>\n<summary><strong>Why is encrypted DNS a problem?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">DNS over HTTPS routes queries straight to external providers, bypassing your corporate resolver. Your filter can no longer see those requests. Without control over that channel, Protective DNS is easily circumvented-by users and malware alike.<\/p>\n<\/details>\n<details>\n<summary><strong>Is Protective DNS suitable for smaller companies?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Especially for them. The effort is minimal; existing infrastructure or a hosted service usually suffices. For teams without a large SOC, it\u2019s one of the few measures that delivers immediate, tangible impact with little ongoing maintenance.<\/p>\n<\/details>\n<details>\n<summary><strong>How can I prevent legitimate services from being blocked?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Start in pure observation mode and roll out blocking gradually. Maintain a clean exception list and set up a clear process for reporting false positives to keep operational acceptance high.<\/p>\n<\/details>\n<p><!--ST-LOWER-CARDS lang=en--><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">Editor&#8217;s Picks<\/h3>\n<p><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/06\/04\/patch-prioritization-cvss-overwhelming-soc\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/06\/patch-priorisierung-cvss-allein-ueberfordert-das-soc-cover-hero-250x143.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Patch Prioritization: Why CVSS Alone Slows Down Your SOC<\/span><\/span><\/a><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/06\/01\/14-malicious-npm-packages-in-four-hours-why-static-third-party-checks-are-no\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/06\/14-boesartige-npm-pakete-in-vier-stunden-warum-statische-third-party-pruefung-nicht-mehr-reicht-cover-hero-250x143.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">14 Malicious npm Packages in Four Hours: Why Static Third-Party Checks Are No Longer Enough<\/span><\/span><\/a><a href=\"https:\/\/www.securitytoday.de\/en\/2026\/06\/24\/when-hci-turns-backup-into-an-attack-surface\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/06\/wenn-hci-auch-das-backup-absichern-muss-hero-250x141.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#69d8ed;margin-bottom:5px;\">Editor&#8217;s Pick<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">When HCI Turns Backup into an Attack Surface<\/span><\/span><\/a><\/p>\n<h3 style=\"margin:48px 0 18px;padding-left:12px;font-size:1.05em;font-weight:800;color:#e6e3da;border-left:3px solid #69d8ed;line-height:1.2;\">More from the MBF Media Network<\/h3>\n<p><a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-ingress-nginx-eol-gateway-api-migration-51550296.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#0bb7fd;margin-bottom:5px;\">cloudmagazin<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">Ingress-NGINX is discontinued: The path to Gateway API<\/span><\/span><\/a><a href=\"https:\/\/mybusinessfuture.com\/en\/13-3-million-people-retire-the-baby-boomer-gap-arrives\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-babyboomer-renteneintritt-demografie-lue-65687936-250x167.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#aa8ac2;margin-bottom:5px;\">MyBusinessFuture<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">13.3 million people retire: The baby boomer gap arrives<\/span><\/span><\/a><a href=\"https:\/\/www.digital-chiefs.de\/en\/vmware-under-broadcom-the-exit-plan-as-a-lever\/\" style=\"display:flex;align-items:center;gap:14px;padding:12px 14px;margin:0 0 10px;background:#23261f;border:1px solid rgba(105,216,237,0.18);border-radius:12px;box-shadow:inset 0 1px 0 rgba(230,227,218,0.06),0 6px 18px rgba(0,0,0,0.22);text-decoration:none;color:#e6e3da;box-sizing:border-box;width:100%;\"><span style=\"flex:0 0 116px;aspect-ratio:16\/9;overflow:hidden;border-radius:8px;background:#111210;border:1px solid rgba(230,227,218,0.08);display:block;\"><img decoding=\"async\" src=\"https:\/\/www.securitytoday.de\/wp-content\/uploads\/2026\/07\/net-vmware-broadcom-lizenz-exit-strategie-ci-72878612-250x143.jpg\" alt=\"\" loading=\"lazy\" width=\"116\" height=\"65\" style=\"width:100%;height:100%;object-fit:cover;display:block;\"><\/span><span style=\"display:block;min-width:0;\"><span style=\"display:block;font-size:0.68em;font-weight:700;letter-spacing:0.1em;text-transform:uppercase;color:#e8828d;margin-bottom:5px;\">Digital Chiefs<\/span><span style=\"display:block;font-size:1.0em;font-weight:650;line-height:1.35;color:#e6e3da;overflow-wrap:anywhere;\">VMware under Broadcom: The Exit Plan as a Lever<\/span><\/span><\/a><!--\/ST-LOWER-CARDS--><\/p>\n","protected":false},"excerpt":{"rendered":"Almost every attack begins with a DNS request. How Protective DNS blocks malware and phishing early, and why DNS over HTTPS fills the gap.","protected":false},"author":10,"featured_media":18006,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_focuskw":"Protective DNS","_yoast_wpseo_title":"Protective DNS: the layer that many overlook","_yoast_wpseo_metadesc":"Okay, the user wants me to translate a German SEO meta description into English. Let me start by understanding the original text.","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"_evm_slot_owner":"","evm_cvss":0,"evm_risk":0,"evm_casefile":"","evm_primary_cve":"","evm_external_preview_token":"","evm_external_preview_expires":"","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[3,255],"tags":[],"class_list":["post-18008","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aktuelles","category-praxis-umsetzung-en"],"evm_reading_time_minutes":7,"wpml_language":"en","wpml_translation_of":18004,"_links":{"self":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/18008","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/comments?post=18008"}],"version-history":[{"count":3,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/18008\/revisions"}],"predecessor-version":[{"id":21028,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/posts\/18008\/revisions\/21028"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media\/18006"}],"wp:attachment":[{"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/media?parent=18008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/categories?post=18008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.securitytoday.de\/en\/wp-json\/wp\/v2\/tags?post=18008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}