Cyb 400 Project 1 Blackstone
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
400
Subject
Information Systems
Date
Apr 3, 2024
Type
docx
Pages
2
Uploaded by ABusch18
The vulnerabilities found by the OpenVAS scan that are categorized as Scheduled Maintenance are primarily patches and software updates. These vulnerabilities include, but are not limited to:
●
NVT: MS15-034 HTTP.sys Remote Code Execution Vulnerability
●
NVT: Microsoft SQL Server Multiple Vulnerabilities
●
NVT: Microsoft SQL Server end of life detector
●
NVT: Microsoft Windows SMB Server NTLM ●
NVT: MS15-034 HTTP.sys Remote Code Execution Vulnerability
These vulnerabilities should be handled by installing the appropriate updates as needed. This should be done during business downtime when the office is closed. This allows for plenty of time for the updates to be downloaded and installed without disrupting business as usual. Once they are installed, another scan should be ran to confirm that the vulnerabilities are no longer a concern. Relevant programs should be accessed to confirm that everything is running as it should be. While all these do not need to be done at the same time, doing so would allow for minimal downtime.
Some updates, such as the Microsoft SQL Server End of Life Detector, might require more time and should be attended to when more time is available, such as a weekend or long holiday. The vulnerabilities classified under Policy Update will take more time to fix. To begin, every compromised username and password must be changed. They should be updated to be more complex and far less predictable. Any login information that follows a similar theme (in that they
are predictable and commonly utilized in brute force or dictionary attacks) should also be changed. Some of the compromised logins are as follows: ●
NVT: SMB Brute Force Logins With Default Credentials (admin:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (Guest:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (User:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (User1:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (user-1:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (Test:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (root:guest)
●
NVT: SMB Brute Force Logins with Default Credentials (buh:guest)
These are far too simplistic and easily guessed either via brute force or dictionary attacks. Usernames and passwords should never be the same word, nor should terms such as ‘admin,’ ‘guest,’ or ‘password’ be utilized as passwords. The policies regarding passwords should be updated to eliminate ‘weak’ passwords. All passwords should require a capital letter, a symbol and a number and be at least 7 characters long. Ideally, the length should be at least 12 characters, but 7 is a more common baseline. (
The State of Password Security 2023 Report | Bitwarden Resources
, 2023) It would be my recommendation to utilize a password generator for important logins that can access vital parts of
the network.
We should also require regular password changes for all logins. This should also include eliminating the use of previously used passwords. The administrative passwords should be updated during yearly auditing, especially if similar vulnerabilities are discovered again. Utilizing multifactor authentication (MFA) for employees with greater access should also be considered. The first vulnerability listed under Other Security Issues we should address is NVT: Cleartext Transmission of Sensitive Information via HTTP. This means that the HTTP communications between user and server are not encrypted and can be eavesdropped on. (
Web Application Abuses : Cleartext Transmission of Sensitive Information via HTTP
, 2018) The solution to this is to establish an encrypted SSL/TLS connection. We will also need to make sure that all users are being redirected to this secure connection before inputting any sensitive data. The second vulnerability is: NVT: SSL/TLS: Certificate Signed Using a Weak Signature Algorithm. This means that the hashing algorithm that signed the certificate is cryptographically weak. Some developers warn of weak certificates when visiting websites, but this is no guarantee of protection. The solution to this is to issue new certificates utilizing SHA-2 instead of SHA-1. (
SSL and TLS : SSL/TLS: Certificate Signed Using a Weak Signature Algorithm
, 2017)
The scheduled maintenance vulnerabilities should be addressed first as they are the quickest and most simple to solve. With these out of the way, we will have more security in place to tackle our
other, more difficult, vulnerabilities. This will provide us with the time and energy needed to fix vulnerabilities that require more time and attention. This should lead to the shortest amount of time possible to dedicate to solving these problems.
References:
The State of Password Security 2023 Report | Bitwarden Resources
. (2023). Bitwarden. https://bitwarden.com/resources/the-state-of-password-
security/#:~:text=Password%20checklist-,Agency%20Advice%3A,way%20to%20make%20it
%20stronger.
Web application abuses : Cleartext Transmission of Sensitive Information via HTTP
. (2018). Securityspace.com. https://www.securityspace.com/smysecure/catid.html?
id=1.3.6.1.4.1.25623.1.0.108440
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