-
Notifications
You must be signed in to change notification settings - Fork 4
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
Running PR for Profile review and Fix #14
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Rony Xavier <[email protected]>
Review comments from @HackerShark V-81843 - WORKS |
V-81853 - WORKS |
|
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: HackerShark <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HackerShark plz see below my notes on ur review
V-81853 - WORKS
agreed
V-81855 - WORKS
Irrational design.
Lets just add a non applicability case if virtualization.system.eql?('docker'). with the rightdesc, caveat
verbiage explaining why its non applicable in a container.
V-81857 - Doesn’t seem to be connecting to database, need to further evaluate after making proper connection
agreed
V-81859 - WORKS
packages(/mongodb/).names
gets us the package names...and the resource handles distro adaptation.
This way input var dont have to be updated for ever version.
also same var can be used for debian and redhat packages...this we we can collapsemongodb_debian_packages
andmongodb_redhat_packages
to a singleapproved_mongo_packages
V-81861 - WORKS
agreed
…nspec.yml Signed-off-by: HackerShark <[email protected]>
V-81863 - Doesn’t seem to be connecting to database, need to further evaluate after making proper connection |
Signed-off-by: HackerShark <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
V-81863 - Doesn’t seem to be connecting to database, need to further evaluate after making proper connection
V-81865 - Doesn’t seem to be connecting to database, need to further evaluate after making proper connection
V-81867 - WORKSThe check code seems to refer to
authenticationMechanisms
settingsSCRAM
andMONGODB-X509
which is not being checked in the control
https://docs.mongodb.com/manual/reference/parameters/#mongodb-parameter-param.authenticationMechanisms
V-81869 - Should the locations for the pemkeyfile and cafile be parameterized for this check? Or is this a static location?
The guidance just says they should be set... so test could be as simple as...it should not be nil
Please also add the describe.one condition where allowInvalidCertificates could be nil or false for a pass
V-81871 - Similar fix to our previous controls, instead of having an input for the pem and cafile will pull those using yaml resource from the mongo conf file. Also doing same var fix for inputs using be_in matcher.
Agreed..input values not required here... file locations can be parsed from the conf file.
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: HackerShark <[email protected]>
V-81867 - Might need to switch this over to a Manual Review as we spoke about before. |
I think in the wings profiles we used.
Is_sensitive for a sensitive env
On Mon, May 24, 2021 at 12:47 AM Mo Shark ***@***.***> wrote:
V-81867 - Might need to switch this over to a Manual Review as we spoke
about before.
V-81873 - WORKS
V-81875 - From the wording of the STIG this check applies if the MongoDB
is deployed in a classified environment. As such we need to have a check
(possibly using an input flag) that sees if we are in a classified
environment then we will do the checks. On top of that the STIG currently
only does the first check, we also need to Check the server log file for
a message that FIPS is active. We would also need to Verify that FIPS has
been enabled at the operating system.
V-81877 - Doesn’t seem to be connecting to database, need to further
evaluate after making proper connection
V-81879 - WORKS
V-81881 - WORKS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALK42EK2HX373JTLPELQX3TPHK63ANCNFSM44437F7Q>
.
--
--------
Aaron Lippold
***@***.***
260-255-4779
twitter/aim/yahoo,etc.
'aaronlippold'
|
Damn auto correct. I think in the windows profiles we used ....
On Mon, May 24, 2021 at 5:47 AM Aaron Lippold ***@***.***>
wrote:
I think in the wings profiles we used.
Is_sensitive for a sensitive env
On Mon, May 24, 2021 at 12:47 AM Mo Shark ***@***.***> wrote:
> V-81867 - Might need to switch this over to a Manual Review as we spoke
> about before.
> V-81873 - WORKS
> V-81875 - From the wording of the STIG this check applies if the MongoDB
> is deployed in a classified environment. As such we need to have a check
> (possibly using an input flag) that sees if we are in a classified
> environment then we will do the checks. On top of that the STIG currently
> only does the first check, we also need to Check the server log file for
> a message that FIPS is active. We would also need to Verify that FIPS has
> been enabled at the operating system.
> V-81877 - Doesn’t seem to be connecting to database, need to further
> evaluate after making proper connection
> V-81879 - WORKS
> V-81881 - WORKS
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#14 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AALK42EK2HX373JTLPELQX3TPHK63ANCNFSM44437F7Q
>
> .
>
--
--------
Aaron Lippold
***@***.***
260-255-4779
twitter/aim/yahoo,etc.
'aaronlippold'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALK42D5ZB4DWPYAQ2DKWR3TPIOCNANCNFSM44437F7Q>
.
--
--------
Aaron Lippold
***@***.***
260-255-4779
twitter/aim/yahoo,etc.
'aaronlippold'
|
V-81883 - WORKS V-81893 - WORKS |
1 similar comment
V-81883 - WORKS V-81893 - WORKS |
|
This is a repost from last one...please post the right list of reviewed controls |
V-81903 - WORKS V-81913 - WORKS V-81923 - WORKS |
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
@HackerShark just pushed an enhanced mongo_command resource. resource should be called as below in the controls
the following input values should in the inspec.yml with the default value seen below
|
Signed-off-by: Rony Xavier <[email protected]>
…ion with sensitive in inspec.yml, added additional inputs to accomodate new mongodb resource in inspec.yml and input.yml Signed-off-by: HackerShark <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
|
|
…81909, 81915, 81919, 81921, 81923 Signed-off-by: HackerShark <[email protected]>
|
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: HackerShark <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
Signed-off-by: HackerShark <[email protected]>
…r the database connection, fixed input name for username in inputs file Signed-off-by: HackerShark <[email protected]>
…input for the database connection Signed-off-by: HackerShark <[email protected]>
…l inputs for the database connection, updated inputs.yml and inspec.yml to accomadate new inputs Signed-off-by: HackerShark <[email protected]>
Signed-off-by: HackerShark <[email protected]>
…. Also did minor touch ups to the inputs in inspec.yml Signed-off-by: HackerShark <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
- made the threshold files well formed yaml - cleaned up local resource Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: GitHub <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
Signed-off-by: Rony Xavier <[email protected]>
@aaronlippold @HackerShark how much work is left for this PR? |
Signed-off-by: Rony Xavier [email protected]