Google Security Operations
Chronicle SIEM and SOAR with Mandiant intelligence.
Scorecard from 0 structured reviews
Exposure signal
None observedAn objective, third-party reading of this vendor's own credential hygiene. It is not part of the community scorecard and does not affect any rating on DBSE.
No staff credential theft is visible in this data set for this vendor. That is a good sign but not a guarantee: it also depends on how much of the vendor is visible to infostealer telemetry at all.
Source: FireIntel (xti.fireintel.net), public domain summary. Source: Hudson Rock (hudsonrock.com), free infostealer intelligence API. About this data. Read 1 month ago, and due a refresh. DBSE does not collect, hold, or sell this data.
Public vulnerability record
23 CVEs across 5 productsWhat the public CVE catalogue holds against this vendor's products. A higher number here is not a worse vendor, and this is scored into nothing at all.
| Product | Catalogued under | CVEs |
|---|---|---|
| Cloud | Splunk | 9 |
| Cloud | Samsung | 8 |
| Cloud | Softnas | 2 |
| Cloud | Tigergraph | 2 |
| Cloud | Jedox | 2 |
Why this is shown and not scored
Counting CVEs punishes the vendors who tell you about them. A company that runs a bug bounty, works with researchers and files CVEs properly will always show more than one that fixes things quietly in a point release. Reading the bigger number as the worse product gets it exactly backwards.
The count also tracks how much software a vendor ships and how long they have shipped it. A vendor with forty products will out-score a vendor with one, whatever either does about security.
And a zero here usually means "not in this catalogue", not "no vulnerabilities found". Absence of a record is not a clean record.
What the list is genuinely good for is specifics: whether the product you are buying appears, and what has been disclosed about it. That is a question for the vendor in a security review, and their answer tells you more than the number does.
Matched in the catalogue as Cloud, Cloud4wi, Cloudacl, Cloudark, Cloudavid. Matching is by name, so it can pick up a namesake or miss a brand filed differently.
Source: CVEFeed (cvefeed.io), public CVE catalogue. About this data. Read 1 month ago. It is not part of the community scorecard, the star rating, or the exposure signal.
Training and certification
Certifications Google Security Operations runs. DBSE does not award them; it verifies that a member holds one, against the issuer's own page or a confirmation from an approved representative of Google Security Operations.
-
Google Cloud Professional Cloud Security EngineerProfessional · valid 24 months– here
Discussions about Google Security Operations
- No threads yet. Start one.