Weak passwords remain the top vulnerability for web users, according to guidance by technology association TechUK.
TechUK published the guide – entitled Securing Web Applications and Infrastructure – in association with government's Cyber Crime Reduction Partnership to identify practices to reduce the impact and cost of cyber crime.
The guide reveals the ten most common web vulnerabilities and contains advice on how to defend against the most common threats.
Penetration tests conducted over the past 12 months showed that, despite the emergence of new threats, well-known vulnerabilities are understood by criminals and the most common.
“These threats may not be new, but all still pose a real risk to UK web users,” said Gordon Morrison, director of technology for government at TechUK.
READ MORE ABOUT WEB APPLICATION SECURITY
- Boards need to get behind application security, says Owasp
- Enterprise web application components raise security risks, finds Veracode
- Cost-effective Web application security testing
- Penetration testing: Finding Web application flaws
- Nearly half of all web application cyber attacks target retailers, study shows
- UK lags US in application security investment
- How can the OWASP Top Ten reduce Web application vulnerabilities?
“The good news for businesses and citizens is that there are well-established fixes available to protect against these vulnerabilities and avoid falling victim to cyber crime.”
Web applications provide significant benefit to consumers and businesses, and TechUK expects their importance to grow.
“Software engineers and industry in general have a responsibility to ensure their products are developed in a manner that is as secure as possible,” the guide said.
TOP TEN VULNERABILTIES
- Account weaknesses, especially a weak password policy;
- Secure Sockets Layer (SSL) issues such as weak ciphers;
- Cross site scripting (XSS);
- Clear test protocols may lead attackers to vulnerabilities;
- No brute force protection;
- Directory listing;
- Lack of ‘clickjacking’ protection;
- Cookies - not marked HTTP only or not marked as secure;
- Host configuration issues, especially firewall issues and IP leakage;
- Information disclosure, and especially user enumeration.
“This is true even if software is simple or does not deliver a function that is safety critical, like the processing of personal data for example.”
Owasp is a non-profit, volunteer organisation set up in 2001 to make web applications secure by educating users, developers, governments and business leaders.
TOP TEN EXAMPLES OF BEST PRACTICE
- Avoid hardcoded, weak cryptography and plain text passwords;
- Use THE most up-to-date SSL version, test and verify its operation and monitor for SSL vulnerabilities;
- Use the various XSS prevention rules and techniques that exist;
- Remove all test code, harnesses and data from an application in release builds;
- Ensure your web application is securely hosted and protected via an up to date firewall, deploy application logging and routinely analyse it to detect brute force attack attempts, and capture and report the attacking IP address to the most appropriate and relevant authority;
- Deploy chroot jail to protect against "clickjacking";
- Send the proper X-Frame-Options HTTP response headers that instruct the browser to not allow framing from other domains, and employ defensive code in the user interface to ensure that the current frame is the most top level window;
- Mark all cookies used within the application as secure;
- Ensure application code does not directly or indirectly expose the user IP address. Test to verify this;
- Ensure password reset and error handling does not provide attackers with information that allows them to determine a password or user name.
“It's good to have any research like this out in public, as it can only help to raise awareness of these issues,” said Justin Clarke, Owasp London Chapter leader and director at Gotham Digital Science.
“And as they’re the most common types of issues found, sometimes they’re also the easiest to remediate, which can only benefit organisations if they look at their own applications and apply best practice before they have a security incident."
Clarke said it was also good to see that the guide links to some of the volumes of free information resources on the Owasp site - especially the Owasp Cheat Sheet series.
“This series is designed to give a developer or security professional a single document on everything they need to understand and fix common web application vulnerabilities,” he said.
“Shared privileged accounts, which include social media credentials, are a commonly overlooked threat,” said Andrey Dulkin, senior director of cyber innovation at CyberArk.
“This is compounded by the fact that many enterprises have numerous social media accounts on Twitter, Facebook, YouTube and LinkedIn – often with unique accounts for different product lines, languages, countries and stakeholders.”
Dulkin said that, with passwords for these accounts being shared among teams, it makes for an easy target – not least because there is no record or accountability for each individual post.
“To make matters worse, the same password is frequently used across multiple accounts, and the passwords are often rarely changed,” he said.
Dulkin warned that lax security opens the door for malicious hackers, as well as rogue current or former employees, or disgruntled social media agency members.