[6.36.1.0] 2026-11-16
- Version: 6.36.1.0 (minor release)
- Date: 2026-11-16
- Requires: RegScale 6.36.0.0 or newer
Summary
RegScale Orchestration Hub (ROH) automates the import and export of data between RegScale and other systems, using integrations and commands that you configure.
This release makes ROH refuse unencrypted connections in production. It also protects more of the API, the log stream and the webhook receiver. Classic integration jobs now run on a newer build of the improved, upgraded command line interface (CLI). ROH now keeps job names, descriptions and commands that use non-Latin characters, instead of turning them into question marks.
Several changes stop ROH from starting until you update its configuration. Read "Before you upgrade" first.
What's new
Encrypted connections in production
When ROH starts in production, it now tests its connections. If a test fails, ROH stops and the log names the setting to fix. The log never shows the setting's value. "Production" means your environment setting is production, which is the default, or that debug is off.
- Redis. ROH refuses a remote Redis address that is not encrypted or has no password. It also refuses a Redis server certificate that does not match, including in cluster mode.
- SQL Server. ROH requires an encrypted connection. It refuses a server certificate that does not match the host name. A certificate with a wildcard name, such as *.database.windows.net, now matches the server name.
- Other RegScale services. ROH refuses an unencrypted web (http) address to another machine, for your ROH address and your RegScale address. A service account with an http RegScale address fails its runs until you correct the address.
- Weak or sample keys. ROH will not start in production with a weak signing, encryption or metrics key, or with a placeholder key copied from an example file. These rules also apply when debug is on and the environment setting is not set.
Sign-in and sign-out
- Signing out now ends your session on the server. Before, the Logout button cleared only the browser, and the session stayed valid until it expired.
- Session tokens are stored encrypted. ROH keeps the RegScale session token in encrypted form in Redis. Each user with an open session signs in again once after the upgrade. Changing SECRETS_ENCRYPTION_KEY now ends all open sessions.
- SAML sign-in is tied to the browser that starts it. Security Assertion Markup Language (SAML) sign-in now finishes only in the browser that began it. If someone finishes it in another browser, or reuses an earlier sign-in attempt, ROH answers "unauthorized" (401). SAML sign-in needs HTTPS (encrypted web traffic) because the cookie it uses is marked Secure.
Log stream and webhooks
- The session token is no longer in the web address. A client of the log stream now sends the session token in its first message instead. ROH refuses a web address that carries a token. The access logs, including nginx's, no longer record anything after the question mark in a web address.
- Webhook size and rate limits. A webhook request can be up to 1 MiB (1,048,576 bytes). One sender address can make 30 requests each second, with a burst of 60. ROH rejects a larger request (413) and any request above the rate (429).
- Webhook checks now run before ROH reads the request body. An unknown webhook gets "not found" (404). A webhook that has a secret but no X-Webhook-Signature header gets "unauthorized" (401). Before, a body that was not valid JSON (a standard data format) got 422 first.
- Old stored webhook headers are cleaned up. A database migration removes every stored webhook header except content-length, content-type, user-agent and x-request-id. Before, some rows written by an earlier rollout still held an Authorization header.
Approved hosts only
ROH now contacts only approved hosts. A source can use Amazon S3, Azure Blob Storage and Google APIs endpoints. A service account can use only the scheme, host and port of your RegScale address. An operator can approve more hosts. Saving a source or service account with any other host fails (400), and a job that uses a refused source or service account fails.
The source connection test now runs as a background task (a worker task). It stops after 55 seconds, and a tenant can run two tests at the same time.
Operator-only routes and a separate failed-task queue for each tenant
Seven administration routes now need an operator token. A tenant session no longer works for them. If no operator token is set, ROH answers "forbidden" (403) to every caller of these routes.
The dead letter queue is the list of tasks that failed for good. ROH now keeps a separate one for each tenant and app. A tenant sees and retries only its own entries. A new operator route, GET /api/v1/operator/dlq/tasks, lists entries across all tenants.
Classic integration jobs run on a newer build of the improved, upgraded CLI
Classic ROH integration jobs now run on a newer build of the improved, upgraded CLI.
- Two new Tanium commands.
tanium sync_benchmarksandtanium sync_stig_benchmarkssync Tanium benchmark findings and Defense Information Systems Agency Security Technical Implementation Guide (DISA STIG) findings to RegScale security checklists. - Tanium Sync CIS Benchmarks. Each checklist goes on the endpoint asset in the security plan that
regscale_idnames. If an endpoint has no asset in that plan, ROH skips its finding, even when another plan holds a copy of that asset. Run Sync Assets first. - Prisma software bill of materials (SBOM). When a job sets
bulk_downloadto false, ROH now passes--no-bulk-downloadto theprisma sync_sbomcommand, and the command syncs one resource. It needsresource_id,resource_type(host or image) andasset_id(1 or more). Before, ROH sent nothing and the CLI downloaded in bulk. - More problems now show as failed jobs. The CLI now reports more errors through an exit code, which is the number a program returns when it finishes. ROH marks every exit code other than 0 as failed, so a job that passed before can now fail. For example, a missing required setting such as
wizUrlends with exit code 5, and aprisma sync_sbomdownload failure ends with exit code 4 or 6. - Microsoft Entra sync settings. The
azure_adsync commands now list five optional secrets:adTenantAdminGroups,adGroupOverrides,adIncludeDisabledUsers,adFollowNestedGroupsandadCascadeRemoveThresholdPct. A secret set can now store them.
What's fixed
- Job names, descriptions and commands keep non-Latin characters. Before, ROH saved a character outside the database code page, such as a Chinese character, as a question mark. Rows that ROH already changed stay changed. A job command can hold up to 512 characters, and an emoji counts as two.
- Split jobs. A split job runs as several parallel pieces, called chunks. When it reached its limit on parallel chunks, it used to send a chunk with a negative limit. ROH now makes fewer, larger chunks instead.
- Amazon Web Services (AWS) Elastic Block Store (EBS) volumes. An EBS volume asset now has the AWS account ID in its key, so Security Hub findings link to the asset.
Security hardening and patching
Minor bug fixes and enhancements
Before you upgrade
Read each row. A row marked "ROH will not start" stops the deployment until you act. The first three columns say what to do. The last column holds the settings and details for the person doing the work.
| What changed | Who is affected | What to do | Settings and details |
|---|---|---|---|
| Four database changes (migrations) run at startup and cannot be reversed. | Everyone who upgrades | Back up the ROH database before you upgrade. After ROH starts, read the startup log for warnings. | Migration 048 removes stored webhook headers that ROH does not keep. Migrations 049, 050 and 051 change the job command, description and name columns to Unicode types. If a migration cannot change a column, it writes a WARNING that starts with the migration number and changes nothing, and ROH still records it as done. Run the statement from the WARNING by hand. Migration 051 changes nothing when the change would give two jobs in one app the same name. |
| Containers must upgrade together. | Everyone who upgrades | Upgrade all ROH containers at the same time. | During a rolling upgrade, a request that reaches a container of the earlier release can fail until all containers run 6.36.1.0. |
| A remote Redis needs encryption and a password. (ROH will not start otherwise.) | Deployments with a remote Redis | Use an encrypted Redis address with a password. | Use a rediss:// address with a password in REDIS_URL, ROH_BROKER_URL and ROH_RESULT_BACKEND. Addresses for localhost, 127.0.0.1 and ::1 are exempt. If you cannot use encryption, set ROH_ALLOW_INSECURE_REDIS=true. A cluster that uses bare IP addresses for its nodes, such as Azure Managed Redis in open source software (OSS) cluster mode, needs REDIS_TLS_VERIFY=false. If your Redis certificate comes from a private certificate authority, set REDIS_TLS_CA_FILE to the CA bundle. |
| SQL Server needs encryption and a matching certificate. (ROH will not start otherwise.) | Deployments that use SQL Server | Use a database host name that appears in the server certificate. An IP address does not match. | The host name in DATABASE_URL must be a name in the server certificate. A certificate from a private CA fails with error 20002 and the log text "TDS server connection failed". To trust a private CA, mount the CA bundle and set SSL_CERT_FILE. This setting replaces the trust store for every OpenSSL client in the process, including HTTPS calls to RegScale. Or mount your own freetds.conf and set FREETDSCONF. Your file replaces the shipped file (/etc/roh/freetds.conf) and must set encryption = require. A deployment with its own Compose or orchestration files must mount the file itself. The user with ID 1001 must be able to read it. DATABASE_ALLOW_UNENCRYPTED=true turns off the SQL Server rules. |
| Service addresses must use https. (ROH will not start otherwise.) | All deployments | Use https addresses for your ROH, RegScale and Next Gen service addresses. | Set https addresses for ROH_PUBLIC_URL, REGSCALE_URL and the two Next Gen service addresses, or set the matching opt-in setting, for example ROH_PUBLIC_URL_ALLOW_INSECURE_HTTP or REGSCALE_ALLOW_INSECURE_HTTP. Use an opt-in only when something else protects the connection, such as a service mesh. |
| Weak and sample keys are refused. (ROH will not start otherwise.) | Docker Compose stacks that use the default keys from the example files, and any deployment with a weak key | Replace default and weak keys with strong ones before you start ROH. | SECRET_KEY needs at least 32 characters. SECRETS_ENCRYPTION_KEY needs exactly 32. ROH_PREFIX_NAMESPACE must not be local_dev. SECRET_KEY, SECRETS_ENCRYPTION_KEY and METRICS_TOKEN must not hold a placeholder from an example file. An empty METRICS_TOKEN is accepted. These rules also apply when DEBUG is on and ENVIRONMENT is not set. If you change SECRET_KEY or SECRETS_ENCRYPTION_KEY, all sessions end, and ROH cannot decrypt credentials stored under the old key, so enter them again. |
| Seven routes need an operator token. | Operators | Set an operator token. | Set ROH_OPERATOR_TOKEN to a random value of at least 32 characters. It must differ from METRICS_TOKEN, SECRET_KEY and SECRETS_ENCRYPTION_KEY. The routes are POST /api/v1/monitoring/recovery/run, GET /api/v1/monitoring/beat/schedule, POST /api/v1/monitoring/beat/trigger/{schedule_name}, GET /api/v1/monitoring/redis/info, POST /api/v1/commands/cache/clear, POST /api/v1/documentation/mapping/reload and POST /api/v1/analytics/metrics/cleanup. Callers send the token in the X-ROH-Operator-Token header. Entries that were in the dead letter queue before the upgrade no longer show in the tenant routes. Only the operator route with scope=legacy shows them. |
| Non-default hosts must be listed. | Sources on MinIO, a private endpoint or a proxy, and service accounts for a RegScale host other than REGSCALE_URL | List each extra host ROH should be allowed to contact, then restart the application and the workers. | List a source's host in SOURCE_EGRESS_EXTRA_HOSTS. List a service account's RegScale host in REGSCALE_EXTRA_HOSTS. Each takes a comma-separated list, and a name such as *.example.com matches any host under example.com. At startup, ROH writes a WARNING with the IDs of stored sources it refuses. A source that resolves to a private address, such as an Azure Private Endpoint, needs its full host name in the list. A worker must read the celery queue for the connection test. Without one, every test ends after 60 seconds. |
| Webhook limits apply. | Webhook senders | Keep each webhook request to 1 MiB or less, and no more than 30 requests each second from one address. | Behind a load balancer, all senders share one address, so they share one limit. |
| The log stream and SAML sign-in changed. | Custom clients only. The ROH web interface already sends the new messages. | Update any custom log stream or SAML client. | Send the session token in the first WebSocket message. The message is a JSON object with type auth and a token field. Send after_id without percent-encoding, and keep the first frame to 8,192 bytes or less. A larger frame closes the connection with code 1009, on every WebSocket route. nginx answers 403 for a log stream web address that has a token parameter or a percent sign in the query. A custom SAML client must keep the cookie that the init call sets and send it with the callback. |
| Classic jobs can now fail where they passed before. | Everyone with classic jobs | Review your classic jobs after the upgrade. | A prisma sync_sbom job with bulk_download set to false needs resource_id, resource_type and asset_id. |
| Image builds check their inputs. | Anyone who builds their own ROH image | Pass a checksum with each pinned download version. | The build fails if FRONTEND_VERSION is latest or a download does not match its digest. Pass FRONTEND_SHA256 with FRONTEND_VERSION, and the matching checksum setting with the version setting for the Next Gen tool download. |
