3,020 karma · joined March 15, 2010
https://signal.me/#eu/tJgEd9pEdyiankVrQI3j1y2n5jPNLW7y4cZ09RJ0Vhjh2mihvq9IwL6toyfg8Kma
The traditional bystander/compliance security team approach shows its limits very quickly. Being embedded that deeply into the DevOps team is by far the most efficient way to secure services.
That said, I agree with the blog post. We are seeing more and more security teams reinvent themselves as they adopt DevOps practices, which really means security is learning to use the CI/CD pipeline and to build controls in IaaS and PaaS. We're moving away from security teams that panicked at the idea of not controlling layer 2 and 3, like they used to in the goold old datacenter, and seeing teams focus on web application security more and more.
It doesn't mean L2/3 are not important. There is still a lot of value to adding an IDS or a proxy to an infrastructure. But there is also tremendous value in testing controls continuously in the delivery pipeline, which means collaborating with devs and ops in the CI/CD pipeline. That's really what "secdevops" is about.
In the next few years, we'll see more and more security teams learn DevOps and that's a good thing. Let's just make sure we don't reinvent decades of infrastructure security in the process.
(shameless plug: I'm writing a book on devops security: https://securing-devops.com/book)
Example run on addons.mozilla.org: https://observatory.mozilla.org/analyze.html?host=addons.moz...
The Observatory measures site's compliance with the Web Security guidelines [1] and the Server Side TLS guidelines [2]. It's primarily meant as a helper for website developers and operators.
[1] https://wiki.mozilla.org/Security/Guidelines/Web_Security
[2] https://wiki.mozilla.org/Security/Server_Side_TLS
(disclaimer: I work on security at Mozilla)
Mutt is a productivity tool, like vim and emacs, but for email instead of code. You need to invest a lot of time into learning it, refining your configuration, and getting comfortable with its interface. It will originally be as frustrating as giving emacs to a notepad user, but eventually pays off the learning cost in productivity.
Some examples of commands I use all the time:
* shift+D deletes an entire thread. Very useful to delete entire github discussions in one command.
* `t` flags a message, then `;+s` moves the entire flag to another folder
* custom macros. For example, I use `short+C` to move the message under the cursor to folder `foo`. I have 5/6 similar macros for the folders I use most.
GnuPG integration is also a big help (I use it constantly). I'm use many other MUA offer similar shortcuts and configurability, but Mutt is the fastest and most flexible by far. The one thing that I haven't found a good solution for is full text search across multiple folders. I still rely on gmail for that.
Because when you have 100,000 users and you need to rotate your host key following a leak, the team in charge of user retention has a heart attack.
[1] https://mozilla.github.io/server-side-tls/ssl-config-generat...
Mozilla’s Services Security Team is looking for an ambitious Security Engineer to help us protect the back-end services that power Firefox and serve millions of users worldwide.
Role:
* develop, implement and operate controls to secure online services and web APIs
* Assist developers in auditing and hardening the security of web applications
* Implement techniques to detect and block abuses of our services
* Advocate security across the organization, be a teacher for security.
See the job listing: https://careers.mozilla.org/position/oQ1k3fwY
The S3 method is kinda experimental. It works for first-level packages but fails for nested packages. We need to look into setting up redirects for those.
The best way to do this yourself is to run an instance of https://github.com/niemeyer/gopkg, but that's not #serverless anymore ;)
We even do it with just an S3 bucket for go.mozilla.org: https://go.mozilla.org/
Timezones are still an issue, but if you're willing to adapt your work hours to meet the majority, being remote allows you to work for fantastic companies without sacrificing your way of life.
As a side note, I recommend creating a separate github account when granting permission to this kind of 3rd party. Don't grant them full read/write on your repos, create an account that's temporarily admin, then make that account read only.
SSLLabs evaluates the highest possible security, while Mozilla's levels compromise to implement the best possible TLS for a given population of users. "best" isn't always determined by security: speed and compatibility are taken into account as well.
That said, Mozilla's modern level ranks A+ in SSLLabs: https://www.ssllabs.com/ssltest/analyze.html?d=jve.linuxwall...
AES256-GCM is prioritized above its 128 bits variant,
and ChaCha20 because we assume that most modern devices
support AESNI instructions and thus benefit from fast
and constant time AES.
https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_com...WebPush is (going to be) an IETF standard: https://datatracker.ietf.org/wg/webpush/documents/