Ungoverned Usage of Third-Party Services
A trial from two years ago still reads every private repo.
What Is Ungoverned Usage of Third-Party Services?
An integration authorised once during a trial holds its permissions forever: nobody owns it, nobody reviews it, and it never appears in a user access review because it is not a user. You'll watch an attacker who breached a small analytics vendor, not the company, use that vendor's two-year-old marketplace grant to read every private repository, then fix it by revoking the dormant grant and governing every integration with an owner, a review date and least-privilege scopes.
What You'll Learn in Ungoverned Usage of Third-Party Services
- An integration authorised once holds its permissions until someone removes them, and it never appears in a user access review because it is not a user.
- An organisation-wide grant to a vendor's app is reachable from the vendor's systems, so a breach at the vendor reaches the company's code without touching the company.
- Keep an inventory of authorised applications, each with a named owner, a review date and the least-privilege scope it needs.
- Re-approve integrations periodically, remove anything dormant, and revoke grants as part of vendor offboarding.
Ungoverned Usage of Third-Party Services — Training Steps
-
A grant nobody remembers
Bob did not breach Oryndel. He breached Caldris Analytics, a small vendor Oryndel trialled two years ago. In that trial, Oryndel authorised the Caldris marketplace app on its code host, and that authorisation is still live. Bob has a Caldris token. He checks what it can still reach.
-
Read the private source
The grant still works, so Bob uses it. He reads the source of a private Oryndel repository through the vendor's app, exactly as the app itself would.
-
Why nobody noticed
-
A breach at the vendor
Caldris Analytics disclosed that their token store was breached. One of the tokens could read Oryndel's private repositories, through a marketplace app Oryndel authorised in a trial two years ago.
-
Find the dormant grant
Alice opens the organisation's authorised applications. These are integrations, not people, so this is the only place their access is listed at all.
-
A legitimate-looking read
The integration's recent activity is the uncomfortable part: a large read of private source that looks entirely normal, because reading repositories is exactly what this app was authorised to do.
-
Revoke it
The first move is to cut the access. Alice revokes the Caldris grant, so the vendor's app, and the breached token with it, can no longer read anything.
-
One grant, not the problem
The Caldris grant is revoked. But revoking the one that happened to be breached is not the fix: the others on this list are governed no better. Any of them could be the next dormant grant nobody owns.
-
Govern every integration
Alice puts every authorised application under the same governance a person's access gets: an owner, a review date, least-privilege scopes, and a periodic re-approval that removes anything dormant.
-
Try the token again
The real test is the exact token from the vendor breach. Alice re-runs Bob's read of the private repository with it.
Security Framework Coverage
OWASP CI/CD Top 10
- CICD-SEC-8 Ungoverned Usage of 3rd Party Services
CWE
- CWE-266 Incorrect Privilege Assignment
- CWE-1357 Reliance on Insufficiently Trustworthy Component
MITRE ATT&CK
- T1199 Trusted Relationship
- T1528 Steal Application Access Token
CIS Controls
- CIS 15 Service Provider Management
- CIS 16 Application Software Security
NIST CSF
- PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
- GV.SC Cybersecurity Supply Chain Risk Management
- PR.PS Platform Security
NICE Framework
- DD-WRL-004 Secure Systems Development
- IO-WRL-005 Systems Administration