Phoenix Security Features – May/June 2023 – Application Security & Vulnerability Management Improvement

May Release

The Cloud Security and AppSec teams at Phoenix Security are pleased to bring you another set of new Phoenix Security Features and improvements for vulnerability management across application and cloud security engines. This release builds on top of previous releases with key additions and progress across multiple areas of the platform.

We are sure that you’ll find these quite interesting!

  • Manage your Vulnerabilities and Assets
    • Vulnerability Filtering and Sorting
    • Location column in Vulnerabilities list
    • Default Configuration for Context Rules
    • Customisation of the number of tickets per backlog
  • Productivity and User Experience
    • Loading indicators and other usability improvements
    • More efficient use of space in Vulns tables
  • Integrations
    • VM integration
    • Unified scanner integrations page
    • Outbound Vulnerability API (preview)

Manage your Vulnerabilities and Assets across application security and cloud security.

Vulnerability Filtering and Sorting

Our users can now leverage the Vulnerabilities page even more. A complete set of filters and sorting options ensures they can select the exact set of vulnerabilities of interest to them. Not only that, but you can even snapshot the “filtering” URL and bookmark it or share it around!

Sortable columns and filters
Vulnerabilities Filters (1)
Vulnerability Filters (2)

Location column in Vulnerabilities list

When working with our Vulnerabilities screen, it might be easy to forget that we look at “findings” rather than vulnerability definitions. In other words, if we have CVE-1234-1234 affecting several “locations” (assets) in our state, we will see one entry for each since we need to address each individually. This can sometimes give the impression that there is duplicity in the platform when in reality, what we see is “detail”.

We have included a Location column in the vulnerabilities list to clarify this screen’s contents and provide additional relevant information. This column displays a recognisable name or ID for the asset or location affected by the vulnerability. And since these names can be quite long and tend to have a common prefix, we are displaying the end of the names – hopefully, this will make them easier to recognise.

Vulnerability location for application security assets

Default Configuration for Context Rules

Phoenix Security’s Context Rules are a powerful way to define which assets are externally accessible. This “locality” has an impact on risk calculation and vulnerability selection.

Since there are some reasonably standard scenarios for infra assets, we have defined a set of default rules based on the type of IP address assigned to the asset: private IPs ranges are considered internal, and the rest are considered external.

These are just defaults, which users can change at any time.

Customisation of the number of tickets per backlog

Phoenix Security always could auto-create issue tickets in external systems configured by our users. We recently introduced a control to determine how many tickets should be auto-created for each external queue or project. Since the number of tickets selected to fix can vary widely depending on the selected risk target, this control offers a safety net for our users.

Now users can define what number of new tickets Phoenix should open on each project at any point in time.

Productivity and User Experience

Loading indicators and other usability improvements

We continuously seek ways to improve our users’ experience on the Phoenix platform. Providing timely feedback when the system is busy fetching or computing is an important part of that, and we are constantly adding UI elements to improve this area.

More efficient use of space in Vulns tables

Further improvements have been made to the Vulnerabilities list page, which now has more visual elements to help users quickly identify the type of vulnerability and scanner for each entry.

Integrations VM integration and others

Joining our native integration with Nessus servers, we now have a direct API integration with your instance to fetch infrastructure (VM) vulnerabilities. Other integrations were available here

It takes two minutes to connect to your instance and fetch vulnerabilities into the Phoenix platform. You can see our guide here:

Unified scanner integrations page

Now users can see all their scanner integrations and all those available in a single page. Creating, editing and removing scanner integrations is now easier than ever.

Outbound Vulnerability API (preview)

In tandem with the vulnerability filtering capabilities in the UI, users can now take advantage of our API to fetch the exact subset of vulnerabilities that they need. This functionality is still in review, but don’t hesitate to contact us if you want to take it for a spin.

Get an overview of your asset lineage

Alfonso brings experience running international teams for multi-million dollar, technologically advanced projects for Telefónica, IBM and Vodafone. Alfonso joins with two decades of experience working for tech leaders, including at Dell EMC, Yahoo! and Intershop.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

Explore ASPM’s role in modern application security, offering a panoramic view that extends beyond code vulnerabilities. This guide demystifies concepts like traceability, reachability analysis, and asset lineage, pivotal for securing digital assets. Learn how ASPM empowers organizations with actionable insights for precise vulnerability management. #Cybersecurity #ASPM #ApplicationSecurity
Francesco Cipollone
Explore the transformative role of ASPM in cybersecurity. Uncover how Application Security Posture Management aligns business and security objectives for effective vulnerability management and risk reduction. Discover Phoenix Security’s innovative approach to tackling the staggering challenge of CVEs with a strategic focus on prioritization. #ASPM #Cybersecurity #VulnerabilityManagement
Francesco Cipollone
Explore the critical insights into the latest container security vulnerabilities named leaky vessels, including CVE-2024-21626, CVE-2024-23651, CVE-2024-23653, and CVE-2024-23652, BuildKit flaws, with our comprehensive guide on mitigation strategies, best practices for application security, and tips for robust vulnerability management in Docker and Kubernetes environments. Stay ahead in securing your container deployments against potential threats with ASPM help
Francesco Cipollone

Jeevan Singh

Founder of Manicode Security

Jeevan Singh is the Director of Security Engineering at Rippling, with a background spanning various Engineering and Security leadership roles over the course of his career. He’s dedicated to the integration of security practices into software development, working to create a security-aware culture within organizations and imparting security best practices to the team.
In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

James Berthoty

Founder of Latio Tech

James Berthoty has over ten years of experience across product and security domains. He founded Latio Tech to help companies find the right security tools for their needs without vendor bias.

Christophe Parisel

Senior Cloud Security Architect

Senior Cloud Security Architect

Chris Romeo

Security Journey

Chris Romeo is a leading voice and thinker in application security, threat modeling, and security champions and the CEO of Devici and General Partner at Kerr Ventures. Chris hosts the award-winning “Application Security Podcast,” “The Security Table,” and “The Threat Modeling Podcast” and is a highly rated industry speaker and trainer, featured at the RSA Conference, the AppSec Village @ DefCon, OWASP Global AppSec, ISC2 Security Congress, InfoSec World and All Day DevOps. Chris founded Security Journey, a security education company, leading to an exit in 2022. Chris was the Chief Security Advocate at Cisco, spreading security knowledge through education and champion programs. Chris has twenty-six years of security experience, holding positions across the gamut, including application security, security engineering, incident response, and various Executive roles. Chris holds the CISSP and CSSLP certifications.

Jim Manico

Founder of Manicode Security

Jim Manico is the founder of Manicode Security, where he trains software developers on secure coding and security engineering. Jim is also the founder of Brakeman Security, Inc. and an investor/advisor for Signal Sciences. He is the author of Iron-Clad Java: Building Secure Web Applications (McGraw-Hill), a frequent speaker on secure software practices, and a member of the JavaOne Rockstar speaker community. Jim is also a volunteer for and former board member of the OWASP foundation.

Join our Mailing list!

Get all the latest news, exclusive deals, and feature updates.