Russians hacked server called 'Solar Winds' (Pentagon, State, Justice, Treasury, NASA, NSA)

[Klaralven]

39. SolarWinds Orion agent requirements

Account Privileges

If you want to deploy agents from the Orion server, the following requirements must be met.

Windows
The account used for remote deployment must have access to the administrative share on the target computer: admin$temp.
User Account Control (UAC) must either be disabled on the target computer, or the built-in Administrator account must be used.
You may need to disable UAC remote restrictions.
Other remote or mass deployment methods do not have the same requirements.

Linux/Unix
An account that can connect remotely through SSH.
An account that can install software and create a user and group.
See Credentials and privileges used on Linux/Unix-based computers for more information.

To deploy a Linux/Unix agent via pull deployment, make sure that the following conditions are met:

Orion Web Console must be accessible from the target Linux computer.
Pull deployment uses wget, curl, or perl to download the installation files from the chosen polling engine.

Agent port requirements
The following ports need to be open both to deploy and to update Orion Agents:

Target computer where the agent is deployed
Server hosting the Orion Platform polling engine
Local agent ports

(followed by quite a list of open ports)

FIPS Support
Starting with Orion Platform 2020.2, Orion Agents support FIPS.

To run FIPS-compliant Orion Agents, enable FIPS on the target computer. FIPS is configured both on the main polling engine and on the polled agent computer so all communication between them is FIPS-compliant.

Remote deployment in FIPS mode is disabled. To run Orion Agents in FIPS-compliant mode, deploy agents manually (Windows or Linux/Unix).

(manual agent deployment would be labor intensive, so FIPS support probably not much used - too bad)

https://documentation.solarwinds.com/en/Success_Center/orionplatform/content/core-agent-requirements-sw476.htm