With the increasing adoption of containers and microservices in the enterprises, there are also risks that come along with containers. For example, If any one of the containers breaks out, it can allow unauthorized access across containers, hosts, or data centers, etc., thus affecting all the containers hosted on the Host OS. To mitigate these risks, we have already looked at various approaches to provide secure isolation for containers. In this post, we are going to look at how to inspect the containers.
Quick Snapshot
Using amicontained tool, we can find out what container runtime, other data points like below:
Install binaries are available from Releases Page. Use the below script from the releases page to install amicontained.
# Export the sha256sum for verification. $ export AMICONTAINED_SHA256="d8c49e2cf44ee9668219acd092ed961fc1aa420a6e036e0822d7a31033776c9f" # Download and check the sha256sum. $ curl -fSL "https://github.com/genuinetools/amicontained/releases/download/v0.4.9/amicontained-linux-amd64" -o "/usr/local/bin/amicontained" \ && echo "${AMICONTAINED_SHA256} /usr/local/bin/amicontained" | sha256sum -c - \ && chmod a+x "/usr/local/bin/amicontained" $ echo "amicontained installed!" # Run it! $ amicontained -h
Verify if we have installed correctly by amicontained -h
Now that we have successfully installed, we can try out different scenarios.
In this scenario, we are going to inspect our containers for the security configuration.
We could see that what are the allowed/blocked syscalls, container runtime, AppArmor profile, capabilities, etc.,
By default, all containers have the PID namespace enabled. PID namespace provides separation of processes. The PID Namespace removes the view of the system processes and allows process ids to be reused.
In this scenario, we are going to inspect the container with PID namespace as host basically allowing processes within the container to see all of the processes on the system and check the output.
In this scenario, we are going to run the container with PID namespace as host basically allowing processes within the container to see all of the processes on the system and check the output.
Congrats! we have learned how to inspect containers using amicontained tool.
Following best practices can help you create a Docker security infrastructure:
If you’re looking for Docker Security tools, check out here.
Like this post? Don’t forget to share it!
Writing software backed by artificial intelligence can create everything from emails to blog articles. AI…
In today's interconnected digital realm, cybersecurity stands as a paramount concern for organizations, irrespective of…
The cryptocurrency market is famed for its volatility, presenting each opportunity and demanding situations for…
Games since time immemorial have been winning at captivating the users and teleporting them onto…
We are living within an innovation curve wherein cutting-edge technologies are making a hustle and…
Whether it’s the healthcare industry or the automobile sector, artificial intelligence has left its impact…
This website uses cookies.