Skip to content

Tanq16/containerized-security-toolkit

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


DISecT
Containerized Security Toolkit (CST)

WikiExample WorkflowDocker Hub


This project contains several Dockerfiles for ARM (Apple Silicon) and x86_64 variants of security focussed docker images. The two main resources here are as follows →

  • Security Image for x86_64
  • Security Image for ARM64

The x86_64 security image is built automatically on GH CI and the ARM is built by me on AWS EC2 (not via GitHub Actions due to free runner limits, ARM limits, and long ARM build times). Both images are pushed to Docker Hub.

Note → The ARM images may be significantly out of date compared to the x86_64 images as several packages require additional care to be properly built on ARM, while some simply don't work outright. I don't readily update ARM, so local builds may fail too.

The image is called sec_docker and multiple versions of it are uploaded as different tags, such as →

x86_64 ARM
tag main main_apple
image ref tanq16/sec_docker:main tanq16/sec_docker:main_apple

It has the cli-productivity-suite preinstalled within the image. The wiki goes over using the pre-built images, building it with modifications, conventions considered when creating the Dockerfiles, and different ways it can be used.


A quick look into the container and its capabilities, built from this image, is as follows →

docker run --name="sec_docker_quickstart" --rm -it tanq16/sec_docker:main /bin/zsh

It is also recommended to run the following command after getting into the container →

export TERM=xterm-256color && rm -rf /etc/localtime && ln -s "/usr/share/zoneinfo/$(curl -s https://ipapi.co/timezone)" /etc/localtime && echo $(curl -s https://ipapi.co/timezone) > /etc/timezone

If you exit the shell, the container will be destroyed along with the information in the ephemeral filesystem.

There are several other nuances related to running the container, such as setting up a persistence diretcory across container restarts, using one-word shell functions to start and stop containers with customized settings. Read the wiki, especially the Example Workflow for a comprehensive and convenient setup process.