Skip to content

feat(C4): add secure-aggregation requirements 4.3.6 and 4.3.7 - #1219

Merged
jmanico merged 1 commit into
OWASP:mainfrom
nikhilred2619:fl-secure-aggregation-1190
Nov 11, 2026
Merged

jmanico merged 1 commit into
OWASP:mainfrom
nikhilred2619:fl-secure-aggregation-1190

Conversation

@nikhilred2619

Copy link
Copy Markdown
Contributor

Refs #1190

This PR adds two Level 3 requirements to C4.3 (Edge & Distributed AI Security) for federated learning deployments that use secure aggregation, following the scope agreed with the maintainers in #1190.

Security gap

Secure aggregation protects individual model updates only when the deployment satisfies the assumptions and parameter constraints established by the protocol's security analysis.

The existing C4.3 requirements do not explicitly verify these conditions or prevent an aggregation server from obtaining aggregates that contain too few contributions.

Changes

C4.3.6 — Secure-aggregation configuration

Verify that the reconstruction threshold, expected participant count, and documented collusion bound satisfy the protocol's published security analysis for the declared adversary model.

C4.3.7 — Minimum aggregate size

Verify that the aggregation server cannot obtain an aggregate, even temporarily, containing fewer contributions than the minimum derived from the protocol's security analysis.

Both requirements are classified as Level 3, as agreed in the issue discussion.

Supporting updates

  • Added both requirements to the C4.3 infrastructure security controls.
  • Mapped C4.3.6 and C4.3.7 under AD.4 in Appendix B.
  • Added glossary definitions for Aggregator, Collusion Bound, Reconstruction Threshold, and Secure Aggregation.
  • Updated the Federated Learning definition to include cross-device and cross-silo deployments.

Validation

The patch preparation included:

  • Markdown linting and spelling checks.
  • Verification of requirement numbering and Appendix B mappings.
  • Git diff and whitespace checks.
  • Confirmation that only the three intended files were modified.

GitHub Actions checks will run after the PR is opened.

References

@jmanico jmanico left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nikhilred2619. The rows match what we agreed on #1190, and the glossary and Appendix B entries look good. Merging. 🙏

@jmanico
jmanico merged commit ab1e184 into OWASP:main Nov 11, 2026
3 checks passed
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.

2 participants