Network and System Administration

Chapter One

Network and system administration

What is Network?
 A network is an arrangement of devices, including computers, servers, routers, switches,
and other hardware and software parts, that are connected to one another in order to enable
data sharing and communication. To put it simply, a network enables resource sharing and
communication between several devices.

What is System Administration?

System administration refers to the management and maintenance of computer systems, networks,
and servers to ensure their smooth and reliable operation. System administrators, also known as
sysadmins, are responsible for the efficient functioning, security, and availability of computer
systems and networks within an organization.

The role of a system administrator typically includes the following responsibilities:

 Installation and Configuration: System administrators set up new computer systems,

servers, and network devices. They install and configure operating systems, software
applications, and necessary services to meet the organization's requirements.
 System Monitoring: Sysadmins monitor the performance and health of computer
systems, networks, and servers. They use various tools and techniques to track system
resources, identify bottlenecks, and ensure optimal performance. Monitoring includes
checking for hardware failures, software issues, network connectivity, and security
vulnerabilities.
 User Management: System administrators handle user accounts and permissions. They
create and manage user accounts, assign access rights, and ensure proper authentication
and authorization mechanisms are in place. They may also manage user directories, email
accounts, and other user-related services.

Prepared by Michael B. 1
 Network and System Administration

 Security 4Management: System administrators play a crucial role in ensuring the

security of computer systems and networks. They implement security measures such as
firewalls, intrusion detection systems, antivirus software, and access controls. They
monitor for security breaches, investigate incidents, and take appropriate actions to
mitigate risks and protect sensitive data.
 Backup and Recovery: Sysadmins establish backup and recovery strategies to protect
data and ensure business continuity. They schedule and perform regular backups of critical
systems and data, and they develop procedures for data restoration in the event of hardware
failures, disasters, or other incidents.
 System Updates and Patching: System administrators keep computer systems and
software up to date by applying security patches, updates, and bug fixes. They stay
informed about the latest vulnerabilities and advisories and apply necessary updates to
protect systems against known threats.
 Troubleshooting and Issue Resolution: Sysadmins diagnose and resolve technical
issues, including hardware failures, software glitches, network connectivity problems, and
user-reported incidents. They employ troubleshooting techniques, analyze system logs,
and collaborate with other IT teams or vendors to resolve complex problems.
 Documentation: System administrators maintain documentation related to system
configurations, procedures, and troubleshooting guides. They document changes, updates,
and system architecture for future reference and knowledge sharing.

System administration is a critical role in ensuring the reliable and secure operation of computer
systems and networks. It requires a combination of technical knowledge, problem-solving skills,
attention to detail, and the ability to adapt to evolving technologies and security threats. Effective
system administrators play a vital role in supporting the IT infrastructure and enabling smooth
business operations.

1. Objectives/Goals:
 Ensure the availability and reliability of computer systems and networks.
 Enhance system and network performance and optimize resource utilization.
 Maintain the security and integrity of systems and data.
 Provide technical support to users and resolve issues promptly.

Prepared by Michael B. 2
 Network and System Administration

 Implement and enforce IT policies, standards, and procedures.

 Plan for future growth and scalability of systems and networks.
 Continuously improve processes and adopt new technologies to enhance efficiency.

2. Challenges:
 Dealing with complex and diverse hardware and software configurations.
 Managing and securing a large number of user accounts and access rights.
 Protecting systems and networks from evolving security threats and attacks.
 Balancing system performance with limited resources and budget constraints.
 Keeping up with rapidly changing technologies and industry standards.
 Managing and troubleshooting issues in distributed and remote environments.
 Ensuring compliance with regulations and organizational policies.
 Dealing with unexpected system failures or disasters and implementing effective backup
and recovery strategies.

3. Unix-like Systems Vs. Windows Systems:

Unix-like Systems:
 Unix-like systems, such as Linux and macOS, are based on the Unix operating system.
 They are known for their stability, security, and flexibility.
 They provide a command-line interface (CLI) and offer powerful scripting capabilities.
 Unix-like systems are widely used in server environments and for development purposes.
 They have a rich ecosystem of open-source software packages and tools.

Windows Systems:
 Windows is a popular operating system developed by Microsoft.
 It is known for its user-friendly graphical user interface (GUI).
 Windows systems are widely used in desktop and client-server environments.
 They have extensive compatibility with a wide range of software applications and games.
 Windows provides comprehensive support for Microsoft products and services.

Prepared by Michael B. 3
 Network and System Administration

 Windows systems are often used in enterprise environments due to their Active Directory
and Group Policy features.

4. Linux Distributions and UIs:

 Linux is an open-source operating system kernel, and there are various distributions
(distros) that package the Linux kernel with different software packages and
configurations.
 Examples of popular Linux distributions include Ubuntu, Fedora, Debian, CentOS, and
Arch Linux.
 Each distribution may have its own package manager, software repositories, and default
desktop environment.
 Desktop environments provide graphical user interfaces (GUIs) and consist of window
managers, panels, and other components.
 Common Linux desktop environments include GNOME, KDE Plasma, Xfce, and
Cinnamon.

5. Linux Operations Review:

 Linux operations involve various tasks, including system administration, software
installation and management, configuration, troubleshooting, and maintenance.
 System administration tasks include managing user accounts, permissions, and file
systems.
 Package managers, such as APT (Advanced Package Tool) or YUM (Yellowdog Updater,
Modified), are used to install, update, and remove software packages.
 Configuration files in Linux are often stored in plain text format, and administrators can
edit them using text editors or command-line tools.
 Troubleshooting in Linux may involve analyzing log files, using command-line utilities for
network diagnostics, and checking system resources.
 Linux offers powerful command-line tools and scripting capabilities, allowing
administrators to automate tasks and perform advanced system operations.

Prepared by Michael B. 4
 Network and System Administration

It's important to note that the information provided here is a general overview, and specific
details may vary depending on the specific operating systems, distributions, and environments
being used.

1.5.1.1 Single-rooted hierarchy, Seamless and Extensible File systems:

 The file system hierarchy in Unix-like systems follows a single-rooted structure, with a
single root directory ("/") from which all other directories and files branch out.
 This hierarchy allows for a logical organization of files and directories, making it easier
to navigate and manage the file system.
 Unix-like file systems support seamless integration of different storage devices and file
systems into the overall hierarchy.
 The extensible nature of file systems means that additional file systems can be mounted
and integrated into the existing hierarchy, expanding the available storage space.

1.5.1.2 Mounting Additional File systems:

 In Unix-like systems, additional file systems can be mounted to the existing file system
hierarchy using the "mount" command.
 Mounting involves attaching a file system to a specific directory (mount point) in the
hierarchy, making its contents accessible at that location.
 The "mount" command requires specifying the device or file system to mount, the mount
point, and any additional options or parameters.
 To mount an additional file system in Linux using the `mount` command, you need to
know the file system type and the device or partition that you want to mount. Here's an
example of how to mount an additional file system:
1. Identify the device or partition: Run the `lsblk` command to list the available block devices
and identify the device or partition you want to mount. Note down the device name, such
as `/dev/sdb1`.

Prepared by Michael B. 5
 Network and System Administration

2. Create a mount point: Choose or create a directory where you want to mount the file
system. For example, you can create a directory called “/mnt/myfiles” using the command
“sudo mkdir /mnt/myfiles”.
3. Mount the file system: Use the `mount` command to mount the file system. The
command syntax is as follows:
sudo mount -t <file_system_type> <device> <mount_point>
Replace `<file_system_type>` with the actual file system type of the device (e.g., ext4, ntfs, xfs),
`<device>` with the device or partition you identified in step 1 (e.g., `/dev/sdb1`), and
`<mount_point>` with the directory you created in step 2 (e.g., `/mnt/myfiles`).

For example, to mount an ext4 file system on `/dev/sdb1` to the `/mnt/myfiles` directory, you
would use the following command:

sudo mount -t ext4 /dev/sdb1 /mnt/myfiles

4. Verify the mount: You can use the `df -h` command to verify that the file system is
mounted. It will display a list of mounted file systems, including the newly mounted one.
df -h
Look for the device you mounted and ensure that the mount point is listed.
5. Access the mounted file system: You can now access the mounted file system by
navigating to the mount point directory (`/mnt/myfiles` in the example). You can read,
write, and modify files on the mounted file system like any other directory on your
system.
6. Unmount the file system: When you're done with the mounted file system, you should
unmount it before removing the device or partition. Use the `umount` command followed
by the mount point:
sudo umount /mnt/myfiles
Remember to replace `/mnt/myfiles` with the actual mount point you used.

By following these steps, you can mount additional file systems in Linux using the `mount`
command.

The command `sudo apt-get install util-linux` is used in Linux-based operating systems with the
Advanced Package Tool (APT) package management system, such as Debian and Ubuntu, to
install the `util-linux` package.

Prepared by Michael B. 6
 Network and System Administration

The `util-linux` package is a collection of essential utilities for managing various aspects of a Linux
system. It provides a set of command-line tools that perform essential system tasks and provide
important functionalities. Some of the utilities included in `util-linux` are:

