- Recon
- Find vuln
- Exploit
- Document it
Unicornscans in cli, nmap in msfconsole to help store loot in database.
vault.barrier.* | |
name="vault_barrier" | |
method="$1" | |
vault.consul.* | |
name="vault_consul" | |
method="$1" | |
vault.route.*.* | |
name="vault_route" |
package main | |
import ( | |
"fmt" | |
"net/http" | |
"sort" | |
"time" | |
) | |
// a struct to hold the result from each request including an index |
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.
This is a copy/paste from an internal wiki on how we should use docker
This guide is to serve as an outline of internal best practices to using Docker. The idea is to give enough information to allow engineers to create containers for new stack components while minimizing the cleanup required to make them production ready.
Before we get to the practices, it's important to understand WHY we are doing this. The key concepts we're concerned about with broad Docker usage are provenance, determinism, repeatability and auditability.
Provenance refers to knowing WHERE something comes from. Generally with the end use of software, this is easy:
deploy: | |
steps: | |
- script: | |
name: create necessary folders | |
code: |- | |
mkdir -p $HOME/.aws | |
mkdir -p $WERCKER_SOURCE_DIR/.elasticbeanstalk | |
- create-file: | |
name: setting up AWS credentials | |
filename: $HOME/.aws/credentials |
#!/bin/bash | |
set -u | |
set -e | |
set -o pipefail | |
export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin | |
cat <<'EOF' > /etc/modprobe.d/blacklist-ipv6.conf |
#!/usr/bin/env python | |
''' | |
This script should be run against an ansible Inventory file | |
in order to return host/group information | |
Contact guy dot matz dot cft at jcrew dot com with any questions, although he's | |
probably completely forgotten everything about this . .. :-( | |
''' | |
import os | |
import json |