Eight hundred thousand calls on one stolen key
Wiz followed two stolen enterprise AI credentials out of one vendor breach. The one that could reach every region served roughly 800,000 calls; the one locked to a single region lost most of 1.7 million attempts to quotas. GitHub, separately, published the order in which an enterprise's plugin setting, a repository's default and a contributor's own choice lose to each other.
How we Build
The enterprise setting beats the repository’s, and the repository’s beats yours
GitHub made repository plugin defaults and enterprise plugin controls generally available on 28 October. A repository can now ship a default set of plugins to everyone who works in it, and an enterprise can require some, block others and restrict installation to approved marketplaces. A required plugin cannot be switched off by the person using it. GitHub states the order in one line: managed settings beat the repository’s defaults, which beat the contributor’s own choice.
Three places can hold a different answer to the same question. Settling that in advance is what we ask a client to do.
Where two systems may hold different values for the same thing, and for how long, is either a decision or an accident.
GitHub has made it a decision and published the order. What the entry leaves out is the second half of that sentence. It says which value wins. It says nothing about how long a machine already running may hold the old one, so a firm can hold the precedence rule and still not know what any contributor’s agent loaded this morning.
How we Assure
The same script, two credentials, and only one of them was throttled
Wiz followed two stolen enterprise AI credentials out of one vendor breach and published the comparison on 30 October. Both were first used within half an hour of the vendor’s own credential-access window. Both were then checked daily by the same small client, for days afterwards. The one whose policy allowed cross-region inference served roughly 800,000 calls over thirty hours, at about 90 per cent success. Spreading the load across regions kept it under the quotas. The one restricted to a single region drew 1.7 million attempts and lost most of them to those same quotas. Wiz puts the pair at over $100,000 of usage at list price.
We ask for a credential bounded by the task it was issued for, and ended by it.
Privilege is scoped to the task and expires with it.
The scope half comes out of this about as well as it can. There was one attacker and one script, and the only variable that moved was a region clause somebody had written. The expiry half is untested, because neither credential expired. Both ran until a person rotated them. This is not the first source to bear on that sentence. A paper of 5 September measured authority that survived revocation across four providers, and it has had no answer since.