Skip to content

Commit a0eecdf

Browse files
authored
Merge pull request #127 from TrevorSmale/u5intro
First pass on U5 Intro
2 parents 9bc39f0 + 86a7d28 commit a0eecdf

File tree

1 file changed

+47
-1
lines changed

1 file changed

+47
-1
lines changed

src/u5intro.md

Lines changed: 47 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,52 @@
11
<div class="flex-container">
22
<img src="https://github.com/ProfessionalLinuxUsersGroup/img/blob/main/Assets/Logos/ProLUG_Round_Transparent_LOGO.png?raw=true" width="64" height="64"></img>
33
<p>
4-
<h1>Under Construction</h1>
4+
<h1>Repos & Patching</h1>
55
</p>
66
</div>
7+
8+
## Overview
9+
10+
Where software originates—and how and when it is updated (patched)—is essential to maintaining system stability and security. Every patch applied to a system must come from a known and trusted source, as introducing changes into a stable environment can have significant consequences. Administrators and engineers ensure that patching is planned and scheduled using verified, trackable repositories and resources.
11+
12+
In this unit, we will examine how this process is implemented in adjacent distributions, where administrators can apply granular control to Red Hat Package Manager (RPM) packages and maintain internal repositories of vetted packages.
13+
14+
## Learning Objectives
15+
16+
1. Understand the importance of package integrity.
17+
2. Understand patching techniques and routines.
18+
3. Understanding automated methods of patching.
19+
4. Understanding custom internal package repositories.
20+
21+
## Relevance and Context
22+
23+
For security engineers, controlling the origin and integrity of software updates is a foundational practice for minimizing attack surfaces. By managing internal repositories and applying strict control over RPM packages, organizations can enforce compliance, prevent supply chain attacks, and ensure only trusted, audited software enters production environments.
24+
25+
## Prerequisites
26+
27+
To be successful, students should have a working understanding of skills and tools including:
28+
29+
1. Basic directory navigation skills.
30+
2. Ability to edit and manage configuration files.
31+
3. Basic knowledge of STIG.
32+
4. Basic knowledge of Ansible.
33+
34+
## Key Terms and Definitions
35+
36+
Patching
37+
38+
Repos
39+
40+
Software
41+
42+
- EPEL
43+
- BaseOS v. Appstream (in RHEL/Rocky)
44+
- Other types you can find?
45+
46+
httpd
47+
48+
patching
49+
50+
GPG Key
51+
52+
DNF/YUM

0 commit comments

Comments
 (0)