Vulnerability Assessments Versus Penetration Tests
In computing, Vulnerability assessment and penetration testing are used to assess systems in light of the organization’s security posture, but they have different purposes.
Let’s first have a look at the definition of some terms:
• Risk — threats × vulnerabilities × consequences
• Threat — something or someone that can take advantage of vulnerabilities
• Vulnerability — the absence of safeguard (vulnerabilities may be the result of poorly or improperly configured systems, known or unknown hardware or software flaws, or operational weaknesses in processes or technical countermeasures).
• Consequence — damage that occurs because the threat took advantage of the vulnerability
• Risk Assessment — identify assets, threats and vulnerabilities
• Risk Analysis — a value of potential risk
• Vulnerability assessments — identify weaknesses
• Penetration testing — exploits weaknesses
In order to evaluate the organization’s security posture; the following steps should be performed:
• Conduct vulnerability assessments.
• Analyze collected information to identify vulnerabilities and potential for exploitation.
• Conduct authorized penetration tests to evaluate the organization’s security posture.
• Analyze and report the results of a penetration test and make mitigation recommendations.
The difference between Vulnerability Assessment and Penetration Testing
Vulnerability assessment is the process of identifying and quantifying security vulnerabilities in an environment. It is an in-depth evaluation of your information security posture, indicating weaknesses as well as providing the appropriate mitigation procedures required to either eliminate those weaknesses or reduce them to an acceptable level of risk.
Vulnerability assessment is normally defined as:
• The process of identifying and quantifying security vulnerabilities in an environment.
• A process that defines, identifies and classifies the security holes (vulnerabilities) in a computer, network, or communications infrastructure.
• The process of identifying, quantifying, and prioritizing (or ranking) the vulnerabilities in a system.
Vulnerability assessments follow these general steps:
• Catalog assets and resources in a system
• Assign quantifiable value and importance to the resources
• Identify the security vulnerabilities or potential threats to each resource
• Mitigate or eliminate the most serious vulnerabilities for the most valuable resources
Vulnerability assessments can use automated tools to search for known vulnerabilities in systems, applications, and networks. These flaws may include missing patches, misconfigurations, or faulty code that exposes the organization to security risks. Penetration testing could follow the vulnerability assessment to further verify that the vulnerability is exploitable.
The intent of a penetration test is to determine the feasibility of an attack and the amount of business impact of a successful exploit if discovered. It is a component of a full security audit. Penetration tests use active tools and security utilities to evaluate security by simulating an attack on a system. A penetration test will verify that a threat exists, then will actively test and bypass security controls, and finally will exploit vulnerabilities in the system.
The Penetration Testing scope should include:
• Determine the possibility of success of attack vectors.
• Identify vulnerabilities.
• Determine the impact on the business if an attack was successful.
• Test the ability of security controls to successfully detect and defend the attack.
• Provide evidence to support increased investments in security personnel and technology.
In a given environment, there should be a security policy in place, and a security audit to review the configuration of security controls, if they are configured correctly to match the policy, for example, hardware configuration, software configuration, default settings, permissions given to users, etc.
A vulnerability assessment is an evaluation of a system’s security and ability to meet compliance requirements based on the configuration state of the system, as represented by information collected from the system. Essentially, the vulnerability assessment determines if the current configuration matches the ideal configuration.
The vulnerability assessment can help identify possible attack vectors and determine whether they have been exploited. Risk assessment depends heavily on vulnerability assessment; It cannot be done without first identifying the vulnerabilities on a system.
The vulnerability assessment process should be performed:
• When you first deploy new or updated systems.
• New vulnerabilities have been identified.
• A security breach occurs.
• When you need to document the security state of systems.
The vulnerability assessment considers the potential impact of loss from a successful attack as well as the vulnerability of the asset to an attack. A key component of the vulnerability assessment is properly defining the ratings for the impact of loss and vulnerability.
Vulnerability assessments should be done on a regular basis to identify new vulnerabilities. This assessment looks at a specific control or compliance issue.
The vulnerability assessment process consists of the following steps:
• Collect a predetermined set of a target.
• Store the collected sample for reference.
• Organize the data to prepare it for analysis and comparison.
• Analyze and document the differences between the current configuration and the baseline.
• Report on the results.
The first step of vulnerability assessment is usually a light discovery of the systems that need to be assessed, such as identifying what services are running on the target system, which version and which firmware version. This information is enough to highlight the system as vulnerable or not. For example, if we are running a server with an old firmware known to be vulnerable, there is no need to further continue in the assessment as this system is definitely vulnerable and exploitable.
After running the first discovery, we can move to a vulnerability scan. There are many tools that can be used to accomplish a vulnerability scan such as Nessus, Nexpose, GFI, etc. These tools try to match conditions found on the target system with known vulnerabilities. They don’t find new vulnerabilities; rather, they count on a database to identify the existence of certain weaknesses.
This stage does not verify or try to exploit the vulnerability; it just lists and ranks the identified weaknesses. It is possible to see false positive results at this stage, which is why we need to continue the vulnerability assessment. The scan can be run with supplemented credentials to reduce the false positive results.
Vulnerability scans may be credentialed in that they implement credentials to ascertain vulnerabilities at the highest privilege levels, or they may be non-credentialed, meaning they run without credentials to see what a hacker would see at a lower level.
While you may discover more weaknesses with a credentialed scan, you sometimes will want to narrow your focus in order to think like an attacker who doesn’t have administrative access. This can also save time and resources, both of which may be more costly in a credentialed scan.
The last stage, which is the actual vulnerability assessment, depends on discovery and scans initiated in the earlier stages. This phase tries to verify the vulnerabilities found, and this process is automated and done with little or no user interaction.
Depending on vulnerability assessment, penetration resting involves exploitation of identified vulnerabilities to gain further access. Using this approach we can understand the ability of an attacker to gain access to confidential information, affect data integrity, or availability of a service and the resultant impact.
Penetration Testing is an intentional attack (simulates a real attack ) on a system to discover security weaknesses left by either the security officer who designed the defence strategy or the security controls that are incapable to defend against a given threat.
Penetration testing is approached using a consistent and complete methodology in a way that allows the tester to use their skills, the output from a range of tools and their own knowledge of networking and systems to find threats that could not be identified by automated tools.
Penetration testing can be automated by using several tools. Although it’s not as accurate or professional as the manual test, it does save time and resources. Automated tests have less impact on the network resources and reduce the human mistakes that could damage a system, however, the main benefit of manual penetration testing is that skilled and expert security professionals are conducting it.
The Penetration testing process consists of the following steps:
• Discovery – Obtain the footprint and information about the target.
• Enumeration – Perform ports scans, OS finger, DNS zone transfer and resource identification.
• Vulnerability mapping – Identify vulnerabilities in systems and resources.
• Exploitation – Attempt to gain unauthorized access by exploiting the vulnerabilities.
• Report – Report the results to management with suggested countermeasures.
The Penetration testing strategies include the following:
• External testing
• Internal testing
• Blind testing – Limited info to the Penetration Testing team
• Double-blind testing – No information to the internal security team
• Targeted testing – Both internal and penetration testing team aware
Penetration testing can be performed either externally or internally. The difference between external and internal testing is what to test. External testing aims to exploit identified vulnerabilities to check what information could be exposed to the outside world. Internal testing simulates what an insider attack could accomplish.
The targets are the same as external Penetration testing, but the difference is the attacker either has authorized access or is starting from a point within the internal network. Internal attacks have the potential of being much more devastating than the external attack because insiders already have the knowledge of which systems are important within a network and where it’s located, something that external attackers don’t usually know from the start.
Penetration testing implementation guidelines are:
• Uses a risk-based approach to determine the preferred scope, method and attack origin for the test.
• Perform at least annually, as well as after significant changes to the environment.
• Carefully plan and perform to avoid potential availability or integrity impacts.
• Sufficient safeguards are in place to minimize any operational impact.
• The outcome is documented and used as an input for the security update process.
The most important first step for a penetration test is getting permission (obtain documented legal authorization from the system’s owner) to conduct the test. A penetration test is a continuous process and should be conducted regularly.
Remember, penetration testing is not complete without testing the human behaviour. Educating employees about security threats and cyber-attacks should not be considered a waste of money, but rather an investment in mitigating threats.
Third-Party Penetration Testing
Occasionally, organizations need to work with a third-party who will conduct penetration tests on their systems, rather than doing these tests in-house. The advantage of relying on a third-party comes from the fact that some attacks will be external and unpredictable, which is not necessarily something you can replicate yourself. It is organization responsibility to keep this third-party grounded and following a strict Rules of Engagement (ROE), it provides the pen tester with guidelines. ROE defines how a pen test will be executed, and what constraints will be in place.
In this case, the organization must ensure that third-party:
• Agreed to a well-defined scope with the relevant constraints.
• Carefully document their approach to pen testing.
• Carry liability insurance.
• Provide the credentials and professional experience of all their personnel.
• Keep track of all their testing actions in a log that can be analyzed.
• Provide well-written reports at the end of the test.
Penetration Testing Considerations
The following are factors must be taken into consideration prior to conducting a penetration test:
• Will the pen test be performed internally or by an external vendor?
• If using an external tester, do they come highly recommended or are they unknown?
• Will the test be conducted in secret or will it be public knowledge?
• Will the test focus on breaking into the system or searching for multiple vulnerabilities?
• Is there a wireless local area network that needs to be included in the test?
• How secure are the physical premises?
• Is there a security awareness program in effect?
• Is social engineering allowed?
• Do employees access the corporate network using a virtual private network?
• Are there clear boundaries for protecting sensitive information during the test?
• Does a written Rule of Engagement (ROE) document exist?
• Will the information security department be involved in the test?
• Have the stakeholders been identified?
Penetration Testing is one type of security assessment where security policy creation, risk identification, vulnerability scan, vulnerability assessment, security audit and penetration testing are effectively used together to give the best result in order to secure an environment.
FedRAMP Issues Guide For Vulnerability Scans
FedRAMP issues guide for vulnerability scans
Mar 21, 2018
To help agencies and cloud service providers ensure a secure cloud environoment, the Federal Risk and Authorization Management Program announced the release of three documents designed to simply the ongoing vulnerability scanning process.
The Guide for Determining Eligibility and Requirements for the Use of Sampling for Vulnerability Scans is designed to limit the amount of information scanned to a subset of assets that can be used to ascertain the state of the entire population.
The ability to use a subset of components is the result of the “high fidelity” of system configurations and processes for each CSP’s assets, John Hamilton, FedRAMP’s program manager of operations, said during a March 13 webinar. This guidance applies only to system builds that are deployed on standard images that remain unchanged when pushed to other devices or machines in production.
The FedRAMP Vulnerability Scanning Requirements, meanwhile, replaces the JAB P-ATO Vulnerability Scan Requirements Guide. It gives CSPs a known vulnerability severity scoring framework so they can create and use an automated Common Vulnerability Scoring System tool for automatic risk adjustments.
By automating the continuous monitoring process, CSPs can take advantage of correlative analytics and cross-cutting metrics to identify commonly found risks across all systems that have Joint Authority Board authorization.
FedRAMP is also asking industry for input on its draft of the Automated Risk Adjustment Framework Guidance.
“Our goal is to enable a CSP to leverage standardized vulnerability risk assessment … based on scores on individual metrics that are transparent,” Hamilton said. “We hope that this will reduce the level of effort and the time required for CSPs to establish the appropriate risks or vulnerabilities within their environment.”
Comments on the draft framework are expected to be open for approximately one year.
About the Author
Sara Friedman is a reporter/producer for GCN, covering cloud, cybersecurity and a wide range of other public-sector IT topics.
Before joining GCN, Friedman was a reporter for Gambling Compliance, where she covered state issues related to casinos, lotteries and fantasy sports. She has also written for Communications Daily and Washington Internet Daily on state telecom and cloud computing. Friedman is a graduate of Ithaca College, where she studied journalism, politics and international communications.
Friedman can be contacted at firstname.lastname@example.org or follow her on Twitter @SaraEFriedman.
Click here for previous articles by Friedman.
San Mateo County Sea Level Rise Vulnerability Assessed, Finalized
REDWOOD CITY-WOODSIDE, CA – From the San Mateo County Government: The San Mateo County Board of Supervisors on Tuesday will consider the finalized Sea Level Rise Vulnerability Assessment, confirming the County’s commitment to preparing and protecting its vulnerable communities.
At the March 13 meeting, the Board will hear a presentation on the assessment and an overview of the County’s larger Climate Change Preparedness Action Plan. Both the assessment and action plan serve as tools to inform and guide the County and its cities in climate change preparedness and adaptation planning.
San Mateo County’s location between the San Francisco Bay and the Pacific Coast makes it especially vulnerable to sea level rise, said Office of Sustainability Director Jim Eggemeyer.
The Office of Sustainability administers Sea Change SMC, the County’s sea level rise initiative, and in June 2015 initiated a comprehensive assessment of flooding, erosion and sea level rise impacts on people, infrastructure and community functions. The assessment focuses on the entire eastern bayshore and along the western coast from Half Moon Bay north.
The assessment’s key findings point to the need for:
Both near- and long-term actions to protect the county’s networked infrastructure which contains roads and highways, levees, electric substations, transmission towers, wastewater treatment plants and pump stations;
Actions at multiple geographic scales focused on emergency preparedness, policy, plan and procedure updates, and shoreline and site-specific protection measures;
Strategies to support residents’ mental and physical health when sea levels rise and prevent post-flood health hazards and social and economic disruption;
Coordinated and collaborative action across multiple jurisdictions.
The assessment not only evaluates the potential impacts but also suggests solutions to protect people and places. However, the work is far from done, said Board President Dave Pine who led two countywide convenings on sea level rise.
“This assessment is an important first step toward a coordinated effort throughout the county to prepare for sea level rise,” Pine said. “Every jurisdiction must understand its own areas of risk, but sea level rise crosses jurisdictional borders so we must work together to keep our communities safe.”
The Office of Sustainability via Sea Change SMC will expand its adaptation planning for sea level rise while simultaneously implementing an overall Climate Change Preparedness Action Plan. The plan will assess sea level rise vulnerability for the south coast of the county and major facilities while also identifying other climate change impacts. The plan will assess sea level rise vulnerability for the south coast of the county and major facilities while also identifying other climate change impacts, including heat, wildfire, storms and precipitation, at-risk transportation and communities and potential adaptation strategies.
“Understanding climate change risks is crucial in building a prepared and stronger county,” Eggemeyer said.
The Climate Change Preparedness Action Plan will raise awareness and build support for collaboration on climate change. The plan includes creating a menu of policies and strategies to integrate climate change adaptation into County and city planning and operations and partnering with cities to develop Community Resilience Plans for vulnerable communities.
View the complete Final Sea Level Rise Vulnerability Assessment along with highlights and summary findings at http://seachangesmc.com
The Board of Supervisors meet Tuesday, March 13, 2018, in Board Chambers, 400 County Center, Redwood City. The complete Board agenda is available at https://sanmateocounty.legistar.com/Calendar.aspx
Image via Shutterstock
Get the Redwood City-Woodside newsletterSubscribe
Link Exchange | Products And Prices
The list of link building products and prices currently offerd at LinkMarket.Net.
The list of link building products and prices currently offerd at LinkMarket.Net.