Splunk Search

deleted data - | delete - a query to prove this command has not been used and no data has been deleted?

r999
Path Finder

How can i tell if any data has been deleted using the | delete command?

how can i prove no data has been deleted?

Can i see if there are any flags against the data on the idnexers?

Does this command hide the data at Search Head leel or at the Indexer?

Edit: To clarify - i understand this command does not actually delete the data. i want to know if any admin user has given themself the can_delete privelege and deleted(hidden) data using |delete.

Tags (2)
1 Solution

jonuwz
Influencer

This search will show you if anyone has run the delete command :

index=_audit sourcetype=audittrail action=search search=*delete* 
| where match(search,"\|\s*delete")
| table search user

As for working out if someone has the capability, you need to look in each copy of authorize.conf to see what roles have the can_delete capability

If you have the SoS application installed, you can run this search within the app :

| btool authorize | extract | where delete_by_keyword="enabled" | table stanza

to get a list of roles with the can_delete capability.

Then you need to look in etc/passwd to see what users have these roles.
If you're going to do it properly, you'll need to factor in role heirarchies.

You might also consider signing the audit events so people cannot tamper with the results.

View solution in original post

jonuwz
Influencer

This search will show you if anyone has run the delete command :

index=_audit sourcetype=audittrail action=search search=*delete* 
| where match(search,"\|\s*delete")
| table search user

As for working out if someone has the capability, you need to look in each copy of authorize.conf to see what roles have the can_delete capability

If you have the SoS application installed, you can run this search within the app :

| btool authorize | extract | where delete_by_keyword="enabled" | table stanza

to get a list of roles with the can_delete capability.

Then you need to look in etc/passwd to see what users have these roles.
If you're going to do it properly, you'll need to factor in role heirarchies.

You might also consider signing the audit events so people cannot tamper with the results.

DaveSavage
Builder

I suspect the answer you seek is already covered in the knowledge base. Ses http://splunk-base.splunk.com/answers/30132/how-to-really-delete-not-hide-data-from-splunk for example.
You may need to differentiate in understanding between deleted (index content which does mean not available) and no longer in your system.
Good luck.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...