1. `mount` and `umount`: These utilities are used for mounting and unmounting file systems,
such as hard drives, partitions, and network file systems.
2. `fdisk` and `parted`: These tools allow for disk partitioning and management, enabling the
creation, deletion, and resizing of disk partitions.
3. `blkid`: This utility provides information about block devices and their associated file
systems, including UUIDs and filesystem types.
4. `login` and `su`: These utilities handle user authentication and login sessions, allowing
users to log in to the system or switch to a different user account.
5. `kill` and `killall`: These commands are used to terminate running processes or send
specific signals to processes.
6. `hwclock`: This utility is used to read and set the hardware clock (real-time clock) of the
system.
7. `agetty` and `login`: These tools manage virtual console logins and provide a login prompt
on virtual terminals.

By running the `sudo apt-get install util-linux` command, you request the package manager to
download and install the `util-linux` package and its associated utilities on your system. The `sudo`
command is used to execute the installation with administrative privileges, ensuring that the
necessary system modifications can be made.

Once the installation is complete, you can use the installed `util-linux` utilities to perform various
system administration tasks, manage disk partitions, handle logins and user sessions, and work
with block devices in your Linux system.

Certainly! Let's break down the command `$sudo apt-get install util-linux` into its components and
explain each part in detail:

Prepared by Michael B. 7
 Network and System Administration

- `$`: The dollar sign at the beginning is often used to represent the command prompt in Linux
documentation or examples. It is not part of the actual command and should not be included when
running the command.

 `sudo`: The `sudo` command stands for "Superuser Do" and is used to execute a command
with administrative privileges. It allows a regular user to perform actions that typically
require root or administrative access.
 `apt-get`: `apt-get` is a command-line package management tool in Debian-based Linux
distributions, such as Ubuntu. It is used to handle package operations, including
installation, removal, and upgrading.
 `install`: The `install` command is an argument passed to `apt-get` and specifies that we
want to install a package.
 `util-linux`: `util-linux` is the name of the package that we want to install. It refers to a
collection of utilities for managing various aspects of a Linux system, as explained in the
previous response.
When you run the command `$sudo apt-get install util-linux`, here's what happens:
1. The `sudo` command prompts you to enter your password. After entering the password, it
verifies your credentials and allows the subsequent command (`apt-get`) to run with
administrative privileges.
2. The `apt-get` command contacts the package manager and checks the available package
lists and repositories to locate the `util-linux` package.
3. If the `util-linux` package is found, `apt-get` downloads the package from the repository to
your system.
4. Once the package is downloaded, `apt-get` installs it on your system. This involves
unpacking the package files, configuring the utilities, and making any necessary system
modifications.
5. During the installation process, you may see progress indicators or prompts asking for your
confirmation or input. Follow the instructions or provide the necessary responses if
prompted.
6. Once the installation is complete, the `util-linux` package and its associated utilities are
now available on your system. You can utilize these utilities by running their respective
commands from the command line.

Prepared by Michael B. 8
 Network and System Administration

Overall, the command `$sudo apt-get install util-linux` is used to install the `util-linux` package,
which provides essential utilities for managing and administering a Linux system.

1.5.1.3 File system Object-Oriented Design and File System Standard:

 Unix-like file systems are designed with an object-oriented approach, where directories,
files, and other objects are represented as objects in the file system.
 Each object has attributes such as permissions, ownership, size, and timestamps.
 The Filesystem Hierarchy Standard (FHS) is a set of guidelines that define the directory
structure, naming conventions, and file placement for Unix-like systems.
 FHS helps ensure compatibility and consistency across different distributions and
simplifies system administration and software development.

1.5.1.4 Unix File and Directory Permissions:

 Unix-like systems use a permission system to control access to files and directories.
 Each file and directory has three types of permissions: read, write, and execute, which
can be granted or denied for three different user categories: owner, group, and others.
 Permissions are represented using a combination of letters and symbols, such as "r" for
read, "w" for write, and "x" for execute.
 The "chmod" command is used to modify permissions, allowing administrators to grant
or revoke access rights.

1.5.2 Essential Shell Commands:

1.5.2.1 Basic File Manipulation Commands and Directory Navigation Commands:
 "ls" command: Lists files and directories in the current directory or a specified directory.
 "cd" command: Changes the current directory.
 "pwd" command: Prints the current working directory.
 "mkdir" command: Creates a new directory.
 "rmdir" command: Removes an empty directory.
 "cp" command: Copies files and directories.
 "mv" command: Moves or renames files and directories.

Prepared by Michael B. 9
 Network and System Administration

 "rm" command: Removes files and directories.

 "cat" command: Displays the contents of a file.

1.5.2.2 Advanced File Manipulation Commands (Init, Processes, and Threads):

 "ps" command: Shows information about running processes.
 "top" command: Displays real-time information about system processes and resource
usage.
 "kill" command: Terminates a running process.
 "bg" and "fg" commands: Manages background and foreground processes.
 "jobs" command: Lists the running or stopped background processes.
 "nice" command: Adjusts the priority of a process.
 "grep" command: Searches for specific patterns within files or command outputs.

1.5.3 Advanced Shell Features:

 Shell scripting: Allows writing and executing scripts to automate tasks and combine
multiple commands.
 Command substitution: Replaces a command with its output in another command or
assignment.
 Redirection: Enables redirecting input and output streams to or from files or other
commands.
 Pipes: Connects the output of one command as the input to another command, allowing
for data processing and manipulation.
 Environment variables: Stores values that can be accessed by processes and scripts,
influencing their behavior.
 Job control: Manages the execution and control of multiple processes simultaneously,
including background and foreground processes.
 Shell customization: Provides options to customize the shell's behavior, prompt, aliases,
and environment settings using configuration files such as ".bashrc" or ".bash_profile".

Prepared by Michael B. 10
 Network and System Administration

Chapter Two
2.1.1 User and Group Concepts, and User Private Group Scheme:

User and Group Concepts:

Prepared by Michael B. 11
 Network and System Administration

In account and security administration, the concepts of users and groups play a fundamental role
in managing access and permissions within a system.

 Users: Users are individual accounts that represent individuals or entities accessing the
system. Each user is assigned a unique username or ID, which serves as their identifier
within the system. User accounts have associated authentication credentials (such as
passwords) that verify their identity during login. Users can be assigned specific roles,
permissions, and access rights based on their responsibilities or job functions.

 Groups: Groups are collections of user accounts that share common access requirements
or permissions. By grouping users together, administrators can assign permissions at the
group level, simplifying access control management. For example, a group named
"Developers" may have access rights to programming tools and source code repositories,
while a group named "Managers" may have access to sensitive financial information.

User Private Group Scheme (User Private Group):

The User Private Group (UPG) scheme is a user administration approach used in some Unix-like
operating systems, such as Linux. In this scheme, when a new user account is created, a
corresponding group with the same name is automatically created. This group serves as the
primary group for the user. For example, if a user account "Chala" is created, a group named
"Chala" is also created.

The UPG scheme provides a level of isolation and security by ensuring that each user has their
own dedicated primary group. It prevents users from inadvertently accessing or modifying files
of other users by setting appropriate permissions and ownership within the user's private group.

2.1.2 User Administration, Modifying Accounts, and Group Administration:

User Administration:

User administration involves creating, managing, and maintaining user accounts within the
system. This includes tasks such as:

Prepared by Michael B. 12
 Network and System Administration

 Creating User Accounts: Administrators create new user accounts by assigning a unique
username or ID and configuring authentication credentials. This typically involves setting
up passwords or other authentication factors.
 Modifying User Accounts: User accounts may need to be modified to reflect changes in
user information or access requirements. Administrators can update account details, such
as changing usernames, modifying contact information, or adjusting user-specific
settings.
 Disabling or Deleting User Accounts: When a user leaves an organization or when an
account is no longer needed, administrators disable or delete user accounts to revoke
access. Proper procedures should be followed to ensure data integrity and security during
the account disabling or deletion process.

Group Administration:

Group administration involves creating, managing, and maintaining groups within the system.
This includes tasks such as:

 Creating Groups: Administrators create groups based on access requirements or specific

roles within the organization. For example, groups can be created for departments,
project teams, or functional units.
 Adding Users to Groups: Users are added to specific groups to grant them access rights
and permissions associated with those groups. By adding users to groups, administrators
can manage access control more efficiently.
 Modifying Group Memberships: As user roles or responsibilities change, administrators
can modify group memberships by adding or removing users from groups. This ensures
that users have appropriate access privileges based on their current requirements.

2.1.3 Password Aging and Default User Files:

Password Aging:

Prepared by Michael B. 13
 Network and System Administration

Password aging is a security measure that enforces regular password changes to enhance system
security. The password aging policy sets rules for password expiration, minimum password age,
and maximum password age.

 Password Expiration: Administrators define a time period after which a user's password
must be changed. For example, a password may expire every 90 days, requiring users to
set a new password.
 Minimum and Maximum Password Age: Administrators can set restrictions on how soon
a user can change their password after the last change (minimum password age) and how
long a password can be used before it must be changed (maximum password age).

Default User Files:

When a new user account is created, default user files can be provided to ensure a consistent user
environment and initial configuration. These files serve as templates or starting points for user-
specific settings and configurations.

Default user files can include:

 Shell Initialization Files: These files define environment variables, aliases, and other shell
settings when a user logs in. Examples include .bashrc, .bash_profile, or .profile.
 Default Configuration Files: Some applications or services may have default configuration
files that are copied to the user's home directory. These files can be customized by the user
to suit their preferences or requirements.
 Skeleton Files: Skeleton files are templates that are used to create initial files or
directories for new user accounts. These files may contain documentation, example files,
or directory structures that are common to all users.

By providing default user files, administrators can ensure consistency, ease of use, and a
predefined environment for users when they first log in to the system.

Overall, account and security administration plays a crucial role in managing user accounts,
groups, access controls, and security measures within a system. This involves creating and
Prepared by Michael B. 14
 Network and System Administration

modifying user accounts, managing groups, implementing password aging policies, and providing
default user files to ensure a secure and controlled system environment.

Privileges refer to the specific rights and permissions granted to users or groups within a system.
These privileges determine the actions or operations that users are allowed to perform on the
system or specific resources. Here are some common types of privileges:

1. Administrative Privileges:

 Superuser/Administrator: This privilege grants unrestricted access and control over the
entire system. Administrators typically have the authority to manage user accounts,
install software, modify system configurations, and perform other administrative tasks.

2. System Privileges:

 System Configuration: Users with system configuration privileges can modify system-
wide settings and parameters. This includes configuring network settings, managing
system services, adjusting security policies, and modifying system behavior.

3. File and Directory Privileges:

 Read: Users with read privileges can access and view the contents of files or directories.
 Write: Users with write privileges can create, modify, or delete files or directories.
 Execute: Users with execute privileges can run executable files or scripts.
 Delete: Users with delete privileges can remove files or directories.
 Modify Permissions: Users with modify permissions privileges can change the access
permissions of files or directories.
4. Network Privileges:

 Network Configuration: Users with network configuration privileges can modify

network settings, such as IP addresses, DNS configurations, firewall rules, and network
interface configurations.
 Network Access: Users with network access privileges can connect to specific networks
or access network resources.

5. Application Privileges:

Prepared by Michael B. 15
 Network and System Administration

 Application Administration: Users with application administration privileges can manage

specific applications, including installation, configuration, and customization.
 Data Management: Users with data management privileges can create, modify, or delete
data within applications.
 Reporting and Analytics: Users with reporting and analytics privileges can generate
reports, access analytical tools, and extract insights from application data.

6. Database Privileges:

 Database Administration: Users with database administration privileges can manage

databases, including creating, modifying, and deleting databases, tables, and other database
objects.
 Data Manipulation: Users with data manipulation privileges can perform operations such
as inserting, updating, and deleting data within databases.
 Data Querying: Users with data querying privileges can retrieve and view data from
databases.

7. Communication Privileges:

 Communication Configuration: Users with communication configuration privileges can

manage communication settings, such as email configurations, messaging services, and
collaboration tools.
 Communication Access: Users with communication access privileges can send and receive
messages, access communication platforms, and participate in collaborative activities.

It's important to note that the specific privileges available within a system may vary depending on
the operating system, network environment, and the applications or services installed. Privileges
should be granted based on the principle of least privilege, where users are given only the necessary
privileges required to perform their tasks, minimizing the risk of unauthorized access or misuse of
resources.

Enforcing access control policies involves implementing and maintaining mechanisms that ensure
that only authorized users or entities are granted access to resources, systems, or sensitive

Prepared by Michael B. 16
 Network and System Administration

information. Access control policies define the rules and criteria for granting or denying access
based on factors such as user identities, roles, permissions, and other attributes. Here are some key
aspects of enforcing access control policies:

1. Authentication:

Authentication is the process of verifying the identity of a user or entity requesting access to a
system or resource. It involves validating credentials, such as usernames and passwords, biometric
data, or cryptographic keys. By enforcing strong authentication mechanisms, such as multi-factor
authentication (MFA), organizations can enhance the security of access control.

2. Authorization:

Authorization determines the actions or operations that an authenticated user or entity is allowed
to perform. It involves granting or denying access based on predefined rules and policies.
Authorization mechanisms may include role-based access control (RBAC), attribute-based access
control (ABAC), or access control lists (ACLs). By properly configuring and maintaining
authorization rules, organizations can ensure that users have appropriate privileges and
permissions.

