Harness Security FAQs

Updated 1 day ago by Michael Cretzman

This article addresses some frequently asked questions about Harness security features.

Before You Begin

General

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

What security features does Harness provide?

Harness includes:

Are Delegate communications secure?

Yes. All network connections from the Delegate in your local network or VPC to Harness SaaS are HTTPS outbound-only.

See Harness Delegate FAQs.

What data does the Delegate send to the Harness Manager?

The Delegate and the Harness Manager (via SaaS) establish a Secure WebSocket channel (WebSocket over TLS) to send new Delegate task event notifications (not the tasks themselves) and exchange connection heartbeats. In the case that the WebSocket connection is dropped, the Harness Delegate falls back to outbound-only, polling-based task fetch.

  • Heartbeat - The Delegate sends a heartbeat to let the Harness Manager that it is running.
  • Deployment data - The information from the API executions the Delegate performs are sent to the Manager for display in the Deployments page.
  • Time series and log data for Continuous Verification - The Delegate connects to the verification providers you have configured and sends their data to the Manager for display in Harness Continuous Verification.

See Harness Delegate FAQs.

Harness ​Role-based access control (RBAC)

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

How does Harness implement RBAC?

Harness provides Role-Based Access Control (RBAC) via User and User Group Account and Application permissions.

Here is an overview of Harness RBAC. It shows how a user is authenticated via its User settings and authorized via its User Group Account and Application Permissions.

See Managing Users and Groups (RBAC).

How are users added?

When you add Harness users manually, they are added using email addresses. When a user is added, they receive an email invite to the Harness account.

Can users be added dynamically?

Yes, you can leverage your existing user management infrastructure by adding them using OAuth 2.0, LDAP, SAML, and SCIM.

See:

Are there best practices for setting up Harness users?

Yes, you can add users for the most common application release scenario. This involves separate Harness User Groups for app devs, DevOps engineers, and release approvers.

See Set Up RBAC for Application Release Process.

Harness Authentication

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

How are Harness users authenticated?

The default method is email address and password.

You can use several other methods:

Can I adjust password policies?

Yes. You can adjust:

Do you support Single Sign-On (SSO)?

Yes. Uou can enable Harness logins via a range of single sign-on mechanisms. Enable the Allow login via public OAuth providers slider to expose sliders for enabling individual OAuth providers.

See:

Do you support Two-Factor Authentication (2FA)?

Yes. Two-Factor Authentication (2FA) can be managed in two ways:

  • Individual user: You can set up 2FA for your own User Profile without impacting other user accounts.
  • All account users: If you have Manage Account permissions, you can enforce 2FA for all users in Harness. First, you set up 2FA for your own account, and then you can enforce 2FA account-wide in the Harness account's Login Settings.

See Two-Factor Authentication.

Secrets Management

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

How are secrets managed in Harness?

Using common secrets managers. Google Cloud Key Management Service is the default Secrets Manager in Harness.

You can use your own secrets manager with Harness. Harness integrates with all of the common secret managers:

You can configure and make use of other Secrets Managers using the Custom Secrets Manager: Add and Use a Custom Secrets Manager.

This diagram shows how Harness handles secrets:

What kind of secrets are supported?

Harness supports:

Where can I use a secret?

You use secrets in many places in Harness.

You use secrets for credentials for Harness connections to third party integrations, such as cloud platform, git repos, and artifact servers.

You use secrets in Harness connections to target infrastructure, such as SSH keys, and also when passing credentials as part of infrastructure provisioning.

You use secrets in Shell Script Workflow steps, as part of your Bash and PowerShell scripts.

You use secrets in Delegate Profiles, which as scripts Harness runs on the hosts/containers/pods running the Harness Delegate.

How do I create a secret?

In Harness Secrets Management, you pick a type of secret, and then enter the secret or upload the file.

See:

How do I use a secret?

In most cases, you select the encrypted text or file secret you created as part of the credentials or value for a setting.

You can also reference a secret using an expression.

You reference a text secret in a script using the expression ${secrets.getValue("secret_name")}.

You can reference a file secret using the expression ${configFile.getAsBase64("secret_name")} or ${configFile. getAsString("secret_name")}.

See:

Can I limit a secret to certain users?

Yes, you can scope Secrets Managers and their secrets, and then you can decrease the scope the secrets further, if needed.

