<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Apache Log4j Vulnerability Detection on sentinelchangelog.net</title><link>http://sentinelchangelog.net/tags/apache-log4j-vulnerability-detection/</link><description>Recent content in Apache Log4j Vulnerability Detection on sentinelchangelog.net</description><generator>Hugo -- 0.157.0</generator><language>en</language><lastBuildDate>Tue, 07 Jul 2026 11:52:51 +0000</lastBuildDate><atom:link href="http://sentinelchangelog.net/tags/apache-log4j-vulnerability-detection/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure WAF Log4j Detection: Schema Gap Closed for details_message_s and details_msg_s Fields</title><link>http://sentinelchangelog.net/posts/2026-07-07-pr-14611/</link><pubDate>Tue, 07 Jul 2026 11:52:51 +0000</pubDate><guid>http://sentinelchangelog.net/posts/2026-07-07-pr-14611/</guid><description>The AzureWAFmatching_log4j_vuln Analytic Rule was silently missing CVE-2021-44228 exploit attempts in WAF logs that surfaced details_message_s via AdditionalFields or used the details_msg_s column variant, leaving a schema-dependent blind spot in Log4Shell detection.</description></item></channel></rss>