You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run ORCA against the same tenant several times in quick succession, I get the results in different sorting and sometimes with different results. Although no one has changed any settings in the tenant or the security settings in the meantime.
Run 1
Run 2
1: Why does it say 'Disabled' behind the entry if it is not 'Disabled' at all?
2: The names of the policies sometimes differ in the ORCA report and in the security portal. Why?
3: If a policy is 'Disabled', its setting still counts (usually positively) towards the score. Why is that? Why are these entries not excluded?
Why are the numbers behind the 'Strict Preset Security Policy' settings and the 'Standard Preset Security Policy' setting? And why are some policies (with different numbers) listed several times, although they only exist once in the tenant?
Regarding point 1:
Regarding point 2:
The text was updated successfully, but these errors were encountered:
When I run ORCA against the same tenant several times in quick succession, I get the results in different sorting and sometimes with different results. Although no one has changed any settings in the tenant or the security settings in the meantime.
Run 1
Run 2
1: Why does it say 'Disabled' behind the entry if it is not 'Disabled' at all?
2: The names of the policies sometimes differ in the ORCA report and in the security portal. Why?
3: If a policy is 'Disabled', its setting still counts (usually positively) towards the score. Why is that? Why are these entries not excluded?
Why are the numbers behind the 'Strict Preset Security Policy' settings and the 'Standard Preset Security Policy' setting? And why are some policies (with different numbers) listed several times, although they only exist once in the tenant?
Regarding point 1:
Regarding point 2:
The text was updated successfully, but these errors were encountered: