Policy Audit Release 1.10 API
April 2, 2026
Before understanding the API release highlights, learn more about the API server URL to be used in your API requests by referring to the Know Your Qualys API Server URL section. For this API Release Notes, <qualys_base_url> is mentioned in the sample API requests.
We have implemented versioning for APIs. For more information on API versioning, refer to the Updates on API Versioning Standards & Deprecation Timelines blog.
PCAS Policy Export API: Confirm Control Definition Updates
| New or Updated API | Updated |
| API Endpoint | /pcas/v3/policy |
| Method | GET |
With this release, the API response includes a new field, controlDefinitionUpdateAvailable, which indicates whether any updates have been made to the existing controls fix values. This helps you identify if any changes are made to the control fix values in the API response, such as updates to the value or description associated with the technology ID.
The response does not show the latest updated control definitions, instead it displays true or false in the controlDefinitionUpdateAvailable field.
Sample - Confirm if a control has updates to its control definitionsSample - Confirm if a control has updates to its control definitions
API Request
curl -X 'GET' '<qualys_base_url>/pcas/v3/policy?policyId=<PolicyId>' -H 'accept: application/json' -H 'Authorization: Bearer <Bearer Token>'
JSON Response
{
"policyId": <PolicyID>,
"policyTitle": "test",
"exported": "26-03-2026 07:41:42",
"isActive": true,
"isLocked": false,
"technologies": [
{
"technologyId": 45,
"technologyName": "Red Hat Enterprise Linux 6.x"
},
{
"technologyId": 80,
"technologyName": "CentOS 7.x"
},
{
"technologyId": 81,
"technologyName": "Red Hat Enterprise Linux 7.x"
},
{
"technologyId": 217,
"technologyName": "Red Hat Enterprise Linux 8.x"
},
{
"technologyId": 261,
"technologyName": "Ubuntu 20.x"
},
{
"technologyId": 372,
"technologyName": "Red Hat Enterprise Linux 9.x"
}
],
"sections": [
{
"sectionNumber": 1,
"sectionHeading": "Untitled",
"controls":
[
{
"controlId": 1071,
"sectionNumber": 1,
"controlNumber": 1,
"statement": "Status of the 'Minimum Password Length' setting",
"criticality": "URGENT",
"isControlDisable": false,
"technologies": [
{
"technologyId": 45,
"technologyName": "Red Hat Enterprise Linux 6.x",
"evaluate": {
"dp": {
"k": "rh06.secman.system.logindefs-min-password-length",
"v": [
"0"
],
"l": 0,
"description": "The following Integer value <b>X</b> indicates the current value of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "To specify password length requirements for new accounts, edit the file \"/etc/login.defs\" and add or correct the following lines: \n\nPASS_MIN_LEN <required value>\n\nexample:\n\nPASS_MIN_LEN 14\n\n\nNote:\nThe DoD requirement is \"14\". If a program consults \"/etc/login.defs\" and also another PAM module (such as \"pam_cracklib\") during a password change operation, then the most restrictive must be satisfied.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": false
},
{
"technologyId": 372,
"technologyName": "Red Hat Enterprise Linux 9.x",
"evaluate": {
"dp": {
"k": "rh06.secman.system.logindefs-min-password-length",
"v": [
"0"
],
"l": 0,
"description": "The following Integer value <b>X</b> indicates the current value of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "To specify password length requirements for new accounts, edit the file \"/etc/login.defs\" and add or correct the following lines: \n\nPASS_MIN_LEN <required value>\n\nexample:\n\nPASS_MIN_LEN 14\n\n\nNote:\nThe DoD requirement is \"14\". If a program consults \"/etc/login.defs\" and also another PAM module (such as \"pam_cracklib\") during a password change operation, then the most restrictive must be satisfied.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": false
},
{
"technologyId": 80,
"technologyName": "CentOS 7.x",
"evaluate": {
"dp": {
"k": "rh06.secman.system.logindefs-min-password-length",
"v": [
"0"
],
"l": 0,
"description": "The following Integer value <b>X</b> indicates the current value of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "To specify password length requirements for new accounts, edit the file \"/etc/login.defs\" and add or correct the following lines: \n\nPASS_MIN_LEN <required value>\n\nexample:\n\nPASS_MIN_LEN 14\n\n\nNote:\nThe DoD requirement is \"14\". If a program consults \"/etc/login.defs\" and also another PAM module (such as \"pam_cracklib\") during a password change operation, then the most restrictive must be satisfied.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": true
},
{
"technologyId": 81,
"technologyName": "Red Hat Enterprise Linux 7.x",
"evaluate": {
"dp": {
"k": "rh06.secman.system.logindefs-min-password-length",
"v": [
"0"
],
"l": 0,
"description": "The following Integer value <b>X</b> indicates the current value of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "To specify password length requirements for new accounts, edit the file \"/etc/login.defs\" and add or correct the following lines: \n\nPASS_MIN_LEN <required value>\n\nexample:\n\nPASS_MIN_LEN 14\n\n\nNote:\nThe DoD requirement is \"14\". If a program consults \"/etc/login.defs\" and also another PAM module (such as \"pam_cracklib\") during a password change operation, then the most restrictive must be satisfied.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": false
},
{
"technologyId": 217,
"technologyName": "Red Hat Enterprise Linux 8.x",
"evaluate": {
"dp": {
"k": "rh06.secman.system.logindefs-min-password-length",
"v": [
"0"
],
"l": 0,
"description": "The following Integer value <b>X</b> indicates the current value of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "To specify password length requirements for new accounts, edit the file \"/etc/login.defs\" and add or correct the following lines: \n\nPASS_MIN_LEN <required value>\n\nexample:\n\nPASS_MIN_LEN 14\n\n\nNote:\nThe DoD requirement is \"14\". If a program consults \"/etc/login.defs\" and also another PAM module (such as \"pam_cracklib\") during a password change operation, then the most restrictive must be satisfied.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": false
},
{
"technologyId": 261,
"technologyName": "Ubuntu 20.x",
"evaluate": {
"dp": {
"k": "deb00.auth.useraccount.password-length",
"v": [
"1"
],
"l": 0,
"description": "This Integer value <b>X</b> indicates the current status of the <b>PASS_MIN_LEN</b> setting as defined within the <b>/etc/login.defs</b> file.",
"op": "ge",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Setting not found"
},
{
"value": "314159265358979",
"set": "1",
"description": "File not found"
}
]
}
},
"remediation": "Configure this setting as per the business requirements or the organization's security policy.",
"rationale": "Among the several characteristics that make 'user identification' via password a secure and workable solution is setting a 'minimum password length' requirement. Each character that is added to the password length squares the difficulty of breaking the password via 'brute force,' which attempts using every combination possible within the password symbol set-space, in order to discover a user's password. While no 'minimum length' can be guaranteed secure, eight (8) is commonly considered to be the minimum for most application access, along with requiring other password security factors, such as increasing the size of the symbol set-space by requiring mixed-cases, along with other forms of password variability creation, increases the difficulty of breaking any password by brute-force attack.",
"controlDefinitionUpdateAvailable": false
}
]
},
]
}
]
}
PCAS Policy Section Control Technology Evaluate API: Retrieve Control Definition Updates
| New or Updated API | Updated |
| API Endpoint | /pcas/v3/policy/section/control/technology/evaluation |
| Method | GET |
With this release, a new input parameter, showUpdatedControlDefinition, is introduced to help view updates made to control definitions for a technology.
If the parameter is set to true, the updated control definition details are retrieved. However, if the parameter is set to false, the response includes the controlDefinitionUpdateAvailable flag, which is set to true to indicate updates are available.
Limitation - If an existing fixed value is updated or deleted, the change does not reflect in the response.
Input ParametersInput Parameters
| Parameter Name | Required / Optional | Data Type | Description |
| showUpdatedControlDefinition={true|false} | Optional | Boolean | Specify 'true' to display the updated control definition details. Specify 'false' to display the controlDefinitionUpdateAvailable flag, indicating updates are available. |
Sample - showUpdatedControlDefinition parameter is set to trueSample - showUpdatedControlDefinition parameter is set to true
API Request
curl -X 'GET' '<qualys_base_url>/pcas/v3/policy/section/control/technology/evaluation?policyId=<PolicyID>§ionNumber=2&controlId=1113&technologyId=45&showUpdatedControlDefinition=true' -H 'accept: application/json' -H 'Authorization: Bearer <Bearer Token>'
JSON Response
{
"technologyId": 45,
"technologyName": "Red Hat Enterprise Linux 6.x",
"evaluate": {
"dp": {
"k": "rh06.secman.general.service-autofs",
"v": [
"3",
"5"
],
"l": 0,
"description": "The following List Integer value(s) <B>X</B> indicate the current states of the <B>autofs</B> service on the host.",
"op": "xeq",
"cd": "is contained in",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Service disabled"
},
{
"value": "314159265358979",
"set": "1",
"description": "Service not found"
},
{
"value": "314159265358980",
"set": "1",
"description": "Enabled"
}
]
}
},
"remediation": "Run the following command to configure 'autofs' service as per business needs and organization's security policies.\n#Check the status\n$ chkconfig --list autofs\n# Use the following command to enable/disable the service\n$chkconfig [service name ] [off|on]\n# Example\n$ chkconfig autofs on",
"rationale": "The 'autofs' (NFS automount daemon) allows non-root users to connect to the Network File System-based information on demand, as if the HDD were mounted locally. As NFS has weak authentication, this may cause a reduced level of protection for sensitive data and it also suffers from the potential of a DoS condition, due to forgotten 'record-locking,' this capability should be disabled/restricted as appropriate to the needs of the business.",
}
Sample - controlDefinitionUpdateAvailable parameter is set to falseSample - controlDefinitionUpdateAvailable parameter is set to false
API Request
curl -X 'GET' '<qualys_base_url>/pcas/v3/policy/section/control/technology/evaluation?policyId=<PolicyID>§ionNumber=2&controlId=1113&technologyId=45&showUpdatedControlDefinition=false' -H 'accept: application/json' -H 'Authorization: Bearer <Bearer Token>'
JSON Response
{
"technologyId": 45,
"technologyName": "Red Hat Enterprise Linux 6.x",
"evaluate": {
"dp": {
"k": "rh06.secman.general.service-autofs",
"v": [
"3",
"5"
],
"l": 0,
"description": "The following List Integer value(s) <B>X</B> indicate the current states of the <B>autofs</B> service on the host.",
"op": "xeq",
"cd": "is contained in",
"fv": [
{
"value": "161803399999999",
"set": "1",
"description": "Service disabled"
},
{
"value": "314159265358979",
"set": "1",
"description": "Service not found"
}
]
}
},
"remediation": "Run the following command to configure 'autofs' service as per business needs and organization's security policies.\n#Check the status\n$ chkconfig --list autofs\n# Use the following command to enable/disable the service\n$chkconfig [service name ] [off|on]\n# Example\n$ chkconfig autofs on",
"rationale": "The 'autofs' (NFS automount daemon) allows non-root users to connect to the Network File System-based information on demand, as if the HDD were mounted locally. As NFS has weak authentication, this may cause a reduced level of protection for sensitive data and it also suffers from the potential of a DoS condition, due to forgotten 'record-locking,' this capability should be disabled/restricted as appropriate to the needs of the business.",
"controlDefinitionUpdateAvailable": true
}
New Oracle Linux Virtualization Manager Record API
| New or Updated API | New |
| API Endpoint | /api/2.0/fo/auth/olvm/ |
| Method | GET and POST |
| DTD Changes | Yes |
With this release, we now support Oracle Linux Virtualization Manager (OLVM) Record API. The new Oracle Linux Virtualization Manager Record API lets you create, update, delete, and list OLVM authentication records.
User permissions for this API are the same as other authentication record APIs.
Input ParametersInput Parameters
| Parameter Name | Required / Optional | Data Type | Description |
| action={action} | Required | String | Specify create, update, delete (using POST) or list (using GET or POST). |
| ids={value} | Required to update or delete record | Integer | Record IDs to update/delete. Specify record IDs and/or ID ranges (for example, 1359-1407). Multiple entries are comma-separated. |
| title={value} | Required to create record, optional to update record | String | A title for the record. The title must be unique. |
| ips={value} | Required to create record | Integer | The IP address(es) the server will log into using the records credentials. Multiple entries are comma-separated. |
| login_type={basic|vault} | Required | String | The login type is basic by default. You can choose vault (for vault based authentication). Set to vault if a third party vault is used to retrieve the password.
For vault based authentication, vault parameters need to be provided in the record. |
| username={value} | Required | String | The user account to be used for authentication to the OLVM database. |
| password={value} | Required | String | The password corresponding to the user account defined in the record for authentication. |
| vault_id={value} | Required | Integer | The vault ID from where you want to retrieve the password. |
| vault_type={value} | Required | Integer | The third party vault to be used to retrieve the password for login. |
| {vault parameters} | Required | Integer | Vault specific parameters required depend on the vault type you have selected. For details on the vault parameters, refer to to Vault Parameters page. |
| port={value} | Optional | Integer | The port number that the OLVM record instance. |
| ssl_verify_with_host={1|0} | Optional | Boolean | SSL verification. Set to 1 if you want to verify the server’s certificate is valid and trusted. |
| hosts={value} | Required if ssl_verify=1 | String | A list of FQDNs for all host IP addresses on which a custom SSL certificate signed by a trusted root CA is installed. |
Sample - Create OLVM RecordSample - Create OLVM Record
API Request
curl -s -S -H 'X-Requested-With:curl' -u "<username>:<password>" -d "action=create&title=olvm&login_type=basic&username=<username>&password=<password>&port=443" "<qualys_base_url>/api/2.0/fo/auth/olvm/"
API Response
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE BATCH_RETURN SYSTEM "<qualys_base_url>/api/2.0/batch_return.dtd">
<BATCH_RETURN>
<RESPONSE>
<DATETIME>2026-03-27T13:10:32Z</DATETIME>
<BATCH_LIST>
<BATCH>
<TEXT>Successfully Created</TEXT>
<ID_SET>
<ID>8419776</ID>
</ID_SET>
</BATCH>
</BATCH_LIST>
</RESPONSE>
</BATCH_RETURN>
Sample - Update OLVM RecordSample - Update OLVM Record
API Request
curl -s -S -H 'X-Requested-With:curl' -u "<username>:<password>" \
-d "action=update&ids=8419776&title=olvm&username=<username>&password=<password> \
"<qualys_base_url>/api/2.0/fo/auth/olvm/"
API Response
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE BATCH_RETURN SYSTEM "<qualys_base_url>/api/2.0/batch_return.dtd">
<BATCH_RETURN>
<RESPONSE>
<DATETIME>2026-03-27T13:11:55Z</DATETIME>
<BATCH_LIST>
<BATCH>
<TEXT>Successfully Updated</TEXT>
<ID_SET>
<ID>8419776</ID>
</ID_SET>
</BATCH>
</BATCH_LIST>
</RESPONSE>
</BATCH_RETURN>
Sample - Delete OLVM RecordSample - Delete OLVM Record
API Request
curl -s -S -H 'X-Requested-With:curl' -u "<username>:<password>" -d "action=delete&ids=8393421" "<qualys_base_url>/api/2.0/fo/auth/olvm/"
API Response
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE BATCH_RETURN SYSTEM "<qualys_base_url>/api/2.0/batch_return.dtd">
<BATCH_RETURN>
<RESPONSE>
<DATETIME>2026-03-27T13:10:02Z</DATETIME>
<BATCH_LIST>
<BATCH>
<TEXT>Successfully Deleted</TEXT>
<ID_SET>
<ID>8393421</ID>
</ID_SET>
</BATCH>
</BATCH_LIST>
</RESPONSE>
</BATCH_RETURN>
Sample - List OLVM RecordsSample - List OLVM Records
API Request
curl -s -S -H 'X-Requested-With:curl' -u "<username>:<password>" -d "action=list" "<qualys_base_url>/api/2.0/fo/auth/olvm/"
API Response
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE AUTH_OLVM_LIST_OUTPUT SYSTEM "<qualys_base_url>/api/2.0/fo/auth/olvm/auth_olvm_list_output.dtd">
<AUTH_OLVM_LIST_OUTPUT>
<RESPONSE>
<DATETIME>2026-03-27T13:06:50Z</DATETIME>
<AUTH_OLVM_LIST>
<AUTH_OLVM>
<ID>8360487</ID>
<TITLE><![CDATA[olvm]]></TITLE>
<USERNAME><![CDATA[admin@internal]]></USERNAME>
<IP_SET>
<IP>10.10.10.100</IP>
</IP_SET>
<PORT><![CDATA[443]]></PORT>
<LOGIN_TYPE><![CDATA[basic]]></LOGIN_TYPE>
<NETWORK_ID>0</NETWORK_ID>
<CREATED>
<DATETIME>2026-03-24T05:57:37Z</DATETIME>
<BY>rstec_rs</BY>
</CREATED>
<LAST_MODIFIED>
<DATETIME>2026-03-24T05:57:37Z</DATETIME>
</LAST_MODIFIED>
</AUTH_OLVM>
<AUTH_OLVM>
<ID>8369474</ID>
<TITLE><![CDATA[OLVM_Test_Update_RM]]></TITLE>
<USERNAME><![CDATA[admin@internal]]></USERNAME>
<IP_SET>
<IP_RANGE>1.1.1.1-1.1.1.100</IP_RANGE>
</IP_SET>
<PORT><![CDATA[443]]></PORT>
<SSL_VERIFY_WITH_HOST><![CDATA[0]]></SSL_VERIFY_WITH_HOST>
<LOGIN_TYPE><![CDATA[basic]]></LOGIN_TYPE>
<NETWORK_ID>0</NETWORK_ID>
<CREATED>
<DATETIME>2026-03-24T10:05:41Z</DATETIME>
<BY>rstec_rs</BY>
</CREATED>
<LAST_MODIFIED>
<DATETIME>2026-03-24T10:44:22Z</DATETIME>
</LAST_MODIFIED>
</AUTH_OLVM>
<AUTH_OLVM>
<ID>8370573</ID>
<TITLE><![CDATA[OLVM_KK]]></TITLE>
<USERNAME><![CDATA[root]]></USERNAME>
<IP_SET>
<IP>10.10.10.100</IP>
</IP_SET>
<PORT><![CDATA[443]]></PORT>
<SSL_VERIFY_WITH_HOST><![CDATA[0]]></SSL_VERIFY_WITH_HOST>
<LOGIN_TYPE><![CDATA[basic]]></LOGIN_TYPE>
<NETWORK_ID>0</NETWORK_ID>
<CREATED>
<DATETIME>2026-03-24T11:32:24Z</DATETIME>
<BY>rstec_rs</BY>
</CREATED>
<LAST_MODIFIED>
<DATETIME>2026-03-24T11:32:24Z</DATETIME>
</LAST_MODIFIED>
</AUTH_OLVM>
</AUTH_OLVM_LIST>
</RESPONSE>
</AUTH_OLVM_LIST_OUTPUT>
DTD UpdateDTD Update
A DTD for the Oracle Linux Virtualization Manager Record API has been added.
<platform API server>/api/2.0/fo/auth/auth_records.dtd
DTD output for the Oracle Linux Virtualization Manager Record API is as follows:
DTD Output
<!-- QUALYS AUTH_RECORDS_OUTPUT DTD -->
<!-- $Revision$ -->
<!ELEMENT AUTH_RECORDS_OUTPUT (REQUEST?, RESPONSE)>
<!ELEMENT REQUEST (DATETIME, USER_LOGIN, RESOURCE, PARAM_LIST?, POST_DATA?)>
<!ELEMENT DATETIME (#PCDATA)>
<!ELEMENT USER_LOGIN (#PCDATA)>
<!ELEMENT RESOURCE (#PCDATA)>
<!ELEMENT PARAM_LIST (PARAM+)>
<!ELEMENT PARAM (KEY, VALUE)>
<!ELEMENT KEY (#PCDATA)>
<!ELEMENT VALUE (#PCDATA)>
<!-- if returned, POST_DATA will be urlencoded -->
<!ELEMENT POST_DATA (#PCDATA)>
<!ELEMENT RESPONSE (DATETIME, AUTH_RECORDS?, WARNING_LIST?)>
<!ELEMENT AUTH_RECORDS (AUTH_UNIX_IDS?, AUTH_WINDOWS_IDS?, AUTH_ORACLE_IDS?, AUTH_ORACLE_LISTENER_IDS?, AUTH_SNMP_IDS?, AUTH_MS_SQL_IDS?, AUTH_IBM_DB2_IDS?, AUTH_VMWARE_IDS?, AUTH_MS_IIS_IDS?, AUTH_APACHE_IDS?, AUTH_IBM_WEBSPHERE_IDS?, AUTH_HTTP_IDS?, AUTH_SYBASE_IDS?, AUTH_MYSQL_IDS?, AUTH_TOMCAT_IDS?, AUTH_ORACLE_WEBLOGIC_IDS?, AUTH_DOCKER_IDS?, AUTH_POSTGRESQL_IDS?, AUTH_MONGODB_IDS?, AUTH_PALO_ALTO_FIREWALL_IDS?, AUTH_VCENTER_IDS?, AUTH_JBOSS_IDS?, AUTH_MARIADB_IDS?, AUTH_INFORMIXDB_IDS?, AUTH_MS_EXCHANGE_IDS?, AUTH_ORACLE_HTTP_SERVER_IDS?, AUTH_GREENPLUM_IDS?, AUTH_MICROSOFT_SHAREPOINT_IDS?, AUTH_KUBERNETES_IDS?, AUTH_SAPIQ_IDS?,AUTH_SAP_HANA_IDS?, AUTH_NEO4J_IDS?, AUTH_AZURE_MS_SQL_IDS?, AUTH_NETWORK_SSH_IDS?, AUTH_NGINX_IDS?, AUTH_INFOBLOX_IDS?, AUTH_BIND_IDS?, AUTH_CISCO_APIC_IDS?, AUTH_CASSANDRA_IDS?, AUTH_MARKLOGIC_IDS?, AUTH_OLVM_IDS?)>
<!ELEMENT AUTH_UNIX_IDS (ID_SET)>
<!ELEMENT AUTH_WINDOWS_IDS (ID_SET)>
<!ELEMENT AUTH_ORACLE_IDS (ID_SET)>
<!ELEMENT AUTH_ORACLE_LISTENER_IDS (ID_SET)>
<!ELEMENT AUTH_SNMP_IDS (ID_SET)>
<!ELEMENT AUTH_MS_SQL_IDS (ID_SET)>
<!ELEMENT AUTH_IBM_DB2_IDS (ID_SET)>
<!ELEMENT AUTH_VMWARE_IDS (ID_SET)>
<!ELEMENT AUTH_MS_IIS_IDS (ID_SET)>
<!ELEMENT AUTH_APACHE_IDS (ID_SET)>
<!ELEMENT AUTH_IBM_WEBSPHERE_IDS (ID_SET)>
<!ELEMENT AUTH_HTTP_IDS (ID_SET)>
<!ELEMENT AUTH_SYBASE_IDS (ID_SET)>
<!ELEMENT AUTH_MYSQL_IDS (ID_SET)>
<!ELEMENT AUTH_TOMCAT_IDS (ID_SET)>
<!ELEMENT AUTH_ORACLE_WEBLOGIC_IDS (ID_SET)>
<!ELEMENT AUTH_DOCKER_IDS (ID_SET)>
<!ELEMENT AUTH_POSTGRESQL_IDS (ID_SET)>
<!ELEMENT AUTH_MONGODB_IDS (ID_SET)>
<!ELEMENT AUTH_PALO_ALTO_FIREWALL_IDS (ID_SET)>
<!ELEMENT AUTH_VCENTER_IDS (ID_SET)>
<!ELEMENT AUTH_JBOSS_IDS (ID_SET)>
<!ELEMENT AUTH_MARIADB_IDS (ID_SET)>
<!ELEMENT AUTH_INFORMIXDB_IDS (ID_SET)>
<!ELEMENT AUTH_MS_EXCHANGE_IDS (ID_SET)>
<!ELEMENT AUTH_ORACLE_HTTP_SERVER_IDS (ID_SET)>
<!ELEMENT AUTH_GREENPLUM_IDS (ID_SET)>
<!ELEMENT AUTH_MICROSOFT_SHAREPOINT_IDS (ID_SET)>
<!ELEMENT AUTH_KUBERNETES_IDS (ID_SET)>
<!ELEMENT AUTH_SAPIQ_IDS (ID_SET)>
<!ELEMENT AUTH_SAP_HANA_IDS (ID_SET)>
<!ELEMENT AUTH_NEO4J_IDS (ID_SET)>
<!ELEMENT AUTH_AZURE_MS_SQL_IDS (ID_SET)>
<!ELEMENT AUTH_NETWORK_SSH_IDS (ID_SET)>
<!ELEMENT AUTH_NGINX_IDS (ID_SET)>
<!ELEMENT AUTH_INFOBLOX_IDS (ID_SET)>
<!ELEMENT AUTH_BIND_IDS (ID_SET)>
<!ELEMENT AUTH_CISCO_APIC_IDS (ID_SET)>
<!ELEMENT AUTH_CASSANDRA_IDS (ID_SET)>
<!ELEMENT AUTH_MARKLOGIC_IDS (ID_SET)>
<!ELEMENT AUTH_OLVM_IDS (ID_SET)>
<!ELEMENT WARNING_LIST (WARNING+)>
<!ELEMENT WARNING (CODE?, TEXT, URL?, ID_SET?)>
<!ELEMENT CODE (#PCDATA)>
<!ELEMENT TEXT (#PCDATA)>
<!ELEMENT URL (#PCDATA)>
<!ELEMENT ID_SET (ID|ID_RANGE)+>
<!ELEMENT ID (#PCDATA)>
<!ELEMENT ID_RANGE (#PCDATA)>
<!-- EOF -->
Issues Addressed
The following reported and notable customer issues are fixed in this release:
| Component/Category | Description |
| SCA | When the user was launching a Cloud Perimeter scan from the SCA application, an error stating 'License does not exist' was displayed. Since users with SCA-only subscriptions cannot perform Cloud Perimeter scans, the scan option should not appear for these subscriptions (SCA application and API). Relevant code changes have been made to fix the issue. |