Blogs and Whitepapers

Is Credential Stuffing Common?

Read on to find out how common, and how targeted, credential stuffing attacks are against websites that we monitor.

Software development teams often employ developers without specific security knowledge to fix security issues. But is it a good idea?

We are often asked whether it is ok to perform input validation on the client only. Read on for the definitive answer to this question.

Should you focus on which software language(s) your Application Security specialist has? Our answer may surprise you.

We have several fake endpoints set up that behave like WordPress endpoints to see what hackers would do with them. What did we learn?

Is input validation a good first measure when securing your software? We'd argue not. Read on to learn why.

Want help separating the signal from the noise when it comes to AI? Read on to learn more about AI, how it works, and what it can (and can't) do.

We have found that developers almost always make mistakes implementing cryptography. Read this to learn about the mistakes and what to do instead.

You can implement CSRF protections correctly and still be vulnerable. Read this to learn why and what you can do about it.

Logging to find bugs is very different than logging for security. ASP.NET Core's logging functionality helps with only one of these.

Learn about the benefits and challenges of DAST (Dynamic Application Security Testing), which essentially is an automated penetration test.

Learn about the benefits and challenges of SAST (Static Application Security Testing), or automated source code analysis

Web Security (10)

Defensive Programming (7)

Introduction (5)

Secure Coding (5)

ASP.NET Core (4)

ASP.NET MVC (3)

Input Validation (3)

Automated Scanning (2)

Credential Stuffing (2)

Research (2)

SAST (2)

WordPress (2)

XSS (2)

Artificial Intelligence (1)

Consulting (1)

DAST (1)

Logging (1)