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

Consider making basic logging part of L1 #1419

Open
jmanico opened this issue Nov 9, 2022 · 4 comments
Open

Consider making basic logging part of L1 #1419

jmanico opened this issue Nov 9, 2022 · 4 comments
Assignees
Labels
Community wanted We would like feedback from the community to guide our decision otherwise we will progress requirement level Issue related to requirement levels V7 Temporary label for grouping logging related issues _5.0 - draft This should be discussed once a 5.0 draft has been prepared.

Comments

@jmanico
Copy link
Member

jmanico commented Nov 9, 2022

Why not make these level 1? Basic logging seems critical for all apps.

1.7.1 | Verify that a common logging format and approach is used across the system. (C9) |   | ✓ | ✓ | 1009
1.7.2 | Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. (C9) |   | ✓ | ✓

#DanWasHere

@jmanico jmanico self-assigned this Nov 9, 2022
@jmanico jmanico added the _5.0 - draft This should be discussed once a 5.0 draft has been prepared. label Nov 9, 2022
@elarlang
Copy link
Collaborator

First - it is hard to set levels, before we have not (re)defined levels.

To change level to 1 for logging, we need to get rid of "blackbox pentestable" from level 1. And if we did, then I think 1.7.1 can be level 1 but I'm not that sure about 1.7.2.

@tghosth tghosth added 1) Discussion ongoing Issue is opened and assigned but no clear proposal yet _5.0 - prep This needs to be addressed to prepare 5.0 Community wanted We would like feedback from the community to guide our decision otherwise we will progress and removed _5.0 - draft This should be discussed once a 5.0 draft has been prepared. labels Dec 7, 2022
@tghosth
Copy link
Collaborator

tghosth commented Dec 12, 2022

I tend to agree given the move towards shaping the levels based on risk.

@elarlang to handle this as part of the V7 reorganization.

1.7.2 is definitely implementation requirement. 1.7.1 maybe needs to be part of the logging inventory/documentation requirement.

@elarlang elarlang added the V7 Temporary label for grouping logging related issues label Dec 13, 2022
@elarlang
Copy link
Collaborator

Update:

@elarlang elarlang added the 4a) Waiting for another This issue is waiting for another issue to be resolved label Jan 17, 2023
@tghosth tghosth added 4b Major-rework These issues need to be part of a full chapter rework and removed 1) Discussion ongoing Issue is opened and assigned but no clear proposal yet labels Jul 10, 2023
@elarlang elarlang added the requirement level Issue related to requirement levels label Oct 30, 2023
@tghosth
Copy link
Collaborator

tghosth commented May 2, 2024

I think this is redundant for now since things got moved around. I think we need to cut down L1 as much as possible so not sure logging will make it. I am going to push this to the draft stage.

@tghosth tghosth added _5.0 - draft This should be discussed once a 5.0 draft has been prepared. V7 Temporary label for grouping logging related issues and removed _5.0 - prep This needs to be addressed to prepare 5.0 4a) Waiting for another This issue is waiting for another issue to be resolved V7 Temporary label for grouping logging related issues 4b Major-rework These issues need to be part of a full chapter rework labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community wanted We would like feedback from the community to guide our decision otherwise we will progress requirement level Issue related to requirement levels V7 Temporary label for grouping logging related issues _5.0 - draft This should be discussed once a 5.0 draft has been prepared.
Projects
None yet
Development

No branches or pull requests

3 participants