{"id":103893,"date":"2025-10-05T10:33:08","date_gmt":"2025-10-05T10:33:08","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/103893\/"},"modified":"2025-10-05T10:33:08","modified_gmt":"2025-10-05T10:33:08","slug":"new-dns-armor-service-helps-google-cloud-workloads-preemptively-block-cyber-threats","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/103893\/","title":{"rendered":"New DNS Armor Service Helps Google Cloud Workloads Preemptively Block Cyber Threats"},"content":{"rendered":"

Google Cloud has launched DNS Armor, a new cloud-native security service developed in partnership with Infoblox<\/a>. The service provides a foundational layer of security by preemptively detecting and mitigating DNS-based threats originating from Google Cloud workloads. The offering addresses a critical vulnerability, with one of Infoblox’s own studies<\/a> finding that 92% of malware utilizes the Domain Name System (DNS) for command and control (C2) communications.<\/p>\n

Google describes the service as preemptive threat detection for internet-bound DNS queries initiated from Google Cloud workloads. Moreover, the company states that it complements its cloud-first network security product portfolio<\/a> by offering a foundational security layer that identifies DNS-based threats, including requests to malicious command and control (C2) servers, DNS tunneling for the exfiltration of sensitive data, and malware using DNS queries.<\/p>\n

Essential DNS Armor provides feed-based detection, identifying both known malicious and high-risk domains, as well as newly registered domains that are likely to be used for malicious attacks. Additionally, it provides algorithm-based threat detection utilizing machine-learning-based detection techniques, including the detection of DNS tunneling attacks, to prevent unauthorized data exfiltration.<\/p>\n

The authors of a Google blog post<\/a> write:<\/p>\n

<\/p>\n

Many sophisticated cyberattacks establish a network connection with their command and control environment. You can use DNS Armor to get visibility into the earliest indicators of suspicious and malicious domains by detecting C2 activity, connections to malware distribution sites, and\u00a0Domain Generation Algorithm<\/a>\u00a0(DGA) traffic originating from your workloads.\u00a0<\/p>\n

\n<\/p><\/blockquote>\n

The focus on DNS is crucial as Michael, an IT Generalist and Network architect, tweeted<\/a> on X:<\/p>\n

<\/p>\n

DNS seems like an odd area to talk security till you realize that DNS is often the first step in communications in any threat vector, from phishing to C&C botnet traffic.<\/p>\n

\n<\/p><\/blockquote>\n

The documentation<\/a> of DNS Armor describes the service’s operation as follows: when enabling a DNS threat detector for a project, DNS Armor securely sends the internet-bound DNS query logs to a Google Cloud-based analysis engine powered by its partner, Infoblox. Their engine uses a combination of threat intelligence feeds and AI-based behavioral analysis to identify threats. Any malicious activity detected generates a DNS Armor threat log, which is then sent back to the users\u00b4 project and written to Cloud Logging for them to view and act upon.<\/p>\n

\"DNS<\/p>\n

(Source: Infoblox blog post<\/a>)<\/p>\n

Lastly, users can deploy DNS Armor as a managed service by Google, as it requires no virtual machines to oversee, and it does not impact the performance of Cloud DNS. Moreover, users can enable DNS Armor at the project level across virtual PCs, allowing them to have precise control over which cloud workloads need protection.<\/p>\n","protected":false},"excerpt":{"rendered":"Google Cloud has launched DNS Armor, a new cloud-native security service developed in partnership with Infoblox. The service…\n","protected":false},"author":2,"featured_media":103894,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[74],"tags":[1705,6390,65494,7266,11264,65495,65493,18,823,65496,19,17,11951,11979,983,82],"class_list":{"0":"post-103893","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-architecture-design","9":"tag-cloud","10":"tag-cloud-security","11":"tag-development","12":"tag-devops","13":"tag-dns","14":"tag-dns-armor-infoblox-security","15":"tag-eire","16":"tag-google","17":"tag-google-cloud-platform","18":"tag-ie","19":"tag-ireland","20":"tag-network-security","21":"tag-networking","22":"tag-security","23":"tag-technology"},"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/103893","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/comments?post=103893"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/103893\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media\/103894"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media?parent=103893"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/categories?post=103893"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/tags?post=103893"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}