Changes related to Securonix release 2.0.13

[scnx-knathani]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

• Updated securonix-get-incident and securonix-list-incidents commands to include the Spotter query in the HR and context by upgrading to the latest version of the API.
• Updated the securonix-list-incidents command to include the Incident ID field in the HR column.
• Updated the securonix-list-violation-data command, where the query argument now supports the auto inclusion of the "index" with a default value as "violation" if not provided.
• Updated the Docker image to: demisto/python3:3.10.13.78960.

Must have

• Tests
• Documentation

[MosheEichler]

Hi @scnx-knathani,
Thank you for your contribution!
Good work :)
Please feel free to reach out to me with any questions - I'm available here or on slack :)
Thanks again.

@melamedbn
Can you please take a look a the Classifiers changes?

@ShirleyDenkberg
Can you please take a look at the docs?

[ShirleyDenkberg]

@melamedbn @MosheEichler Doc review completed.

[melamedbn]

Hi @scnx-knathani,

Can you please explain the changes made to the mappers?

Best regards,
Ben

[scnx-knathani]

Hi @scnx-knathani,

Can you please explain the changes made to the mappers?

Best regards, Ben

Previously we removed the index=violation from the Spotter query using the transformers in the Mapper but from now onwards this will be handled in the command logic itself we'll show the full query to the end user without trimming the layout hence this change was made in the Mapper. Please let me know if you've further questions on this.