The trinity of ‘developer experience + security standards + operational efficiency’ is greater than the sum of its parts. We call it ‘ergonomic cybersecurity’.

Cambridge, England
Joined August 2019
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 ...
1
2
1
51
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…
1
1
134
🎉 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
2
5
1,245
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.
2
3
Chaser Systems retweeted
Replying to @SwiftOnSecurity
Defeats most c2 and exfil, just like that
1
1
1,279
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.
1
1
1,794
Chaser Systems retweeted
Replying to @SwiftOnSecurity
This is a thing even I'VE learned in 8 months. Why's it not a thing everywhere???
1
1
1,642
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.
1
7
1
55
23,378
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...
1
18
2,393
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.
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.
18
38
1
532
158,644
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…
12
476
73
744
523,559
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
14
4
6