Latest News
Enhancing Security Measures: Anota's Updated RFC/RFA Process
At Anota, we prioritise the security of our client systems. We constantly evaluate and refine our security management strategies in our commitment to providing a top-notch service. As part of this ongoing effort, we are pleased to announce an important update to our Request for Change/Request for Access (RFC/RFA) process, aimed at reinforcing the security framework for both Anota and our valued customers.
Our RFC/RFA process is designed with three key objectives in mind: ensuring auditability for any changes made to live systems, enhancing security for both Anota and our customers, and building trust by transparently addressing customer requests. This evolution in our support standard operating procedures is a testament to our dedication to continuous improvement and maintaining the highest security standards in our operations.
Key Features of the RFC/RFA Process:
Auditability for Live System Changes
We understand the critical importance of tracking and documenting any alterations made to live systems. Our updated RFC/RFA process ensures comprehensive auditability, providing a clear trail of changes for accountability and transparency.
Enhanced Security Measures
Security is at the core of our operations. The revised RFC/RFA process incorporates additional layers of security to safeguard both Anota and our customers. This proactive approach is aligned with industry best practices, ensuring a robust defence against potential threats.
Building Trust with Customers
Trust is paramount in our client relationships. By implementing the new RFC/RFA process, we aim to instil confidence in our customers. The transparent handling of requests fosters a sense of security and reliability, reinforcing the trust our clients place in us.
RFC/RFA Process Updates
At Anota, we are committed to a culture of continuous improvement, in response to valuable feedback received, we have fine-tuned our RFC/RFA process to streamline and focus on key areas. Moving forward, we will no longer send Request for Change documents for certain routine tasks, including:
Republishing an errored workflow that has unpublished
Restarting errored documents or pushing them back around in a workflow
Reactivating C2M if it turns off
Sending password reset emails (unless the email is being changed)
Generating user lists and audit logs
Installing/Updating a user's desktop apps
Re-establishing LDC connection
Restarting a service
Generating Verto logs
It's important to note that, unless a blanket RFA is in place, an RFA will still be issued for accessing the system to complete the above tasks.
Photos by Mart Production and Aaron Lares on Pexels
