-
Notifications
You must be signed in to change notification settings - Fork 243
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into feature-flag-proposal
- Loading branch information
Showing
16 changed files
with
124 additions
and
360 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -63,6 +63,15 @@ A single Zoom account should not be used for back-to-back meetings or for more t | |
| You can see which Zoom account any potentially conflicting meetings are using in the meeting descriptions. | ||
| (Note: posting the URLs publicly on GitHub leads to Zoom bombing by random bots). | ||
|
|
||
| #### Zoom link generation process | ||
| _This is the process that the person responding to Zoom link creation issues will follow. The instructions under this heading are for project admins (Governance Committee members) who have access to OpenTelemetry's Zoom account credentials._ | ||
|
|
||
| 1. View the OpenTelemetry meeting calendar, and find your desired time slot, along with the meetings that occur immediately before, during, and after it. | ||
| 2. See which OpenTelemetry Zoom accounts are being used for the meetings immediately before, during, and after your desired time. The Zoom account name / number is typically listed in the description of each meeting; if it isn't, you can join a meeting (even if it isn't occurring now), click on the green shield icon in the top left, and see the account name / number in the 'host' field. | ||
| 3. Choose a Zoom account that isn't already being used for one of the meetings immediately before, during, or after your desired time slot. You may also choose a Zoom account that is being used *exactly* once immediately before, during, or after (we can run a maximum of two concurrent meetings with each account). | ||
| 4. Log into that Zoom account, click "Schedule a meeting", and create a recurring meeting with the desired meeting name and no fixed schedule. | ||
| 5. Copy the newly generated unique Zoom link and paste it into the calendar event's description and location. | ||
|
|
||
| ### Inviting attendees | ||
| All meetings should invite a publicly joinable google group `[email protected]` which is specific to the meeting series. | ||
| The google group should be set up as follows: | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
| # Security Semantic Conventions | ||
|
|
||
| ## Description | ||
|
|
||
| The purpose of this project is to bring in the security domain for the OpenTelemetry community. | ||
|
|
||
| As outlined in the [ECS OTEP](https://github.com/open-telemetry/oteps/blob/main/text/0199-support-elastic-common-schema-in-opentelemetry.md), the Elastic Common Schema (ECS) is currently being contributed to the semantic conventions schema. Given the significance of security within ECS, establishing this SIG is crucial as it will expedite the donation of ECS fields tailored to security use cases. Beyond expanding the schema, our aim is to craft a clear vision for the instrumentation required. | ||
|
|
||
| ## Deliverables | ||
|
|
||
| * Our current focus is on defining essential semantic conventions for security use cases. | ||
| * This includes but is not limited to the following namespaces: | ||
| * [`Code signature`](https://www.elastic.co/guide/en/ecs/current/ecs-code_signature.html) | ||
| * [`DLL`](https://www.elastic.co/guide/en/ecs/current/ecs-dll.html) | ||
| * [`DNS`](https://www.elastic.co/guide/en/ecs/current/ecs-dns.html) | ||
| * [`File`](https://www.elastic.co/guide/en/ecs/current/ecs-file.html) | ||
| * [`Group`](https://www.elastic.co/guide/en/ecs/current/ecs-group.html) | ||
| * [`Hash`](https://www.elastic.co/guide/en/ecs/current/ecs-hash.html) | ||
| * [`Host`](https://www.elastic.co/guide/en/ecs/current/ecs-host.html) | ||
| * [`Network`](https://www.elastic.co/guide/en/ecs/current/ecs-network.html) | ||
| * [`Operating System`](https://www.elastic.co/guide/en/ecs/current/ecs-os.html) | ||
| * [`Package`](https://www.elastic.co/guide/en/ecs/current/ecs-package.html) | ||
| * [`Process`](https://www.elastic.co/guide/en/ecs/current/ecs-process.html) | ||
| * [`Registry`](https://www.elastic.co/guide/en/ecs/current/ecs-registry.html) | ||
| * [`Risk information`](https://www.elastic.co/guide/en/ecs/current/ecs-risk.html) | ||
| * [`Rule`](https://www.elastic.co/guide/en/ecs/current/ecs-rule.html) | ||
| * [`Threat`](https://www.elastic.co/guide/en/ecs/current/ecs-threat.html) | ||
| * [`TLS`](https://www.elastic.co/guide/en/ecs/current/ecs-tls.html) | ||
| * [`User`](https://www.elastic.co/guide/en/ecs/current/ecs-user.html) | ||
| * [`Vulnerability`](https://www.elastic.co/guide/en/ecs/current/ecs-vulnerability.html) | ||
| * Please note that some of the above-mentioned namespaces are already a part of the Semantic Conventions schema. The goal is to expand these namespaces to include additional fields that are relevant to security use cases. | ||
|
|
||
| * As new use cases and namespaces are introduced to the semantic conventions, there may be a need for additional instrumentation to accommodate them. It is anticipated that this aspect will expand through an iterative process. | ||
|
|
||
| ## Staffing / Help Wanted | ||
|
|
||
| We are seeking security experts to collaborate with us in expanding the security domain within the community. | ||
|
|
||
| ### Required staffing | ||
|
|
||
| There is an open [PR](https://github.com/open-telemetry/semantic-conventions/issues/580) to create a `semconv-security-approver` group for all PRs related to security fields. | ||
|
|
||
| * project lead: @trisch-me (Elastic) | ||
| * domain expert: @mjwolf (Elastic) | ||
| * domain expert: @raesene (Datadog) | ||
| * domain expert: @lambdanis (Isovalent) | ||
| * domain expert: @mdelfabro (Dynatrace) | ||
| * domain expert: @kelnage (Grafana Labs) | ||
| * domain expert: @alexvanboxel (Collibra) | ||
|
|
||
| * TC sponsor: @reyang | ||
| * TC sponsor: @jsuereth | ||
|
|
||
| Need more | ||
| - [ ] domain experts | ||
| - [ ] potentially, maintainers of language-specific instrumentation may be needed if the need arises. | ||
|
|
||
|
|
||
| ## Meeting Times | ||
|
|
||
| There is an allocated time in the Semantic Conventions SIG for this project. | ||
| - Mondays at 8 AM PST | ||
|
|
||
| For async conversation please use #otel-semconv-security slack channel from official CNCF slack workspace. | ||
|
|
||
| ## Timeline | ||
|
|
||
| The goal is to have the security semantic conventions implemented by the end of 2024. | ||
|
|
||
| The timeline for this project is as follows: | ||
| December 2023: Initial Draft | ||
| April 2024: Review and Refinement | ||
| May 2024-December 2024: Introducing the Security Semantic Conventions | ||
|
|
||
|
|
||
| ## Labels | ||
|
|
||
| * security | ||
|
|
||
| ## Linked Issues and PRs | ||
|
|
||
| * [Donating ECS to OpenTelemetry](https://github.com/open-telemetry/oteps/blob/main/text/0199-support-elastic-common-schema-in-opentelemetry.md) | ||
| * [Creation of semconv-security-approver group](https://github.com/open-telemetry/semantic-conventions/issues/580) |
This file was deleted.
Oops, something went wrong.
27 changes: 0 additions & 27 deletions
27
working-groups/end-user/discussion-group-code-of-conduct.md
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.