Security & Privacy
Last updated
Last updated
This is the official documentation of the agent_ruby
Ruby agent.
When logging into the Forest Admin UI in your browser, you will connect to:
the Forest Admin servers to retrieve the Forest Admin layouts configuration,
the Agent to retrieve your data and populate the Forest Admin UI with it.
As your data is transmitted directly from the Agent hosted on your end and the user browser, it never transits through our servers.
Whatever your project plan (free or paying plan), Forest Admin guarantees the respect of data privacy.
In addition, Forest Admin provides an option to completely disable any third-party vendors that could track metadata of your activity available from your browser.
You need to be on a Forest Admin Pro plan ↗ to have access to this feature.
The connection to both the Agent and the Forest Admin Servers are protected using 2 different JWT ↗ signed by 2 different keys:
FOREST_ENV_SECRET
to authenticate all requests made to the Forest Admin Servers
FOREST_AUTH_SECRET
to authenticate all requests made to the Agent
FOREST_ENV_SECRET
is provided by Forest Admin and ensures your Agent interacts with the relevant environment configuration on Forest Admin servers.
FOREST_AUTH_SECRET
is chosen freely by you and is unknown by Forest Admin.
Both secrets must never be disclosed to anyone.
The JWT Data Token contains all the details of the requesting user. On any authenticated request to your Agent, you can use that information to implement custom behaviors.
The IP whitelisting ↗ feature allows you to create a list of trusted IP addresses or IP ranges from which your admin users can both access to the Forest Admin UI and interact with your Agent.
You're free to host your Agent in the cloud architecture you want to be compliant with your security infrastructure (DMZ, VPN, etc.).
We’re already working with companies compliant with the following Industry Standard Certifications.