Skip to content

UnExplainableFish52/linux-sysadmin-security-project

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

6 Commits
Β 
Β 
Β 
Β 

Repository files navigation

🐧 Linux System Administration & Security Project by UnExplainableFish52

Building a Secure Multi-User Infrastructure from Scratch

Linux Bash Security VirtualBox Kali Linux Educational


πŸ“Έ Project Demo

# Tree 
/company/
β”œβ”€β”€ executive
β”‚Β Β  β”œβ”€β”€ financial
β”‚Β Β  β”‚Β Β  β”œβ”€β”€ payroll_data.txt
β”‚Β Β  β”‚Β Β  └── Q4_2025_budget.txt
β”‚Β Β  └── strategy
β”‚Β Β      └── business_plan_2026.txt
β”œβ”€β”€ hr
β”‚Β Β  β”œβ”€β”€ employee_records
β”‚Β Β  β”‚Β Β  β”œβ”€β”€ employee_contracts.txt
β”‚Β Β  β”‚Β Β  └── salary_information.txt
β”‚Β Β  └── recruitment
β”‚Β Β      └── job_openings.txt
β”œβ”€β”€ intern
β”‚Β Β  └── learning
β”‚Β Β      β”œβ”€β”€ practice_exercises.txt
β”‚Β Β      └── tutorial_notes.txt
β”œβ”€β”€ marketing
β”‚Β Β  β”œβ”€β”€ campaigns
β”‚Β Β  β”‚Β Β  └── Q1_2026_campaign.txt
β”‚Β Β  └── content
β”‚Β Β      └── blog_post_ideas.txt
β”œβ”€β”€ projects
β”‚Β Β  β”œβ”€β”€ backend
β”‚Β Β  β”‚Β Β  └── api_development.txt
β”‚Β Β  β”œβ”€β”€ frontend
β”‚Β Β  β”‚Β Β  └── homepage_redesign.txt
β”‚Β Β  β”œβ”€β”€ fullstack
β”‚Β Β  β”‚Β Β  └── client_portal.txt
β”‚Β Β  └── mobile
β”‚Β Β      └── android_app.txt
β”œβ”€β”€ readme.md
β”œβ”€β”€ shared
β”‚Β Β  β”œβ”€β”€ general
β”‚Β Β  β”‚Β Β  β”œβ”€β”€ announcements.txt
β”‚Β Β  β”‚Β Β  └── company_handbook.txt
β”‚Β Β  └── meeting_notes
β”‚Β Β      └── weekly_standup_notes.txt
└── testing
    β”œβ”€β”€ reports
    β”‚Β Β  └── bug_report_001.txt
    └── staging
        └── test_environment_setup.txt

πŸš€ Project Overview

Welcome! This project demonstrates how to design, build, and secure a complete Linux system infrastructure from the ground up. We created a realistic company environment for TheIdealDevs β€” a fictional IT solutions company based in Lalitpur, Nepal.

What makes this project special:

  • βœ… Real-world company scenario with 12 employees across 8 departments
  • βœ… Hands-on implementation of cybersecurity principles
  • βœ… Complete documentation for learners at any level
  • βœ… Production-ready security configurations

Whether you're a beginner learning Linux, a student studying cybersecurity, or a professional refreshing your sysadmin skills β€” this project will teach you practical, job-ready techniques.


✨ What We Built

Component Details
Company TheIdealDevs (IT Solutions)
Location Natole, Lalitpur, Nepal
Users Created 12 employees with unique roles
Groups Configured 8 department-based groups
Directory Structure 23 directories mimicking real company layout
Files Created 18 sample files (employee data, projects, policies)
Operating System Kali Linux on VirtualBox
Security Status βœ… Fully secured with least privilege access

🏒 Department Breakdown

