Last Modified: Dec 20, 2019
See more info
Known Affected Versions:
13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.3, 184.108.40.206, 220.127.116.11, 14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.0.1, 220.127.116.11, 14.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.2, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Aug 20, 2018
The existing AuthZ roles for Application Security are: -- Application Security Administrator (aka ASA aka WASA) -- Application Security Editor (aka ASE aka WASE) ASA is an administrator role and has significant authority to make device-wide changes. On the other hand, ASE is very limited in capabilities.
ASOA will not be able to create or delete Virtual Servers or LTM policies in GUI or in tmsh.
There is a specific demand for a role which can manipulate virtual server association for ASM, but is not an administrator.
You can use the ASA role to perform required tasks.
A new role was added, to be called Application Security Operations Administrator (aka ASOA) which can associate and disassociate ASM policies and Logging Profiles with Virtual Servers. ASOA will have the same capabilities as ASE. Additionally, on the 'Virtual Server:: Security :: Policies' GUI page, ASOA will be able to: -- associate ASM policy with virtual server (which will implicitly create a LTM policy for the association). -- disassociate ASM policy from virtual server (which will implicitly delete the associated L7 policy). -- associate Logging Profile with virtual server. -- disassociate Logging Profile with virtual server. -- associate DoS Profile with virtual server. -- disassociate DoS Profile from virtual server. -- associate Bot Profile with virtual server. -- disassociate Bot Profile from virtual server. -- ASOA will also be able to associate and disassociate these policies/profiles from the 'Security :: Overview :: Summary' page. ASOA will have read access to the virtual server list and LTM policy list in both GUI and tmsh. ASOA will also be able to modify the list of LTM policies associated with a virtual server in both GUI and tmsh.