Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amends Vaulty data headers #231

Merged
merged 1 commit into from Mar 10, 2022
Merged

Amends Vaulty data headers #231

merged 1 commit into from Mar 10, 2022

Conversation

kibaffo33
Copy link
Contributor

Amends headers to match research rather than DB.

As queried here https://twitter.com/kibaffo33/status/1501212458417102858

@AlexisBrignoni ALEAPP etiquette question - when research shows a column header is inaccurate/better described another way (eg date modified is date added) - should the ALEAPP artefact reflect the DB or the research? #aleapp #dfir pic.twitter.com/Ird6vbousd

— Bob (@kibaffo33) March 8, 2022

I name the fields in a way that accurately reflects the proper interpretation of the data.

This is where having a blogpost for the research is key. You can put a link to it in the artifact report. See usage of the description variable below. pic.twitter.com/KQBRB2NSAV

— Brigs 💬 (@AlexisBrignoni) March 8, 2022

Thanks!

@abrignoni abrignoni merged commit da171f5 into abrignoni:master Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants