In May last year, the world’s biggest nonprofit archive on the internet – the Internet Archive, got hacked with attackers stealing information of more than 31 million users. There were multiple denial-of-service attacks to disrupt their servers and websites.
It left the organization in shock since nothing like this had happened before since they were founded in 1996.
The hackers posted a message on their website saying, “Have you ever felt like Internet Archive runs on sticks and is constantly on the verge of suffering a catastrophic security breach? It just happened. See 31 million of you on HIBP!”
According to cybersecurity experts, the organization was relying on a lot of legacy systems, and the cyber attack was due to minor oversight of security configurations that were exploited by hackers to gain unauthorized access to terabytes of their data.
Let us understand what they are and how to prevent them.
What is security misconfiguration?
A security misconfiguration is a gap, vulnerability, or weakness in the security configuration/settings of applications, servers, systems, and networks. It can expose them to a range of risks and vulnerabilities exploitable by cybercriminals to carry out a massive attack targeting their infrastructure and sensitive information assets.
In the long run, unnoticed accumulation of misconfigurations can cause a configuration drift or security drift that can be a silent killer exposing the organization to massive cyber attack.
Terabytes of customer, corporate and sensitive highly confidential army data have been stolen due to misconfigured Amazon S3 buckets. It is no surprise why misconfiguration is number 5 on OWASP’s (Open Source Web Application Security) Top 10 Security Risks.
How does security misconfiguration occur? (Some common reasons)
Security misconfigurations occur when:
- the default security settings of applications, servers, systems, or networks are left unchanged or unassessed
- there is a lack of awareness of the risks associated with misconfigurations and best practices to prevent them
- team members fail to document or don’t follow the proper channel or authorization matrix while making changes to the server, systems, or network settings
- systems are not updated regularly/poor patch management
- security teams overlook essential security settings or updates
- there is an unnoticed drift of security configurations away from baseline due to infrastructural (like adding new technology) or architectural changes (like moving from on-premises to cloud)
What are the consequences of security misconfiguration?
Security misconfiguration can cause major consequences for organizations. It can:
- Increase the exposure to data breaches revealing sensitive data, giving unauthorized access to sensitive data, including Personally Identifiable Information, Financial Information, and Intellectual Property.
- Cause a huge financial lossfrom operational disruption, taking remediation measures from a cyber attack to paying huge sums of fines due to non-compliance.
- Cause massive disruption in operations from misconfiguration-based cyber attack, impacting days, months, and years of business.
- Attract fines and penalties due to non-compliance with global and regional cybersecurity regulations like GDPR, HIPAA, PCI DSS, ADHICS, SAMA, Essential Eight, and FISMA.
- Damage reputation severely due to exposure of data, operational disruption, and non-compliance, making it challenging to rebuild trust among customers and investors.
Common types of security misconfiguration
Here are some of the common types of security misconfigurations:
- Network security misconfiguration
- Unpatched/outdated systems
- Misconfigured web servers
- Cloud security misconfiguration
- API security misconfiguration
- Identity Access misconfiguration
- Insecure coding practices
- Unencrypted personal or financial data
- Unchanged/default configuration/settings
- Open and unused ports on servers
How to prevent security misconfiguration?
The following are some of the effective ways to identify and prevent security misconfiguration:
- Regular security auditsinvolving a comprehensive review of configurations, policies, and other reviews to check signs of configuration drift
- Assessment of infrastructure through pentestingand red teaming for misconfigurations and other weaknesses that can be exploited to orchestrate cyber attacks
- Patch managementfor effective and timely dispatch of patches and updates
- Comprehensive reviewof coding practices
- Security trainingon proactively identifying and addressing security misconfigurations