See:

Can I use my existing secrets in Harness?

Yes. If you already have secrets created in a secrets manager such as HashiCorp Vault or AWS Secrets Manager, you do not need to re-create the existing secrets in Harness.

Harness does not query the secrets manager for existing secrets, but you can create a secret in Harness that references an existing secret in HashiCorp Vault or AWS Secrets Manager.

No new secret is created in those providers. If you delete the secret in Harness, it does not delete the secret in the provider.

See Reference Existing Secret Manager Secrets.

Can I migrate secrets between secrets managers?

Yes. Harness Secrets Management supports the ability to migrate your secrets between secrets managers.

See Migrate Secrets between Secrets Managers.

Are my secrets exposed in logs?

No. Text secrets are not exposed. Harness sanitizes logs and secrets are masked.

See Secrets and Log Sanitization.

File secrets are not masked in Harness logs. As noted above they can be encoded in different formats, but they are not masked from users.

Auditing

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

Can I view all my setup events and changes in Harness?

Yes. Harness provides auditing of events for many Harness account, Applications, and Application components. The Audit Trail enables you to track and review all events in one place.

See Audit Trail.

Can I view deployment history?

The Audit Trail feature covers events in accounts and Applications. To see your deployment history use Harness Manager's Continuous Deployment. See Filtering Deployments.

What can I see in the audit trail?

For each event, you can see details such as:

  • Date and time.
  • User who made the change (Updated By).
  • Underlying REST API call (Event Source).
  • Harness entity and Application affected (Resource).
  • Details summary.
  • YAML diff.

Can I set a date range for an audit?

Yes. You can restrict the Audit Trail's displayed events by date and time, or define detailed filters by these and other criteria.

Can I filter audit events?

Yes, extensively. You can set multiple conditions on the events displayed.

You can save your filters, also.

See Modify the Audit Trail View.

Governance

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

Does Harness provide governance features?

Yes. Harness Pipeline Governance feature enables you to measure how conformant your Pipelines are with your regulatory and operations standards.

See Pipeline Governance.

How do set up governance?

Using Harness Pipeline Governance is a simple process. After you create Workflows that perform or verify some regulatory operation, you describe them using Tags.

Next, you use those Tags to create rules in a Pipeline Governance Standard. You assign a weight to each rule to indicate how important it is.

The standards are used to score the conformance of Pipelines. A score lets you measure the conformance level of the Workflows a Pipeline contains.

You can see the score before you deploy a Pipeline, and during Pipeline Approval steps.

Below is an example of a Pipeline Governance Standard and how a Pipeline Approval step measures conformance with the standard during deployment:

When can I measure conformance?

Before and during deployment.

When you open a Pipeline in Harness, you will see all of the Pipeline Governance Standards available to it, and their individual scores.

Approval steps in Pipelines display the Pipeline Governance Standards available to that Pipeline.

For example, here is an Approval step in a Pipeline displaying two standards and their scores:

IP Whitelisting

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

Can I whitelist IPs for connections to my Harness accounts?

Yes. You can whitelist the IP addresses that may access your Harness account.

You can enter individual IP addresses or a CIDR (Classless Inter-Domain Routing) block.

Once you add and enable an IP Whitelist, only users connecting from the IP address/CIDR block may log into Harness.

See IP Whitelist Management.

Can I whitelist IPs for the Harness Delegate?

No. Harness IP Whitelisting is for user connections to a Harness account. It will not perform IP whitelisting for Harness Delegate connections.

API Keys

For an overview of Harness' support for platforms, methodologies, and related technologies, see Supported Platforms and Technologies.

Can I register Harness with third-party apps?

Yes, by using Harness API keys.

To integrate Harness with some third-party apps, you need to register Harness with the app and then supply a Harness API key.

The API key is a simple encrypted string that other applications can use to access Harness without a private Harness account.

See API Keys.

Is there a limit on how many API calls I can make?

Yes. The Harness API has a usage rate limit of 1 query per second per API Key. If the rate limit is reached, you will receive this response in the API call:

Too Many requests. Throttled. Max QPS: 1.0

Can I use an API key to track deployments?

Yes. Once you have generated an API key in Harness, deployment status can be tracked by making a REST call to Harness.

For more information, see Add a Trigger.


How did we do?