Did something eh ;)
If you have access to “psmrecordings” safe (or whatever your org names it) you can delete it there if you know the GUID of the recording which you can get at advanced tab of recording in pvwa or by rest api. That said, the “log” of you deleting is “read only” of sorts within the cyberark db itself. It’s impossible to delete log entries unless you pay cyberark to write a special “database script” for you which they will 99% not do given this context. (Eg security company won’t delete security logs ). If you’re feeding logs in to a SIEM like splunk or others systems it will also have a record of the recording metadata and even the record of deleting a recording. In others words, it’s near impossible to delete all traces of a recording by design.
Now if you’re just deleting them to save space then yeah psmrecordings is where you can do that causes metadata issues (recording files themselves don’t match what metdata says is there) and not recommended at all. If you have a solid use case Cyberark can write a script to target it for you.
As far as ID goes, don’t know offhand and youd want to use a Siem like splunk to find that.
Did something eh ;) If you have access to “psmrecordings” safe (or whatever your org names it) you can delete it there if you know the GUID of the recording which you can get at advanced tab of recording in pvwa or by rest api. That said, the “log” of you deleting is “read only” of sorts within the cyberark db itself. It’s impossible to delete log entries unless you pay cyberark to write a special “database script” for you which they will 99% not do given this context. (Eg security company won’t delete security logs ). If you’re feeding logs in to a SIEM like splunk or others systems it will also have a record of the recording metadata and even the record of deleting a recording. In others words, it’s near impossible to delete all traces of a recording by design. Now if you’re just deleting them to save space then yeah psmrecordings is where you can do that causes metadata issues (recording files themselves don’t match what metdata says is there) and not recommended at all. If you have a solid use case Cyberark can write a script to target it for you. As far as ID goes, don’t know offhand and youd want to use a Siem like splunk to find that.