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

Secure fallback defaults for publisherTrustedAlgorithmPublishers and publisherTrustedAlgorithms #24

Open
Abrom8 opened this issue Jun 11, 2024 · 0 comments

Comments

@Abrom8
Copy link

Abrom8 commented Jun 11, 2024

Secure Default Configuration for publisherTrustedAlgorithmPublishers and publisherTrustedAlgorithms

Current Configuration Definition

  • Type: Array of string
  • Behavior:
    • If not defined: Any published algorithm/publisher is allowed.
    • If empty array: No algorithm/publisher is allowed.
    • If not empty: Only algorithms published by the defined publishers are allowed.

Issue

The current configuration allows any published algorithm to be executed if the publisherTrustedAlgorithmPublishers field is not defined. This default behavior poses a significant security risk, potentially allowing untrusted or malicious algorithms.

Proposed Change

Modify the default behavior to enhance security:

  • New Default Behavior (If not defined): No algorithm is allowed.

This change will ensure that in the absence of an explicit configuration, the system defaults to the most secure state by not allowing the execution of any algorithms.

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

No branches or pull requests

1 participant