You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposal is to extend the File Object by adding details about the type of drive where the file is located. This enrichment would offer greater security insight, assisting the SOC team in determining whether files are created off a network drive or say a USB thumb drive.
Some advantages if this is added:
Better file activity tracking
Data Compliance and Governance
Improved incident response
We can add two optional fields called drive_type and drive_type_id under File Object to take care of this. drive_type_id can take one of the following values : 0 = "Unknown", 1 = "Removable", 2 = "Fixed", 3 = "Remote", 4 = "CD-ROM", 5 = "Ram Disk", 99 = "Other"
and the drive_type would be string equivalent.
Example : If a user creates a file on a Windows network share say \\10.0.2.3\public\users\testusers\ocsf_file_create.exe, the File System Activity can include the File Object with drive_type_id as 3 and drive_type as Remote
"Removable" (e.g., USB drives)
"Fixed" (e.g., internal hard drives)
"Remote" (e.g., network drives)
"CD-ROM" (e.g., optical drives)
"RAM Disk" (e.g., temporary storage in RAM)
"Other" (for any other types not specifically listed)
The text was updated successfully, but these errors were encountered:
#### Related Issue:
1286 - Add drive_type and drive_type_id under File Object
#1286
#### Description of changes:
The proposal is to extend the File Object by adding details about the
type of drive where the file is located. This enrichment would offer
greater security insight, assisting the SOC team in determining whether
files are created off a network drive or say a USB thumb drive.
The below list was inspired by a Win32 API :
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getdrivetypea
I have added two optional fields called drive_type and drive_type_id
under File Object to take care of this.
drive_type_id can take one of the following values :
```0 = "Unknown", 1 = "Removable", 2 = "Fixed", 3 = "Remote", 4 = "CD-ROM", 5 = "RAM Disk", 99 = "Other" ```
and the drive_type would be string equivalent.
<img width="1297" alt="Screenshot 2024-12-12 at 9 03 49 PM" src="https://github.com/user-attachments/assets/ff14b6b6-94f3-4efe-a635-c711180ba993" />
---------
Signed-off-by: [email protected] <[email protected]>
Co-authored-by: [email protected] <[email protected]>
The proposal is to extend the File Object by adding details about the type of drive where the file is located. This enrichment would offer greater security insight, assisting the SOC team in determining whether files are created off a network drive or say a USB thumb drive.
Some advantages if this is added:
We can add two optional fields called
drive_type
anddrive_type_id
under File Object to take care of this.drive_type_id
can take one of the following values :0 = "Unknown", 1 = "Removable", 2 = "Fixed", 3 = "Remote", 4 = "CD-ROM", 5 = "Ram Disk", 99 = "Other"
and the
drive_type
would be string equivalent.Example : If a user creates a file on a Windows network share say
\\10.0.2.3\public\users\testusers\ocsf_file_create.exe
, the File System Activity can include the File Object withdrive_type_id
as3
anddrive_type
asRemote
"Removable" (e.g., USB drives)
"Fixed" (e.g., internal hard drives)
"Remote" (e.g., network drives)
"CD-ROM" (e.g., optical drives)
"RAM Disk" (e.g., temporary storage in RAM)
"Other" (for any other types not specifically listed)
The text was updated successfully, but these errors were encountered: