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

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

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.

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...