Department Members Access Level Purpose
Executive Saksham (CEO), Amy (CFO/CTO) High - Confidential Strategic planning, financials
Development Suman, Amrit, Sushank, Kushal Collaborative Software projects, code repositories
QA David Department-specific Testing, quality assurance
Marketing Aadarsh Collaborative Campaigns, content, analytics
HR Richard High - Confidential Employee records, policies
Intern Ramesh Limited - Learning Training materials, sandboxed access
Staff Isha Basic - General Reception, shared resources
SysAdmin Loki Full System Access Infrastructure management

πŸŽ“ What You'll Learn

By following this project, you'll master:

Technical Skills

  • βœ… User & Group Management β€” Creating, modifying, and organizing users
  • βœ… File Permissions β€” Understanding octal (755) and symbolic (rwxr-xr-x) notation
  • βœ… Access Control β€” Using chmod and chown for security
  • βœ… Directory Design β€” Building logical, scalable file structures
  • βœ… Security Auditing β€” Verifying and testing access controls

Security Concepts

  • βœ… Principle of Least Privilege β€” Users get only what they need
  • βœ… Role-Based Access Control (RBAC) β€” Permissions based on job functions
  • βœ… Department Isolation β€” HR can't see dev files, devs can't access HR data
  • βœ… Defense in Depth β€” Multiple security layers
  • βœ… Need-to-Know Basis β€” Sensitive data restricted appropriately

Professional Skills

  • βœ… Technical Documentation β€” Writing clear, comprehensive guides
  • βœ… System Planning β€” Designing infrastructure before implementation
  • βœ… Problem-Solving β€” Troubleshooting permission issues
  • βœ… Best Practices β€” Industry-standard security approaches

πŸ› οΈ Tech Stack

  • OS: Kali Linux (VirtualBox VM on Windows 11 Pro)
  • Hardware: Acer Nitro V15 (RTX 3050, 16GB DDR5)
  • Shell: Bash
  • Tools: useradd, groupadd, chmod, chown, tree, getent, su
  • Concepts: Linux permissions, user management, RBAC, security auditing

⚑ Quick Start Guide

Want to replicate this project? Follow these condensed steps:

1️⃣ Set Up Your Environment

# Use any Linux distribution (Ubuntu, Kali, Debian, etc.)
# VirtualBox recommended for isolated testing

2️⃣ Create the Base Directory

sudo mkdir /company
cd /company

3️⃣ Create All Users (Example)

sudo useradd -m -s /bin/bash -c "Saksham Sharma - CEO" saksham
sudo passwd saksham
# Repeat for all 12 users... 

4️⃣ Create Groups

sudo groupadd executives
sudo groupadd developers
sudo groupadd hr
# Create all 8 groups...

5️⃣ Assign Users to Groups

sudo usermod -aG executives saksham
sudo usermod -aG developers suman
# Assign all users to appropriate groups...

6️⃣ Build Directory Structure

sudo mkdir -p /company/executive/financial
sudo mkdir -p /company/projects/frontend
sudo mkdir -p /company/hr/employee_records
# Create all 23 directories...

7️⃣ Set Permissions

sudo chmod 750 /company/executive/
sudo chown root:executives /company/executive/

sudo chmod 770 /company/projects/
sudo chown root:developers /company/projects/
# Configure all directory permissions...

8️⃣ Create Sample Files

echo "Q4 Financial Report" | sudo tee /company/executive/financial/budget.txt
sudo chmod 640 /company/executive/financial/budget.txt
# Create sample files for realism...

9️⃣ Audit & Test

# View structure
tree /company/

# Test access as different users
sudo su - ramesh
cd /company/executive/  # Should be denied βœ…
exit

πŸ“š For detailed step-by-step commands, see the Command Reference below.


πŸ“‚ Project Structure

/company/
β”œβ”€β”€ executive/
β”‚   β”œβ”€β”€ financial/
β”‚   β”‚   β”œβ”€β”€ budget.txt (640 - rw-r-----)
β”‚   β”‚   └── revenue.txt
β”‚   └── strategy/
β”‚       └── roadmap.txt
β”œβ”€β”€ projects/
β”‚   β”œβ”€β”€ frontend/
β”‚   β”‚   └── app.js
β”‚   β”œβ”€β”€ backend/
β”‚   β”‚   └── api.py
β”‚   └── docs/
β”‚       └── architecture.md
β”œβ”€β”€ testing/
β”‚   β”œβ”€β”€ test_cases.txt
β”‚   └── bug_reports.txt
β”œβ”€β”€ marketing/
β”‚   β”œβ”€β”€ campaigns/
β”‚   β”‚   └── social_media.txt
β”‚   └── analytics/
β”‚       └── metrics.txt
β”œβ”€β”€ hr/
β”‚   β”œβ”€β”€ employee_records/
β”‚   β”‚   └── employee_data.txt (600 - rw-------)
β”‚   β”œβ”€β”€ policies/
β”‚   β”‚   └── code_of_conduct.txt
β”‚   └── payroll/
β”‚       └── salary_info.txt
β”œβ”€β”€ intern/
β”‚   β”œβ”€β”€ training/
β”‚   β”‚   └── onboarding.txt
β”‚   └── assignments/
β”‚       └── task_list.txt
└── shared/
    β”œβ”€β”€ handbook. txt
    β”œβ”€β”€ announcements.txt
    └── resources/

Total: 23 directories, 18 files

πŸ” Security Principles Applied

1. Principle of Least Privilege

Users receive only the minimum access required for their role.

  • Interns can't access executive financial data
  • Developers can't view HR employee records
  • Marketing can't modify development code

2. Role-Based Access Control (RBAC)

Permissions are group-based, not individual.

  • All developers share access to /company/projects/
  • All executives share access to /company/executive/
  • Changes to one group affect all members (easier management)

3. Department Isolation

Sensitive departments are protected from unauthorized access.

  • HR directory: 750 permissions, only hr group can read
  • Executive directory: 750 permissions, only executives group can read
  • Testing directory: Only QA team has full access

4. Collaborative Workspaces

Teams can work together in shared directories.

  • Developers: 770 on /company/projects/ β€” all devs can read/write/execute
  • Marketing: 770 on /company/marketing/ β€” team collaboration enabled

5. Defense in Depth

Multiple layers of security controls:

  • User authentication (passwords)
  • Group membership (authorization)
  • Directory permissions (access control)
  • File permissions (data protection)

πŸ“š Complete Command Reference

We organized all commands by category for easy reference. Click any section to expand.


πŸ‘€ User Management Commands

Creating Users

sudo useradd -m -s /bin/bash -c "Full Name - Role" username

Flags Explained:

  • sudo β€” Execute with administrative privileges
  • useradd β€” Command to create a new user
  • -m β€” Create home directory (/home/username)
  • -s /bin/bash β€” Set default shell to Bash
  • -c "comment" β€” Add descriptive comment (usually name and role)
  • username β€” The login name for the user

Example:

sudo useradd -m -s /bin/bash -c "Saksham Sharma - CEO" saksham

Setting Passwords

sudo passwd username

Example:

sudo passwd saksham
# Enter password when prompted

Viewing User Information

id username                    # Show user ID, groups, and GIDs
cat /etc/passwd | grep username  # Show user entry in passwd file
getent passwd username         # Get user entry from system database

Examples:

id saksham
cat /etc/passwd | grep saksham
getent passwd saksham

Deleting Users (if needed)

sudo userdel username          # Delete user (keeps home directory)
sudo userdel -r username       # Delete user and home directory

πŸ‘₯ Group Management Commands

Creating Groups

sudo groupadd groupname

Example:

sudo groupadd developers

Adding Users to Groups

sudo usermod -aG groupname username

Flags Explained:

  • usermod β€” Modify user account
  • -a β€” Append (add without removing from other groups)
  • -G groupname β€” Specify the group to add user to
  • username β€” The user to modify

Example:

sudo usermod -aG developers suman

