ISSC297_Week6_Lab6_Kintz_David.docx

David Kintz ISSC297 Week 6, Lab 6 Section 1 In the lab report file, describe each of the Top 10 vulnerabilities and summarize the recommendations for preventing each attack. OWASP Top 10 for 2017 (descriptions cited direct from OWASP.org) Vulnerability Description Prevention Injection Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, 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. Use a safe API, avoiding the use of an interpreter; use prepared statements; minimize database privileges; use web application firewalls; customize database errors to display a generic error message; keep DMBS and OS patched. Broken Authentication Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently. Use two-factor authentication; enforce a strong password policy; store passwords in hashed or encrypted form; use account lockout after X amount of password attempts and CAPTCHA; use session ID protection; use SSL to protect credentials in transit. Sensitive Data Exposure Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser. Encrypt sensitive data in transit and at rest; Apply classification controls; store passwords with an algorithm usef ro password protection; disable auto complete for forms on pages that contain sensitive data; if the sensitive data is not necessary, discard it; classify data as per privacy laws. XML External Entities Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks. Attack awareness and validate server-side input; patch XML processors and libraries; proper input sanitization; disable DTDs Broken Access Control Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc. Access deny all should be the default; implement access control measures through the application; monitor and log access control failures; disable direct calls for objects from the database; rule proper roles-based authentication methods. Security Misconfiguration Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, Set up processes to review all permissions; issues separate credentials to each department; disable administrator interfaces; run scans and audits; remove unused pages and user accounts;

David Kintz ISSC297 Week 6, Lab 6 open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion. implement strong password policy; use a white list for webpages; remove any unnecessary and unused features that are installed or enabled. Cross-Site Scripting XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites. Set up the server to escape special character output; use context- sensitive encoding when modifying browser content on the client side; whitelist good input & blacklist bad input. Insecure Deserialization Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks. Perform input validation for all objects; use digital signatures and perform integrity checks; run deserialization in low privileged environments; monitor the deserialization activity and log exceptions and failures. Using Components w/ Known Vulnerabilities Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts. Use up-to-date patches and implement a patching policy; all components should be identified and monitored; stay informed of the latest news and data; remove anything that is unused, unnecessary. Insufficient Logging & Monitoring Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring. Ensure that all login, access control, and server-side validation failures are logged for later analysis; logs should be formatted to be easily read and centralized; use proper security measured and well trained personnel; implement a response and recovery plan. Make a screen capture showing the results of the SQL injection attempt and paste it into the lab file.

David Kintz ISSC297 Week 6, Lab 6 Make a screen capture showing the results of the command execution attempt and paste it into the lab file.

David Kintz ISSC297 Week 6, Lab 6

David Kintz ISSC297 Week 6, Lab 6 Make a screen capture showing the results of the file inclusion attempt and paste it into the lab file.

David Kintz ISSC297 Week 6, Lab 6

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help