Connect with us

Security

GitHub security alerts now support Java and .NET projects

Published

on

Code hosting service GitHub has updated its platform this week, and among the many developer-centric changes, the company also rolled out three new security features for project owners.

The most important of these new security improvements is the expansion of the Security Alerts feature, which now also supports Java and .NET projects, on top of the original JavaScript, Ruby, and Python.

GitHub launched this feature last year, and it works by scanning a project’s dependencies for outdated libraries and modules for which known vulnerabilities exist.

If GitHub’s scanner finds that a developer has used an old library that’s affected by a known security bug, it will show or send an alert, urging the developer to update his project’s dependencies.

GitHub launched this feature to great success in November 2017 for JavaScript and Ruby projects and later expanded it to Python projects in July 2018.

Industry experts anticipated that GitHub would expand support for Java –one of the most used programming languages thanks to the success of the Android OS– and .NET –expected move after Microsoft bought GitHub earlier this year.

By default, GitHub will scan manifest files such as package.json (for JavaScript projects), gemfiles (for Ruby projects), requirements.txt or Pipfile.lock (for Python projects), pom.xml (for Java projects), and one of the many .NET manifest files such as app.manifest, project.json, .csproj files, and .MSBuild files –so make sure your project uses one.

The security alerts feature is available for all users, and they can find it in each GitHub project’s “Insights” tab, under the “Alert” option.


Image: GitHub

In case developers manage a large number of projects and don’t have the time to manually visit each project’s GitHub page, GitHub also lets developers set different notification methods such as:

  • A banner in the GitHub interface
  • Web notifications on the GitHub domain
  • Email notifications for each new vulnerability
  • Daily or weekly email digests of all new vulnerabilities

GitHub’s security alerts system isn’t perfect, as it can only detect vulnerabilities that have received a CVE identifier and have been indexed in the DHS’s NVD portal. Some vulnerabilities are expected to slip through the cracks, but GitHub’s alerts system has already proven to be very effective.

In a blog post in March, GitHub said that within a month of its launch last year, developers acted on security alerts and removed 450,000 vulnerabilities from their projects.

But the expanded security alerts weren’t the only security-themed updates that GitHub announced. The company also rolled out something called GitHub Token Scanning.

This new tool is still in beta. GitHub says Token Scanning will help maintainers of public code repositories. The tool works by scanning users’ public source code in search of API or other authentication tokens.

These tokens are the equivalent of leaving a server password in the code, and GitHub plans to alert users if they accidentally leave one inside their projects.

Currently, GitHub Token Scanning supports token formats for services like Amazon Web Services (AWS), Azure, GitHub, Google Cloud, Slack, and Stripe.

Besides alerting the user, GitHub says this new service will also alert the provider as well, so they can invalidate or revoke the token to prevent abuse.

Last but not least, GitHub also announced the Security Advisory API. This new API will provide developers with an API that aggregates all security-related information for their accounts. This not only includes security alerts for vulnerabilities in project dependencies, but also alerts for accounts that use weak or already-compromised passwords, alerts for attempts to break into a GitHub account, and more.

The API is intended for developers that manage a large number of projects or for companies who want to make sure their projects and employee access live up to its internal security standards.

Readers who are interested in finding out more about the other changes made to the GitHub platform can read about developer and business-related updates, here.

RELATED COVERAGE:

Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Security

Security Tools Help Bring Dev and Security Teams Together

Published

on

Software development teams are increasingly focused on identifying and mitigating any issues as quickly and completely as possible. This relates not only to software quality but also software security. Different organizations are at different levels when it comes to having their development teams and security teams working in concert, but the simple fact remains that there are far more developers out there than security engineers.

Those factors are leading organizations to consider security tooling and automation to proactively discover and resolve any software security issues throughout the development process. In the recent report, “GigaOm Radar for Developer Security Tools,” Shea Stewart examines a roundup of security tools aimed at software development teams.

Stewart identified three critical criteria to bear in mind when evaluating developer security tools. These include:

  • Vendors providing tools to improve application security can and should also enhance an organization’s overall security posture.
  • The prevailing “shift-left” mindset doesn’t necessarily mean the responsibility for reducing risk should shift to development, but instead focusing on security earlier in the process and continuing to do so throughout the development process will reduce risk and the need for extensive rework.
  • Security throughout the entire software development lifecycle (SDLC) is critical for any organization focused on reducing risk.

Figure 1. How Cybersecurity Applies Across Each Stage of the Software Development Lifecycle *Note: This report focuses only on the Developer Security Tooling area

