Platform updates
Vulcan API v2 is here
We’re excited to introduce Vulcan API v2, offering expanded support and designated documentation for multiple request types in a newly designed, API-friendly interface.
The new API v2 is available here: https://apidocs.vulcancyber.com/reference/welcome
What’s new?
With Vulcan API v2, we’re introducing an enhanced, developer-friendly interface designed to streamline your experience with our API. This new platform consolidates all API resources in one place, making it easier for developers to explore, interact, and get started with the Vulcan API. The new interface combines all essential resources, including API references, help guides, and sample code tutorials, allowing you to get everything you need to use our API effectively in one convenient location. Plus, you can try out API requests directly from within the Vulcan Cyber ExposureOS, giving you instant feedback and real-time logs to track what’s working.
Key Benefits
Expanded API support: Vulcan API v2 supports GET, PUT, POST, and PATCH requests.
User-friendly interface: Access a dedicated interface designed for easier API management.
Dual API access: Both API v1 and v2 are available directly from the Vulcan Cyber ExposureOS, allowing users to choose the version that best fits their needs.
Future updates: This new version is an ongoing development, and additional endpoints and request types will be added in future updates.
Why does this matter to you?
The new Vulcan API v2 provides enhanced capabilities for interacting with the Vulcan Cyber ExposureOS. By supporting more request types, you gain greater control over automating tasks, fetching data, and integrating Vulcan Cyber with your existing tools. This update ensures flexibility as we continue to expand our API offerings.
What should you do next?
You’ll find both v1 and v2 available for use. Feel free to begin with the currently supported request types (GET, PUT, POST, PATCH), and keep an eye out for future updates as more endpoints and features are added.
To access Vulcan API v1 and V2:
Go to the Vulcan Platform > Help and Support > Select the relevant API version.
Data updates
Table-formatted widgets in customized reports
We’re excited to announce a powerful new feature in Customized Reports and Widgets that allows users to create table-formatted widgets for better data visualization and management.
What’s new?
You can now create widgets in a table format, customize the columns and measures, and view the data in a clear and organized layout. Additionally, you can export the table as an Excel file for further use.
Create table-formatted widgets: Customize your widgets by adding columns and measures.
View data in table format: Arrange and display your data in an organized table view.
Export to Excel: Download and export the table as an Excel file for further analysis or reporting.
Why does this matter to you?
Table-formatted widgets give you more control over your data, making it easy to interpret and export for reporting and team collaboration.
What should you do next?
Head to Reports to create a table-formatted widget. Customize your columns and measures, then export as needed for reporting.
Improved transparency for Connector processing time
Previously, the Connector Logs showed only the total processing time, which could include long periods of waiting while other connectors completed their synchronization. In this release, we’re enhancing the transparency of the processing time in the Connector Logs by distinguishing between actual processing time and waiting time.
What’s new?
Enhanced visibility: Gain clear visibility with Connector logs that now indicate both the total processing time and the total waiting duration, helping you understand how much time was actually spent processing.
Why does this matter to you?
This change gives you more clarity and insight into the performance of your connectors. By understanding the difference between waiting time and actual processing time, you can better assess the efficiency of your connector setup and manage expectations when syncing multiple connectors.
What should you do next?
When reviewing the connector logs, simply check the waiting time listed in the time stamps. Deduct this from the total processing time to determine the actual time spent processing. This new level of visibility will help you better track and manage your connector synchronization.
For example, as shown in the above screen, if the log shows 11 hours and 47 minutes as the total time, and 6 hours and 51 minutes of waiting, users can quickly calculate that the actual processing took around 4 hours and 56 minutes.
Vulcan Connectors and integration updates
Veracode SAST connector now supports fetching DAST findings
We’re excited to announce an enhancement to the Veracode connector!
What’s new?
Until now, the connector only supported fetching SAST findings. This release now lets you fetch both DAST (dynamic) and SAST (static) findings, giving you more control over your security data.
Select which findings to fetch: SAST, DAST, or both.
Easily configure your preferences from the connector setup page.
Filter vulnerability findings by SAST, DAST, or both.
SAST and DAST findings are mapped to Code Projects.
Best practice guides
Managing remediation workflow best practice
This best practice outlines an integrated cybersecurity operating model to enhance risk management and remediation processes. It emphasizes the importance of aligning security efforts across teams, prioritizing critical vulnerabilities, and ensuring effective communication between Product Owners, Security Champions, and the GRC team.