FSEstyle

Description: A design about the the common weakness enumeration 89 represented in an iconic way. Good for secure coding guideline and awareness to avoid being vulnerable to sql injection attacks.

Description: 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.

Description: A design about the the common weakness enumeration 79 represented in an iconic way. Good for secure coding guideline and awareness to avoid being vulnerable to XSS attacks.

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

Description: Design made for threat researchers who investigates and extracts invaluable information from new threats with techniques like reverse engineering, and may contribute to the security community to fight against malicious actors around the world.

Description: A cool design made in red version for malware reverse engineers who had master these skills and studied any certification or degree about. Their contributions in form of yara rules, IOCs and threat intelligence are invaluable for the cybersecurity community.

Description: A cool design made for malware reverse engineers who had master these skills and studied any certification or degree about. Their contributions in form of yara rules, IOCs and threat intelligence are invaluable for the cybersecurity community. This is a blue version of the design, enjoy it!

Description: Kind secure coding advice for developers to ensure that the content security policy header is used on http responses and mitigate XSS attacks on users visiting your website.

Description: A funny design to concern developers that the usage of eval() to process or parse untrusted data could let attackers to inject code to run.

Description: 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.

Description: Never forget to handle a potential exception thrower code to avoid any undesired web application status. Run the code within a try and process the error on the catch section.

Description: The well known quote "Maybe Three People" with the bug bounty programs. If you hunt bugs for living then this is absolutely your design!

Description: Want to avoid the undesired clickjacking attack on your website? Then X-Frame-Options should be one of the headers to respond with sameorigin value. Or you can make it even more restrictive with deny. The result is avoiding any eventual attacker to use hidden frames to compromise the website user.

Description: Phishing is one of the most used methods by attackers to compromise a target organisation. No matter how sophisticated your security controls are, it can be defeated by attacking the weakest security layer which normally are the humans. This design gives a hint on when an email is suspicious of phishing attempt.

Description: In case that x-powered-by header is delivered by your service, override it with misleading information to make attackers life harder like "Not Your Business 1.0"

Description: One of the most important activities in cybersecurity is to patch regularly the systems to fix the vulnerabilities that may affect it. Failing to do so will leave the system at risk and you'll need to pray the gods for not being attacked by a malicious actor.

Description: A Red Team motivational slogan to keep trying hard on finding flaws or vulnerabilities on network or systems. Keep struggling in order to find the vulnerabilities and report them before any eventual attacker.

Description: This is a motivational and "can do" design for cybersecurity Blue Team. Do whatever it takes to reduce the risk, lateral think to seek ways to improve security posture, struggle with other teams to get the desired logs or to fully deploy a security control and so on.

Description: Running out of file descriptors due to a DoS or DDoS attack on your website and it is crashing the whole system? Then ulimit is your friend. The ulimit command sets a limit of file descriptors to a user to avoid consuming all the resources in case of DoS attack.

Description: Administrators tends to su or login as root to perform privileged actions on Linux systems while they shouldn't. It is a bad practice to use root account so, instead, the recommendation is to use a non-root user to elevate with sudo to perform those actions or give them enough capabilities.

Description: A design made for providing guidance to CSRF attack prevention. If it is not prevented adequately, it may leave attackers to trigger undesired actions from victims' browser like performing inadvertent transactions on your website.

Description: To protect from file upload attacks on your website that could leave attackers to upload malicious software or backdoors, here's some of the protections to prevent such attacks.

Description: This design represents some of the technical security controls that you might want to put in place in order to practice layered defense.

Description: Here's a cheat sheet like design to remind some of the secure coding measures to prevent all kind XSS attacks: Reflective, Stored or DOM based. Failing to do so, will imply code execution on victim's browser when visiting your site.

Description: A cool design for developers to remind them to practice secure coding. It shows some of the items from OWASP or CWE guidelines in a compelling way.

Description: The cybersecurity threat hunters may known also as threat busters. They improve the soc's visibility by researching new use cases to detect new threats or indicators of compromise.

Description: The CAPTCHA is annoying for us as humans, but it could be a great way to stop automatic attacks or bots like brute force, CSRF or even XSS attacks.

Description: Malware reverse engineers could be known as Malware busters as well. They analyze samples in order to identify their static patterns and behavioural indicators to finally share this knowledge with the security community.

Description: Malware reverse engineers design for those who had master these skills or studied any certification or degree about. Their contributions in form of yara rules, IOCs and threat intelligence are invaluable for the cybersecurity community.

Description: The principle of the Zero Trust architecture is to assume the breach inside your network, therefore, never trust any asset access before validation or authentication. Therefore, in a funny way, it should be similar to validate your dog before he can enter home.

Description: Statistics say that 123456 is the most common used password, which is definitely not the most secure passwords possible. To be honest, is not even a password strictly saying since it can be defeated in a blink of an eye. Therefore, as a tip, try to not use this kind of passwords.

Description: This is a calling in army style for talented people to join to one of the most specialized professionals in Cybersecurity. The Red Team.

Description: Threat Intelligence could be great source for your cybersecurity program. They can provide useful IOC, feeds, notifications and vigilance on your tech stack. No matter what threat intelligence you use, either paid support or the security community, it's like defending your organization alongside with them.

Description: Reusing passwords, specially when using the same for social media, personal email and your employer accounts, increases the chance that attackers could access to your jobs accounts. Therefore, avoid doing such practice.

Description: This is design for calling new talented people to join one of the most specialized cybersecurity professionals. The Blue Team.

Description: The principle of the Zero Trust architecture is to assume the breach inside your network, therefore, never trust any asset access before validation or authentication. Is like validating your cat before he can enter home.