Chaser Systems retweeted
I was mighty upset with Google on 12 Feb. We had discovered that the issue affecting egress filtering for a DiscrimiNAT customer on GCP was in fact Post-Quantum Cryptography TLS handshakes. It was a combination of the most up-to-date OpenSSL version in a container image and ...
Chaser Systems retweeted
Another short-lived credential leak causes widespread data theft. Here at @ChaserSystems we're researching & prototyping practical second-factor methods for service account style usage.
cloud.google.com/blog/topics…
Chaser Systems retweeted
🎉 AWS Marketplace customers can now view CloudTrail logs to monitor procurement activity in your account.
You can view activity logs when a user subscribes or unsubscribes to an AWS Marketplace SaaS, AMI, Container, or Professional Services product.
go.aws/44GbFIt
AWS Marketplace supports AWS CloudTrail for procurement monitoring
🎉 AWS Marketplace customers can now view CloudTrail logs to monitor procurement activity in your account!
Chaser Systems retweeted
Replying to @colmmacc
When considering mandating TLS 1.2 on benthamsgaze.org I found a non-trivial number of TLS 1.1 connections. On further investigation, every single one was trying to exploit some non-existent vulnerability. I was not sad to lose this traffic.
Chaser Systems retweeted
Replying to @SwiftOnSecurity
I've seen C2 callbacks that got past host security and got dropped on egress. The outbound C2 attempt probably would have worked too if it tried to use the configured system proxy since it was a bit too promiscuous.
Chaser Systems retweeted
Replying to @SwiftOnSecurity
This is a thing even I'VE learned in 8 months. Why's it not a thing everywhere???
Chaser Systems retweeted
Replying to @SwiftOnSecurity
On a recent two week pen test, the red team who is normally pretty good was completely unable to do anything against the client company. They cited egress filtering as a major reason.
Chaser Systems retweeted
Replying to @SwiftOnSecurity
There is a reason we do strict egress filtering at every bigger server infra, even if tedious, even if multiple monitoring warnings get ignored by ops, but the amount of bullets that get dodged with that simple measure is not even funny anymore...
Chaser Systems retweeted
I talked with an exec at a firm who said they had crappy security, but they did strict outbound network filtering, and they survived basically everything without deserving to. It is stupid fucking effective and shows immense organizational vision.
Replying to @SwiftOnSecurity @bob_zim
It was stunning (by which I really mean "the very opposite of stunning") to find out those firms don't use outbound server traffic allowlisting themselves. So APT29 hacked most big name US tech & security vendors with a backdoor that sent traffic to [subdomains].avsvmcloud[.]com.
Chaser Systems retweeted
If you installed PyTorch-nightly on Linux between Dec. 25 and Dec. 30, uninstall it and torchtriton immediately and use the latest nightly binaries.
Read the security advisory here: pytorch.org/blog/compromised…
Chaser Systems retweeted
Does a #firewall for a #cloudnative environment (!) needs deep app/protocol visibility and other modern enterprise firewall features? [cc @dustintodd]
55%Yes, reasons in comments
18%No, reasons in comments
27%It depends, see comments
78 votes • Final results Chaser Systems retweeted
AWS’s Egregious Egress. cfl.re/3BwVWOL















