Top 10 OWASP application security best recommendations
There are many bugs, flaws, vulnerabilities and more when it comes to cyber security challenges and philosophies.
Below are the OWASP top 10 :
– Injection flaws include SQL, QS, and LDAP
– injections occur when untrusted data is sent to an interpreter as part of a command or query
– The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization
2> Broken Authentication and Session Management:
– Application functions related to authentication and session management are often because they are not always implemented correctly, thus allowing an attacker to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities
3> Cross-Site Scripting (XSS):
– XSS flaws occur when an application takes untrusted data and sends it to a web browser without proper validation or escaping
– XSS allows attackers to execute scripts in the victim’s browser, which can hijack user sessions, deface websites, or redirect the user to malicious sites
4> Insecure Direct Object Reference:
– direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key
– Without an access control check or other protection, attackers can manipulate these references to access unauthorized data
5> Security Misconfiguration:
– Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform
– Secure settings should be defined, implemented, and maintained, as defaults are often insecure
– software should be kept up to date
6> Sensitive Data Exposure:
– Some web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Think PII and more.
– Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes
– Sensitive data deserves extra protection such as encryption at rest or in transit
– special precautions should be configured when exchanged with the browser
7> Missing Function Level Access Control:
– Most web applications verify function-level access rights before making that functionality visible in the UI
– applications need to perform the same access control checks on the server when each function is accessed
– If requests are not verified attackers will be able to forge requests in order to access functionality without proper authorization
8> Cross-Site Request Forgery (CSRF):
– A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application
– allows the attacker to force the victim’s browser to generate requests the vulnerable application things are legitimate requests from the victim
9> Using Components with Known Vulnerabilities
– Components, such as libraries, frameworks and other software modules, almost run with full privileges
– If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover
– Application components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts
10> Unvalidated Redirects and Forwards
– Web applications frequently redirect and forward users to other pages and websites, and uses untrusted data to determine the destination pages
– Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages
Read More Articles
Supply chain and logistics is a complex and complicated space. But supply chain mechanisms and supply chain automation and supply chain security isn’t a simple conversation or easy button solution. It’s a global supply chain society.
Can blockchain help ? Can IOT help ? Can Big data analytics help ? Can robotics and automation help ?
But of course blockchain can sort of help when you think about it. As Bruce Schneier said about the supply chain and public policy, “you have to trust everyone yet you can’t trust anyone.”
Cool use case for blockchain and agriculture and the supply chain.
Developers at Starbucks exposed an API key that might be used by an attacker to access internal IT systems and manipulate the list of authorized users.
The issue has been rated as ‘critical’ because it could allow attackers to execute commands on systems, add or remove users which have access to internal systems, and potentially AWS account takeover.
The key was found in a public GitHub repository.
Serious impacts ignored
Vulnerability hunter Vinoth Kumar found the key in a public GitHub repository and disclosed it responsibly through the HackerOne vulnerability coordination and bug bounty platform.