Skip to content

HyperActive - External Login Password Spray #40185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

idovandijk
Copy link
Contributor

@idovandijk idovandijk commented Jun 4, 2025

Status

Ready

Related Issues

fixes: https://jira-dc.paloaltonetworks.com/browse/CIAC-13969

Description

  • Added Hyperactive playbook for External Login Password Spray alerts.
  • Removed the "External Login Password Spray" variation from the old trigger file

External_Login_Password_Spray_dev_Wed_Jun_04_2025

@idovandijk idovandijk requested a review from AdiPeret June 4, 2025 15:17
@idovandijk idovandijk changed the title External login password spray hyperactive HyperActive - External Login Password Spray Jun 4, 2025
@idovandijk idovandijk added ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines docs-approved labels Jun 5, 2025
@content-bot
Copy link
Collaborator

This PR was automatically updated by a GitHub Action

  • CortexResponseAndRemediation pack version was bumped to 1.1.59.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

@content-bot
Copy link
Collaborator

This PR was automatically updated by a GitHub Action

  • CortexResponseAndRemediation pack version was bumped to 1.1.60.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

@content-bot
Copy link
Collaborator

Validate summary

Verdict: PR can be force merged from validate perspective? ✅

@content-bot
Copy link
Collaborator

This PR was automatically updated by a GitHub Action

  • CortexResponseAndRemediation pack version was bumped to 1.1.61.

To stop automatic version bumps, add the ignore-auto-bump-version label to the github PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants