Skip to content

Commit

Permalink
[pre-commit.ci] auto fixes from pre-commit.com hooks
Browse files Browse the repository at this point in the history
for more information, see https://pre-commit.ci
  • Loading branch information
pre-commit-ci[bot] committed Dec 12, 2024
1 parent aec74ea commit 85b3457
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 21 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,9 @@ B. Respond accordingly:

More information on [incident response roles and responsibilities](incident-response-plan.md#roles-and-responsibilities):

- [Responder](incident-response-plan.md#responder)
- [Incident Commander (IC)](incident-response-plan.md#incident-commander)
- [Communications Officer (CO)](incident-response-plan.md#communications-officer)
- [Responder](incident-response-plan.md#responder)
- [Incident Commander (IC)](incident-response-plan.md#incident-commander)
- [Communications Officer (CO)](incident-response-plan.md#communications-officer)

Check warning on line 42 in common-practices-tools/security/incident-response-checklist.md

View workflow job for this annotation

GitHub Actions / remark-lint-problem

[remark-lint-problem] common-practices-tools/security/incident-response-checklist.md#L42

Unexpected indented code block, expected fenced code blocks code-block-style remark-lint
Raw output
40:3-42:94     warning Unexpected indented code block, expected fenced code blocks                                 code-block-style                 remark-lint

Use the [_Explicit Handoff Ceremony_](incident-response-plan.md#explicit-handoff-ceremony) when transferring/changing roles.

Expand Down
36 changes: 18 additions & 18 deletions common-practices-tools/security/incident-response-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,18 +161,18 @@ B. Respond accordingly:

An example message follows. The format is not important, but the information fields are useful.

**Description**: [Short description of the event and its impact]
**Status**: investigating
**Severity**: unknown
**Incident Reporter**: [name of the person who reported the issue]
**Incident Commander**: [your name]
**Responders**: [names of other _Responders_]
**Details**: [Extra details about the event]
**Description**: [Short description of the event and its impact]
**Status**: investigating
**Severity**: unknown
**Incident Reporter**: [name of the person who reported the issue]
**Incident Commander**: [your name]
**Responders**: [names of other _Responders_]
**Details**: [Extra details about the event]

Check warning on line 170 in common-practices-tools/security/incident-response-plan.md

View workflow job for this annotation

GitHub Actions / remark-lint-problem

[remark-lint-problem] common-practices-tools/security/incident-response-plan.md#L170

Unexpected indented code block, expected fenced code blocks code-block-style remark-lint
Raw output
164:3-170:57   warning Unexpected indented code block, expected fenced code blocks                                 code-block-style                 remark-lint

Observe the following guidelines for communications:

- During this stage of incident response, the event status is "investigating".
- An unconfirmed issue is called an _event_. A confirmed issue is called an _incident_.
- During this stage of incident response, the event status is "investigating".
- An unconfirmed issue is called an _event_. A confirmed issue is called an _incident_.

Check warning on line 175 in common-practices-tools/security/incident-response-plan.md

View workflow job for this annotation

GitHub Actions / remark-lint-problem

[remark-lint-problem] common-practices-tools/security/incident-response-plan.md#L175

Unexpected indented code block, expected fenced code blocks code-block-style remark-lint
Raw output
174:3-175:98   warning Unexpected indented code block, expected fenced code blocks                                 code-block-style                 remark-lint

2. For an incident requiring more than 30 minutes to resolve:

Expand All @@ -181,11 +181,11 @@ B. Respond accordingly:

More information on [incident response roles and responsibilities](#roles-and-responsibilities):

- [Responder](#responder)
- [Incident Commander (IC)](#incident-commander)
- [Communications Officer (CO)](#communications-officer)
- [Responder](#responder)
- [Incident Commander (IC)](#incident-commander)
- [Communications Officer (CO)](#communications-officer)

Use the [Explicit Handoff Ceremony](#explicit-handoff-ceremony) when transferring/changing roles.
Use the [Explicit Handoff Ceremony](#explicit-handoff-ceremony) when transferring/changing roles.

Check warning on line 188 in common-practices-tools/security/incident-response-plan.md

View workflow job for this annotation

GitHub Actions / remark-lint-problem

[remark-lint-problem] common-practices-tools/security/incident-response-plan.md#L188

Unexpected indented code block, expected fenced code blocks code-block-style remark-lint
Raw output
184:3-188:108  warning Unexpected indented code block, expected fenced code blocks                                 code-block-style                 remark-lint

- False alarm

Expand Down Expand Up @@ -226,11 +226,11 @@ _Reminder: Use the [Explicit Handoff Ceremony](#explicit-handoff-ceremony) when

Here is an example _sitrep_:

**Subject**: \[sitrep\] Chickens are escaping
**Severity**: low
**Incident Commander**: Farmer Jane
**Responders**: Spot the Dog, Farmer Dave
**Description**: We've confirmed reports of escaped chickens. Looks like a fox may have tunneled into the run. Dave is working to fix the fence. Spot is tracking the fox.
**Subject**: \[sitrep\] Chickens are escaping
**Severity**: low
**Incident Commander**: Farmer Jane
**Responders**: Spot the Dog, Farmer Dave
**Description**: We've confirmed reports of escaped chickens. Looks like a fox may have tunneled into the run. Dave is working to fix the fence. Spot is tracking the fox.

Check warning on line 233 in common-practices-tools/security/incident-response-plan.md

View workflow job for this annotation

GitHub Actions / remark-lint-problem

[remark-lint-problem] common-practices-tools/security/incident-response-plan.md#L233

Unexpected indented code block, expected fenced code blocks code-block-style remark-lint
Raw output
229:3-233:181  warning Unexpected indented code block, expected fenced code blocks                                 code-block-style                 remark-lint

- For an issue with potential Project impact, ensure that a ticket/issue has been created. This should be done, even if the _First Responder/IC_ manages the incident fully, for example, by simply re-starting a service.

Check warning on line 235 in common-practices-tools/security/incident-response-plan.md

View workflow job for this annotation

GitHub Actions / remark-lint-suggestions

[remark-lint-suggestions] common-practices-tools/security/incident-response-plan.md#L235

Unexpected potentially insensitive use of `simply`, try not to use it simple retext-equality
Raw output
235:190-235:196 warning Unexpected potentially insensitive use of `simply`, try not to use it                                                                                                                                                                                                                                  simple                      retext-equality

Expand Down

0 comments on commit 85b3457

Please sign in to comment.