Viewing Group Information

groups username                # Show all groups a user belongs to
getent group groupname         # Show all members of a group
cat /etc/group | grep groupname  # View group entry in group file
id username                    # Shows user's groups with GIDs

Examples:

groups suman
getent group developers
cat /etc/group | grep developers

Understanding getent:

  • getent = "Get Entry" from system databases
  • getent group groupname β€” Get group information and list all members
  • getent passwd username β€” Get user information from passwd database

Deleting Groups (if needed)

sudo groupdel groupname

πŸ“ Directory & File Management Commands

Creating Directories

sudo mkdir directory_name                # Create single directory
sudo mkdir -p /path/to/nested/directory  # Create with parent directories

Flags Explained:

  • mkdir β€” Make directory
  • -p β€” Create parent directories as needed (no error if exists)

Examples:

sudo mkdir /company
sudo mkdir -p /company/executive/financial

Creating Files

sudo touch filename                      # Create empty file
echo "content" | sudo tee filename       # Create file with content

Examples:

sudo touch /company/hr/employee_data.txt
echo "Company Handbook" | sudo tee /company/shared/handbook.txt

Viewing Directory Contents

ls                      # List files
ls -l                   # Long format (permissions, owner, size, date)
ls -a                   # Show hidden files
ls -la                  # Long format including hidden files
ls -ld /path/           # Show directory itself (not contents)
ls -lR /path/           # Recursive (show all subdirectories)
tree /path/             # Visual tree structure (if installed)

Examples:

ls -l /company/
ls -ld /company/executive/
ls -lR /company/
tree /company/

Installing tree command

sudo apt update
sudo apt install tree

Viewing File Contents

cat filename            # Display entire file
head filename           # Show first 10 lines
tail filename           # Show last 10 lines
less filename           # View file page by page (press 'q' to quit)

πŸ”’ Permission Management Commands

Changing Permissions (chmod)

Octal Notation (Numeric)

sudo chmod 755 /path/              # rwxr-xr-x
sudo chmod 750 /path/              # rwxr-x---
sudo chmod 770 /path/              # rwxrwx---
sudo chmod 644 filename            # rw-r--r--
sudo chmod 640 filename            # rw-r-----
sudo chmod 660 filename            # rw-rw----
sudo chmod -R 750 /path/           # Recursive (apply to all contents)

Symbolic Notation

chmod u+rwx file       # Give owner read+write+execute
chmod g+rx file        # Give group read+execute
chmod o-rwx file       # Remove all permissions from others
chmod g+w file         # Add write permission to group
chmod a+r file         # Give read to all (owner+group+others)
chmod u=rwx,g=rx,o=r file  # Set exact permissions

Common Permission Patterns

Octal Symbolic Use Case
755 rwxr-xr-x Public directories, executable files
750 rwxr-x--- Department directories (group access only)
770 rwxrwx--- Collaborative team directories
700 rwx------ Private directories (owner only)
644 rw-r--r-- Public readable files
640 rw-r----- Group readable files
660 rw-rw---- Collaborative team files
600 rw------- Private files (owner only)

Examples:

sudo chmod 750 /company/hr/
sudo chmod -R 770 /company/projects/
sudo chmod 640 /company/executive/financial/budget.txt

Permission Calculation

Octal to Symbolic Conversion:

Octal Binary Symbolic Meaning
7 111 rwx Read + Write + Execute
6 110 rw- Read + Write
5 101 r-x Read + Execute
4 100 r-- Read only
3 011 -wx Write + Execute
2 010 -w- Write only
1 001 --x Execute only
0 000 --- No permissions

Calculating Octal Permissions:

  • Read (r) = 4
  • Write (w) = 2
  • Execute (x) = 1

Example: rwxr-x--- to octal

rwx = 4+2+1 = 7
r-x = 4+0+1 = 5
--- = 0+0+0 = 0

Result: 750

Example: 644 to symbolic

6 = 4+2 = rw-
4 = 4   = r--
4 = 4   = r--

Result: rw-r--r--

πŸ‘‘ Ownership Management Commands

Changing Ownership (chown)

sudo chown user:group /path/              # Change both user and group
sudo chown user /path/                    # Change user only
sudo chown : group /path/                  # Change group only
sudo chown -R user:group /path/           # Recursive (all contents)

Flags Explained:

  • chown β€” Change ownership
  • -R β€” Recursive (apply to directory and all its contents)
  • user:group β€” New owner: group (colon separates them)

Examples:

sudo chown root:executives /company/executive/
sudo chown -R root:developers /company/projects/
sudo chown : hr /company/hr/employee_records/

Changing Group Only (alternative method)

sudo chgrp groupname /path/               # Change group
sudo chgrp -R groupname /path/            # Recursive

πŸ” System Audit Commands

Viewing Permissions and Ownership

ls -l /path/                   # List with permissions and ownership
ls -ld /path/                  # Show directory itself
ls -lR /path/                  # Recursive listing
stat /path/                    # Detailed file/directory statistics

Viewing Group Memberships

groups username                # Show user's groups
getent group groupname         # Show group members
id username                    # Detailed user/group info with IDs
cat /etc/group                 # View entire group file

Searching in System Files

cat /etc/passwd | grep username              # Find user in passwd file
cat /etc/group | grep groupname              # Find group in group file
grep -E "user1|user2" /etc/passwd            # Search for multiple users

Understanding System Files:

  • /etc/passwd β€” Contains all user accounts
  • /etc/group β€” Contains all groups and their members
  • /etc/shadow β€” Contains encrypted passwords (root access only)

πŸ”„ User Switching & Testing Commands

Switching Users

su - username              # Switch to another user (with their environment)
su username                # Switch without loading environment
exit                       # Return to previous user

Examples:

su - suman                 # Switch to suman's account
cd /company/projects/      # Test if suman can access this
exit                       # Return to your account

Switching to Root

sudo su -                  # Switch to root with root's environment
sudo -i                    # Switch to root (alternative method)
sudo su                    # Switch to root without environment
exit                       # Return to regular user

Differences:

  • sudo su - or sudo -i β€” Full root environment (recommended)
  • sudo su β€” Root privileges but keeps current environment
  • su - requires root password (unless using sudo)

Testing Access as Different Users

# Switch to a user
sudo su - ramesh

# Try to access restricted directory
cd /company/executive/financial/

# If denied:  Permission denied βœ… (security working)
# If allowed: Access granted βœ… (authorized user)

# Return to your account
exit

🌲 Advanced Directory Navigation

Using tree Command

tree /path/                    # Show visual tree structure
tree -L 2 /path/               # Limit depth to 2 levels
tree -d /path/                 # Show directories only
tree -p /path/                 # Show permissions
tree -pu /path/                # Show permissions and owner

Examples:

tree /company/
tree -L 2 /company/
tree -pu /company/executive/

Why tree is Useful:

  • Visual representation of directory structure
  • Quickly see what files/folders exist
  • Shows what you CAN access and CANNOT access
  • Great for understanding the Filesystem hierarchy

Testing What a User Can See

# Switch to a user
sudo su - suman

# Navigate and view accessible structure
cd /company/
tree

# This will ONLY show directories suman can access
# Restricted directories won't appear or will show "Permission denied"

exit

πŸ”Ž File Search Commands

Finding Files

find /path/ -name "filename"               # Search by exact name
find /path/ -name "*.txt"                  # Search by pattern
find /path/ -type f                        # Find files only
find /path/ -type d                        # Find directories only
find /path/ -user username                 # Find files owned by user
find /path/ -group groupname               # Find files owned by group

Examples:

find /company/ -name "*.txt"
find /company/ -type d
find /company/ -group developers

Searching File Contents

grep "search_term" filename                # Search in single file
grep -r "search_term" /path/               # Recursive search
grep -i "search_term" filename             # Case-insensitive search

