I hereby claim:
- I am eradical on github.
- I am eradical (https://keybase.io/eradical) on keybase.
- I have a public key ASDlCWmGmZ5yZeoJW_F-PLWuF2oikjuwUqvYqvNtvp9s_Qo
To claim this, I am signing this object:
[root@gabriel-laptop batch]# docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=test -d mariadb:latest | |
6c413f68aa72c13a56f6d10c677cd547a2d607b7309ef85679718208350f5710 | |
[root@gabriel-laptop batch]# docker exec -it some-mariadb bash | |
root@6c413f68aa72:/# export TERM=dumb | |
root@6c413f68aa72:/# mysql -uroot -ptest | |
Welcome to the MariaDB monitor. Commands end with ; or \g. | |
Your MariaDB connection id is 2 | |
Server version: 10.1.13-MariaDB-1~jessie mariadb.org binary distribution | |
Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. |
# /etc/systemd/system/clustercheck.socket | |
[Unit] | |
Description=MySQL Clustercheck Socket | |
[Socket] | |
ListenStream=9200 | |
Accept=true | |
[Install] |
I hereby claim:
To claim this, I am signing this object:
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon
with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
--- | |
# 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 |
FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
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 has 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.
PII and public facing = high
PII and internal facing = medium
no PII and public facing = medium
no PII and internal facing = low