Skip to content

Commit e5ba937

Browse files
[8.11] Replace placeholder URLs (backport #6990) (#6998)
* Replace placeholder URLs (#6990) (cherry picked from commit 1633469) # Conflicts: # docs/AI-for-security/connect-to-byo.asciidoc # docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc # docs/release-notes/8.16.asciidoc * resolve conflict --------- Co-authored-by: natasha-moore-elastic <[email protected]> Co-authored-by: natasha-moore-elastic <[email protected]>
1 parent 0360097 commit e5ba937

File tree

5 files changed

+9
-9
lines changed

5 files changed

+9
-9
lines changed

docs/cloud-native-security/cspm-get-started-aws.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ You can use the AWS CLI to generate temporary credentials. For example, you coul
227227

228228
[source,console]
229229
----------------------------------
230-
sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email@example.com --duration-seconds 129600 --token-code 123456
230+
sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email<example-url> --duration-seconds 129600 --token-code 123456
231231
----------------------------------
232232

233233
The output from this command includes the following fields, which you should provide when configuring the CSPM integration:

docs/cloud-native-security/kspm-get-started.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ You can use the AWS CLI to generate temporary credentials. For example, you coul
159159

160160
[source,console]
161161
----------------------------------
162-
`sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email@example.com --duration-seconds 129600 --token-code 123456`
162+
`sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email@<example-url> --duration-seconds 129600 --token-code 123456`
163163
----------------------------------
164164

165165
The output from this command includes the following fields, which you should provide when configuring the KSPM integration:

docs/detections/prebuilt-rules/rule-details/multiple-vault-web-credentials-read.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,12 +68,12 @@ sequence by winlog.computer_name, winlog.process.pid with maxspan=1s
6868
[any where event.code : "5382" and
6969
(winlog.event_data.SchemaFriendlyName : "Windows Web Password Credential" and winlog.event_data.Resource : "http*") and
7070
not winlog.event_data.SubjectLogonId : "0x3e7" and
71-
not winlog.event_data.Resource : "http://localhost/"]
71+
not winlog.event_data.Resource : "<LOCAL_HOST_URL>"]
7272
7373
[any where event.code : "5382" and
7474
(winlog.event_data.SchemaFriendlyName : "Windows Web Password Credential" and winlog.event_data.Resource : "http*") and
7575
not winlog.event_data.SubjectLogonId : "0x3e7" and
76-
not winlog.event_data.Resource : "http://localhost/"]
76+
not winlog.event_data.Resource : "<LOCAL_HOST_URL>"]
7777
7878
----------------------------------
7979

docs/release-notes/8.8.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
3636

3737
. Right-click anywhere on the Alerts page, then select *Inspect* to open Chrome's Developer Tools.
3838
. Go to *Application -> Storage*, then expand *Local Storage*.
39-
. Click on the name of your Kibana instance, for example, http://localhost:1234.
39+
. Click on the name of your Kibana instance, for example, <LOCAL_HOST_URL>:1234.
4040
. Search for the `detection-engine-alert-table-securitySolution-rule-details-gridView` key and copy its value. The value you copied is the JSON blob that's used to persist the Alerts table's state, including the table's selected columns.
4141
. Paste the JSON blob into a text file and edit it as follows:
4242
.. Remove the `id:file.name` string from the `columns` array.
@@ -259,7 +259,7 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
259259

260260
. Right-click anywhere on the Alerts page, then select *Inspect* to open Chrome's Developer Tools.
261261
. Go to *Application -> Storage*, then expand *Local Storage*.
262-
. Click on the name of your Kibana instance, for example, http://localhost:1234.
262+
. Click on the name of your Kibana instance, for example, <LOCAL_HOST_URL>:1234.
263263
. Search for the `detection-engine-alert-table-securitySolution-rule-details-gridView` key and copy its value. The value you copied is the JSON blob that's used to persist the Alerts table's state, including the table's selected columns.
264264
. Paste the JSON blob into a text file and edit it as follows:
265265
.. Remove the `id:file.name` string from the `columns` array.
@@ -413,7 +413,7 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
413413

414414
. Right-click anywhere on the Alerts page, then select *Inspect* to open Chrome's Developer Tools.
415415
. Go to *Application -> Storage*, then expand *Local Storage*.
416-
. Click on the name of your Kibana instance, for example, http://localhost:1234.
416+
. Click on the name of your Kibana instance, for example, <LOCAL_HOST_URL>:1234.
417417
. Search for the `detection-engine-alert-table-securitySolution-rule-details-gridView` key and copy its value. The value you copied is the JSON blob that's used to persist the Alerts table's state, including the table's selected columns.
418418
. Paste the JSON blob into a text file and edit it as follows:
419419
.. Remove the `id:file.name` string from the `columns` array.

docs/release-notes/8.9.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
4848

4949
. Right-click anywhere on the Alerts page, then select *Inspect* to open Chrome's Developer Tools.
5050
. Go to *Application -> Storage*, then expand *Local Storage*.
51-
. Click on the name of your Kibana instance, for example, http://localhost:1234.
51+
. Click on the name of your Kibana instance, for example, <LOCAL_HOST_URL>:1234.
5252
. Search for the `detection-engine-alert-table-securitySolution-rule-details-gridView` key and copy its value. The value you copied is the JSON blob that's used to persist the Alert table's state, including the table's selected columns.
5353
. Paste the JSON blob into a text file and edit it as follows:
5454
.. Remove the `id:file.name` string from the `columns` array.
@@ -115,7 +115,7 @@ NOTE: These instructions only apply to the Google Chrome browser. Modify the ste
115115

116116
. Right-click anywhere on the Alerts page, then select *Inspect* to open Chrome's Developer Tools.
117117
. Go to *Application -> Storage*, then expand *Local Storage*.
118-
. Click on the name of your Kibana instance, for example, http://localhost:1234.
118+
. Click on the name of your Kibana instance, for example, <LOCAL_HOST_URL>:1234.
119119
. Search for the `detection-engine-alert-table-securitySolution-rule-details-gridView` key and copy its value. The value you copied is the JSON blob that's used to persist the Alert table's state, including the table's selected columns.
120120
. Paste the JSON blob into a text file and edit it as follows:
121121
.. Remove the `id:file.name` string from the `columns` array.

0 commit comments

Comments
 (0)