Topic
NIST
NIST Bans Periodic Password Rotation While Russia's FSTEC Mandates 90-Day Changes for Government Systems
Policy & Regulation
AI Agents Given Code and API Access Can Now Assist Attackers
AI Security
Prompt Injection Emerges as Top Risk for LLM Applications in Production
AI SecuritySecurity Vision SIEM Tackles Alert Overload with Data Quality Monitoring and MITRE ATT&CK Coverage
The article examines persistent SIEM challenges illustrated by the 2013 Target breach, where FireEye detected the compromise but response processes failed. It cites recent statistics showing organizations receive nearly 3,000 daily alerts with 46 percent false positives and 63 percent left uninvestigated. Security Vision SIEM, built on the Low-Code Security Vision 5 platform, integrates event collection, normalization, correlation, asset context, and basic response. Key July 2026 updates add collection stability monitoring, SLA dashboards, statistical anomaly detection, Sigma rule exchange, and retrospective process chain reconstruction. The product offers more than 1,200 correlation rules covering over 70 percent of MITRE ATT&CK techniques along with FSTEC BDU mappings and expert response recommendations. It supports remote and agent-based collection across 150 integrations while providing visual No-Code tools for connectors, rules, and dashboards.
Password Rotation Policies Under Scrutiny: NIST Guidelines, Historical Origins, and Logical Flaws
The article examines the long-standing practice of mandatory password rotation every 90 days, contrasting it with modern recommendations from NIST that advocate changing passwords only upon confirmed compromise rather than on a fixed schedule. It dissects common arguments in favor of periodic rotation, such as limiting offline hash cracking time and terminating unknown sessions, and demonstrates how these rely on reverse logic that starts from the control rather than from actual threats. Historical analysis traces the 90-day rule back to the 1985 DoD Green Book (CSC-STD-002-85), revealing that its own calculations showed password lifetime has minimal impact on security when proper rate limiting is in place. The piece distinguishes between data leakage and credential compromise, emphasizing that internal organizational signals provide far better indicators for targeted password changes than public breach databases. It concludes that scheduled rotation only makes sense as a substitute for mature detection capabilities, a trade-off explicitly recognized in PCI DSS v4.0.