git init
or
# Modify this file accordingly for your specific requirement. | |
# http://www.thegeekstuff.com | |
# 1. Delete all existing rules | |
iptables -F | |
# 2. Set default chain policies | |
iptables -P INPUT DROP | |
iptables -P FORWARD DROP | |
iptables -P OUTPUT DROP |
# /etc/systemd/system/clustercheck.socket | |
[Unit] | |
Description=MySQL Clustercheck Socket | |
[Socket] | |
ListenStream=9200 | |
Accept=true | |
[Install] |
Picking the right architecture = Picking the right battles + Managing trade-offs
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
--- | |
# List here all data controllers | |
controllers: | |
- name: Control Corporation | |
address: 42 control road, 75000 Paris, France | |
organisational_part: Control Part | |
contact_person: Jean-Claude Control | |
# That's all recipients for this data, wether internal database or an |
DevSecOps has finally become popular within the wider IT industry in 2019. I started as a web developer in 2001, learned about testing automation, system deployment automation, and "infrastructure as code" in 2012, when DevOps was becoming a popular term. DevOps became common after the release of The Phoenix Project in Jan 2013. It has taken 7+ years for security to become integrated within the DevOps methodology. The following is a list of concepts I go through with project owners, project managers, operations, developers, and security teams, to help establish how mature their DevOps and security automation is, and to help them increase that maturity over time. This model is based on experience consulting with a variety of US Financial, Healthcare, and Department of Defense, organizations, and combines: