Applocker and Host-based intrusion detection/prevention system for off domain Vaults.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Applocker and Host-based intrusion detection/prevention system for off domain Vaults.

L0 Member

Hello all,

 

I am standing up a new CyberArk environment and going over the STIGs my security has sent me to remediate. There are 2 that I would like to get exceptions for but cannot find a specific document to point to as a reference, any help would be appreciated.

1) WN22-00-000080 - Windows Server 2022 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.

2) WN22-00-000120 - Windows Server 2022 must have a host-based intrusion detection or prevention system.

 

I want to say something along the lines of "Cyberark has proprietary server hardening implemented that locks down the server to only specific users at specific workstations" but i dont think thats a strong enough case, if anyone has something I can either point to or has a better justification please let me know.

 

Thanks!

3 REPLIES 3

L7 Applicator

Hi @Colin Brodie​ 

 

Yes for both of these STIG requirements, you can justify exceptions by referencing CyberArk’s built-in security controls and hardening measures.

 

CyberArk implements server hardening and privileged access controls that meet or exceed the intent of this STIG by

 

For WN22-00-000080:

 

You can mention that only CyberArk designated users can access the server through PVWA and PSM.

 

PSM enforces session isolation and records the privileged sessions when executed.

 

The Vault server runs in a locked-down mode, restricting execution to only CyberArk approved services and applications.

 

For WN22-00-000120:

 

You can mention that Vault uses proprietary encryption and access controls.

 

PSM recordings records all privileged activities, providing visibility into potential security events.

 

If you have PTA, you can mention that PTA detects suspicious privileged activity.

 

Hope it helps !

 

 

 

 

 

 

 

 

 

L6 Presenter
  • WN22-00-000080 - Windows Server 2022 must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs
    • Vault - stringently hardened machine, strongly recommended to not have any third party applications installed on the Vault. Only Vault related software and utilities (PrivateArk). Not even a backup solution is recommended directly on the vault, recommended to use CyberArk's utilities on a different server to pull data
    • PSM - Inherently uses AppLocker to whitelist applications that can be executed on the PSM machine - satisfies the requirement already
    • PVWA / CPM - They don't have any such restriction on them as part of the CyberArk installation and config process as far as I know. The hardening scripts and GPOs ensure they're hardened to a CyberArk recommended security standard but no explicit software whitelisting here
    • More here (I'm linking for the PVWA, but the CPM and PSM have similar sections):
      • https://docs.cyberark.com/pam-self-hosted/14.4/en/content/pas%20inst/pvwa-install-post-installation.htm
      • https://docs.cyberark.com/pam-self-hosted/14.4/en/content/pas%20inst/pvwa-hardening-task-descriptions.htm
      • https://docs.cyberark.com/pam-self-hosted/14.4/en/content/pas%20inst/pvwa-hardening-post-hardening-tasks.htm
      • https://docs.cyberark.com/pam-self-hosted/14.4/en/content/pas%20inst/pvwa-install-gpo-settings-in-domain.htm

 

  • WN22-00-000120 - Windows Server 2022 must have a host-based intrusion detection or prevention system.
    • Vault - This is a highly secure server. It shouldn't be domain-joined, shouldn't have DNS entries, and the hardening takes control of the Firewall to ensure the only communication to and from this server takes place on TCP 1858, so locked down pretty well
    • That said, nothing in the installation and hardening speaks directly to this requirement of an IDS / IPS. Organizations definitely do set up their agents on the component servers, but you'll have to test to ensure no functionality breaks

 

This is what I could think of and Malhar has mentioned very helpful points as well. You could wait to see what inputs other community members have!

L4 Transporter

Hi @Colin Brodie​ 

 

Since several community members answered your question, please let us know if these solutions addressed your query.

If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.

 

Thank you, Liad.

  • 124 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!