Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
English (US)
US English (US)
CO Spanish (Colombia)
  • Home
  • Cibersecurity and Compliance

Are All Changes Documented and Approved Through Formal Procedures?

Written by Jhon Bairon Figueroa

Updated at November 6th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • wvx Digital Interaction
  • wvx Voice Interaction
  • wvx Conversational AI
  • wvx Control Interactions
  • wvx CRM
  • wvx Agent
  • wvx Studio
  • Cibersecurity and Compliance
  • Release
    wolkvox Manager release wolkvox Agent release wolkvox CRM release
+ More

Table of Contents

Description Features

Description

Wolkvox implements a formal change control process within its Information Security Management System (ISMS), designed to ensure that all modifications to infrastructure, software, or critical configurations are documented, reviewed, and approved before implementation. This approach guarantees traceability, prevents operational errors, and protects the integrity of the production environment. Each change follows a structured workflow that includes risk assessment, approval by responsible parties, and detailed logging, thereby minimizing risks associated with unauthorized or poorly implemented modifications.

 

Features

Formal Change Control Procedure

  • Documented Request: Every change must be recorded in a standardized format, including its justification, scope, potential impact, and responsible parties.
  • Risk Assessment: Before approval, the potential impact of the change on security, availability, and regulatory compliance is analyzed.
  • Hierarchical Approval: Changes require authorization from technical and security teams, depending on their criticality, following a clear chain of responsibility.

 

Traceability and Logging

  • Change Log: Each modification is recorded in a centralized system, with details such as date, time, responsible party, actions taken, and results.
  • Versioning and Rollback: Previous versions of configurations and software are maintained, allowing changes to be reverted in case of incidents or undesired outcomes.
  • Automatic Notifications: Relevant teams are alerted before and after implementation, ensuring transparency and coordination.

 

Benefits for Security and Operations

  • Risk Reduction: By documenting and approving each change, unauthorized modifications that could compromise security or system stability are prevented.
  • Regulatory Compliance: The process complies with requirements from standards such as ISO/IEC 27001, facilitating internal and external audits.
  • Continuous Improvement: The historical record of changes allows for trend analysis, process optimization, and prevention of recurring errors.

 

 

formal approval official procedures

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Are Vendors’ Security Compliance Periodically Evaluated According to ISO 27001 and PCI DSS Controls?
  • Is the Correct Time Synchronization of Servers with Google’s Atomic Clock Audited Periodically?
  • Is the Current Legal Framework for International Data Transfer to the U.S. Validated After the Invalidity of Privacy Shield?

2025 Wolkvox

Information security policy | Privacy Policy

Expand