Your SOC should have detection rules for every system that can move money. Starting today, @dfnsHQ can export its audit trail to your SIEM, starting with @datadoghq Cloud SIEM 🐕 Privileged action signed on DFNS, like moving funds, exporting a key, changing a user, a policy, or an access control, arrives in your security operations as a structured log the moment it resolves. It will show you: 𝗮𝗹𝗹𝗼𝘄𝗲𝗱, 𝗱𝗲𝗻𝗶𝗲𝗱, or 𝗳𝗮𝗶𝗹𝗲𝗱. This includes the attempts, such as a transfer signed and denied by policy. The type of signal that reveals stolen credentials or insider testing limits... What your SOC can now do with it: ⚠️ Alert on any key export, anywhere, instantly ⚠️ Flag policy changes outside the change window ⚠️ Catch a spike in denied actions from one user ⚠️ Surface a transfer at 3am from someone who's never operated at night ⚠️ Correlate a DFNS action with the same user's suspicious IdP login 20 minutes earlier 🛡️ We built SIEM Export like a security control. It never blocks the action it observes, but instead runs on an isolated channel so a SIEM outage can't touch your webhooks. Your API key is encrypted and never logged. When your analysts see something, DFNS can: → suspend an Org → revoke a User → tighten a Policy → deny a Wallet Your SIEM also holds an independent copy of the record, in your domain. Even if DFNS itself were ever compromised, your SOC keeps the history. That's what onchain core banking is for. 📖 Read the announcement: ⌨️ Start building today: