CrowdStrike ex-employees: 'Quality control was not part of our process'

Re:CrowdStrike ex-employees: 'Quality control was not part o... by x3n0ph3n3 on Friday September 13, 2024 @06:47PM (#41535908)

Can you provide some more info on this? How do you know? Is this documented somewhere?

I'm sure this is going to raise red-flags in my IT department.

[ Parent | on HN ]

Re:CrowdStrike ex-employees: 'Quality control was not part o... by skewer99 on Friday September 13, 2024 @08:00PM (#41536317)

AKIDs... ugh. They'll be there if you use AWS + Mac.

Again, the plaintext is the problem.

These environment variables get loaded from the command line, scripts, etc. - CrowdStrike and all of the best EDRs also collect and send home all of that, but probably in an encrypted stream?

[ Parent | on HN ]

Re:CrowdStrike ex-employees: 'Quality control was not part o... by zxexz on Saturday September 14, 2024 @02:34AM (#41537925)

I usually remote dev on an instance in a VPC because of crap like this. If you like terrible ideas (I don't use this except for debugging IAM stuff, occasionally), you can use the IMDS like you were an AWS instance by giving a local loopback device the link-local ipv4 address 169.254.169.254/32 and binding traffic on the instance's 169.254.169.254/32 port 80 to your lo's port 80, and a local AWS SDK will use the IAM instance profile of the instance you're connected to. I'll repeat, this is not a good idea.

[ Parent | on HN ]

Re:CrowdStrike ex-employees: 'Quality control was not part o... by st3fan on Friday September 13, 2024 @06:49PM (#41535920)

Ask them to search for the usual env var names like GITHUB_TOKEN or AWS_ACCESS_KEY_ID.

[ Parent | on HN ]