Funding rounds, leadership changes, incidents, new capabilities and announcements across the vendors in this catalog — collected automatically from vendors' own public feeds. Product release versions are on their own page, so the landing feed here never reads as one vendor's changelog.Where this comes fromEvery item links to the vendor's own published source: a GitHub release feed, a changelog, a status page, an SEC filing or a company blog. Nothing here is written or editorially reviewed by 0-Doubt, and nothing is a recommendation — it is machine-collected public record, labelled the same way as all other baseline content on the platform. Coverage is uneven by design: a vendor that publishes no public feed will not appear, and that absence is not a judgement about the vendor.
65 matching stories — in Shadow IT Discovery — showing up to 3 per vendorPer-vendor capWhile browsing, no single vendor may fill more than three slots on any one page, so a vendor with a chatty release cadence cannot buy the page you are looking at. That means a page can render fewer stories than the count above. Searching a headline or naming a vendor turns the cap off, because then you have asked to see everything that matches.
At 1Password, we believe strong security should feel like part of the workflow, not an interruption. That is the goal behind our work on user verification (UV) for passkeys.UV is a local identity check a website can require as part of a passkey action, to confirm the person approving the action is the person authorized to do so. This decision belongs to the website, not 1Password, as the site will validate UV occurred before accepting the operation. A useful analogy is paying with a bank card. F
In most organizations, standing privileges don’t show up all at once. They accumulate quietly. A role is added “temporarily.” A contractor needs broad access to finish a project. A service account gets oversized permissions because no one has time to fine-tune them. None of these choices seem harmful in the moment, but over time they build into a privilege surface that’s far too large to monitor and far too easy to misuse.The challenge is that standing privileges often look harmless until someth
In the first post in this series, Wade shared how our team laid the foundation for using AI in detection engineering. The short version is that an LLM doesn't know your stack. Without documentation and workflow context, it can produce plausible results that are difficult to trust, regardless of which model you use.That post closed with an instruction: Validate before you ship, because the output can look completely right and still be wrong. Every detection an agent writes still needs to go throu
Augmentt has completed its annual SOC 2 Type 2 audit and renewed the attestation we first earned in 2022. An independent auditor looked at the controls that protect the Augmentt platform. They checked that those controls were designed well and that they actually ran throughout the audit period.  When you connect a client tenant to […]
Secure Score shows a single number, not your tenant's actual policies. Here is what applied security standards really cover and which tools give MSPs full visibility across every client tenant.
A practical guide for MSPs on auditing inherited Microsoft 365 tenants, transferring GDAP and CSP relationships, and standardizing security baselines across an expanded client book after an acquisition.
