mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2593] [Feature Request]: More granular anti-phishing policy configuration within standards #1306
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1306
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kakaiwa on GitHub (Jun 24, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2593
Originally assigned to: @kakaiwa on GitHub.
Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.
There are several parameters for anti-phishing policy not configurable in standards. These includes:
AuthenticationFailAction, SpoofQuarantineTag, TargetedUserQuarantineTag, TargetedDomainQuarantineTag
Adding these will help admin make more granular quarantine decision depending on the detection.
PowerShell commands you would normally use to achieve above request
No response
@kakaiwa commented on GitHub (Jun 24, 2024):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Jun 24, 2024):
Great! I assigned you (@kakaiwa) to the issue. Have fun working on it!
@KelvinTegelaar commented on GitHub (Jun 28, 2024):
Closing the issue as the PR is in place, and about to be accepted with one minor change :)