Add tty, ses columns to process_events table schema
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 23.6k
- Forks
- 2.6k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 14
Description
disclaimer: not a contribution
Feature request
What new feature do you want?
Please add the following columns to the schema for process_events
ttyses
these fields are already available in the test data in process_events_tests.cpp
How is this new feature useful?
tty allows associating a process event with the specific tty it spawned in.
ses allows associating a process event with the specific session
How can this be implemented?
-
around https://github.com/osquery/osquery/blob/master/osquery/events/linux/auditeventpublisher.cpp#L185 the values can be unpacked from the
audit_event_record -
around https://github.com/osquery/osquery/blob/master/osquery/tables/events/linux/process_events.cpp#L170 the table code could read these values
-
schema could be updated at https://github.com/osquery/osquery/blob/master/specs/posix/process_events.table
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with osquery/events/linux/auditeventpublisher.cpp around line 185 and osquery/tables/events/linux/process_events.cpp around line 170 to trace the tty and ses values from audit_event_record into the process_events table. Update specs/posix/process_events.table and verify the existing data and expectations in osquery/tables/events/tests/linux/process_events_tests.cpp cover both columns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100