Skip to main content

SOC Prime Platform Product Release Notes 5.0.8

S
Written by Sergey Bayrachny

December 29, 2021

© 2021 SOC Prime Inc.

All rights reserved. This product and documentation related are protected by copyright and distributed under licenses restricting their use, copying, distribution, and decompilation. No part of this product or documentation related may be reproduced in any form or by any means without the prior written authorization of SOC Prime. While every precaution has been taken in the preparation of this book, SOC Prime assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice.

Duplicate Names in Chronicle Security


With this release, we've improved checks for duplicate content item names before deployment into Chronicle Security. Now, if a content item name is already present in the selected Chronicle Security instance, an error popup is shown and deployment is not performed.

Filter for Dynamic Content Lists


To improve the user experience in Continuous Content Management, we've updated and simplified advanced filters for Dynamic Content Lists:

  • Removed four deprecated content metrics:

    • Severity

    • Pain

    • Action

    • Impact

  • Renamed Sigma Level to Severity

New Endpoint in CCM API


With this release, we've added to the Continuous Content Management API a new endpoint /ccm/content-list with GET method, which shows content lists available to a given company.

Unified Icon for Context Menu


With this latest release, we've unified the design of the context menu icon across all pages and modules of the SOC Prime Platform. This makes the Platform design more consistent and intuitive.

Key Bug Fixes & Improvements


With this release, we’ve made the following key bug fixes and improvements to enhance the user experience with the SOC Prime Platform:

  • Resolved the issue with Jobs for Elasticsearch in Continuous Content Management. In some cases, an error occurred when a Job attempted to deploy a Detection Rule for Elasticsearch with a Preset applied.

Did this answer your question?