3. Access Control Lists (ACLs):

ACLs are lists associated with resources, such as files, directories, or network devices, that specify
which users or groups are granted or denied access. ACLs define permissions, such as read, write,
execute, or delete, for each user or group. By managing and regularly reviewing ACLs,
organizations can control fine-grained access to resources.

4. Least Privilege:

The principle of least privilege (PoLP) states that users should be given minimal privileges
necessary to perform their tasks. Enforcing least privilege ensures that users have only the
permissions required to fulfill their job responsibilities, reducing the risk of unauthorized access
or accidental misuse of resources.

5. Regular Auditing and Monitoring:

Prepared by Michael B. 17
 Network and System Administration

Enforcement of access control policies should be accompanied by regular auditing and monitoring.
This involves reviewing access logs, analyzing user activities, and identifying any anomalies or
unauthorized access attempts. By monitoring access events, organizations can detect and respond
to potential security incidents or policy violations.

6. Security Awareness and Training:

Enforcing access control policies also requires educating users about the importance of security
practices and promoting security awareness. Users should be trained on safe computing practices,
the risks associated with unauthorized access, and the proper handling of sensitive information.
Regular security awareness programs help reinforce access control policies and foster a security-
conscious culture within an organization.

7. Periodic Reviews and Updates:

Access control policies should be periodically reviewed and updated to align with changing
business needs, technological advancements, and evolving threats. Regular assessments of access
control mechanisms help identify gaps, ensure compliance with regulations or industry standards,
and adapt to new security challenges.

Enforcing access control policies is essential for protecting critical systems, sensitive data, and
resources. By implementing robust authentication, authorization mechanisms, and following
security best practices, organizations can mitigate the risks associated with unauthorized access
and maintain a secure computing environment.

Configuring security settings involves customizing various parameters, options, and controls
within a system or software application to establish a secure environment. These settings are
designed to protect against potential security threats, vulnerabilities, and unauthorized access. Here
are some key aspects of configuring security settings:

1. User Authentication:

Configuring user authentication settings involves defining the requirements and mechanisms for
verifying the identity of users accessing the system. This may include options such as password
complexity requirements, multi-factor authentication (MFA), biometric authentication, or
integration with external identity providers.

Prepared by Michael B. 18
 Network and System Administration

2. Access Controls:

Access control settings determine who is granted access to specific resources or functionalities
within a system. This includes configuring permissions, roles, and privileges for users or user
groups. Access controls can be based on factors such as user roles, job responsibilities, or specific
attributes.

3. Encryption:

Encryption settings involve enabling and configuring encryption mechanisms to protect sensitive
data at rest and in transit. This includes options such as full disk encryption, secure communication
protocols (e.g., HTTPS, SSL/TLS), or database encryption. Configuring encryption settings helps
ensure that data remains confidential and protected from unauthorized access.

4. Network Security:

Configuring network security settings involves implementing measures to secure network

communications and protect against unauthorized access or malicious activities. This may include
configuring firewalls, intrusion detection and prevention systems (IDPS), virtual private networks
(VPNs), or network segmentation to isolate sensitive resources.

Configuring security update and patch settings involves establishing processes and preferences
for applying security updates and patches to the system and software components. This includes
5. Security Updates and Patching:

configuring automatic update settings, scheduling regular update checks, and defining policies
for testing and deploying updates to mitigate vulnerabilities and address security flaws.

6. Logging and Auditing:

Configuring logging and auditing settings involves specifying what events and activities should
be logged and monitored within the system. This includes enabling and configuring audit trails,
defining log retention policies, and setting up alerts or notifications for security-related events.
Effective logging and auditing help in detecting and investigating security incidents and
supporting forensic analysis.

7. Security Policies and Compliance:

Prepared by Michael B. 19
 Network and System Administration

Configuring security settings also involves defining and enforcing security policies and
compliance requirements within the system. This includes configuring password policies, defining
acceptable use policies, specifying data retention or disposal policies, and ensuring compliance
with relevant regulations or industry standards (e.g., GDPR, PCI DSS, HIPAA).

8. Application Security:

Configuring application security settings involves implementing measures to protect software

applications from common security risks and vulnerabilities. This may include options such as
input validation, secure coding practices, session management, error handling, and secure
configuration of application frameworks or platforms.

9. Physical Security:

Configuring physical security settings involves implementing measures to protect physical access
to systems, data centers, or other critical infrastructure. This includes options such as access
controls, surveillance systems, alarm systems, and environmental controls (e.g., fire suppression,
temperature regulation).

10. User Education and Awareness:

Configuring security settings also involves promoting user education and awareness about security
best practices. This includes providing training, guidelines, and resources to help users understand
their security responsibilities, recognize social engineering or phishing attempts, and follow secure
computing practices.

Configuring security settings is an ongoing process that requires regular updates, monitoring, and
adjustment to address emerging threats and changing business requirements. By customizing
security settings based on industry best practices and the specific needs of the organization, a
robust security posture can be established to protect against potential risks and vulnerabilities.

There are numerous potential threats that can pose risks to computer systems, networks, and data.
These threats can vary in nature and impact, and they continuously evolve as technology advances.
Here are some common types of potential threats:

1. Malware:

Prepared by Michael B. 20
 Network and System Administration

Malware refers to malicious software designed to disrupt, damage, or gain unauthorized access to
computer systems or networks. This includes viruses, worms, Trojans, ransomware, spyware, and
adware. Malware can be distributed through email attachments, malicious websites, infected
software, or compromised networks.

2. Phishing and Social Engineering:

Phishing is a technique used by attackers to trick individuals into revealing sensitive information,
such as login credentials, credit card details, or personal data. Social engineering involves
manipulating individuals through psychological manipulation or deception to gain unauthorized
access or information. These attacks often occur through deceptive emails, fraudulent websites, or
phone calls.

3. Network Attacks:

Network attacks target vulnerabilities in network infrastructure or protocols to gain unauthorized

access, disrupt services, or intercept data. Examples include Distributed Denial of Service (DDoS)
attacks, Man-in-the-Middle (MitM) attacks, packet sniffing, or network intrusion attempts.

4. Data Breaches:

Data breaches involve unauthorized access or disclosure of sensitive or confidential information.

These breaches can occur due to various factors, including cyberattacks, insider threats, poor
security practices, or compromised systems. The stolen data can be used for identity theft,
financial fraud, or other malicious purposes.

5. Insider Threats:

Insider threats refer to risks posed by individuals within an organization who have authorized
access to systems and data but misuse or abuse their privileges. This can include intentional or
unintentional actions that compromise security, such as data theft, sabotage, or accidental data
leaks.

6. Vulnerabilities and Exploits:

Software vulnerabilities are weaknesses or flaws in software applications or systems that can be
exploited by attackers to gain unauthorized access or control. Exploits are specific techniques or

Prepared by Michael B. 21
 Network and System Administration

tools that take advantage of these vulnerabilities. It is crucial to promptly apply security patches
and updates to mitigate these risks.

7. Physical Threats:

Physical threats involve risks to hardware, infrastructure, or physical access to systems. This can
include theft, unauthorized access to data centers or server rooms, damage from natural disasters,
or physical tampering with devices.

8. Advanced Persistent Threats (APTs):

APTs are sophisticated and targeted attacks that aim to gain persistent unauthorized access to
systems or networks over an extended period. These attacks typically involve multiple stages,
including reconnaissance, infiltration, and data exfiltration. APTs are often associated with well-
funded or state-sponsored attackers.

9. Mobile and IoT Security Risks:

With the increasing use of mobile devices and Internet of Things (IoT) devices, security risks have
expanded to include vulnerabilities in mobile applications, insecure wireless connections, and
compromised IoT devices. These risks can lead to unauthorized access, data leakage, or control of
connected devices.

10. Supply Chain Attacks:

Supply chain attacks target the software or hardware supply chain by compromising trusted
vendors or suppliers. Attackers inject malicious code or tampered components into the supply
chain, which can be distributed widely and compromise the integrity of systems or applications.

It's important to note that this is not an exhaustive list, and new threats continue to emerge as
technology evolves. Implementing a comprehensive approach to cybersecurity, including robust
security measures, regular updates, employee education, and proactive monitoring, can help
mitigate these threats and protect systems and data from potential harm.

Default user files refer to the files and directories that are automatically created or provided by the
operating system or software applications when a new user account is created. The specific default

Prepared by Michael B. 22
 Network and System Administration

user files can vary depending on the operating system and software installed. Here are some
examples of common default user files:

1. User Profile Folder: In Windows operating systems, a user profile folder is created for each
user account. It typically contains various default files and directories, including:

 Documents: A folder where users can store their personal documents and files.
 Downloads: A folder designated for downloaded files.
 Desktop: The default location for storing files and shortcuts that appear on the desktop.
 Pictures: A folder for storing image files.
 Music: A directory for storing music files.
 Videos: A folder for storing video files.

