









Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
CompTIA Cybersecurity Analyst (CySA+) 2.0 Vulnerability Management
Typology: Exams
1 / 15
This page cannot be seen from the preview
Don't miss anything!










2.1 Given a scenario, implement an information security vulnerability management process. - CompTIA
Federal Information Security Management Act of 2002 (FISMA) - is United States legislation that defines a comprehensive framework to protect government information, operations and assets against natural or man-made threats. It requires that government agencies and other organizations OS's on behalf of government agencies comply with a series of security standards. Federal Information Processing Standards (FIPS) - a set of standards that describe document processing, encryption algorithms and other information technology standards for use within non-military government agencies and by government contractors and vendors who work with the agencies.
limitations on the design of a solution that derive from the technology used in its implementation. See also business constraint. They may limit the frequency of scanning. For example, the scanning system may only be capable of performing a certain number of scans per day, and organizations may need to adjust scan frequency. Capacity - used to denote computational resources expressed in cycles of CPU time, bytes of primary and secondary memory, and bits per second (bps) of network connectivity. -Business Constraints - limitations placed on the solution design by the organization that needs the solution. They may limit the organization from conducting resource-intensive vulnerability scans during periods of high business activity to avoid disruption of critical processes. Licensing Limitations - may curtail the bandwidth consumed by the scanner or the number of scans that may be conducted simultaneously.
necessary access across the network infrastructure. It is generally best to have a dedicated account for the scanning tool or, alternatively, to execute it within the context of the user responsible for running the scan. In either case, minimally privileged accounts should be used to minimize risks (that is, do not run the scanner as root unless you have no choice).
can also use Nessus's own formats. As an administrator, it's important that you consider what kinds of reporting your utility is capable of and how you might automate the reporting process. Getting the pertinent information to the right people in a timely fashion is the key to successfully capitalizing on vulnerability scans.
Organizational Governance - The system of processes and rules an organization uses to direct and control its operations. It aims to strike a sensible balance between the priorities of company stakeholders. In some cases, governance may interrupt the application of remedial steps because those actions might negatively affect other business areas. Business Process Interruption - There's never a good time to apply a patch or take other remedial actions. Highly efficient business and industrial processes such as just-in-time manufacturing have allowed businesses to reduce process time and increase overall efficiency. Underpinning these systems are production IT systems that themselves are optimized to the business. A major drawback, however, is that some systems might be more susceptible to disruption due to their optimized states. This fear of unpredictably or instability in the overall process is often enough for company leadership to delay major changes to production systems, or to avoid them altogether. Degrading Functionality - The most common barrier to vulnerability scanning raised by technology professionals. Vulnerability scans consume network bandwidth and tie up the resources on systems that are the targets of scans. This may degrade system functionality and poses a risk of interrupting business processes. CySA's may address these concerns by tuning scans to consume less bandwidth and coordinating scan times with operational schedules.
Automated vulnerability reporting is never perfectly accurate. The CySA must review and make sense of it before passing it on to others in the organization. The two most important outcomes of this process are to identify false positives and exceptions to policies. Once entries in these categories are removed from consideration, one must then prioritize response actions.
The most common vulnerability in these interfaces is their misconfiguration. Even competent technical personnel can forget to harden or properly configure this critical control device if they do not strictly follow a security technical implementation guide.