# Change Management

Change management is all about **making changes to a system in a controlled and organized way**. When we want to make a change to a system, **the most important thing is to ensure that the change is approved and authorized**. We don't want any unauthorized changes happening.

There are a few steps involved in the change management process. First, we need to **request the change and get it approved**. Then, we d**ocument the change and test it** to make sure it works properly. We p**resent the testing results to a change control board for review**. Once the change is approved, we **implement it and document the changes** made.

Two important things in change management are **approval and documentation**. Only approved changes should happen, and we need to keep a record of all the changes made. This helps us ensure that everything is done properly and that we can track any changes made to the system.

There are also different environments in change management. The **development environment** is where we create and develop a new system. The **production environment** is where the system is used for day-to-day operations. We also have a **test environment** where we can make changes without affecting the production environment. It's important to have proper approval and separation of duties when making changes in these environments.

Overall, change management is about making changes to a system in a controlled and authorized way, while keeping proper documentation and following a predictable process.

## Audit Trail

* Name
* Timestamp
* Who has given approval
* Before image
* After image

## Change control follows a predictable process

1. **Request** the change
2. **Approve** the change request
3. **Document** the change request
4. **Test** the proposed change
5. **Present** the results to the change-control board
6. **Implement** the change, if approved
7. **Document** the new configuration


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://davidjosearaujo.gitbook.io/online-courses/is-auditing-controls-and-assurance/is-maintenance-and-control/change-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.