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

Review quirementes 14.2.6 and 14.2.8, potential move to V10 #2166

Open
elarlang opened this issue Oct 20, 2024 · 3 comments
Open

Review quirementes 14.2.6 and 14.2.8, potential move to V10 #2166

elarlang opened this issue Oct 20, 2024 · 3 comments
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet next meeting Filter for leaders V14

Comments

@elarlang
Copy link
Collaborator

Spin-off from #2088 / the discussion over 14.2.6 and/or 14.2.8 comes from #1425.

Current requirements:

# Description L1 L2 L3 CWE
14.2.6 [MODIFIED, SPLIT TO 14.2.8, LEVEL L2 > L3] Verify that risky third party libraries or those with a history of vulnerabilities are encapsulated such that only required behaviour is available to the application, to reduce attack surface. 1061
14.2.8 [ADDED, SPLIT FROM 14.2.6] Verify that risky third party libraries or those with a history of vulnerabilities are sandboxed away from the most sensitive system modules/services so that even if a vulnerability in the library was successfully exploited, the sensitive system modules/services would not be compromised. 1061

The need for those requirements are questioned for example in comments:

For me the "main error" is, if we talk about L3 requirement, then those application can not use any "too risky" and not trustful component anyway.

By content, both are more "software architecture" requirements, not a clear configuration requirements. Most likely we need a chapter for V10 for that, something to say "Software Architecture" or "Sandboxing".

@elarlang elarlang added 1) Discussion ongoing Issue is opened and assigned but no clear proposal yet V14 labels Oct 20, 2024
@jmanico
Copy link
Member

jmanico commented Oct 20, 2024 via email

@elarlang
Copy link
Collaborator Author

Those are current requirements that are questioned by 2 persons...

@jmanico
Copy link
Member

jmanico commented Oct 20, 2024

With a little wordsmithing, I personally like them. That's all.

@elarlang elarlang added the next meeting Filter for leaders label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet next meeting Filter for leaders V14
Projects
None yet
Development

No branches or pull requests

2 participants