CompTIA Domain 1.3

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/17

flashcard set

Earn XP

Description and Tags

These flashcards cover key concepts from the CompTIA Security+ (SY0-701) lecture notes, focusing on change management processes and their impact on security.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

18 Terms

1
New cards

Approval Process

Formal authorization procedure for proposed changes to ensure they align with organizational and security policies.

2
New cards

Ownership

Identifies who is responsible for a system, process, or asset to maintain accountability.

3
New cards

Stakeholders

Individuals or groups impacted by or responsible for approving the change.

4
New cards

Impact Analysis

Evaluates how a proposed change affects systems, users, and overall security posture.

5
New cards

Test Results

Provide validation that the change performs as intended without introducing vulnerabilities.

6
New cards

Backout Plan

Defines steps to revert to a previous state if a change causes issues or instability.

7
New cards

Maintenance Window

Scheduled time frame for implementing changes with minimal disruption.

8
New cards

Standard Operating Procedure (SOP)

Established, documented process ensuring consistency and compliance with policies.

9
New cards

Allow Lists / Deny Lists

Control which applications, IPs, or users are permitted or blocked, preventing unauthorized access.

10
New cards

Restricted Activities

Define actions that are prohibited for users or systems to reduce security risks.

11
New cards

Downtime

The period when systems are unavailable during maintenance or unexpected failure, potentially affecting availability.

12
New cards

Service Restart

Required when a service must be stopped and restarted to apply updates or configuration changes.

13
New cards

Application Restart

Necessary to apply updates or configuration changes that impact software performance.

14
New cards

Legacy Applications

Older software that may not support current security standards but remains essential to business operations.

15
New cards

Dependencies

Components or systems that rely on one another; changing one may impact others unintentionally.

16
New cards

Updating Diagrams

Ensures network and system architecture visuals reflect current configurations after changes.

17
New cards

Updating Policies/Procedures

Keeps administrative and technical documentation aligned with operational changes.

18
New cards

Version Control

Tracks and manages changes to files, configurations, or code to ensure integrity, accountability, and rollback capability.