A1 ratingsGoogle CloudGoogle Security Operations

Google Security Operations

Google Cloud · platform · Any industry Provisional
B
BGrade
60Score
±1895% range
≈#249Rank of 1136
0%From fleets
FR-CAT-01177Catalog no.
Provisional: the range is wide because some facts are thin or not yet known. It narrows as research and fleets fill in.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Cloud billing export (Google Cloud billing (commitment, data-ingested and overage SKUs)) · prices published
63±38
Desk research 76 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

Security Token consumption in SecOps dashboards; daily paid-token limits via UI or Chronicle API
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

partial
50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

Spend cap: Hard cap · Per-agent keys: Scoped · Audit log: By API · Revoke: By API · SSO: SSO + SCIM
75±38
Desk research 100 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans don't get the data
14±27
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research40%Neutral starting point60%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Spend capHard cap
Per-agent keysScoped
Audit logBy API
RevokeBy API
SSOSSO + SCIM
PricesPublished

Price changes: GCP fees may change at any time unless fixed in an Order Form; Looker (original) 30 days

Budgets alert by default; Spend Cap budgets (GA since Oct 13, 2026) hard-stop Gemini API, Agent Platform, Cloud Run and Cloud Run Functions. SecOps itself lets admins set daily paid Security Token limits (UI or Chronicle API), requires per-tenant activation of paid tokens, and stops new agents when included tokens run out. Service accounts with IAM, Cloud Audit Logs and SAML with directory sync are standard.

History

11-12 B 6011-13 B 6011-14 B 6011-15 B 6011-16 B 6011-17 B 6011-18 B 6011-19 B 60
First rated 2026-10-06 at 64 (B). Now 60. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-05.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Cloud billing export Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct
Prices published
Cost
Yes Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
Usage API
Usage
Security Token consumption in SecOps dashboards; daily paid-token limits via UI or Chronicle API Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct
Cost per agent
Per agent
partial Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct
Per-agent keys
Controls
Scoped Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
Revoke access
Controls
By API Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Inferred 2026-10-31
3 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct

Prices · Standard/Enterprise/Enterprise Plus via sales, priced by ingestion; Security Tokens add-on for agents; Enterprise Plus/GUS include 10M/20M/60M free tokens per day by contract size

Notes · Billed through a Cloud billing account (commitment SKU plus metered data-ingested SKU, overage at negotiated rate, PAYG list price during renewal grace period); GA agents (e.g. Triage and Investigation Agent) consume Security Tokens on commit-plus-overage, paid token use from Aug 31, 2026; assistive features and preview agents use none. Paid consumption must be activated per tenant.

Scored with the rubric for Platforms and APIs (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Run agents on Google Security Operations?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.