ℹ️ System Information Commands

Viewing Current User

whoami                     # Show current username
id                         # Show current user's ID and groups

Viewing Logged-in Users

who                        # Show who is logged in
w                          # Show who is logged in and what they're doing
last                       # Show login history

Disk Usage

df -h                      # Show disk space usage
du -sh /path/              # Show directory size
du -h /path/               # Show size of all contents

πŸ› Troubleshooting Commands

Permission Denied Issues

# Check permissions
ls -ld /path/

# Check ownership
ls -l /path/

# Check your groups
groups

# Check if you're in the required group
id | grep groupname

Fixing Common Issues

# Can't enter directory but should be able to
sudo chmod +x /path/                      # Add execute permission

# Group members can't write
sudo chmod g+w /path/                     # Add group write permission

# Wrong group ownership
sudo chown : correct_group /path/          # Fix group ownership

⚑ Project-Specific Quick Commands

Quick Setup (All Users)

sudo useradd -m -s /bin/bash -c "Saksham Sharma - CEO" saksham
sudo useradd -m -s /bin/bash -c "Amy Cooper - CFO & CTO" amy
sudo useradd -m -s /bin/bash -c "Richard Stallman - HR Manager" richard
sudo useradd -m -s /bin/bash -c "Suman Sharma - Frontend Engineer" suman
sudo useradd -m -s /bin/bash -c "Amrit Paudel - Backend Engineer" amrit
sudo useradd -m -s /bin/bash -c "Sushank Subedi - FullStack Engineer" sushank
sudo useradd -m -s /bin/bash -c "Kushal Pun - Mobile Developer" kushal
sudo useradd -m -s /bin/bash -c "David Oli - QA Engineer" david
sudo useradd -m -s /bin/bash -c "Aadarsh Dhami - Marketing Manager" aadarsh
sudo useradd -m -s /bin/bash -c "Ramesh Shahi - Intern" ramesh
sudo useradd -m -s /bin/bash -c "Isha Misha - Receptionist" isha
sudo useradd -m -s /bin/bash -c "Loki - System Administrator" loki

Quick Setup (All Groups)

sudo groupadd executives
sudo groupadd developers
sudo groupadd qa
sudo groupadd marketing
sudo groupadd hr
sudo groupadd interns
sudo groupadd staff
sudo groupadd sysadmins

Quick Group Assignment

sudo usermod -aG executives saksham
sudo usermod -aG executives amy
sudo usermod -aG developers suman
sudo usermod -aG developers amrit
sudo usermod -aG developers sushank
sudo usermod -aG developers kushal
sudo usermod -aG qa david
sudo usermod -aG marketing aadarsh
sudo usermod -aG hr richard
sudo usermod -aG interns ramesh
sudo usermod -aG staff isha
sudo usermod -aG sysadmins loki

Quick Audit Commands

# View all company directories
ls -l /company/

# View all groups and members
getent group | grep -E "executives|developers|qa|marketing|hr|interns|staff|sysadmins"

# Complete system audit
ls -lR /company/

# Visual tree
tree /company/

πŸ§ͺ Testing & Validation

We tested our security implementation by:

1. Access Control Testing

# Test 1: Can intern access executive files? 
sudo su - ramesh
cd /company/executive/financial/
# Result: Permission denied βœ…

# Test 2: Can developers access project files?
sudo su - suman
cd /company/projects/
ls -la
# Result: Access granted βœ…

# Test 3: Can HR manager access employee records?
sudo su - richard
cat /company/hr/employee_records/employee_data.txt
# Result: Access granted βœ…

2. Permission Verification

# Verify executive directory (should be 750)
ls -ld /company/executive/
# Expected: drwxr-x--- root executives

# Verify projects directory (should be 770)
ls -ld /company/projects/
# Expected: drwxrwx--- root developers

