GitHub · Vendor notice
How we took malware advisories beyond npm
What the vendor said
Read the notice at github.blog
The headline above is the vendor's own. Phylax holds no more of the notice than that.
What it states about your secrets
Not yet read by a person. Until someone has, this page gives it no level: read the vendor's notice and judge it for yourself.
Rotating a key, in order
If you decide to rotate anyway, replace first and revoke once the new key works. If a key is known to be leaked, revoke it first.
- Create a new key at the provider that issued the old one.
- Put the new key into every service that uses it.
- Redeploy, so that running services pick the new key up.
- Check one workload end to end with the new key.
- Revoke the old key.
- Read the provider's access logs for use of the old key that was not yours.
If personal data of people in the EU may be involved, the 72 hours for telling the regulator run from when you become aware of it. This is not legal advice.