Sast Mugs

A black background version with white letters of an awareness design to tell your peer developers to implement input validation to prevent injection, buffer overflows, denial of service or even log sanitisation.

A cool and funny way to remind one of the OWASP guidelines, the A6:2021 vulnerable and outdated components. This design will guide your developers to follow the best practices and mitigate the risks of using any vulnerable or old dependencies in the software.

A reminder for developers to review commented code and take care of it to avoid disclosing secrets or giving hints to a malicious actor. Black background with white letters design.

Awareness design to remind the importance of validating zip files before decompressing it like limiting the number of files, the decompressed size and a maximum decompressed file size.

Any input that is controllable by the user is susceptible of being manipulated and turn it as an evil payload for remote code execution on the victim server.

A design about the the common weakness enumeration 787 represented in an iconic way. Good for secure coding guideline.

This is a cool and funny design to certify that the code is free of any possible injection threats following the best practices like OWASP or CWE.

HSTS is a must when it comes to securing web application HTTPS connections. So, if there is no HSTS header, no deal.

Developers are under great pressure with aggressive delivering dates but, one of the most important things that they shouldn't overlook, is to applying input validation in the functions or methods.

A reminder for developers to review commented code and take care of it to avoid disclosing secrets or giving hints to a malicious actor. After all secure coding.

HSTS is a must when it comes to securing web application HTTPS connections. So, if there is no HSTS header, no deal. This is a black background with white letters design.

An awareness design to tell your peer developers to implement input validation to prevent injection, buffer overflows, denial of service or even log sanitisation.

Threat modeling should be a mainstream activity for every current and new designs, to better understand which could be the threats and which could be the security measures to mitigate the risk. This is a black background with white letters design version.

This design is for secure coding awareness, because if any of your coworker developers performs git push with secrets, it not only implies the clean up of the secrets on the git repo, but also the clean up the git history which will contain the secrets as well.

When dealing with multithreading applications, it is important to make a copy of the input mutable object before processing it to avoid race conditions.

A black background with white letters design version about one of the guidelines provided by OWASP, to put in place security measures to restrict the import or usage of packages with known vulnerabilities.

One of the recommendations of secure coding is to practice pair programming, because 4 eyes catches more than 2 and it is a good way to share context and knowledge between coworkers.

A design version with white letters and black background, This is a reminder for developers to replace any print used for debugging purposes with logger to write them in files.

DevSecOps is an approach to software development that integrates security into the DevOps process, with the goal of delivering secure, high-quality software at a faster pace. A minimalist DevSecOps design would involve a streamlined, focused approach to security, with an emphasis on simplicity and efficiency.

A security funny awareness design to remind developers that secrets, passwords or api tokens is not a good practice.

Another secure coding design about the sensitive information disclosure caused by pushing code with secrets to the git repository. One of the ways to avoid this is by introducing the file names of the project with secrets into the .gitignore file. This is a black background version with white letters.

IT operation should be really careful when dealing with domain administrators. The best practice is that it should be only one per domain otherwise, it could be a nightmare to manage.

DevSecOps is an approach to software development that integrates security into the DevOps process, with the goal of delivering secure, high-quality software at a faster pace. A minimalist DevSecOps design would involve a streamlined, focused approach to security, with an emphasis on simplicity and efficiency. This is a design version with black background.