Individual vendors have made varying levels of progress and innovation toward enhancing developer security. Following several acquisitions, Red Hat, Palo Alto Networks, and Rapid7 have all added tooling for developer security to their platforms. Stewart sees a couple of the smaller vendors like JFrog and Sonatype as continuing to innovate to remain ahead of the market.

Vendors delving into this category and moving deeper into “DevSecOps” all seem to be taking different approaches to their enhanced security tooling. While they are involving security in every aspect of the development process, some tend to be moving more quickly to match the pace of the SDLC. Others are trying to shore up existing platforms by adding functionality through acquisition. Both infrastructure and software developers are now sharing toolsets and processes, so these development security tools must account for the requirements of both groups.

While none of the 12 vendors evaluated in this report can provide comprehensive security throughout the entire SDLC, they all have their particular strengths and areas of focus. It is therefore incumbent upon the organization to fully and accurately assess its SDLC, involve the development and security teams, and match the unique requirements with the functionality provided by these tools. Even if it involves using more than one at different points throughout the process, focus on striking a balance between stringent security and simplifying the development process.

Read more: Key Criteria for Evaluating Developer Security Tools, and the Gigaom Radar for Developer Security Tool Companies.

The post Security Tools Help Bring Dev and Security Teams Together appeared first on Gigaom.

Continue Reading

Security

Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA)

Published

on

Cybersecurity is a multidisciplinary practice that not only grows in complexity annually but evolves nearly as quickly. A survey of the security landscape today would reveal concerns ranging from the classic compromised servers to the relatively new DevSecOps practices aimed at securing the rapid deployment of new code and infrastructure. However, some things remain constant no matter how much change is introduced. While technology evolves and complexity varies, there is almost always a human component in
risks presented to an organization.

User Behavior Analysis (UBA) was designed to analyze the actions of users in an organization and attempt to identify normal and abnormal behaviors. From this analysis, malicious or risky behaviors can be detected. UBA solutions identify events that are not detectable using other methods because, unlike classic security tools (an IDS or SIEM for example), UBA does not simply pattern match or apply rule sets to data to identify security events. Instead, it looks for any and all deviations from baseline user activity.

As technology advanced and evolved, and the scope of what is connected to the network grew, the need to analyze entities other than users emerged. In response, entity analysis has been added to UBA to create UEBA or User and Entity Behavior Analysis. The strategy remains the same, but the scope of analysis has expanded to include entities involving things like daemons, processes, infrastructure, and so on.

How to Read this Report

This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:

Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.

GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.

Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.

The post Key Criteria for Evaluating User and Entity Behavior Analytics (UEBA) appeared first on Gigaom.

Continue Reading

Security

GigaOm Radar for Developer Security Tools

Published

on

As we learned in the associated GigaOm report, “Key Criteria for Evaluating Developer Security Tools,” the most cost-effective method for reducing risk in software development is to identify and fix issues as close to the developer as possible. As the number of software developers continues to vastly outnumber the number of security professionals allocated to any software project, organizations need to invest in security tooling and automation that can help software developers consider and mitigate security risks in a proactive manner.

Add to this situation an appreciation for how the role of the developer has changed vastly over the last few years: Developers aren’t just responsible for software components; they can write infrastructure components, security controls, automations/integrations, and so forth. This has blended the worlds of the traditional software developers and the infrastructure and operations teams responsible for the environments that software components are deployed to. A much wider range of job titles can be incorporated into the developer role now, which requires the same security tooling and process oversight as does traditional software development.

As we consider how to evaluate vendors for developer security tools, we need to take these points into account:

  • All vendors involved in improving application security can contribute to an organization’s overall enhanced security posture.
  • “Shift-left” mindsets do not imply that the work of reducing risk is simply shifted to the developer, but rather that adding a focus on security early in the process will reduce risk and rework as software moves through the delivery pipeline.
  • Security throughout the entire software development lifecycle (SDLC) is key for any organization that is focused on reducing risk.

In this report we have identified a number of vendors that address the specific need to catch and remediate security issues earlier in the software development lifecycle, which we articulate in the report as table stakes, key criteria, and evaluation metrics. While we review 12 vendor solutions here, we ruled out many more, including several offering capabilities focused on runtime protection, which merit review in upcoming GigaOm Key Criteria and Radar Reports.

How to Read this Report

This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding consider reviewing the following reports:

Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.

GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.

Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.

The post GigaOm Radar for Developer Security Tools appeared first on Gigaom.

Continue Reading

Trending