Repository navigation
feat(C4): add secure-aggregation requirements 4.3.6 and 4.3.7 - #1219
Merged
Merged
Conversation
jmanico
approved these changes
Nov 11, 2026
jmanico
left a comment
Member
There was a problem hiding this comment.
Thanks @nikhilred2619. The rows match what we agreed on #1190, and the glossary and Appendix B entries look good. Merging. 🙏
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Validation
The patch preparation included:
GitHub Actions checks will run after the PR is opened.
References