Our documentation site page detailing our platform release notes highlights that in the November R1 2025 release of our application, a bug was fixed which is currently causing some confusion.

Prior to this application release there was an option present in the application Menu > Administration > Access Control >
which allowed for the creation, modifying and deletion of Service API accounts.

The same account controls were present for our Securonix internal service accounts. The use case details for of each of our UDS service accounts are provided on our documentation site. The application relies on these accounts for many internal processes and without the accounts many core functions do not work.

For example, without these two ResponseServiceUser accounts - incident generation will not work correctly.
In an effort to follow their company’s cyber security policies by limiting access some customers removed some of these accounts and effectively halted SOC operations.
Currently the ability to create or modify service api accounts is limited to Securonix employees.
Please submit a support ticket if you have a service account needing modified, created, deleted, etc and our Support team will be able to assist with your needs.
