This is a table of all of the information systems and information types classified by confidentiality, integrity, availability, and accountability.

The first and foremost thing that you should understand about change management is that all changes have a definitive lifecycle. There is a beginning and an ending. While changes themselves will be never ending, the process that changes move through begins and ends.

A change model is a repeatable way of dealing with change. A change model defines specific steps that will be followed for any given change. Change models can be very simple with limited requirements for pre-approval before a change and post review after a change, or they can be quite complex, with many steps that require both approval and review.

What's the proper way to request a change? Read this for the answer.

Who should be on the change management team? Those that will help move the ball forward and those that play well together, that's who. But that's just the short answer. Read this story to find the long answer.

There are two ways to handle changes to systems. The first method allows anyone to make a change at any time, once the change has been approved. This is an okay (but not great) method for small organizations with very little change to happening to their systems. However, larger organizations with multiple requests for changes to the same system cannot operate this way.

There are seven aspects to creating a robust change control program within any given organization. Those aspects are Acceptance, Awareness, Policies and Procedures, Tools and Automation, Skills and Expertise, Responsibility and Accountability, and Measurement. We'll go over each of them.