Skip to content

Improve artifact definition specification #13

Open
@joachimmetz

Description

@joachimmetz

Done

To do

  • add tags/labels e.g. for persistence method
    • this is not going to be very useful as filter method since there are many persistence methods
    • Labels will be removed in Change legacy definitions to use alias #465
    • separate "trait" definitions might be more useful, especially if they can be pro-grammatically validated
  • Make path relative to the file system root (absolute?)
  • Change provides so that it has clear type indicators like sources
  • Define a way to specify data streams
  • have artifact names contain type information e.g "files" in "browser history files"
    • add source type to artifact name e.g. instead of ChromeHistory use ChromeHistoryFiles
  • define environment variables (path expanders)

Based on #12 there is a need to specify:

  • NTFS ADS names
  • HFS resource fork
  • extended attribute names

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions