web-application-security Archives | Page 19 of 20

PCI Compliance – The Good, The Bad, and The Insecure – Part 2

In this second part of the compliance article, the author explains in detail how each and every category in the PCI DSS requirements should be dealt with to ensure that your websites, web applications and also business are operating securely. This is the definitive guide to PCI DSS compliance every business and organization should read.

PCI Compliance – The Good, The Bad, and The Insecure

In this first part of a two part article about PCI compliance and web application security, the author looks into the history of compliance, rules and regulations and explores the common shortcomings of such rules. The author also explains why there are such shortcomings and explains that by being compliant, does not necessarily mean having secure web applications.

How to evaluate web application security scanners

Top 10 Mistakes when Performing a Web Vulnerability Assessment

In Information Technology there are numerous mistakes, oversights, and blunders that are repeated consistently day after day. But given what there is to lose when it comes to web application security, why not learn from the mistakes of others so you don’t get burned? This blog post lists the top 10 mistakes typical web application security experts do and that you need to be aware of when seeking out the real business risks in your web vulnerability assessments:

14 years of SQL injection history and still the most dangerous vulnerability

Getting developers on board to transition from part of the problem to part of the process

Are your web application developers key players in the web application security equation? They are often the unsung heroes who help prevent many security problems from ever occurring, or closing down web vulnerabilities once identified. Yet in the real world they are often portrayed as a large part of the security problem. It doesn’t have to be that way.

Shared Hosting and Web Application Security – The Opposites

Shared hosting might be an affordable solution for many businesses and startups, but because of the way shared hosting works web application security is not in your control. Read about all the pitfalls of shared web hosting and what you should look for when choosing a hosting provider for your web applications.

Should you pay for a Web Application Security Scanner?

If you ask 10 web security specialists which is their favorite web vulnerability scanner, most probably you will get 30 different answers. Digging deeper you will also find that while some prefer to use free tools, several others prefer to rely on a commercial web vulnerability scanning solution. This web security blog post highlights the differences between free web security tools and commercial web application security scanners.

Web Application Security Testing should be part of QA Testing

Web vulnerability scanning should form part of the normal QA process when developing web applications to ensure that a business develops and releases secure web applications. Unless project managers start classifying security vulnerabilities and other web application security issues as normal functionality bugs, web developers will keep on developing vulnerable web applications.

Why Web Vulnerability Testing Needs to be Automated

There are several pitfalls in web application security and one of them is sticking to manual audits only. This blog posts highlights the benefits of automating the process of finding vulnerabilities and other security issues in modern web applications. It also looks into the common pitfalls encountered by web security specialists when trying to identify all web application vulnerabilities manually.

Create Own Scan Policies with Netsparker Scan Policy Editor

In Netsparker version 3 we introduced the Scan Policy Editor. The Scan Policy Editor allows Netsparker users to create new scan policies in which they can specify which web application vulnerability checks should be included in a web security scan. Read this blog post for more information on the Scan Policy Editor and how you can use it to create your own scan policies and launch more efficient web application security scans.

An XSS Vulnerability is Worth up to $10,000 According to Google

Google are willing to pay up to $10,000 to anyone who discovers a cross-site scripting vulnerability in one of their web applications. Why are Google doing so? Definitely not by coincidence. By exploiting a cross-site scripting vulnerability a malicious hacker can easily gain administrative access on a web application, gain control over it and where possible infiltrate deeper into the corporate network. Read this blog post for more information about the impact an exploited XSS can have on your business.