add origin_referrer_url and origin_url to the file attribute

.chloggen/file_originevents.yaml

@@ -0,0 +1,23 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: file
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: This adds file.origin_referrer_url and file.origin_url attributes.
+      In addition, it also adds file.open event under event.yaml
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [1430]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

docs/attributes-registry/file.md

@@ -25,11 +25,13 @@ Describes file attributes.
 | <a id="file-mode" href="#file-mode">`file.mode`</a> | string | Mode of the file in octal representation. | `0640` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-modified" href="#file-modified">`file.modified`</a> | string | Time when the file content was last modified, in ISO 8601 format. | `2021-01-01T12:00:00Z` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-name" href="#file-name">`file.name`</a> | string | Name of the file including the extension, without the directory. | `example.png` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| <a id="file-origin-referrer-url" href="#file-origin-referrer-url">`file.origin_referrer_url`</a> | string | The URL of the webpage that linked to the file. [7] | `http://example.com/article1.html` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| <a id="file-origin-url" href="#file-origin-url">`file.origin_url`</a> | string | The URL where the file is hosted. [8] | `http://example.com/imgs/article1_img1.jpg` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-owner-id" href="#file-owner-id">`file.owner.id`</a> | string | The user ID (UID) or security identifier (SID) of the file owner. | `1000` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-owner-name" href="#file-owner-name">`file.owner.name`</a> | string | Username of the file owner. | `root` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-path" href="#file-path">`file.path`</a> | string | Full path to the file, including the file name. It should include the drive letter, when appropriate. | `/home/alice/example.png`; `C:\Program Files\MyApp\myapp.exe` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | <a id="file-size" href="#file-size">`file.size`</a> | int | File size in bytes. |  | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
-| <a id="file-symbolic-link-target-path" href="#file-symbolic-link-target-path">`file.symbolic_link.target_path`</a> | string | Path to the target of a symbolic link. [7] | `/usr/bin/python3` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| <a id="file-symbolic-link-target-path" href="#file-symbolic-link-target-path">`file.symbolic_link.target_path`</a> | string | Path to the target of a symbolic link. [9] | `/usr/bin/python3` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 
 **[1] `file.accessed`:** This attribute might not be supported by some file systems — NFS, FAT32, in embedded OS, etc.
 
@@ -44,4 +46,8 @@ Describes file attributes.
 **[6] `file.fork_name`:** On Linux, a resource fork is used to store additional data with a filesystem object. A file always has at least one fork for the data portion, and additional forks may exist.
 On NTFS, this is analogous to an Alternate Data Stream (ADS), and the default data stream for a file is just called $DATA. Zone.Identifier is commonly used by Windows to track contents downloaded from the Internet. An ADS is typically of the form: C:\path\to\filename.extension:some_fork_name, and some_fork_name is the value that should populate `fork_name`. `filename.extension` should populate `file.name`, and `extension` should populate `file.extension`. The full path, `file.path`, will include the fork name.
 
-**[7] `file.symbolic_link.target_path`:** This attribute is only applicable to symbolic links.
+**[7] `file.origin_referrer_url`:** This information comes from metadata or alternate data streams linked to the file. `file.origin_url` represents the URL from which the file was downloaded, and `file.origin_referrer_url` indicates the URL of the page where that URL was listed. There may be cases where both `file.origin_url` and `file.origin_referrer_url` exist, or only one of them is present. Note that the URL itself may contain sensitive information.
+
+**[8] `file.origin_url`:** This information comes from metadata or alternate data streams linked to the file. `file.origin_url` represents the URL from which the file was downloaded, and `file.origin_referrer_url` indicates the URL of the page where that URL was listed. There may be cases where both `file.origin_url` and `file.origin_referrer_url` exist, or only one of them is present. Note that the URL itself may contain sensitive information.
+
+**[9] `file.symbolic_link.target_path`:** This attribute is only applicable to symbolic links.

model/file/events.yaml

@@ -0,0 +1,31 @@
+groups:
+  - id: event.file.open
+    stability: experimental
+    type: event
+    name: file.open
+    brief: >
+      A file is defined as a set of information that has been created on,
+      or has existed on a filesystem.
+      A file open event represents the action of a process accessing a file
+      on the filesystem. It includes details such as the file's name,
+      path, directory, size, extension, and metadata, including
+      file access time, file origin information and more. It addition,
+      it also includes information about the process that accessed the file.
+    attributes:
+      - ref: file.name
+      - ref: file.path
+      - ref: file.directory
+      - ref: file.size
+      - ref: file.extension
+      - ref: file.accessed
+      - ref: file.created
+      - ref: file.owner.name
+      - ref: file.owner.id
+      - ref: file.origin_referrer_url
+      - ref: file.origin_url
+      - ref: process.pid
+        brief: Process id of the process that accessed the file.
+      - ref: process.user.name
+        brief: Process name of the process that accessed the file.
+      - ref: process.executable.name
+        brief: Executable file name of the process that accessed the file.

model/file/registry.yaml

@@ -112,6 +112,30 @@ groups:
           The user ID (UID) or security identifier (SID) of the file owner.
         stability: experimental
         examples: ["1000"]
+      - id: file.origin_referrer_url
+        type: string
+        brief: >
+          The URL of the webpage that linked to the file.
+        note: >
+          This information comes from metadata or alternate data streams linked to the file.
+          `file.origin_url` represents the URL from which the file was downloaded, and `file.origin_referrer_url`
+          indicates the URL of the page where that URL was listed. There may be cases where both `file.origin_url`
+          and `file.origin_referrer_url` exist, or only one of them is present. Note that the URL itself may contain
+          sensitive information.
+        stability: experimental
+        examples: ['http://example.com/article1.html']
+      - id: file.origin_url
+        type: string
+        brief: >
+          The URL where the file is hosted.
+        note: >
+          This information comes from metadata or alternate data streams linked to the file.
+          `file.origin_url` represents the URL from which the file was downloaded, and `file.origin_referrer_url`
+          indicates the URL of the page where that URL was listed. There may be cases where both `file.origin_url`
+          and `file.origin_referrer_url` exist, or only one of them is present. Note that the URL itself may contain
+          sensitive information.
+        stability: experimental
+        examples: ['http://example.com/imgs/article1_img1.jpg']
       - id: file.owner.name
         type: string
         brief: >