2. Bash Profile: In Unix-like operating systems (e.g., Linux, macOS), the Bash profile is a script
file that is executed when a user logs in. It allows users to customize their environment and
define aliases, environment variables, and other settings. The default Bash profile file is typically
named ".bashrc" or ".bash_profile" and resides in the user's home directory.

3. Shell Configuration Files: Similar to the Bash profile, other shell environments may have
their own configuration files with default settings. For example:

 Zsh: The Zsh shell commonly uses the ".zshrc" file for user-specific configurations.
 PowerShell: In Windows, the PowerShell profile file is named
"Microsoft.PowerShell_profile.ps1" and can contain customizations and functions.

4. Browser Configuration Files: Web browsers create default user files to store user
preferences, bookmarks, and other settings. These files can include:

 Bookmarks: A file or database that stores the user's bookmarked websites.

 Cookies: Files that store information about websites visited by the user.
 History: A file or database that records the user's browsing history.

Prepared by Michael B. 23
 Network and System Administration

5. Email Client Configuration Files: Email clients, such as Microsoft Outlook or Mozilla
Thunderbird, create default user files to store email account configurations, contacts, and other
settings.

6. Text Editor Settings: Text editors like Notepad++, Sublime Text, or Vim may create default
configuration files that determine the editor's behavior, syntax highlighting preferences, and
keybindings.

It's important to note that these examples are not exhaustive, and the specific default user files can
vary depending on the operating system, software applications, and user settings. Additionally,
users can customize or delete these default files based on their preferences and requirements.

Sure! Here's an explanation of managing file ownership, controlling access to files, and managing
disk quotas:

2.2.1 Managing File Ownership:

File ownership refers to the user or group that has control over a particular file or directory. In
most operating systems, each file is associated with an owner, and the owner determines the
permissions and access rights for that file. Managing file ownership involves assigning or changing
the ownership of files. This is typically done using the following commands:

 “chown”: This command is used to change the ownership of a file or directory. For
example, to change the owner of a file named "myfile.txt" to a user named "john," you
would use the command: `chown john myfile.txt`.

 “chgrp”: This command is used to change the group ownership of a file or directory. For
example, to change the group ownership of "myfile.txt" to a group named "users," you
would use the command: `chgrp users myfile.txt`.

2.2.2 Controlling Access to Files:

Controlling access to files involves managing permissions to determine who can read, write, or
execute a file. The permissions are typically set for three different categories: the owner, the group,
and others. The most common permissions are:

Prepared by Michael B. 24
 Network and System Administration

 Read (r) : Allows reading/viewing the contents of a file.

 Write (w): Allows modifying or deleting a file.
 Execute (x): Allows executing or running a file if it is a program or script.

Permissions can be assigned or modified using the following commands:

 chmod: This command is used to change the permissions of a file or directory. Permissions
can be specified using symbolic or numeric representations. For example, to give the owner
read and write permissions on a file named "myfile.txt," you would use the command:
`chmod u+rw myfile.txt`. Here, "u" represents the owner, "+" adds the permissions, and
"rw" indicates read and write permissions.
 chown and chgrp: As mentioned earlier, changing ownership also affects access control
since the owner and group have specific permissions. By changing ownership, you can
control who has access to the file.

2.2.3 Managing Disk Quotas:

Disk quotas are used to limit the amount of disk space that a user or group can utilize on a file
system. This helps ensure fair and efficient use of storage resources. Disk quotas can be set and
managed using the following steps:

 Enabling quotas: First, you need to enable disk quotas on the file system. This is typically
done by modifying the system configuration file or using specific commands provided by
the operating system.

 Setting quotas: Once quotas are enabled, you can set specific limits for individual users or
groups. For example, you can set a limit of 1 GB for a user's disk usage.
 Monitoring and enforcing quotas: After quotas are set, the system will monitor disk usage
for each user or group. If a user exceeds their allocated quota, the system can generate
warnings or take action, such as preventing further writes or sending notifications.
 Modifying quotas: Quotas can be modified as needed. You can increase or decrease the
allocated disk space for users or groups.

Prepared by Michael B. 25
 Network and System Administration

Each operating system has its own specific commands and procedures for managing disk quotas.
For example, on Linux, you can use commands like `quota` and `edquota` to manage disk
quotas.

It's important to note that the exact steps and commands for managing file ownership, access
control, and disk quotas can vary depending on the operating system and file system being used.
It's recommended to refer to the documentation or resources specific to your operating system
for detailed instructions and examples.

Prepared by Michael B. 26