Headline
Announcing the CVRF API 3.0 upgrade
At the Microsoft Security Response Center, we are committed to continuously improving the security and performance of our services to meet the evolving needs of our customers. We are excited to announce the rollout of the latest version of our Common Vulnerability Reporting (CVRF) API. This update brings improvements in both security and performance, without requiring any changes to your existing invocation methods.
At the Microsoft Security Response Center, we are committed to continuously improving the security and performance of our services to meet the evolving needs of our customers. We are excited to announce the rollout of the latest version of our Common Vulnerability Reporting (CVRF) API. This update brings improvements in both security and performance, without requiring any changes to your existing invocation methods. While updating the PowerShell module is optional, it can provide some additional performance benefits.
Faster response times
The CVRF API 3.0 offers significant performance improvements over its predecessor (2.0). When running code that performs multiple queries, you’ll experience noticeably faster response times.
Optional PowerShell update for direct access
While it’s not required to update your PowerShell module, doing so can provide additional performance benefits. Without the update, your requests will go to the 2.0 URL, which will then redirect to the 3.0 URL. By updating your PowerShell module, your requests go directly to the 3.0 URL, eliminating the need for redirection and further enhancing performance.
To take advantage of these improvements, we recommend updating your PowerShell module using the steps below:
Set-PsRepository -Name PSGallery -InstallationPolicy Trusted
Uninstall-Module -Name MsrcSecurityUpdates
Install-Module -Name MsrcSecurityUpdates -Force -SkipPublisherCheck
For more detailed examples and information, visit our GiHub repository.
Enhanced security
The new API is rewritten in a new format and hosted on a more reliable platform, providing enhanced security. Choosing to remain on the old API will mean customers becoming more susceptible to security incidents. Upgrading to the new API ensures you benefit from these security improvements.
Staying within rate limits With the faster 3.0 version, there’s a chance you might inadvertently exceed the API rate limit. If you encounter the error message “Too many follow-up requests: 21”, consider adjusting your query frequency. Staying within the rate limits ensures a smooth experience.
This upgrade empowers you with improved performance and security. We encourage you to explore the new capabilities and make the most of our CVRF API. As always, we welcome feedback on this new feature and other improvements here.