[MokoCBRegGuard] [FEATURE] Configurable per-flag risk weights #18

New Issue

2026-06-02T19:31:34Z

jmiller commented

2026-06-02 19:31:34 +00:00

Migrated from MokoCBRegGuard#22

Feature Description

Expose per-flag weight overrides as plugin parameters so administrators can tune the risk scoring to their community's threat profile.

Problem or Use Case

Flag weights are currently hardcoded in RegGuardHelper::calculateRiskScore() (SFS = 3, IP_FREQUENCY = 2, RDNS_HOSTING = 1, etc.). Different communities have very different threat profiles:

An age-restricted site needs BIRTHDAY_AGE_LOW weighted higher
A site that allows VPN use wants RDNS_HOSTING weighted lower
A site heavily targeted by SFS-listed spammers may want even higher SFS weights

There is no way to adjust these without modifying source code.

Proposed Solution

Add per-flag weight parameters to the plugin configuration:

weight_sfs_ip (default: 3)
weight_sfs_email (default: 3)
weight_ip_frequency (default: 2)
weight_birthday_future (default: 2)
weight_birthday_invalid (default: 2)
weight_birthday_age_low (default: 2)
weight_rdns_hosting (default: 1)
weight_ip_localhost (default: 1)
weight_birthday_suspicious (default: 1)
weight_birthday_year_old (default: 1)
weight_birthday_age_high (default: 1)

Fall back to current hardcoded defaults when a param is not set (backward compatible).

Alternative Solutions

Adjust risk thresholds instead (coarser control, does not change relative flag importance)
Provide preset profiles like strict / moderate / lenient (less flexible)

Benefits

Who: Any administrator wanting to fine-tune risk scoring for their specific community
Problem solved: Eliminates need to modify source code for scoring adjustments
Value: Makes the plugin adaptable to diverse community types and threat landscapes

Implementation Details (Optional)

New params in cbregguard.xml (one per flag type)
Modify RegGuardHelper::calculateRiskScore() to accept params and read weights from config
Maintain current defaults as fallbacks for backward compatibility
Group weight params in a dedicated XML fieldset for clean UI

Relevant Standards

Code quality standards

Checklist

I have searched for similar feature requests before creating this one
I have clearly described the use case and benefits
I have considered alternative solutions
This feature aligns with the project's goals and scope

> Migrated from MokoCBRegGuard#22 ## Feature Description Expose per-flag weight overrides as plugin parameters so administrators can tune the risk scoring to their community's threat profile. ## Problem or Use Case Flag weights are currently hardcoded in `RegGuardHelper::calculateRiskScore()` (SFS = 3, IP_FREQUENCY = 2, RDNS_HOSTING = 1, etc.). Different communities have very different threat profiles: - An age-restricted site needs `BIRTHDAY_AGE_LOW` weighted higher - A site that allows VPN use wants `RDNS_HOSTING` weighted lower - A site heavily targeted by SFS-listed spammers may want even higher SFS weights There is no way to adjust these without modifying source code. ## Proposed Solution Add per-flag weight parameters to the plugin configuration: - `weight_sfs_ip` (default: 3) - `weight_sfs_email` (default: 3) - `weight_ip_frequency` (default: 2) - `weight_birthday_future` (default: 2) - `weight_birthday_invalid` (default: 2) - `weight_birthday_age_low` (default: 2) - `weight_rdns_hosting` (default: 1) - `weight_ip_localhost` (default: 1) - `weight_birthday_suspicious` (default: 1) - `weight_birthday_year_old` (default: 1) - `weight_birthday_age_high` (default: 1) Fall back to current hardcoded defaults when a param is not set (backward compatible). ## Alternative Solutions - Adjust risk thresholds instead (coarser control, does not change relative flag importance) - Provide preset profiles like strict / moderate / lenient (less flexible) ## Benefits - **Who:** Any administrator wanting to fine-tune risk scoring for their specific community - **Problem solved:** Eliminates need to modify source code for scoring adjustments - **Value:** Makes the plugin adaptable to diverse community types and threat landscapes ## Implementation Details (Optional) - New params in `cbregguard.xml` (one per flag type) - Modify `RegGuardHelper::calculateRiskScore()` to accept params and read weights from config - Maintain current defaults as fallbacks for backward compatibility - Group weight params in a dedicated XML fieldset for clean UI ## Relevant Standards - [x] Code quality standards ## Checklist - [x] I have searched for similar feature requests before creating this one - [x] I have clearly described the use case and benefits - [x] I have considered alternative solutions - [x] This feature aligns with the project's goals and scope

jmiller added the pending: testing regguard labels 2026-06-02 19:52:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomCommunity#18