# Verify sensitive files (should be 640 or 600)
ls -l /company/executive/financial/budget.txt
# Expected: -rw-r----- root executives

3. Group Membership Audit

# Verify all developers are in developers group
getent group developers
# Expected: developers: x:1001:suman,amrit,sushank,kushal

# Verify all executives are in executives group
getent group executives
# Expected: executives:x:1000:saksham,amy

Result: βœ… All security controls functioning as designed


🌍 Real-World Applications

This project prepared us for:

Career Opportunities

  • βœ… Junior System Administrator β€” Managing users, groups, and permissions
  • βœ… IT Support Specialist β€” Troubleshooting access issues
  • βœ… Security Analyst β€” Understanding and implementing access controls
  • βœ… DevOps Engineer (Entry-level) β€” Linux infrastructure management
  • βœ… Cybersecurity Roles β€” Applying security principles in practice

Skills Employers Look For

  • Linux command-line proficiency βœ…
  • User and permission management βœ…
  • Security best practices (least privilege, RBAC) βœ…
  • Technical documentation βœ…
  • Hands-on practical experience βœ…

Industry Standards Demonstrated

  • ISO 27001 principles (access control, least privilege)
  • NIST Cybersecurity Framework (identity management, access control)
  • CIS Controls (controlled use of administrative privileges)

βœ… Best Practices Summary

Security Best Practices

  1. βœ… Always apply the principle of least privilege
  2. βœ… Use groups for permission management (not individual users)
  3. βœ… Regularly audit permissions and group memberships
  4. βœ… Remove execute permissions from regular files (use 640 not 750)
  5. βœ… Keep sensitive directories at 750 or stricter (700, 710)
  6. βœ… Use 755 for shared/public directories
  7. βœ… Document all permission changes
  8. βœ… Test access controls after making changes

Command Best Practices

  1. βœ… Always use sudo for system-wide changes
  2. βœ… Use -R flag carefully (it affects all subdirectories)
  3. βœ… Verify changes with ls -l after modifications
  4. βœ… Use getent for clean group/user information
  5. βœ… Test permissions by switching users (su - username)
  6. βœ… Use tree for quick visual understanding
  7. βœ… Keep backups before making major permission changes

πŸ“Š Project Metrics

Metric Value
Total Users 12
Total Groups 8
Total Directories 23
Total Files 18
Security Status βœ… Fully Secured
Access Control βœ… Functioning
Audit Status βœ… Passed
Production Ready βœ… Yes

🎯 Key Takeaways

Technical Skills Gained

  • βœ… User and group management in Linux
  • βœ… File permissions (symbolic and octal notation)
  • βœ… Using chmod and chown effectively
  • βœ… Directory structure design
  • βœ… Access control implementation
  • βœ… System auditing techniques

Security Concepts Mastered

  • βœ… Principle of least privilege
  • βœ… Role-based access control (RBAC)
  • βœ… Department isolation
  • βœ… Collaborative workspace design
  • βœ… Security auditing methodology

Professional Development

  • βœ… Technical documentation writing
  • βœ… Project planning and execution
  • βœ… Security-first thinking
  • βœ… Problem-solving approach
  • βœ… Attention to detail

πŸ“¬ Connect With Me

If you found this project helpful or have questions:


πŸ™ Acknowledgments

  • Google Cybersecurity Professional Certificate β€” For foundational security principles
  • Linux Documentation Project β€” Comprehensive command references
  • TheIdealDevs Team β€” Fictional but inspired by real company structures
  • Open Source Community β€” For tools like tree, bash, and VirtualBox

πŸ”₯ Project Status

Status: βœ… COMPLETE
Security: βœ… FULLY SECURED
Documentation: βœ… COMPREHENSIVE
Production Ready: βœ… YES


⭐ If you found this project helpful, please star the repository!

Built by Saksham Sharma | UnExplainableFish52 | loki | System Administrator Enthusiast & Cyber Security Specialist


End of Documentation

About

a project by loki,

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published