Hacking Google to Defend Enterprises - YouTube - https://m.youtube.com/watch?v=dhdz5VZ4S88 Summary: Chief Information Security Officer of Google Cloud, Phil Venables, covers all the teams listed in prior videos and describes how Google Cloud helps secure its customers. Response: As an outsider watching video series, while it is possible I misunderstood, appears the Google Cloud CISO is the highest-level security... - Source: Hacker News / over 1 year ago

Compliance wise all major cloud datacenters are compliant from the moon and back https://cloud.google.com/security/ + https://docs.microsoft.com/en-us/azure/compliance/ unlike most IT departments. Source: over 2 years ago

I would argue that my data is safer with Google than with Apple. Especially since Google encrypts data even at rest. More here - https://cloud.google.com/security/. Source: almost 3 years ago

We undergo independent verification of our security, privacy, and compliance controls to help you meet your regulatory and policy objectives. Find details on our full set of compliance offerings, like ISO/EC 27001/27017/27018/27701, SOC 1/2/3, PCI DSS, and FedRAMP certifications, and alignment with HIPAA GDPR, and CCPA, among others, in our Compliance resSOurce center. Source: about 3 years ago

I remember hating shorewall and similar ones because, well, I know iptables, and I know exactly what I want so using anything that tries to abstract it into it's own approach is torture as I need to take the rules I want and translate it to whatever mediocre paradigm shorewall (or ufw, or near-any other firewall manager in the wild) decided to put on top of iptables. I ended up using ferm... - Source: Hacker News / 11 months ago

I'm a big fan of ferm. Many major distros have it readily available as a package, and it makes for beautifully readable firewall definitions. Source: over 1 year ago

The last time I needed to do complex iptables stuff, I found FERM really helpful. The structured config language greatly reduces the amount of boilerplate code you have to type, while still having a pretty direct mapping to the emitted iptables rules. A bit like compiling sass to css. Source: about 2 years ago

Also just about last thing I want is to deploy another configuration management system alongside the system that manages everything else on machine. Currently we just use Puppet to deploy ferm rules (which is best described as "iptables+", naming convention and such are still iptables-like but a lot of macros/syntax sugar around it). Source: about 3 years ago