-
Notifications
You must be signed in to change notification settings - Fork 46
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
Recommendations 1.5 and 1.6 returns N/A #1528
Comments
Thank you for filing this issue.
Dormant users, i.e., users that have never logged in or for some time are a security risk and should be deactivated. |
Thank you very much for your reply. |
I will keep you posted for 1.5 and 1.6. |
@G3N1J4L4C Does your tenacy have IAM domains? 'N/A' for 1.5 and 1.6 will be shown for OCI tenancies that are not yet migrated to IAM domains. |
Yes, all tenancies have IAM all in same region, and all have same result (5+ tenancies). |
Wording is a strange beast. OCI IAM and OCI IAM Domains are two different things. I assume you mean OCI IAM Domains. Do you run version 241206? |
Thx. The script is using the following URL to determine whether domains are enabled: Can you run this and check the |
Hello, I had to change login part of the URL (as I said this region is not connected to cloud.oracle.com) so it's now: Response is as follows (isHenosisEnabled" : true): |
Noted. I filed an internal issue for the script. |
Great, thank you! |
Recommendations 1.5 (Ensure IAM password policy expires passwords within 365 days) and 1.6 (Ensure IAM password policy prevents password reuse) return N/A even though both are fulfilled.

We get the same result no matter what is written in Password policy.
It's added to non-compliant recommendations, giving false negative.
Also, item 1.7 (Ensure MFA is enabled for all users with a console password) returns false negative for users who never logged in. We forced MFA on tenancy level, but newly created users (or users who never logged in) are marked as non-compliant although they do not have any console passwords created.
Is there a way to improve these 3 items, or some workaround?
The text was updated successfully, but these errors were encountered: