Skip to content
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

docs: add comment on inspection level and machine learning parameters #104

Conversation

RoseSecurity
Copy link
Member

what

  • Adds additional comments for clarity on how inspection_levels and enable_machine_learning can be configured

why

  • The Bot Control managed rule group provides two levels of protection: COMMON and TARGETED. We tested an inspection level set to COMMON, which uses traditional bot detection techniques, such as static request data analysis and does not support machine learning analysis. The mismatch of protection levels and configuration were causing continual drift

references

@RoseSecurity RoseSecurity requested review from a team as code owners October 21, 2024 21:25
@RoseSecurity RoseSecurity changed the title add comment on inspection level and machine learning parameters docs: add comment on inspection level and machine learning parameters Oct 21, 2024
@RoseSecurity
Copy link
Member Author

/terratest

@mergify mergify bot added the triage Needs triage label Oct 21, 2024
@RoseSecurity RoseSecurity closed this by deleting the head repository Nov 1, 2024
@mergify mergify bot removed the triage Needs triage label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant