Ascent 2.16.5

More control over integration visibility — Integration access can now be limited to people who hold View permission, so only the right team members can see how integrations are set up.

Stronger access control on forwarders — Access policies are now enforced on forwarders, keeping forwarder access aligned with the same permission rules used across the platform.

Access to one source extension no longer reveals all source extensions.
Fixed an issue where access permissions could occasionally behave differently across parts of a deployment. Permissions now stay consistent across the board.

Smarter checks when setting up policies — When creating a policy, Ascent now confirms that the target resource is valid and actually exists, helping prevent policies that point to something that isn't there.

Some checks that previously failed to load screenshots now display them correctly.
The "Hide Empty Group" checkbox in check views now works as expected.

Components

Version

Flash

v3.21.3

Coffee

v3.22.5

ASM

13.40.0

NG Private Agent

1.0.9

Check Execution Container: Browser

fpr-c-130n-10.2.1-716-r-2025.04.02-0-base-2.0.0

Check Execution Container: Zebratester

zt-7.5a-p0-r-2025.04.02-0-base-1.2.0

Check Execution Container: Runbin

runbin-2025.04.17-0-base-2.2.1

Check Execution Container: Postman

postman-2025.04.17-0-base-1.4.1

Bnet (Chrome Version)

10.2.2 (Chrome 130)

Zebratester

7.5A

ALT

6.13.3.240

IronDB

1.5.1

Last updated 2 months ago

Was this helpful?