From 89f85fe0a8512870ea62964b312877ebaeeb1728 Mon Sep 17 00:00:00 2001 From: Alexandre Florez De La Colina Date: Thu, 11 Dec 2025 11:06:47 +0100 Subject: [PATCH 1/2] Update Cloud SIEM paths to match new prefix --- .../create-a-cloud-siem-detection-rule.md | 12 +++++------ .../en/getting_started/security/cloud_siem.md | 4 ++-- content/en/security/cloud_siem/_index.md | 4 ++-- .../custom_detection_rules/_index.md | 2 +- .../create_rule/historical_job.md | 2 +- .../create_rule/real_time_rule.md | 2 +- .../detect_and_monitor/historical_jobs.md | 4 ++-- .../detect_and_monitor/mitre_attack_map.md | 4 ++-- .../detect_and_monitor/version_history.md | 2 +- .../cloud_siem/ingest_and_enrich/_index.md | 2 +- .../ingest_and_enrich/content_packs.md | 2 +- .../entities_and_risk_scoring.md | 4 ++-- .../investigate_security_signals.md | 8 ++++---- .../triage_and_investigate/investigator.md | 8 ++++---- content/en/security/detection_rules/_index.md | 4 ++-- content/en/security/suppressions.md | 4 ++-- .../create-a-cloud-siem-detection-rule.md | 12 +++++------ .../es/getting_started/security/cloud_siem.md | 4 ++-- content/es/integrations/hcp_terraform.md | 2 +- content/es/integrations/meraki.md | 2 +- content/es/integrations/sentinelone.md | 4 ++-- content/es/integrations/snowflake_web.md | 12 +++++------ content/es/integrations/twilio.md | 2 +- content/es/integrations/wiz.md | 2 +- content/es/integrations/workday.md | 2 +- content/es/security/cloud_siem/_index.md | 4 ++-- .../cloud_siem/ingest_and_enrich/_index.md | 2 +- content/es/security/detection_rules/_index.md | 2 +- content/es/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 14 ++++++------- content/fr/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 6 +++--- content/ja/integrations/hcp_terraform.md | 14 ++++++------- content/ja/integrations/meraki.md | 2 +- content/ja/integrations/sentinelone.md | 2 +- content/ja/integrations/snowflake_web.md | 8 ++++---- content/ja/integrations/wiz.md | 2 +- content/ja/integrations/workday.md | 2 +- content/ja/integrations/zendesk.md | 2 +- content/ja/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 6 +++--- content/ko/integrations/meraki.md | 2 +- content/ko/integrations/snowflake_web.md | 20 +++++++++---------- content/ko/integrations/workday.md | 2 +- content/ko/integrations/zendesk.md | 2 +- content/ko/security/suppressions.md | 2 +- 46 files changed, 105 insertions(+), 105 deletions(-) diff --git a/content/en/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/en/developers/integrations/create-a-cloud-siem-detection-rule.md index 854e4b564dd..fa78e9e1222 100644 --- a/content/en/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/en/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -38,9 +38,9 @@ Within your integration in the Integration Developer Platform, navigate to the C ## Verify your detection rule in production -To see the out-of-the-box detection rule, the relevant integration tile must be `Installed` in Datadog, and Cloud SIEM must be enabled. +To see the out-of-the-box detection rule, the relevant integration tile must be `Installed` in Datadog, and Cloud SIEM must be enabled. -1. Find your detection rule in the [Detection Rules list][2], and click to expand it. +1. Find your detection rule in the [Detection Rules list][2], and click to expand it. 2. Ensure that its logos render correctly. 3. Verify that the rule is enabled. @@ -68,7 +68,7 @@ This error means that the JSON located at `` is considered invalid JS ``` partnerRuleId is empty for rule name="" - partnerRuleId= is available ``` -A `partnerRuleId` is required for each rule and is missing. Use the generated ``. +A `partnerRuleId` is required for each rule and is missing. Use the generated ``. ``` partnerRuleId= is in the incorrect format for rule name="", it must follow the format=^[a-z0-9]{3}-[a-z0-9]{3}-[a-z0-9]{3}$ - partnerRuleId= is available @@ -130,9 +130,9 @@ Reach out to Datadog to address the issue. {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/security/cloud_siem/detection_rules diff --git a/content/en/getting_started/security/cloud_siem.md b/content/en/getting_started/security/cloud_siem.md index 9c39249dc5a..50172e52d54 100644 --- a/content/en/getting_started/security/cloud_siem.md +++ b/content/en/getting_started/security/cloud_siem.md @@ -127,7 +127,7 @@ Contact [support][26] to disable Cloud SIEM. [6]: https://www.datadoghq.com/blog/monitoring-cloudtrail-logs/ [7]: https://www.datadoghq.com/blog/how-to-monitor-authentication-logs/ [8]: https://app.datadoghq.com/security/landing -[9]: https://app.datadoghq.com/security/content-packs +[9]: https://app.datadoghq.com/security/siem/content-packs [10]: https://app.datadoghq.com/security/configuration/siem/log-sources [11]: https://app.datadoghq.com/security/configuration/siem/setup [12]: /security/default_rules/#cat-cloud-siem-log-detection @@ -137,7 +137,7 @@ Contact [support][26] to disable Cloud SIEM. [16]: https://app.datadoghq.com/security/configuration/notification-rules [17]: /security/notifications/rules/ [18]: https://app.datadoghq.com/security/configuration/reports -[19]: https://app.datadoghq.com/security/investigator/ +[19]: https://app.datadoghq.com/security/siem/investigator/ [20]: /security/cloud_siem/triage_and_investigate/investigator [21]: https://app.datadoghq.com/dashboard/lists/preset/100 [22]: /dashboards/#overview diff --git a/content/en/security/cloud_siem/_index.md b/content/en/security/cloud_siem/_index.md index d59f86f4ebc..1203c382f04 100644 --- a/content/en/security/cloud_siem/_index.md +++ b/content/en/security/cloud_siem/_index.md @@ -71,7 +71,7 @@ Cloud SIEM embeds both cloud and on-premises telemetry directly into security wo ### Flexible cost control for security data -As your organization scales, controlling the ingestion cost of security logs without compromising visibility is critical. Cloud SIEM is integrated with Datadog Log Management so you can choose the appropriate retention and querying capability for your security logs. This flexibility helps you balance cost efficiency with your threat detection needs. +As your organization scales, controlling the ingestion cost of security logs without compromising visibility is critical. Cloud SIEM is integrated with Datadog Log Management so you can choose the appropriate retention and querying capability for your security logs. This flexibility helps you balance cost efficiency with your threat detection needs. Store logs using one of the available options: - [Standard indexing][6] for logs that need to be queried frequently with the most compute. @@ -263,7 +263,7 @@ See which rules are the noisiest by calculating the percentage of signals that a [1]: https://securitylabs.datadoghq.com/ [2]: https://www.datadoghq.com/product/cloud-siem/ -[3]: https://app.datadoghq.com/security/home? +[3]: https://app.datadoghq.com/security/siem/home? [4]: /getting_started/security/cloud_siem/ [5]: /security/cloud_siem/investigate_security_signals/#case-management [6]: /logs/log_configuration/indexes diff --git a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/_index.md b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/_index.md index 7518caf8540..551df95dbc0 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/_index.md +++ b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/_index.md @@ -87,7 +87,7 @@ Use unit testing to test your rules against sample logs and make sure the detect {{< partial name="whats-next/whats-next.html" >}} [1]: /security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/real_time_rule/ -[2]: https://app.datadoghq.com/security/rules +[2]: https://app.datadoghq.com/security/siem/rules [3]: /security/cloud_siem/detect_and_monitor/custom_detection_rules/threshold/ [4]: /security/cloud_siem/detect_and_monitor/custom_detection_rules/new_value/ [5]: /security/cloud_siem/detect_and_monitor/custom_detection_rules/anomaly/ diff --git a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/historical_job.md b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/historical_job.md index f01cc568b5f..d78fa24ad2a 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/historical_job.md +++ b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/historical_job.md @@ -238,5 +238,5 @@ Click **Add Root Query** to add additional queries. {{% security-rule-say-whats-happening %}} -[1]: https://app.datadoghq.com/security/rules/new +[1]: https://app.datadoghq.com/security/siem/rules/new [2]: /security_platform/notifications/#notification-channels \ No newline at end of file diff --git a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/real_time_rule.md b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/real_time_rule.md index 7c4171070b1..5df48210542 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/real_time_rule.md +++ b/content/en/security/cloud_siem/detect_and_monitor/custom_detection_rules/create_rule/real_time_rule.md @@ -343,4 +343,4 @@ In the **Preview detection** section, check the steps, transitions, and time win {{% cloud_siem/create_suppression %}} -[1]: https://app.datadoghq.com/security/rules/new \ No newline at end of file +[1]: https://app.datadoghq.com/security/siem/rules/new \ No newline at end of file diff --git a/content/en/security/cloud_siem/detect_and_monitor/historical_jobs.md b/content/en/security/cloud_siem/detect_and_monitor/historical_jobs.md index b819dc82018..8977c7726e4 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/historical_jobs.md +++ b/content/en/security/cloud_siem/detect_and_monitor/historical_jobs.md @@ -73,9 +73,9 @@ See [Calculated Fields Formulas][5] for the available functions and operators. {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/security/rules +[1]: https://app.datadoghq.com/security/siem/rules [2]: https://app.datadoghq.com/security/configuration/siem/rules/new-job?product=siem -[3]: https://app.datadoghq.com/security/detections/historical-jobs +[3]: https://app.datadoghq.com/security/siem/detections/historical-jobs [4]: /logs/explorer/calculated_fields/ [5]: /logs/explorer/calculated_fields/formulas/ [6]: https://app.datadoghq.com/security/configuration/siem/rules/new-job?product=siem#rule-editor-define-queries diff --git a/content/en/security/cloud_siem/detect_and_monitor/mitre_attack_map.md b/content/en/security/cloud_siem/detect_and_monitor/mitre_attack_map.md index 954c5282f56..84bcd090b3b 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/mitre_attack_map.md +++ b/content/en/security/cloud_siem/detect_and_monitor/mitre_attack_map.md @@ -62,7 +62,7 @@ This is an example of the format you need to use for tagging custom rules and th {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/security/rules +[1]: https://app.datadoghq.com/security/siem/rules [2]: https://docs.datadoghq.com/security/cloud_siem/guide/how-to-setup-security-filters-using-cloud-siem-api/ -[3]: https://app.datadoghq.com/security/rules?query=product=siem&sort=date&viz=attck-map +[3]: https://app.datadoghq.com/security/siem/rules?query=product=siem&sort=date&viz=attck-map [4]: https://docs.datadoghq.com/security/cloud_siem/detect_and_monitor/custom_detection_rules/?tab=threshold diff --git a/content/en/security/cloud_siem/detect_and_monitor/version_history.md b/content/en/security/cloud_siem/detect_and_monitor/version_history.md index 40b52d171fb..ce46840e762 100644 --- a/content/en/security/cloud_siem/detect_and_monitor/version_history.md +++ b/content/en/security/cloud_siem/detect_and_monitor/version_history.md @@ -34,4 +34,4 @@ To see the version history of a rule: {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/security/rules \ No newline at end of file +[1]: https://app.datadoghq.com/security/siem/rules \ No newline at end of file diff --git a/content/en/security/cloud_siem/ingest_and_enrich/_index.md b/content/en/security/cloud_siem/ingest_and_enrich/_index.md index 6c93f10b17e..f45492aa021 100644 --- a/content/en/security/cloud_siem/ingest_and_enrich/_index.md +++ b/content/en/security/cloud_siem/ingest_and_enrich/_index.md @@ -47,7 +47,7 @@ Datadog provides built-in [Threat Intelligence][5] for Cloud SIEM logs and also {{< partial name="whats-next/whats-next.html" >}} [1]: /security/cloud_siem/content_packs/ -[2]: https://app.datadoghq.com/security/content-packs +[2]: https://app.datadoghq.com/security/siem/content-packs [3]: /integrations/ [4]: /logs/log_collection/ [5]: /security/threat_intelligence/#threat-intelligence-sources diff --git a/content/en/security/cloud_siem/ingest_and_enrich/content_packs.md b/content/en/security/cloud_siem/ingest_and_enrich/content_packs.md index f8cc1150d66..c5a96217f25 100644 --- a/content/en/security/cloud_siem/ingest_and_enrich/content_packs.md +++ b/content/en/security/cloud_siem/ingest_and_enrich/content_packs.md @@ -49,7 +49,7 @@ further_reading: {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/security/content-packs +[1]: https://app.datadoghq.com/security/siem/content-packs [2]: /security/detection_rules/ [3]: /security/cloud_siem/triage_and_investigate/investigator [4]: /service_management/workflows/ \ No newline at end of file diff --git a/content/en/security/cloud_siem/triage_and_investigate/entities_and_risk_scoring.md b/content/en/security/cloud_siem/triage_and_investigate/entities_and_risk_scoring.md index 568f66be506..07f92d10298 100644 --- a/content/en/security/cloud_siem/triage_and_investigate/entities_and_risk_scoring.md +++ b/content/en/security/cloud_siem/triage_and_investigate/entities_and_risk_scoring.md @@ -51,7 +51,7 @@ The **Next steps** section of the entity side panel includes the available mitig ## Risk scoring -An entity's risk score approximates the entity's risk level over the past 14 days of activity. +An entity's risk score approximates the entity's risk level over the past 14 days of activity. The risk score is calculated from the characteristics of the entity's associated signals, such as the severity level of the signal and how many times the signal has fired. @@ -87,6 +87,6 @@ The severity threshold of an entity is calculated by adding up the score impact [1]: /security/cloud_siem/guide/aws-config-guide-for-cloud-siem/ [2]: https://docs.datadoghq.com/security/cloud_security_management/setup [3]: https://app.datadoghq.com/security -[4]: https://app.datadoghq.com/security/entities +[4]: https://app.datadoghq.com/security/siem/risk-insights [5]: /security/cloud_siem/guide/google-cloud-config-guide-for-cloud-siem/ [6]: /security/cloud_siem/guide/azure-config-guide-for-cloud-siem/ diff --git a/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md b/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md index 508016ad428..20062058504 100644 --- a/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md +++ b/content/en/security/cloud_siem/triage_and_investigate/investigate_security_signals.md @@ -61,12 +61,12 @@ To view your signals by MITRE ATT&CK Tactic and Technique: 1. Click on a security signal from the table. 1. In the **What Happened** section, see the logs that matched the query. Hover over the query to see the query details. - You can also see specific information like username or network IP. In **Rule Details**, click the funnel icon to create a suppression rule or add the information to an existing suppression. See [Create suppression rule][11] for more details. -1. In the **Next Steps** section: +1. In the **Next Steps** section: a. Under **Triage**, click the dropdown to change the triage status of the signal. The default status is `OPEN`. - `Open`: Datadog Security triggered a detection based on a rule, and the resulting signal is not yet resolved. - `Under Review`: During an active investigation, change the triage status to `Under Review`. From the `Under Review` state, you can move the status to `Archived` or `Open` as needed. - `Archived`: When the detection that caused the signal has been resolved, update the status to `Archived`. When a signal is archived, you can give a reason and description for future reference. If an archived issue resurfaces, or if further investigation is necessary, the status can be changed back to `Open`. All signals are locked 30 days after they have been created. - b. Click **Assign Signal** to assign a signal to yourself or another Datadog user. + b. Click **Assign Signal** to assign a signal to yourself or another Datadog user. c. Under **Take Action**, you can create a case, declare an incident, edit suppressions, or run workflows. Creating a case automatically assigns the signal to you and sets the triage status to `Under Review`. {{< img src="security/security_monitoring/investigate_security_signals/signal_side_panel.png" alt="The signal side panel of a compromised AWS IAM user access key showing two IP addresses and their locations" style="width:90%;" >}} @@ -130,7 +130,7 @@ Click the **Logs** tab to view the logs related to the signal. Click **View All To investigate entities: 1. Click the **Entities** tab to see entities related to the signal, such as users or IP addresses. -1. Click the down arrow next to **View Related Logs** and: +1. Click the down arrow next to **View Related Logs** and: - Select **View IP Dashboard** to see more information about the IP address in the IP Investigation dashboard. - Select **View Related Signals** to open Signals Explorer and see the other signals associated with the IP address. 1. For cloud environment entities, such as an assumed role or IAM user, view the activity graph to see what other actions the user took. Click **View in Investigator** to go to the Investigator to see more details. @@ -209,7 +209,7 @@ You can also launch this query directly from the signal panel: [2]: /account_management/audit_trail/events/#cloud-security-platform-events [3]: /account_management/rbac/ [4]: /logs/explorer/saved_views/ -[5]: https://app.datadoghq.com/security/home +[5]: https://app.datadoghq.com/security/siem/home [6]: /service_management/case_management/ [7]: /service_management/incident_management/ [8]: /service_management/workflows/trigger/#trigger-a-workflow-from-a-security-signal diff --git a/content/en/security/cloud_siem/triage_and_investigate/investigator.md b/content/en/security/cloud_siem/triage_and_investigate/investigator.md index bafff22f476..ab5dbac7425 100644 --- a/content/en/security/cloud_siem/triage_and_investigate/investigator.md +++ b/content/en/security/cloud_siem/triage_and_investigate/investigator.md @@ -46,7 +46,7 @@ The Cloud SIEM Investigator provides a graphical interface for you to pivot from 4. Click on a node and select **View related logs** or **View related signals** to investigate further. Use the **Search for** dropdown menu to filter by actions. -[1]: https://app.datadoghq.com/security/investigator/aws +[1]: https://app.datadoghq.com/security/siem/investigator?provider=aws {{% /tab %}} @@ -60,7 +60,7 @@ The Cloud SIEM Investigator provides a graphical interface for you to pivot from 4. Click on a node and select **View related logs** or **View related signals** to investigate further. Use the **Search for** dropdown menu to filter by actions. -[1]: https://app.datadoghq.com/security/investigator/gcp +[1]: https://app.datadoghq.com/security/siem/investigator?provider=gcp {{% /tab %}} {{% tab "Azure" %}} @@ -73,7 +73,7 @@ The Cloud SIEM Investigator provides a graphical interface for you to pivot from 4. Click on a node and select **View related logs** or **View related signals** to investigate further. Use the **Search for** dropdown menu to filter by actions. -[1]: https://app.datadoghq.com/security/investigator/azure +[1]: https://app.datadoghq.com/security/siem/investigator?provider=azure {{% /tab %}} {{% tab "Datadog" %}} @@ -86,7 +86,7 @@ The Cloud SIEM Investigator provides a graphical interface for you to pivot from 4. Click on a node and select **View related Audit Trail** or **View related signals** to investigate further. Use the **Search for** dropdown menu to filter by actions. -[1]: https://app.datadoghq.com/security/investigator/datadog +[1]: https://app.datadoghq.com/security/siem/investigator?provider=datadog {{% /tab %}} {{< /tabs >}} diff --git a/content/en/security/detection_rules/_index.md b/content/en/security/detection_rules/_index.md index 7e14a6a8634..d2ad484bfe6 100644 --- a/content/en/security/detection_rules/_index.md +++ b/content/en/security/detection_rules/_index.md @@ -176,7 +176,7 @@ The rule deprecation process is as follows: 1. There is a warning with the deprecation date on the rule. In the UI, the warning is shown in the: - Signal side panel's **Rule Details > Playbook** section - Misconfigurations side panel (Cloud Security Misconfigurations only) - - [Rule editor][10] for that specific rule + - [Rule editor][10] for that specific rule 2. Once the rule is deprecated, there is a 15 month period before the rule is deleted. This is due to the signal retention period of 15 months. During this time, you can re-enable the rule by [cloning the rule](#clone-a-rule) in the UI. 3. Once the rule is deleted, you can no longer clone and re-enable it. @@ -199,6 +199,6 @@ The rule deprecation process is as follows: [13]: /security/cloud_security_management/misconfigurations/custom_rules [14]: /security/workload_protection/workload_security_rules?tab=host#create-custom-rules [15]: https://app.datadoghq.com/security/configuration/ -[16]: https://app.datadoghq.com/security/rules +[16]: https://app.datadoghq.com/security/siem/rules [17]: https://app.datadoghq.com/security/workload-protection/detection-rules diff --git a/content/en/security/suppressions.md b/content/en/security/suppressions.md index 8e2fbd4fab3..14051a9ffcb 100644 --- a/content/en/security/suppressions.md +++ b/content/en/security/suppressions.md @@ -55,7 +55,7 @@ The [suppression list][3] provides a centralized and organized way for you to ma 1. Select the detection rules you want to apply this suppression to. You can select multiple detection rules. 1. In the **Add Suppression Query** section, you have the option to enter suppression queries so that a signal is not generated when the values are met. For example, if a user `john.doe` is triggering a signal, but their actions are benign and you no longer want signals triggered from this user, input the log query: `@user.username:john.doe`. {{< img src="security/security_monitoring/suppressions/suppression_query.png" alt="The add suppression query with the query @user.username:john.doe" style="width:65%;" >}} - Suppression rule queries are based on **signal attributes**. + Suppression rule queries are based on **signal attributes**. 1. Additionally, you can add a log exclusion query to exclude logs from being analyzed. These queries are based on **log attributes**. **Note**: The legacy suppression was based on log exclusion queries, but it is now included in the suppression rule's **Add a suppression query** step. ### Restrict edit permissions @@ -69,5 +69,5 @@ The [suppression list][3] provides a centralized and organized way for you to ma [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/rules +[4]: https://app.datadoghq.com/security/siem/rules [5]: /logs/explorer/facets/#log-side-panel diff --git a/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md index f7f3c212786..cd3c8131cf5 100644 --- a/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -41,9 +41,9 @@ Para crear una integración de Datadog, consulta la sección de [creación de un ## Verificar tu regla de detección en producción -Para ver la regla de detección lista para utilizar, el cuadro de integración relevante debe ser `Installed` en Datadog y Cloud SIEM debe estar habilitado. +Para ver la regla de detección lista para utilizar, el cuadro de integración relevante debe ser `Installed` en Datadog y Cloud SIEM debe estar habilitado. -1. Busca tu regla de detección en la [lista de reglas de detección][2] y expándela. +1. Busca tu regla de detección en la [lista de reglas de detección][2] y expándela. 2. Asegúrate de que tus logotipos se muestran correctamente. 3. Comprueba que la regla está habilitada. @@ -79,7 +79,7 @@ Este error significa que el JSON ubicado en `` se considera un JSON i ``` partnerRuleId is empty for rule name="" - partnerRuleId= is available ``` -Se requiere un `partnerRuleId` para cada regla y este no está presente. Utiliza el `` generado. +Se requiere un `partnerRuleId` para cada regla y este no está presente. Utiliza el `` generado. ``` partnerRuleId= is in the incorrect format for rule name="", it must follow the format=^[a-z0-9]{3}-[a-z0-9]{3}-[a-z0-9]{3}$ - partnerRuleId= is available @@ -141,9 +141,9 @@ Ponte en contacto con Datadog para abordar el problema. {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/es/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/es/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/es/security/cloud_siem/log_detection_rules \ No newline at end of file diff --git a/content/es/getting_started/security/cloud_siem.md b/content/es/getting_started/security/cloud_siem.md index c064d328214..ad7de88fd02 100644 --- a/content/es/getting_started/security/cloud_siem.md +++ b/content/es/getting_started/security/cloud_siem.md @@ -127,7 +127,7 @@ Después de mover el índice a la primera posición, revisa la configuración y [6]: https://www.datadoghq.com/blog/monitoring-cloudtrail-logs/ [7]: https://www.datadoghq.com/blog/how-to-monitor-authentication-logs/ [8]: https://app.datadoghq.com/security/landing -[9]: https://app.datadoghq.com/security/content-packs +[9]: https://app.datadoghq.com/security/siem/content-packs [10]: https://app.datadoghq.com/security/configuration/siem/log-sources [11]: https://app.datadoghq.com/security/configuration/siem/setup [12]: /es/security/default_rules/#cat-cloud-siem-log-detection @@ -137,7 +137,7 @@ Después de mover el índice a la primera posición, revisa la configuración y [16]: https://app.datadoghq.com/security/configuration/notification-rules [17]: /es/security/notifications/rules/ [18]: https://app.datadoghq.com/security/configuration/reports -[19]: https://app.datadoghq.com/security/investigator/ +[19]: https://app.datadoghq.com/security/siem/investigator/ [20]: /es/security/cloud_siem/investigator [21]: https://app.datadoghq.com/dashboard/lists/preset/100 [22]: /es/dashboards/#overview diff --git a/content/es/integrations/hcp_terraform.md b/content/es/integrations/hcp_terraform.md index 3811585102e..67d2fca1cd2 100644 --- a/content/es/integrations/hcp_terraform.md +++ b/content/es/integrations/hcp_terraform.md @@ -120,7 +120,7 @@ hcp-terraform no incluye eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][5]. -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.datadoghq.com/logs/pipelines?search=hcp-terraform [3]: https://app.datadoghq.com/dash/integration/31325/hcp-terraform-overview [4]: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-the-entitlement-set diff --git a/content/es/integrations/meraki.md b/content/es/integrations/meraki.md index e6fd1074a6a..4f8fd951eac 100644 --- a/content/es/integrations/meraki.md +++ b/content/es/integrations/meraki.md @@ -24,7 +24,7 @@ title: Cisco Meraki --- ## Información general -Esta integración proporciona una visibilidad completa de tu entorno de Cisco Meraki mediante la recopilación de métricas para [Network Device Monitoring](https://app.datadoghq.com/devices), logs de eventos de red y logs de eventos de seguridad para [Cloud SIEM](https://app.datadoghq.com/security/home). +Esta integración proporciona una visibilidad completa de tu entorno de Cisco Meraki mediante la recopilación de métricas para [Network Device Monitoring](https://app.datadoghq.com/devices), logs de eventos de red y logs de eventos de seguridad para [Cloud SIEM](https://app.datadoghq.com/security/siem/home). **Network Device Monitoring** diff --git a/content/es/integrations/sentinelone.md b/content/es/integrations/sentinelone.md index 15d6aee78fb..ad3485a9cb3 100644 --- a/content/es/integrations/sentinelone.md +++ b/content/es/integrations/sentinelone.md @@ -111,7 +111,7 @@ Los clientes de SentinelOne pueden recopilar alertas, amenazas y logs de activid Configura los siguientes parámetros: - - `DdApiKey`: Tu clave de API Datadog + - `DdApiKey`: Tu clave de API Datadog - `DdSite`: Tu [sitio Datadog][6] - `DdTags`: `source:sentinelone,service:sentinelone,endpoint:EDR_Telemetry` @@ -153,7 +153,7 @@ El SentinelOne integración no incluye ninguna eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][8]. -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://www.sentinelone.com/platform/singularity-cloud-funnel/ [3]: https://community.sentinelone.com/s/article/000006282 [4]: https://community.sentinelone.com/s/article/000006285 diff --git a/content/es/integrations/snowflake_web.md b/content/es/integrations/snowflake_web.md index fcc87e8107f..6bc1dd791fc 100644 --- a/content/es/integrations/snowflake_web.md +++ b/content/es/integrations/snowflake_web.md @@ -103,7 +103,7 @@ Se recomienda la integración del Snowflake original con el Agent para configura #### Conecta tu cuenta de Snowflake -1. Busca la [URL de tu cuenta de Snowflake][2]. +1. Busca la [URL de tu cuenta de Snowflake][2]. ![Menú de la cuenta con la opción de copiar URL de la cuenta seleccionada en la interfaz de Snowflake][3] @@ -141,7 +141,7 @@ La siguiente tabla describe los tipos de logs recopilados y qué tablas de Snowf Seguridad - Utiliza estos logs con Cloud SIEM para detectar y responder mejor a las amenazas de seguridad en tu entorno. + Utiliza estos logs con Cloud SIEM para detectar y responder mejor a las amenazas de seguridad en tu entorno. SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -284,7 +284,7 @@ Las [tablas de referencia][12] te permiten enriquecer y unir automáticamente tu 9. Ve a Tablas de referencia y busca la tabla que acabas de crear, utilizando el nombre de la tabla de Datadog. 10. Revisa el estado de tu tabla de Snowflake que se encuentra en la sección **Archivo**. Si aparece algún error, resuélvelo en Snowflake. -## Prácticas recomendadas para la ingesta de tablas de Snowflake en tablas de referencia de Datadog +## Prácticas recomendadas para la ingesta de tablas de Snowflake en tablas de referencia de Datadog Al integrar datos de Snowflake en Datadog, es importante estructurar las tablas de forma eficiente para optimizar el rendimiento y los costes. Esta sección te ofrece recomendaciones sobre cómo preparar tus tablas de Snowflake para la ingesta. @@ -492,7 +492,7 @@ El check de Snowflake está incluido en el paquete del [Datadog Agent][24]. # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
@@ -670,8 +670,8 @@ Snowflake no incluye ningún evento. ### Agent: checks de servicio -**snowflake.can_connect** -Devuelve `CRITICAL` si el check no puede autenticar las credenciales de Snowflake. En caso contrario, devuelve `OK`. +**snowflake.can_connect** +Devuelve `CRITICAL` si el check no puede autenticar las credenciales de Snowflake. En caso contrario, devuelve `OK`. _Estados: ok, crítico_ ## Agent: solucionar problemas diff --git a/content/es/integrations/twilio.md b/content/es/integrations/twilio.md index 024d188b230..d9d0dcf50cb 100644 --- a/content/es/integrations/twilio.md +++ b/content/es/integrations/twilio.md @@ -128,7 +128,7 @@ La integración de Twilio ingiere [recursos de eventos][1]. [2]: https://www.twilio.com/docs/messaging/api/message-resource [3]: https://www.twilio.com/docs/voice/voice-insights/api/call/call-summary-resource [4]: https://www.twilio.com/docs/voice/voice-insights/advanced-features -[5]: https://app.datadoghq.com/security/home +[5]: https://app.datadoghq.com/security/siem/home [6]: https://www.twilio.com/docs/iam/api-keys#create-an-api-key [7]: https://app.datadoghq.com/integrations/twilio [8]: https://app.datadoghq.com/cost diff --git a/content/es/integrations/wiz.md b/content/es/integrations/wiz.md index a43b9c482cc..405ceaa455c 100644 --- a/content/es/integrations/wiz.md +++ b/content/es/integrations/wiz.md @@ -172,7 +172,7 @@ La integración Wiz recopila logs y problemas de auditoría. ¿Necesitas ayuda? Ponte en contacto con el [soporte de Datadog][5] o el [soporte de Wiz][6]. -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.wiz.io/login [3]: https://docs.wiz.io/wiz-docs/docs/webhook-format [4]: https://docs.wiz.io/wiz-docs/docs/issues-overview diff --git a/content/es/integrations/workday.md b/content/es/integrations/workday.md index 6ba644e0254..47781df2bdb 100644 --- a/content/es/integrations/workday.md +++ b/content/es/integrations/workday.md @@ -143,7 +143,7 @@ La integración Workday no incluye eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][5]. -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/es/security/cloud_siem/_index.md b/content/es/security/cloud_siem/_index.md index 1413250b4d1..0a6d3aebf81 100644 --- a/content/es/security/cloud_siem/_index.md +++ b/content/es/security/cloud_siem/_index.md @@ -72,7 +72,7 @@ Cloud SIEM integra la telemetría en la nube y on-premises directamente en los f ### Control flexible de los costes de los datos de seguridad -A medida que tu organización crece, es fundamental controlar el coste de ingesta de los logs de seguridad sin comprometer la visibilidad. Cloud SIEM está integrado con Datadog Log Management para que puedas elegir la capacidad de retención y consulta adecuada para tus logs de seguridad. Esta flexibilidad te ayuda a equilibrar la rentabilidad con tus necesidades de detección de amenazas. +A medida que tu organización crece, es fundamental controlar el coste de ingesta de los logs de seguridad sin comprometer la visibilidad. Cloud SIEM está integrado con Datadog Log Management para que puedas elegir la capacidad de retención y consulta adecuada para tus logs de seguridad. Esta flexibilidad te ayuda a equilibrar la rentabilidad con tus necesidades de detección de amenazas. Almacena logs utilizando una de las opciones disponibles: - [Indexación estándar][6] para logs que deben consultarse frecuentemente con el mayor número de cálculos. @@ -264,7 +264,7 @@ Ve qué reglas son las más ruidosas calculando el porcentaje de señales que se [1]: https://securitylabs.datadoghq.com/ [2]: https://www.datadoghq.com/product/cloud-siem/ -[3]: https://app.datadoghq.com/security/home? +[3]: https://app.datadoghq.com/security/siem/home? [4]: /es/getting_started/security/cloud_siem/ [5]: /es/security/cloud_siem/investigate_security_signals/#case-management [6]: /es/logs/log_configuration/indexes diff --git a/content/es/security/cloud_siem/ingest_and_enrich/_index.md b/content/es/security/cloud_siem/ingest_and_enrich/_index.md index 803a4e3f41f..44d8eb6c563 100644 --- a/content/es/security/cloud_siem/ingest_and_enrich/_index.md +++ b/content/es/security/cloud_siem/ingest_and_enrich/_index.md @@ -47,7 +47,7 @@ Datadog proporciona [Inteligencia de amenazas][5] integrada para los logs de Clo {{< partial name="whats-next/whats-next.html" >}} [1]: /es/security/cloud_siem/content_packs/ -[2]: https://app.datadoghq.com/security/content-packs +[2]: https://app.datadoghq.com/security/siem/content-packs [3]: /es/integrations/ [4]: /es/logs/log_collection/ [5]: /es/security/threat_intelligence/#threat-intelligence-sources diff --git a/content/es/security/detection_rules/_index.md b/content/es/security/detection_rules/_index.md index 8dce40f46d3..84589eca6dc 100644 --- a/content/es/security/detection_rules/_index.md +++ b/content/es/security/detection_rules/_index.md @@ -200,5 +200,5 @@ El proceso de obsolescencia de las reglas es el siguiente: [13]: /es/security/cloud_security_management/misconfigurations/custom_rules [14]: /es/security/workload_protection/workload_security_rules?tab=host#create-custom-rules [15]: https://app.datadoghq.com/security/configuration/ -[16]: https://app.datadoghq.com/security/rules +[16]: https://app.datadoghq.com/security/siem/rules [17]: https://app.datadoghq.com/security/workload-protection/detection-rules \ No newline at end of file diff --git a/content/es/security/suppressions.md b/content/es/security/suppressions.md index ec8dd96d055..c6162a72a28 100644 --- a/content/es/security/suppressions.md +++ b/content/es/security/suppressions.md @@ -65,5 +65,5 @@ La [lista de supresiones][3] proporciona una forma centralizada y organizada de [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /es/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/rules +[4]: https://app.datadoghq.com/security/siem/rules [5]: /es/logs/explorer/facets/#log-side-panel diff --git a/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md index 3c024677ad6..b4ef4e9779a 100644 --- a/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -26,7 +26,7 @@ Pour améliorer la visibilité des utilisateurs sur la sécurité, les partenair Dans votre sandbox Datadog, [créez une nouvelle règle][4]. -{{< img src="developers/integrations/detection_rule.png" alt="La page Créer une nouvelle règle dans l'espace Règles de détection de Datadog" style="width:100%;" >}}  +{{< img src="developers/integrations/detection_rule.png" alt="La page Créer une nouvelle règle dans l'espace Règles de détection de Datadog" style="width:100%;" >}} Suivez les [bonnes pratiques](#bonnes-pratiques-de-configuration) décrites dans ce guide pour configurer votre règle. @@ -34,14 +34,14 @@ Suivez les [bonnes pratiques](#bonnes-pratiques-de-configuration) décrites dans Dans votre intégration, sur la plateforme de développement d'intégrations, accédez à l'onglet Content. Sélectionnez ensuite **Import Detection Rule** pour choisir parmi les règles disponibles. Vous pouvez en inclure jusqu'à 10 avec votre intégration. -{{< img src="developers/integrations/content_tab.png" alt="L'onglet Content dans la plateforme de développement" style="width:100%;" >}}  +{{< img src="developers/integrations/content_tab.png" alt="L'onglet Content dans la plateforme de développement" style="width:100%;" >}} ## Vérifier votre règle de détection en production -Pour voir la règle de détection prête à l'emploi, le carré d'intégration concerné doit être `Installed` dans Datadog, et Cloud SIEM doit être activé.  +Pour voir la règle de détection prête à l'emploi, le carré d'intégration concerné doit être `Installed` dans Datadog, et Cloud SIEM doit être activé. -1. Recherchez votre règle dans la [liste des règles de détection][2], puis cliquez pour l'afficher.  +1. Recherchez votre règle dans la [liste des règles de détection][2], puis cliquez pour l'afficher. 2. Assurez-vous que les logos s'affichent correctement. 3. Vérifiez que la règle est bien activée. @@ -131,9 +131,9 @@ Contactez Datadog pour résoudre ce problème. {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/fr/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/fr/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/fr/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/fr/security/suppressions.md b/content/fr/security/suppressions.md index 6698fc513d3..2c9b6b2aa44 100644 --- a/content/fr/security/suppressions.md +++ b/content/fr/security/suppressions.md @@ -65,5 +65,5 @@ La [liste des suppressions][3] permet de gérer les suppressions de façon centr [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /fr/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/rules +[4]: https://app.datadoghq.com/security/siem/rules [5]: /fr/logs/explorer/facets/#log-side-panel diff --git a/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md index 523b08631f8..561a82e63bf 100644 --- a/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -130,9 +130,9 @@ Internal failure for = name=""- Contact Datadog {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/ja/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/ja/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/ja/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/ja/integrations/hcp_terraform.md b/content/ja/integrations/hcp_terraform.md index fd346825305..f2fa6b02455 100644 --- a/content/ja/integrations/hcp_terraform.md +++ b/content/ja/integrations/hcp_terraform.md @@ -81,15 +81,15 @@ HCP Terraform のログを確認するには、Datadog ログで `source:hcp-ter ### インストール **ステップ 1: HCP Terraform 用の組織トークンを作成する** -1. [HashiCorp アカウント](https://app.terraform.io/)にログインし、該当する組織を選択して **Settings** をクリックします。 -2. **Security** の下にある **API tokens** をクリックします。 -3. **Create an organization token** をクリックします。 -4. 必要に応じて有効期限を設定します。 -5. **Generate token** をクリックします。 +1. [HashiCorp アカウント](https://app.terraform.io/)にログインし、該当する組織を選択して **Settings** をクリックします。 +2. **Security** の下にある **API tokens** をクリックします。 +3. **Create an organization token** をクリックします。 +4. 必要に応じて有効期限を設定します。 +5. **Generate token** をクリックします。 6. 作成された組織トークンをコピーし、保存しておきます。 **ステップ 2: Datadog インテグレーションを作成する** -1. 下記の **Organization Token** フィールドに上記で作成したトークンを貼り付けます。 +1. 下記の **Organization Token** フィールドに上記で作成したトークンを貼り付けます。 2. アカウント名を入力します。 ### 構成 @@ -118,7 +118,7 @@ hcp-terraform にはイベントは含まれていません。 ご不明な点は、[Datadog のサポートチーム][5]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.datadoghq.com/logs/pipelines?search=hcp-terraform [3]: https://app.datadoghq.com/dash/integration/31325/hcp-terraform-overview [4]: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-the-entitlement-set diff --git a/content/ja/integrations/meraki.md b/content/ja/integrations/meraki.md index 18f0b463761..33f2129f13c 100644 --- a/content/ja/integrations/meraki.md +++ b/content/ja/integrations/meraki.md @@ -171,7 +171,7 @@ Datadog は、サーバーから Meraki にアクセスする際に問題が発 - [Datadog で Cisco Meraki を監視する][13] [1]: https://app.datadoghq.com/devices -[2]: https://app.datadoghq.com/security/home +[2]: https://app.datadoghq.com/security/siem/home [3]: https://developer.cisco.com/meraki/api/get-network-appliance-security-events/ [4]: https://app.datadoghq.com/logs/pipelines?search=meraki [5]: https://developer.cisco.com/meraki/api/get-network-events/ diff --git a/content/ja/integrations/sentinelone.md b/content/ja/integrations/sentinelone.md index a8c38bcd2e6..947a234b483 100644 --- a/content/ja/integrations/sentinelone.md +++ b/content/ja/integrations/sentinelone.md @@ -151,7 +151,7 @@ SentinelOne インテグレーションにはイベントは含まれていま ご不明な点は、[Datadog のサポートチーム][8]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://www.sentinelone.com/platform/singularity-cloud-funnel/ [3]: https://community.sentinelone.com/s/article/000006282 [4]: https://community.sentinelone.com/s/article/000006285 diff --git a/content/ja/integrations/snowflake_web.md b/content/ja/integrations/snowflake_web.md index 55b8ea93db7..038fc436103 100644 --- a/content/ja/integrations/snowflake_web.md +++ b/content/ja/integrations/snowflake_web.md @@ -111,8 +111,8 @@ Snowflake データをパースした後、Datadog は[すぐに使える概要 以下の表では、収集されるメトリクスの種類と関連するメトリクスのプレフィックスについて説明します。 -| **型** | **説明** | **収集されるメトリクスのプレフィックス** | -|------|-------------|-----------------------------| +| **型** | **説明** | **収集されるメトリクスのプレフィックス** | +|------|-------------|-----------------------------| | **アカウント使用量** | アカウントレベルでのストレージ使用量、クレジット消費量、およびクエリメトリクス。
_毎時収集_。 | `snowflake.auto_recluster`
`snowflake.billing`
`snowflake.data_transfer`
`snowflake.logins`
`snowflake.pipe`
`snowflake.query`
`snowflake.replication`
`snowflake.storage`
`snowflake.storage.database`
`snowflake.storage.table` | | **組織使用量** | 組織レベルでのクレジット消費量、データ転送履歴、予算メトリクス
_毎日収集_。 | `snowflake.organization` | @@ -133,7 +133,7 @@ Snowflake データをパースした後、Datadog は[すぐに使える概要 セキュリティ -これらのログを Cloud SIEM と組み合わせて使用し、環境内のセキュリティ脅威をより適切に検出し対応します。 +これらのログを Cloud SIEM と組み合わせて使用し、環境内のセキュリティ脅威をより適切に検出し対応します。 SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -366,7 +366,7 @@ grant role DATADOG to user ; # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
diff --git a/content/ja/integrations/wiz.md b/content/ja/integrations/wiz.md index 74f8a7eaf8c..c4b589e7e36 100644 --- a/content/ja/integrations/wiz.md +++ b/content/ja/integrations/wiz.md @@ -170,7 +170,7 @@ Wiz インテグレーションは監査ログと課題を収集します。 お困りの際は、[Datadog サポート][5] または [Wiz サポート][6] までご連絡ください。 -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.wiz.io/login [3]: https://docs.wiz.io/wiz-docs/docs/webhook-format [4]: https://docs.wiz.io/wiz-docs/docs/issues-overview diff --git a/content/ja/integrations/workday.md b/content/ja/integrations/workday.md index a1bfa740aab..61a9d58ddf6 100644 --- a/content/ja/integrations/workday.md +++ b/content/ja/integrations/workday.md @@ -141,7 +141,7 @@ Workday インテグレーションには、イベントは含まれません。 ご不明な点は、[Datadog のサポートチーム][5]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/ja/integrations/zendesk.md b/content/ja/integrations/zendesk.md index c3b218febdf..71d21454f73 100644 --- a/content/ja/integrations/zendesk.md +++ b/content/ja/integrations/zendesk.md @@ -143,7 +143,7 @@ Zendesk チケットを作成してグループに割り当てることができ ご不明な点は、[Datadog のサポートチーム][13]までお問合せください。 [1]: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/ -[2]: https://app.datadoghq.com/security/home +[2]: https://app.datadoghq.com/security/siem/home [3]: https://app.datadoghq.com [4]: https://app.datadoghq.com/account/settings#integrations/zendesk [5]: https://docs.datadoghq.com/ja/real_user_monitoring/ diff --git a/content/ja/security/suppressions.md b/content/ja/security/suppressions.md index b98030b5bc1..c6bf0b00536 100644 --- a/content/ja/security/suppressions.md +++ b/content/ja/security/suppressions.md @@ -69,5 +69,5 @@ title: 抑制 [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /ja/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/rules +[4]: https://app.datadoghq.com/security/siem/rules [5]: /ja/logs/explorer/facets/#log-side-panel \ No newline at end of file diff --git a/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md index 5978c1623a8..bd1b9cd4f4f 100644 --- a/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -130,9 +130,9 @@ Internal failure for = name=""- Contact Datadog {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/ko/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/ko/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/ko/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/ko/integrations/meraki.md b/content/ko/integrations/meraki.md index 78dea6e5b84..98df8283482 100644 --- a/content/ko/integrations/meraki.md +++ b/content/ko/integrations/meraki.md @@ -183,7 +183,7 @@ Datadog 서버에서 Meraki에 액세스하는 데 문제가 발생하는 경우 - [Datadog으로 Cisco Meraki 모니터링][13] [1]: https://app.datadoghq.com/devices -[2]: https://app.datadoghq.com/security/home +[2]: https://app.datadoghq.com/security/siem/home [3]: https://developer.cisco.com/meraki/api/get-network-appliance-security-events/ [4]: https://app.datadoghq.com/logs/pipelines?search=meraki [5]: https://developer.cisco.com/meraki/api/get-network-events/ diff --git a/content/ko/integrations/snowflake_web.md b/content/ko/integrations/snowflake_web.md index 50fb9a2bdc7..4836066b4c7 100644 --- a/content/ko/integrations/snowflake_web.md +++ b/content/ko/integrations/snowflake_web.md @@ -99,7 +99,7 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 #### Snowflake 계정과 연결 -1. [Snowflake 계정 URL][2]을 찾습니다. +1. [Snowflake 계정 URL][2]을 찾습니다. ![Snowflake UI에서 계정 URL 복사 옵션이 선택된 계정 메뉴][3] @@ -111,8 +111,8 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 하단 표는 수집되는 메트릭 유형과 관련 메트릭 접두어에 대해 설명합니다. -| **유형** | **설명** | **수집된 메트릭 접두어** | -|------|-------------|-----------------------------| +| **유형** | **설명** | **수집된 메트릭 접두어** | +|------|-------------|-----------------------------| | **계정 사용량** | 계정 수준에서 사용량, 크레딧 사용량, 쿼리 메트릭을 보관합니다.
_매 시간 수집됩니다_. | `snowflake.auto_recluster`
`snowflake.billing`
`snowflake.data_transfer`
`snowflake.logins`
`snowflake.pipe`
`snowflake.query`
`snowflake.replication`
`snowflake.storage`
`snowflake.storage.database`
`snowflake.storage.table` | | **조직 사용량** | 조직 수준에서 크레딧 사용량, 데이터 전송 기록 및 예산 메트릭을 보관합니다.
_매 시간 수집됩니다_. | `snowflake.organization` | @@ -133,7 +133,7 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 보안 - Cloud SIEM과 함께 이러한 로그를 활용하여 사용자 환경에서 보안 위협을 보다 효율적으로 탐지하고 이에 대응할 수 있습니다. + Cloud SIEM과 함께 이러한 로그를 활용하여 사용자 환경에서 보안 위협을 보다 효율적으로 탐지하고 이에 대응할 수 있습니다. SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -208,7 +208,7 @@ Datadog이 Snowflake 계정에서 데이터를 수집하려면 특정 IP 주소 #### 커스텀 메트릭 -Snowflake 통합은 커스텀 쿼리 를 지원하며 커스텀 메트릭를 수집합니다. 사용자는 커스텀 SQL 쿼리를 작성하여 특정 데이터를 추출하고 Datadog에서 메트릭 및 메트릭 태그로 확인할 수 있습니다. +Snowflake 통합은 커스텀 쿼리 를 지원하며 커스텀 메트릭를 수집합니다. 사용자는 커스텀 SQL 쿼리를 작성하여 특정 데이터를 추출하고 Datadog에서 메트릭 및 메트릭 태그로 확인할 수 있습니다. 기본적으로 통합은 공유 `SNOWFLAKE` 데이터베이스 및 `ACCOUNT_USAGE` 스키마에 연결됩니다. `ACCOUNT_USAGE` 스키마 외부의 테이블을 쿼리하는 경우에는 설정된 역할에 해당 테이블에 액세스할 수 있는 적절한 권한이 있는지 확인하세요. @@ -260,7 +260,7 @@ Snowflake 웹 통합에는 서비스 점검이 포함되어 있지 않습니다. ## 에이전트: 개요 -이 점검은 Datadog Agent를 통해 [Snowflake][15]를 모니터링합니다. Snowflake는 SaaS 분석 데이터 웨어하우스이며 클라우드 인프라스트럭처에서 완전히 실행됩니다. +이 점검은 Datadog Agent를 통해 [Snowflake][15]를 모니터링합니다. Snowflake는 SaaS 분석 데이터 웨어하우스이며 클라우드 인프라스트럭처에서 완전히 실행됩니다. 이 통합은 크레딧 사용량, 빌링, 저장 공간, 쿼리 메트릭 등을 모니터링합니다.
참고: 메트릭은 Snowflake에 대한 쿼리를 통해 수집됩니다. Datadog 통합으로 생성된 쿼리는 Snowflake에서 청구 가능합니다..
@@ -364,7 +364,7 @@ Snowflake 점검은 [Datadog Agent][16] 패키지에 포함되어 있습니다. # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
@@ -443,7 +443,7 @@ Snowflake에서는 [프록시 구성을 위한 환경 변수][21] 설정을 권 또한 [snowflake.d/conf.yaml][19]의 `init_config`에서 `proxy_host`, `proxy_port`, `proxy_user`,`proxy_password`를 설정할 수 있습니다. -**참고**: Snowflake는 자동으로 프록시 구성 형식을 지정하고 [표준 프록시 환경 변수][22]를 설정합니다. +**참고**: Snowflake는 자동으로 프록시 구성 형식을 지정하고 [표준 프록시 환경 변수][22]를 설정합니다. 이러한 변수는 Docker, ECS, Kubernetes와 같은 오케스트레이터를 포함한 통합의 모든 요청에도 영향을 미칩니다. #### Snowflake 구성에 대한 프라이빗 연결 @@ -537,8 +537,8 @@ Snowflake는 이벤트를 포함하지 않습니다. ### 에이전트: 서비스 점검 -**snowflake.can_connect** -점검에서 Snowflake 자격 증명을 인증할 수 없는 경우 `CRITICAL`을 반환합니다. 그렇지 않으면 `OK`를 반환합니다. +**snowflake.can_connect** +점검에서 Snowflake 자격 증명을 인증할 수 없는 경우 `CRITICAL`을 반환합니다. 그렇지 않으면 `OK`를 반환합니다. *Statuses: ok, critical* ## 에이전트: 트러블슈팅 diff --git a/content/ko/integrations/workday.md b/content/ko/integrations/workday.md index dd07764f4a3..05796e5ee51 100644 --- a/content/ko/integrations/workday.md +++ b/content/ko/integrations/workday.md @@ -141,7 +141,7 @@ Workday 통합은 이벤트를 포함하지 않습니다. 도움이 필요하신가요? [Datadog 지원팀][5]에 문의하세요. -[1]: https://app.datadoghq.com/security/home +[1]: https://app.datadoghq.com/security/siem/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/ko/integrations/zendesk.md b/content/ko/integrations/zendesk.md index aa157d75c3f..8fc01d96874 100644 --- a/content/ko/integrations/zendesk.md +++ b/content/ko/integrations/zendesk.md @@ -143,7 +143,7 @@ Zendesk 티켓을 생성하여 그룹에 할당할 수 있습니다. 먼저 Data 도움이 필요하세요? [Datadog 지원팀][13]에 문의하세요. [1]: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/ -[2]: https://app.datadoghq.com/security/home +[2]: https://app.datadoghq.com/security/siem/home [3]: https://app.datadoghq.com [4]: https://app.datadoghq.com/account/settings#integrations/zendesk [5]: https://docs.datadoghq.com/ko/real_user_monitoring/ diff --git a/content/ko/security/suppressions.md b/content/ko/security/suppressions.md index 3df21d10e78..2ad37daf909 100644 --- a/content/ko/security/suppressions.md +++ b/content/ko/security/suppressions.md @@ -65,5 +65,5 @@ title: 억제 [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /ko/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/rules +[4]: https://app.datadoghq.com/security/siem/rules [5]: /ko/logs/explorer/facets/#log-side-panel From ce51a7e3ade10b9a96d4e834adf1f97464fd4029 Mon Sep 17 00:00:00 2001 From: Alexandre Florez De La Colina Date: Thu, 11 Dec 2025 17:05:25 +0100 Subject: [PATCH 2/2] Revert changes on non english documentation --- .../create-a-cloud-siem-detection-rule.md | 12 +++++------ .../es/getting_started/security/cloud_siem.md | 4 ++-- content/es/integrations/hcp_terraform.md | 2 +- content/es/integrations/meraki.md | 2 +- content/es/integrations/sentinelone.md | 4 ++-- content/es/integrations/snowflake_web.md | 12 +++++------ content/es/integrations/twilio.md | 2 +- content/es/integrations/wiz.md | 2 +- content/es/integrations/workday.md | 2 +- content/es/security/cloud_siem/_index.md | 4 ++-- .../cloud_siem/ingest_and_enrich/_index.md | 2 +- content/es/security/detection_rules/_index.md | 2 +- content/es/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 14 ++++++------- content/fr/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 6 +++--- content/ja/integrations/hcp_terraform.md | 14 ++++++------- content/ja/integrations/meraki.md | 2 +- content/ja/integrations/sentinelone.md | 2 +- content/ja/integrations/snowflake_web.md | 8 ++++---- content/ja/integrations/wiz.md | 2 +- content/ja/integrations/workday.md | 2 +- content/ja/integrations/zendesk.md | 2 +- content/ja/security/suppressions.md | 2 +- .../create-a-cloud-siem-detection-rule.md | 6 +++--- content/ko/integrations/meraki.md | 2 +- content/ko/integrations/snowflake_web.md | 20 +++++++++---------- content/ko/integrations/workday.md | 2 +- content/ko/integrations/zendesk.md | 2 +- content/ko/security/suppressions.md | 2 +- 30 files changed, 71 insertions(+), 71 deletions(-) diff --git a/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md index cd3c8131cf5..f7f3c212786 100644 --- a/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/es/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -41,9 +41,9 @@ Para crear una integración de Datadog, consulta la sección de [creación de un ## Verificar tu regla de detección en producción -Para ver la regla de detección lista para utilizar, el cuadro de integración relevante debe ser `Installed` en Datadog y Cloud SIEM debe estar habilitado. +Para ver la regla de detección lista para utilizar, el cuadro de integración relevante debe ser `Installed` en Datadog y Cloud SIEM debe estar habilitado. -1. Busca tu regla de detección en la [lista de reglas de detección][2] y expándela. +1. Busca tu regla de detección en la [lista de reglas de detección][2] y expándela. 2. Asegúrate de que tus logotipos se muestran correctamente. 3. Comprueba que la regla está habilitada. @@ -79,7 +79,7 @@ Este error significa que el JSON ubicado en `` se considera un JSON i ``` partnerRuleId is empty for rule name="" - partnerRuleId= is available ``` -Se requiere un `partnerRuleId` para cada regla y este no está presente. Utiliza el `` generado. +Se requiere un `partnerRuleId` para cada regla y este no está presente. Utiliza el `` generado. ``` partnerRuleId= is in the incorrect format for rule name="", it must follow the format=^[a-z0-9]{3}-[a-z0-9]{3}-[a-z0-9]{3}$ - partnerRuleId= is available @@ -141,9 +141,9 @@ Ponte en contacto con Datadog para abordar el problema. {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/es/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/es/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/es/security/cloud_siem/log_detection_rules \ No newline at end of file diff --git a/content/es/getting_started/security/cloud_siem.md b/content/es/getting_started/security/cloud_siem.md index ad7de88fd02..c064d328214 100644 --- a/content/es/getting_started/security/cloud_siem.md +++ b/content/es/getting_started/security/cloud_siem.md @@ -127,7 +127,7 @@ Después de mover el índice a la primera posición, revisa la configuración y [6]: https://www.datadoghq.com/blog/monitoring-cloudtrail-logs/ [7]: https://www.datadoghq.com/blog/how-to-monitor-authentication-logs/ [8]: https://app.datadoghq.com/security/landing -[9]: https://app.datadoghq.com/security/siem/content-packs +[9]: https://app.datadoghq.com/security/content-packs [10]: https://app.datadoghq.com/security/configuration/siem/log-sources [11]: https://app.datadoghq.com/security/configuration/siem/setup [12]: /es/security/default_rules/#cat-cloud-siem-log-detection @@ -137,7 +137,7 @@ Después de mover el índice a la primera posición, revisa la configuración y [16]: https://app.datadoghq.com/security/configuration/notification-rules [17]: /es/security/notifications/rules/ [18]: https://app.datadoghq.com/security/configuration/reports -[19]: https://app.datadoghq.com/security/siem/investigator/ +[19]: https://app.datadoghq.com/security/investigator/ [20]: /es/security/cloud_siem/investigator [21]: https://app.datadoghq.com/dashboard/lists/preset/100 [22]: /es/dashboards/#overview diff --git a/content/es/integrations/hcp_terraform.md b/content/es/integrations/hcp_terraform.md index 67d2fca1cd2..3811585102e 100644 --- a/content/es/integrations/hcp_terraform.md +++ b/content/es/integrations/hcp_terraform.md @@ -120,7 +120,7 @@ hcp-terraform no incluye eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][5]. -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.datadoghq.com/logs/pipelines?search=hcp-terraform [3]: https://app.datadoghq.com/dash/integration/31325/hcp-terraform-overview [4]: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-the-entitlement-set diff --git a/content/es/integrations/meraki.md b/content/es/integrations/meraki.md index 4f8fd951eac..e6fd1074a6a 100644 --- a/content/es/integrations/meraki.md +++ b/content/es/integrations/meraki.md @@ -24,7 +24,7 @@ title: Cisco Meraki --- ## Información general -Esta integración proporciona una visibilidad completa de tu entorno de Cisco Meraki mediante la recopilación de métricas para [Network Device Monitoring](https://app.datadoghq.com/devices), logs de eventos de red y logs de eventos de seguridad para [Cloud SIEM](https://app.datadoghq.com/security/siem/home). +Esta integración proporciona una visibilidad completa de tu entorno de Cisco Meraki mediante la recopilación de métricas para [Network Device Monitoring](https://app.datadoghq.com/devices), logs de eventos de red y logs de eventos de seguridad para [Cloud SIEM](https://app.datadoghq.com/security/home). **Network Device Monitoring** diff --git a/content/es/integrations/sentinelone.md b/content/es/integrations/sentinelone.md index ad3485a9cb3..15d6aee78fb 100644 --- a/content/es/integrations/sentinelone.md +++ b/content/es/integrations/sentinelone.md @@ -111,7 +111,7 @@ Los clientes de SentinelOne pueden recopilar alertas, amenazas y logs de activid Configura los siguientes parámetros: - - `DdApiKey`: Tu clave de API Datadog + - `DdApiKey`: Tu clave de API Datadog - `DdSite`: Tu [sitio Datadog][6] - `DdTags`: `source:sentinelone,service:sentinelone,endpoint:EDR_Telemetry` @@ -153,7 +153,7 @@ El SentinelOne integración no incluye ninguna eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][8]. -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://www.sentinelone.com/platform/singularity-cloud-funnel/ [3]: https://community.sentinelone.com/s/article/000006282 [4]: https://community.sentinelone.com/s/article/000006285 diff --git a/content/es/integrations/snowflake_web.md b/content/es/integrations/snowflake_web.md index 6bc1dd791fc..fcc87e8107f 100644 --- a/content/es/integrations/snowflake_web.md +++ b/content/es/integrations/snowflake_web.md @@ -103,7 +103,7 @@ Se recomienda la integración del Snowflake original con el Agent para configura #### Conecta tu cuenta de Snowflake -1. Busca la [URL de tu cuenta de Snowflake][2]. +1. Busca la [URL de tu cuenta de Snowflake][2]. ![Menú de la cuenta con la opción de copiar URL de la cuenta seleccionada en la interfaz de Snowflake][3] @@ -141,7 +141,7 @@ La siguiente tabla describe los tipos de logs recopilados y qué tablas de Snowf Seguridad - Utiliza estos logs con Cloud SIEM para detectar y responder mejor a las amenazas de seguridad en tu entorno. + Utiliza estos logs con Cloud SIEM para detectar y responder mejor a las amenazas de seguridad en tu entorno. SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -284,7 +284,7 @@ Las [tablas de referencia][12] te permiten enriquecer y unir automáticamente tu 9. Ve a Tablas de referencia y busca la tabla que acabas de crear, utilizando el nombre de la tabla de Datadog. 10. Revisa el estado de tu tabla de Snowflake que se encuentra en la sección **Archivo**. Si aparece algún error, resuélvelo en Snowflake. -## Prácticas recomendadas para la ingesta de tablas de Snowflake en tablas de referencia de Datadog +## Prácticas recomendadas para la ingesta de tablas de Snowflake en tablas de referencia de Datadog Al integrar datos de Snowflake en Datadog, es importante estructurar las tablas de forma eficiente para optimizar el rendimiento y los costes. Esta sección te ofrece recomendaciones sobre cómo preparar tus tablas de Snowflake para la ingesta. @@ -492,7 +492,7 @@ El check de Snowflake está incluido en el paquete del [Datadog Agent][24]. # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
@@ -670,8 +670,8 @@ Snowflake no incluye ningún evento. ### Agent: checks de servicio -**snowflake.can_connect** -Devuelve `CRITICAL` si el check no puede autenticar las credenciales de Snowflake. En caso contrario, devuelve `OK`. +**snowflake.can_connect** +Devuelve `CRITICAL` si el check no puede autenticar las credenciales de Snowflake. En caso contrario, devuelve `OK`. _Estados: ok, crítico_ ## Agent: solucionar problemas diff --git a/content/es/integrations/twilio.md b/content/es/integrations/twilio.md index d9d0dcf50cb..024d188b230 100644 --- a/content/es/integrations/twilio.md +++ b/content/es/integrations/twilio.md @@ -128,7 +128,7 @@ La integración de Twilio ingiere [recursos de eventos][1]. [2]: https://www.twilio.com/docs/messaging/api/message-resource [3]: https://www.twilio.com/docs/voice/voice-insights/api/call/call-summary-resource [4]: https://www.twilio.com/docs/voice/voice-insights/advanced-features -[5]: https://app.datadoghq.com/security/siem/home +[5]: https://app.datadoghq.com/security/home [6]: https://www.twilio.com/docs/iam/api-keys#create-an-api-key [7]: https://app.datadoghq.com/integrations/twilio [8]: https://app.datadoghq.com/cost diff --git a/content/es/integrations/wiz.md b/content/es/integrations/wiz.md index 405ceaa455c..a43b9c482cc 100644 --- a/content/es/integrations/wiz.md +++ b/content/es/integrations/wiz.md @@ -172,7 +172,7 @@ La integración Wiz recopila logs y problemas de auditoría. ¿Necesitas ayuda? Ponte en contacto con el [soporte de Datadog][5] o el [soporte de Wiz][6]. -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.wiz.io/login [3]: https://docs.wiz.io/wiz-docs/docs/webhook-format [4]: https://docs.wiz.io/wiz-docs/docs/issues-overview diff --git a/content/es/integrations/workday.md b/content/es/integrations/workday.md index 47781df2bdb..6ba644e0254 100644 --- a/content/es/integrations/workday.md +++ b/content/es/integrations/workday.md @@ -143,7 +143,7 @@ La integración Workday no incluye eventos. ¿Necesitas ayuda? Ponte en contacto con el [servicio de asistencia de Datadog][5]. -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/es/security/cloud_siem/_index.md b/content/es/security/cloud_siem/_index.md index 0a6d3aebf81..1413250b4d1 100644 --- a/content/es/security/cloud_siem/_index.md +++ b/content/es/security/cloud_siem/_index.md @@ -72,7 +72,7 @@ Cloud SIEM integra la telemetría en la nube y on-premises directamente en los f ### Control flexible de los costes de los datos de seguridad -A medida que tu organización crece, es fundamental controlar el coste de ingesta de los logs de seguridad sin comprometer la visibilidad. Cloud SIEM está integrado con Datadog Log Management para que puedas elegir la capacidad de retención y consulta adecuada para tus logs de seguridad. Esta flexibilidad te ayuda a equilibrar la rentabilidad con tus necesidades de detección de amenazas. +A medida que tu organización crece, es fundamental controlar el coste de ingesta de los logs de seguridad sin comprometer la visibilidad. Cloud SIEM está integrado con Datadog Log Management para que puedas elegir la capacidad de retención y consulta adecuada para tus logs de seguridad. Esta flexibilidad te ayuda a equilibrar la rentabilidad con tus necesidades de detección de amenazas. Almacena logs utilizando una de las opciones disponibles: - [Indexación estándar][6] para logs que deben consultarse frecuentemente con el mayor número de cálculos. @@ -264,7 +264,7 @@ Ve qué reglas son las más ruidosas calculando el porcentaje de señales que se [1]: https://securitylabs.datadoghq.com/ [2]: https://www.datadoghq.com/product/cloud-siem/ -[3]: https://app.datadoghq.com/security/siem/home? +[3]: https://app.datadoghq.com/security/home? [4]: /es/getting_started/security/cloud_siem/ [5]: /es/security/cloud_siem/investigate_security_signals/#case-management [6]: /es/logs/log_configuration/indexes diff --git a/content/es/security/cloud_siem/ingest_and_enrich/_index.md b/content/es/security/cloud_siem/ingest_and_enrich/_index.md index 44d8eb6c563..803a4e3f41f 100644 --- a/content/es/security/cloud_siem/ingest_and_enrich/_index.md +++ b/content/es/security/cloud_siem/ingest_and_enrich/_index.md @@ -47,7 +47,7 @@ Datadog proporciona [Inteligencia de amenazas][5] integrada para los logs de Clo {{< partial name="whats-next/whats-next.html" >}} [1]: /es/security/cloud_siem/content_packs/ -[2]: https://app.datadoghq.com/security/siem/content-packs +[2]: https://app.datadoghq.com/security/content-packs [3]: /es/integrations/ [4]: /es/logs/log_collection/ [5]: /es/security/threat_intelligence/#threat-intelligence-sources diff --git a/content/es/security/detection_rules/_index.md b/content/es/security/detection_rules/_index.md index 84589eca6dc..8dce40f46d3 100644 --- a/content/es/security/detection_rules/_index.md +++ b/content/es/security/detection_rules/_index.md @@ -200,5 +200,5 @@ El proceso de obsolescencia de las reglas es el siguiente: [13]: /es/security/cloud_security_management/misconfigurations/custom_rules [14]: /es/security/workload_protection/workload_security_rules?tab=host#create-custom-rules [15]: https://app.datadoghq.com/security/configuration/ -[16]: https://app.datadoghq.com/security/siem/rules +[16]: https://app.datadoghq.com/security/rules [17]: https://app.datadoghq.com/security/workload-protection/detection-rules \ No newline at end of file diff --git a/content/es/security/suppressions.md b/content/es/security/suppressions.md index c6162a72a28..ec8dd96d055 100644 --- a/content/es/security/suppressions.md +++ b/content/es/security/suppressions.md @@ -65,5 +65,5 @@ La [lista de supresiones][3] proporciona una forma centralizada y organizada de [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /es/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/siem/rules +[4]: https://app.datadoghq.com/security/rules [5]: /es/logs/explorer/facets/#log-side-panel diff --git a/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md index b4ef4e9779a..3c024677ad6 100644 --- a/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/fr/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -26,7 +26,7 @@ Pour améliorer la visibilité des utilisateurs sur la sécurité, les partenair Dans votre sandbox Datadog, [créez une nouvelle règle][4]. -{{< img src="developers/integrations/detection_rule.png" alt="La page Créer une nouvelle règle dans l'espace Règles de détection de Datadog" style="width:100%;" >}} +{{< img src="developers/integrations/detection_rule.png" alt="La page Créer une nouvelle règle dans l'espace Règles de détection de Datadog" style="width:100%;" >}}  Suivez les [bonnes pratiques](#bonnes-pratiques-de-configuration) décrites dans ce guide pour configurer votre règle. @@ -34,14 +34,14 @@ Suivez les [bonnes pratiques](#bonnes-pratiques-de-configuration) décrites dans Dans votre intégration, sur la plateforme de développement d'intégrations, accédez à l'onglet Content. Sélectionnez ensuite **Import Detection Rule** pour choisir parmi les règles disponibles. Vous pouvez en inclure jusqu'à 10 avec votre intégration. -{{< img src="developers/integrations/content_tab.png" alt="L'onglet Content dans la plateforme de développement" style="width:100%;" >}} +{{< img src="developers/integrations/content_tab.png" alt="L'onglet Content dans la plateforme de développement" style="width:100%;" >}}  ## Vérifier votre règle de détection en production -Pour voir la règle de détection prête à l'emploi, le carré d'intégration concerné doit être `Installed` dans Datadog, et Cloud SIEM doit être activé. +Pour voir la règle de détection prête à l'emploi, le carré d'intégration concerné doit être `Installed` dans Datadog, et Cloud SIEM doit être activé.  -1. Recherchez votre règle dans la [liste des règles de détection][2], puis cliquez pour l'afficher. +1. Recherchez votre règle dans la [liste des règles de détection][2], puis cliquez pour l'afficher.  2. Assurez-vous que les logos s'affichent correctement. 3. Vérifiez que la règle est bien activée. @@ -131,9 +131,9 @@ Contactez Datadog pour résoudre ce problème. {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/fr/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/fr/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/fr/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/fr/security/suppressions.md b/content/fr/security/suppressions.md index 2c9b6b2aa44..6698fc513d3 100644 --- a/content/fr/security/suppressions.md +++ b/content/fr/security/suppressions.md @@ -65,5 +65,5 @@ La [liste des suppressions][3] permet de gérer les suppressions de façon centr [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /fr/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/siem/rules +[4]: https://app.datadoghq.com/security/rules [5]: /fr/logs/explorer/facets/#log-side-panel diff --git a/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md index 561a82e63bf..523b08631f8 100644 --- a/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/ja/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -130,9 +130,9 @@ Internal failure for = name=""- Contact Datadog {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/ja/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/ja/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/ja/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/ja/integrations/hcp_terraform.md b/content/ja/integrations/hcp_terraform.md index f2fa6b02455..fd346825305 100644 --- a/content/ja/integrations/hcp_terraform.md +++ b/content/ja/integrations/hcp_terraform.md @@ -81,15 +81,15 @@ HCP Terraform のログを確認するには、Datadog ログで `source:hcp-ter ### インストール **ステップ 1: HCP Terraform 用の組織トークンを作成する** -1. [HashiCorp アカウント](https://app.terraform.io/)にログインし、該当する組織を選択して **Settings** をクリックします。 -2. **Security** の下にある **API tokens** をクリックします。 -3. **Create an organization token** をクリックします。 -4. 必要に応じて有効期限を設定します。 -5. **Generate token** をクリックします。 +1. [HashiCorp アカウント](https://app.terraform.io/)にログインし、該当する組織を選択して **Settings** をクリックします。 +2. **Security** の下にある **API tokens** をクリックします。 +3. **Create an organization token** をクリックします。 +4. 必要に応じて有効期限を設定します。 +5. **Generate token** をクリックします。 6. 作成された組織トークンをコピーし、保存しておきます。 **ステップ 2: Datadog インテグレーションを作成する** -1. 下記の **Organization Token** フィールドに上記で作成したトークンを貼り付けます。 +1. 下記の **Organization Token** フィールドに上記で作成したトークンを貼り付けます。 2. アカウント名を入力します。 ### 構成 @@ -118,7 +118,7 @@ hcp-terraform にはイベントは含まれていません。 ご不明な点は、[Datadog のサポートチーム][5]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.datadoghq.com/logs/pipelines?search=hcp-terraform [3]: https://app.datadoghq.com/dash/integration/31325/hcp-terraform-overview [4]: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/organizations#show-the-entitlement-set diff --git a/content/ja/integrations/meraki.md b/content/ja/integrations/meraki.md index 33f2129f13c..18f0b463761 100644 --- a/content/ja/integrations/meraki.md +++ b/content/ja/integrations/meraki.md @@ -171,7 +171,7 @@ Datadog は、サーバーから Meraki にアクセスする際に問題が発 - [Datadog で Cisco Meraki を監視する][13] [1]: https://app.datadoghq.com/devices -[2]: https://app.datadoghq.com/security/siem/home +[2]: https://app.datadoghq.com/security/home [3]: https://developer.cisco.com/meraki/api/get-network-appliance-security-events/ [4]: https://app.datadoghq.com/logs/pipelines?search=meraki [5]: https://developer.cisco.com/meraki/api/get-network-events/ diff --git a/content/ja/integrations/sentinelone.md b/content/ja/integrations/sentinelone.md index 947a234b483..a8c38bcd2e6 100644 --- a/content/ja/integrations/sentinelone.md +++ b/content/ja/integrations/sentinelone.md @@ -151,7 +151,7 @@ SentinelOne インテグレーションにはイベントは含まれていま ご不明な点は、[Datadog のサポートチーム][8]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://www.sentinelone.com/platform/singularity-cloud-funnel/ [3]: https://community.sentinelone.com/s/article/000006282 [4]: https://community.sentinelone.com/s/article/000006285 diff --git a/content/ja/integrations/snowflake_web.md b/content/ja/integrations/snowflake_web.md index 038fc436103..55b8ea93db7 100644 --- a/content/ja/integrations/snowflake_web.md +++ b/content/ja/integrations/snowflake_web.md @@ -111,8 +111,8 @@ Snowflake データをパースした後、Datadog は[すぐに使える概要 以下の表では、収集されるメトリクスの種類と関連するメトリクスのプレフィックスについて説明します。 -| **型** | **説明** | **収集されるメトリクスのプレフィックス** | -|------|-------------|-----------------------------| +| **型** | **説明** | **収集されるメトリクスのプレフィックス** | +|------|-------------|-----------------------------| | **アカウント使用量** | アカウントレベルでのストレージ使用量、クレジット消費量、およびクエリメトリクス。
_毎時収集_。 | `snowflake.auto_recluster`
`snowflake.billing`
`snowflake.data_transfer`
`snowflake.logins`
`snowflake.pipe`
`snowflake.query`
`snowflake.replication`
`snowflake.storage`
`snowflake.storage.database`
`snowflake.storage.table` | | **組織使用量** | 組織レベルでのクレジット消費量、データ転送履歴、予算メトリクス
_毎日収集_。 | `snowflake.organization` | @@ -133,7 +133,7 @@ Snowflake データをパースした後、Datadog は[すぐに使える概要 セキュリティ -これらのログを Cloud SIEM と組み合わせて使用し、環境内のセキュリティ脅威をより適切に検出し対応します。 +これらのログを Cloud SIEM と組み合わせて使用し、環境内のセキュリティ脅威をより適切に検出し対応します。 SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -366,7 +366,7 @@ grant role DATADOG to user ; # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
diff --git a/content/ja/integrations/wiz.md b/content/ja/integrations/wiz.md index c4b589e7e36..74f8a7eaf8c 100644 --- a/content/ja/integrations/wiz.md +++ b/content/ja/integrations/wiz.md @@ -170,7 +170,7 @@ Wiz インテグレーションは監査ログと課題を収集します。 お困りの際は、[Datadog サポート][5] または [Wiz サポート][6] までご連絡ください。 -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.wiz.io/login [3]: https://docs.wiz.io/wiz-docs/docs/webhook-format [4]: https://docs.wiz.io/wiz-docs/docs/issues-overview diff --git a/content/ja/integrations/workday.md b/content/ja/integrations/workday.md index 61a9d58ddf6..a1bfa740aab 100644 --- a/content/ja/integrations/workday.md +++ b/content/ja/integrations/workday.md @@ -141,7 +141,7 @@ Workday インテグレーションには、イベントは含まれません。 ご不明な点は、[Datadog のサポートチーム][5]までお問い合わせください。 -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/ja/integrations/zendesk.md b/content/ja/integrations/zendesk.md index 71d21454f73..c3b218febdf 100644 --- a/content/ja/integrations/zendesk.md +++ b/content/ja/integrations/zendesk.md @@ -143,7 +143,7 @@ Zendesk チケットを作成してグループに割り当てることができ ご不明な点は、[Datadog のサポートチーム][13]までお問合せください。 [1]: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/ -[2]: https://app.datadoghq.com/security/siem/home +[2]: https://app.datadoghq.com/security/home [3]: https://app.datadoghq.com [4]: https://app.datadoghq.com/account/settings#integrations/zendesk [5]: https://docs.datadoghq.com/ja/real_user_monitoring/ diff --git a/content/ja/security/suppressions.md b/content/ja/security/suppressions.md index c6bf0b00536..b98030b5bc1 100644 --- a/content/ja/security/suppressions.md +++ b/content/ja/security/suppressions.md @@ -69,5 +69,5 @@ title: 抑制 [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /ja/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/siem/rules +[4]: https://app.datadoghq.com/security/rules [5]: /ja/logs/explorer/facets/#log-side-panel \ No newline at end of file diff --git a/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md b/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md index bd1b9cd4f4f..5978c1623a8 100644 --- a/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md +++ b/content/ko/developers/integrations/create-a-cloud-siem-detection-rule.md @@ -130,9 +130,9 @@ Internal failure for = name=""- Contact Datadog {{< partial name="whats-next/whats-next.html" >}} [1]: https://docs.datadoghq.com/ko/security/cloud_siem/ -[2]: https://app.datadoghq.com/security/siem/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name +[2]: https://app.datadoghq.com/security/rules?deprecated=hide&groupBy=tactic&product=siem&sort=rule_name [3]: https://docs.datadoghq.com/ko/developers/integrations/agent_integration/ -[4]: https://app.datadoghq.com/security/siem/rules/new?product=siem -[5]: https://github.com/DataDog/integrations-extras +[4]: https://app.datadoghq.com/security/rules/new?product=siem +[5]: https://github.com/DataDog/integrations-extras [6]: https://github.com/DataDog/marketplace [7]: https://docs.datadoghq.com/ko/security/cloud_siem/detection_rules \ No newline at end of file diff --git a/content/ko/integrations/meraki.md b/content/ko/integrations/meraki.md index 98df8283482..78dea6e5b84 100644 --- a/content/ko/integrations/meraki.md +++ b/content/ko/integrations/meraki.md @@ -183,7 +183,7 @@ Datadog 서버에서 Meraki에 액세스하는 데 문제가 발생하는 경우 - [Datadog으로 Cisco Meraki 모니터링][13] [1]: https://app.datadoghq.com/devices -[2]: https://app.datadoghq.com/security/siem/home +[2]: https://app.datadoghq.com/security/home [3]: https://developer.cisco.com/meraki/api/get-network-appliance-security-events/ [4]: https://app.datadoghq.com/logs/pipelines?search=meraki [5]: https://developer.cisco.com/meraki/api/get-network-events/ diff --git a/content/ko/integrations/snowflake_web.md b/content/ko/integrations/snowflake_web.md index 4836066b4c7..50fb9a2bdc7 100644 --- a/content/ko/integrations/snowflake_web.md +++ b/content/ko/integrations/snowflake_web.md @@ -99,7 +99,7 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 #### Snowflake 계정과 연결 -1. [Snowflake 계정 URL][2]을 찾습니다. +1. [Snowflake 계정 URL][2]을 찾습니다. ![Snowflake UI에서 계정 URL 복사 옵션이 선택된 계정 메뉴][3] @@ -111,8 +111,8 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 하단 표는 수집되는 메트릭 유형과 관련 메트릭 접두어에 대해 설명합니다. -| **유형** | **설명** | **수집된 메트릭 접두어** | -|------|-------------|-----------------------------| +| **유형** | **설명** | **수집된 메트릭 접두어** | +|------|-------------|-----------------------------| | **계정 사용량** | 계정 수준에서 사용량, 크레딧 사용량, 쿼리 메트릭을 보관합니다.
_매 시간 수집됩니다_. | `snowflake.auto_recluster`
`snowflake.billing`
`snowflake.data_transfer`
`snowflake.logins`
`snowflake.pipe`
`snowflake.query`
`snowflake.replication`
`snowflake.storage`
`snowflake.storage.database`
`snowflake.storage.table` | | **조직 사용량** | 조직 수준에서 크레딧 사용량, 데이터 전송 기록 및 예산 메트릭을 보관합니다.
_매 시간 수집됩니다_. | `snowflake.organization` | @@ -133,7 +133,7 @@ Snowflake 데이터를 구문 분석한 후 Datadog는 [즉기 사용 가능한 보안 - Cloud SIEM과 함께 이러한 로그를 활용하여 사용자 환경에서 보안 위협을 보다 효율적으로 탐지하고 이에 대응할 수 있습니다. + Cloud SIEM과 함께 이러한 로그를 활용하여 사용자 환경에서 보안 위협을 보다 효율적으로 탐지하고 이에 대응할 수 있습니다. SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.SESSIONS
SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS
SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY
SNOWFLAKE.ACCOUNT_USAGE.STAGES @@ -208,7 +208,7 @@ Datadog이 Snowflake 계정에서 데이터를 수집하려면 특정 IP 주소 #### 커스텀 메트릭 -Snowflake 통합은 커스텀 쿼리 를 지원하며 커스텀 메트릭를 수집합니다. 사용자는 커스텀 SQL 쿼리를 작성하여 특정 데이터를 추출하고 Datadog에서 메트릭 및 메트릭 태그로 확인할 수 있습니다. +Snowflake 통합은 커스텀 쿼리 를 지원하며 커스텀 메트릭를 수집합니다. 사용자는 커스텀 SQL 쿼리를 작성하여 특정 데이터를 추출하고 Datadog에서 메트릭 및 메트릭 태그로 확인할 수 있습니다. 기본적으로 통합은 공유 `SNOWFLAKE` 데이터베이스 및 `ACCOUNT_USAGE` 스키마에 연결됩니다. `ACCOUNT_USAGE` 스키마 외부의 테이블을 쿼리하는 경우에는 설정된 역할에 해당 테이블에 액세스할 수 있는 적절한 권한이 있는지 확인하세요. @@ -260,7 +260,7 @@ Snowflake 웹 통합에는 서비스 점검이 포함되어 있지 않습니다. ## 에이전트: 개요 -이 점검은 Datadog Agent를 통해 [Snowflake][15]를 모니터링합니다. Snowflake는 SaaS 분석 데이터 웨어하우스이며 클라우드 인프라스트럭처에서 완전히 실행됩니다. +이 점검은 Datadog Agent를 통해 [Snowflake][15]를 모니터링합니다. Snowflake는 SaaS 분석 데이터 웨어하우스이며 클라우드 인프라스트럭처에서 완전히 실행됩니다. 이 통합은 크레딧 사용량, 빌링, 저장 공간, 쿼리 메트릭 등을 모니터링합니다.
참고: 메트릭은 Snowflake에 대한 쿼리를 통해 수집됩니다. Datadog 통합으로 생성된 쿼리는 Snowflake에서 청구 가능합니다..
@@ -364,7 +364,7 @@ Snowflake 점검은 [Datadog Agent][16] 패키지에 포함되어 있습니다. # disable_generic_tags: true ``` -
In the default `conf.yaml`, the min_collection_interval is 1 hour. +
In the default `conf.yaml`, the min_collection_interval is 1 hour. Snowflake metrics are aggregated by day, you can increase the interval to reduce the number of queries.
Note: Snowflake ACCOUNT_USAGE views have a known latency of 45 minutes to 3 hours.
@@ -443,7 +443,7 @@ Snowflake에서는 [프록시 구성을 위한 환경 변수][21] 설정을 권 또한 [snowflake.d/conf.yaml][19]의 `init_config`에서 `proxy_host`, `proxy_port`, `proxy_user`,`proxy_password`를 설정할 수 있습니다. -**참고**: Snowflake는 자동으로 프록시 구성 형식을 지정하고 [표준 프록시 환경 변수][22]를 설정합니다. +**참고**: Snowflake는 자동으로 프록시 구성 형식을 지정하고 [표준 프록시 환경 변수][22]를 설정합니다. 이러한 변수는 Docker, ECS, Kubernetes와 같은 오케스트레이터를 포함한 통합의 모든 요청에도 영향을 미칩니다. #### Snowflake 구성에 대한 프라이빗 연결 @@ -537,8 +537,8 @@ Snowflake는 이벤트를 포함하지 않습니다. ### 에이전트: 서비스 점검 -**snowflake.can_connect** -점검에서 Snowflake 자격 증명을 인증할 수 없는 경우 `CRITICAL`을 반환합니다. 그렇지 않으면 `OK`를 반환합니다. +**snowflake.can_connect** +점검에서 Snowflake 자격 증명을 인증할 수 없는 경우 `CRITICAL`을 반환합니다. 그렇지 않으면 `OK`를 반환합니다. *Statuses: ok, critical* ## 에이전트: 트러블슈팅 diff --git a/content/ko/integrations/workday.md b/content/ko/integrations/workday.md index 05796e5ee51..dd07764f4a3 100644 --- a/content/ko/integrations/workday.md +++ b/content/ko/integrations/workday.md @@ -141,7 +141,7 @@ Workday 통합은 이벤트를 포함하지 않습니다. 도움이 필요하신가요? [Datadog 지원팀][5]에 문의하세요. -[1]: https://app.datadoghq.com/security/siem/home +[1]: https://app.datadoghq.com/security/home [2]: https://app.datadoghq.com/logs/pipelines?search=workday [3]: https://community.workday.com/sites/default/files/file-hosting/restapi/index.html#privacy/v1/get-/activityLogging [4]: https://github.com/DataDog/integrations-internal-core/blob/master/workday/assets/service_checks.json diff --git a/content/ko/integrations/zendesk.md b/content/ko/integrations/zendesk.md index 8fc01d96874..aa157d75c3f 100644 --- a/content/ko/integrations/zendesk.md +++ b/content/ko/integrations/zendesk.md @@ -143,7 +143,7 @@ Zendesk 티켓을 생성하여 그룹에 할당할 수 있습니다. 먼저 Data 도움이 필요하세요? [Datadog 지원팀][13]에 문의하세요. [1]: https://developer.zendesk.com/api-reference/ticketing/account-configuration/audit_logs/ -[2]: https://app.datadoghq.com/security/siem/home +[2]: https://app.datadoghq.com/security/home [3]: https://app.datadoghq.com [4]: https://app.datadoghq.com/account/settings#integrations/zendesk [5]: https://docs.datadoghq.com/ko/real_user_monitoring/ diff --git a/content/ko/security/suppressions.md b/content/ko/security/suppressions.md index 2ad37daf909..3df21d10e78 100644 --- a/content/ko/security/suppressions.md +++ b/content/ko/security/suppressions.md @@ -65,5 +65,5 @@ title: 억제 [1]: https://app.datadoghq.com/security/configuration/siem/rules/new [2]: /ko/security/detection_rules/ [3]: https://app.datadoghq.com/security/configuration/suppressions -[4]: https://app.datadoghq.com/security/siem/rules +[4]: https://app.datadoghq.com/security/rules [5]: /ko/logs/explorer/facets/#log-side-panel