- Image Development
- Installing SW without proper configuration, e.g. default passwords...
- Exposed credentials in
Dockerfiles
- Malware in 3rd party resources used to build the image
STRIDE is a method to categorize security threats:
-
Spoofing identity. Can someone spoof an identity and then abuse its authority? Spoofing identity allows attackers to do things they are not supposed to do.
-
Tampering with data. How hard is it for an attacker to modify the data they submit to your system? Can they break a trust boundary and modify the code which runs as part of your system?
-
Repudiation (Nichtanerkennung). How hard is it for users to deny performing an action? What evidence does the system collect to help you to prove otherwise? Non-repudiation refers to the ability of a system to ensure people are accountable for their actions.
package main | |
import ( | |
"bufio" | |
"bytes" | |
"encoding/json" | |
"flag" | |
"fmt" | |
"github.com/danicat/simpleansi" | |
"log" |
This is a short summary of our DevOps Stuttgart Meetup from March 5th about automated security testing in Continuous Integration. For the meetup we had Christian Kühn and Arnold Franke from Synyx with us as speakers.
Chris started the presentation with a question who is currently running security tests in their pipelines and I was surprised by the majority of hands being raised. Also it seems like nowadays more then half of the audience is running production workloads in containers.
For motivating the topic of security testing, we've been introduced to a recent security incident at Euquifax, where a huge amount of private data (i.e. social security numbers and credit card data) leaked, due to a
- collect topics upfront, cluster them and give people slots to present them during the meetup
- try to get people from remote companies involved (e.g. GitLab), to share their experience
- have a Mattermost chat in parallel where you cancollect topics before bringing them into the stream