Microsoft 365 audit log retention: 180 days and what to export
Microsoft Purview Audit Standard keeps records 180 days; Premium keeps some for a year. What that means for investigations and what to export.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Microsoft Purview Audit Standard keeps records 180 days; Premium keeps some for a year. What that means for investigations and what to export.
Hashing an email is not the same as anonymising it. What GDPR says pseudonymisation is, and how analytics teams should treat hashed data.
What belongs in a security questionnaire for AI and agent vendors: data use, model providers, agent permissions, testing, incident handling and exit terms.
Inventory every component, resolve unknown licenses, sort findings against a policy, fix the high impact ones and assemble notices and evidence.
pgAudit adds detailed audit logs to PostgreSQL. Compare session and object logging, pick log classes and avoid writing secrets into your audit trail.
When a supplier could not attest to every practice, M-22-18 and M-23-16 allowed a plan of action and milestones. How it worked and why OMB tightened it.
NIST SP 800-53 treats penetration testing (CA-8) and vulnerability scanning (RA-5) as separate controls. Here is what each asks for and how they connect.
PCI DSS asks for vulnerability scans (11.3), penetration tests (11.4) and application assessments (6.4.1) as separate activities. A comparison table.
PCI DSS 8.6.2 bars hard coded passwords for application and system accounts used for interactive login. Scope, what to use instead, and a short checklist.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.