Live data from Hacker News

CISA Admin Leaked AWS GovCloud Keys on GitHub

krebsonsecurity.com

141–150 of 205 posts

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#141

Earlier quoted context omitted.

We deleted the root credentials efter initial setup where we added mgmt iam accounts used by our automation. If we ever needed them we used the recovery process. All users and services use temporary credentials.

I made an assumption that you have federated AWS account setup. One organization management AWS account and then federated accounts under it and you are referring to deletion of deletion of ROOT credentials in the federated accounts. Considering thats not the case, what you just did is move the goal post to a account recovery process. Question becomes who has ability to recover the account, in case its tied with emai…

One account, org, federated, whatever. You don't need to store the root credentials.

An email per account where only security team has access. Whoever can modify domain can already do this.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#142
post #124
post #67

Earlier quoted context omitted.

Sometimes I feel like it's a cover for some other org actually just wanting to steal the data and this being the excuse.

You mean like if our government was compromised at the highest levels and they wanted to undermine everything without the public realizing? Btw what happened to all the social security data that DOGE exfiltrated?

the fact we're asking about it means the public realized

the problem is the public is dumb, at least when it comes to security, and couldn't tell you why password123 is bad

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#143

In 2026, storing government credentials in a repo and not having scanners to flag it should be investigated. I am highly suspicious of anyone doing this in a professional capacity. If I worked at a foreign intelligence agency and saw this, I would first think it's a honeypot, and an unimaginative one because it's so lacking in subtlety.

good thing we know DOGE has been trying to exfil all US Gov data like all gov employees, or all SSNs

under a previous administration I'd assume CISA was doing a dirty dangle, but given how corrupt and incompetent this administration is, to include firing lots of CISA, this may just be a legit fuckup.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#145

Earlier quoted context omitted.

> While I agree that it should not have happened, at the same time its probably true that most people are never formally trained on security. This isn’t a grocery store or something it’s CISA. This is like a gun going off in a cop’s holster while he’s texting and driving without a seatbelt. Yeah he’s a contractor but that doesn’t suddenly allow for such incompetence.

I have worked with some of the experienced folks in federal space in the past, who were super smart, experienced and COSTLY from managements perspective. They had the ability to challenge the management on such things. Most of them have either retired, managed out or moved on. What you have here is not a reflection of the individual but the entire management chain. Its a race to make most money and at times these con…

Totally agree

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#146

Earlier quoted context omitted.

OAuth with refresh tokens. IAM roles/workload identity. Even time-limited or signed JWT, though has a separate issues. Maybe you'll say 'those are both just text values passed like an apikey' though api keys don't frequently rotate/time limited, which is an important security feature.

> OAuth with refresh tokens. Then the LLM slurps up your refresh token. What's next?

depends on the grant type and what scenario we're talking about. things change if we're talking about 3-legged oauth or client-device oauth. for example, in an authorization code flow, the refresh token is useless without the client id/secret.

more providers are making refresh-tokens single shot. this means that if someone refreshes your token for you, your own auth will break as you will not be eligible to refresh the token, at which point you could reconnect the app and void the old (stolen) session.

time-limiting and single-purposing the tokens are not cure-alls, but they do certainly offer enhanced security by limiting the amount and scope of damage.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#147

Earlier quoted context omitted.

Reading that article makes it look like Trump/Noem filled positions with foreign moles. One day the American people will have an accounting.

After reading Madhu's Wikipedia page and some basic research it looks like he failed his polygraph required to access controlled compartmentalized information (SCI), then DHS (under Noem) then fired six career staffers because of him failing his polygraph. He also does not appear to meet the US Persons requirement for TS:SCI clearance. That's somehow more bananas to me than so many other things the Trump admin has do…

Wow. That is bananas. How in the world did anyone ever consider him to be the right guy for the job? There has to be an agreement in place to leak sensitive stuff to anyone who will pay for it. Cut a check and we'll let your guy handle it.

I can't wait until we round up all these thieves.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#148

Earlier quoted context omitted.

You might like varlock - it helps keep secrets out of plaintext by using plugins to pull from various backends (aws ssm, gcp, vault, 1pass, etc). Also has built in local encryption with shared team vaults coming soon. Additionally provides pre commit scanning, log redaction, and much more.

But then you need creds to access AWS SSM, Vault, etc., and those end up getting stored the same way the actual creds you needed were being stored, and you're back at square one.

Nah you can get machine creds automatically via the metadata service when running inside AWS. Nothing need be on disk.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#149

In 2026, storing government credentials in a repo and not having scanners to flag it should be investigated. I am highly suspicious of anyone doing this in a professional capacity. If I worked at a foreign intelligence agency and saw this, I would first think it's a honeypot, and an unimaginative one because it's so lacking in subtlety.

good thing we know DOGE has been trying to exfil all US Gov data like all gov employees, or all SSNs under a previous administration I'd assume CISA was doing a dirty dangle, but given how corrupt and incompetent this administration is, to include firing lots of CISA, this may just be a legit fuckup.

When negligence is so bad that it looks like sabotage from a hostile agent, then criminal investigations are needed to learn more about the people who did it, the others who enabled it, and deter similar future acts.

DOGE did a lot of bad things, but it didn't force anyone to commit credentials to a repo, disable scanners to get away with it, and then make the repo public.

Re: CISA Admin Leaked AWS GovCloud Keys on GitHub

#150

Earlier quoted context omitted.

The analogy to not posting secrets to the public isn't medical schools and doctors, it's a sign in the bathroom that says "employees must wash hands".

They replaced the people who put the signs up with people who think signs are too woke.

[flagged]
Post reply on HN