Skip to main content

Tools for the paranoia

The moment you start diving deep into web security, your live will change forever. Possible vulnerabilities appear everywhere in your web application and you don’t know where to start.

So here are some free security tools/sites that help you on the right track:

The Open Web Application Security Project (OWASP) is a 501c3 not-for-profit worldwide
charitable organization focused on improving the security of application
software. In their web site, you almost could find every piece of information
regarding security.

A practical process we could follow to make our software more secure.

Burp Suite is an integrated platform for performing security testing of web applications. Its
various tools work seamlessly together to support the entire testing process,
from initial mapping and analysis of an application's attack surface, through
to finding and exploiting security vulnerabilities.

DOMinator is a Firefox based software for analysis and identification of DOM Based Cross Site
Scripting issues (DOMXss).

Dom Snitch is a Chrome based software for analysis and identification of DOM Based Cross Site
Scripting issues (DOMXss).

Web Application Configuration Analyzer (WACA) analyzes server configuration for security best practices
related to General Windows, IIS, ASP.net and SQL server settings.

CAT.net is a binary code analysis tool that
helps identify common variants of certain prevailing vulnerabilities that can
give rise to common attack vectors such as Cross-Site Scripting (XSS), SQL
Injection and XPath Injection

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more