Connect WordPress to ECA
Give ECA governed access to WordPress through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add WordPress to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve WordPress in Runlayer
Add WordPress from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches WordPress’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to WordPress
An admin adds WordPress credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use WordPress from ECA
WordPress’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
WordPress tools in ECA
WordPress reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every WordPress call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more