![]() |
| Ethical Hacking |
🛡️ Ethical Hacking — Day 30
Security Monitoring, Logging & Incident Response Basics
⚠️ LEARNING PURPOSE ONLY: This tutorial is strictly for educational and defensive cybersecurity learning. Perform all practical exercises only on systems, applications, networks, and logs that you own or are explicitly authorized to access. Never access, modify, delete, or investigate another organization's systems without permission.
Welcome to Day 30 of the Ethical Hacking learning series.
Today, we will learn about:
🔍 Security Monitoring, Logging & Incident Response Basics
Security is not only about preventing attacks.
Organizations must also be able to:
DETECT
↓
ANALYZE
↓
RESPOND
↓
RECOVER
Even strong security controls may not prevent every incident.
That is why:
Monitoring and logging are essential parts of cybersecurity.
🎯 Day 30 Learning Objectives
By the end of today's tutorial, you will understand:
What security monitoring is
What security logging is
Why logs are important
Important security events
Types of logs
Log analysis fundamentals
Indicators of suspicious activity
Linux log analysis
Windows Event Viewer basics
Windows security events
macOS Unified Logs
SIEM concepts
Alerting fundamentals
Incident response basics
Incident response lifecycle
Evidence preservation
Safe log analysis labs
Linux practical session
Windows practical session
macOS practical session
Application logging with Laravel
Logging and monitoring with Spring Boot
Professional incident documentation
1. What Is Security Monitoring?
Security monitoring is the continuous observation of systems and security events to identify unusual or potentially harmful activity.
Conceptually:
SYSTEMS
│
▼
GENERATE EVENTS
│
▼
COLLECT LOGS
│
▼
ANALYZE
│
▼
DETECT SUSPICIOUS ACTIVITY
│
▼
RESPOND
Examples of monitored activity include:
Login attempts
Failed authentication
Account changes
File changes
Privilege changes
Application errors
Network activity
Security alerts
2. What Is Logging?
Logging is the process of recording events that occur within a system.
For example:
User logged in
User logged out
Password changed
Application started
Database connection failed
Unauthorized request blocked
A simple log entry may contain:
TIME
USER OR PROCESS
EVENT
SOURCE
RESULT
Example:
2026-09-03 10:30:15
User: test-user
Event: Login
Result: Success
3. Why Are Logs Important?
Logs can help answer important questions:
WHAT happened?
WHEN did it happen?
WHERE did it happen?
WHO or WHICH process was involved?
HOW did the system respond?
Without useful logs:
SECURITY INCIDENT
│
▼
LIMITED VISIBILITY
│
▼
DIFFICULT INVESTIGATION
4. Security Logging vs Monitoring
Logging
RECORD EVENTS
Example:
Failed login recorded.
Monitoring
ANALYZE EVENTS
Example:
Multiple unusual failed logins detected.
Together:
LOGGING
+
MONITORING
=
BETTER VISIBILITY
5. Important Security Events
Organizations may monitor events such as:
Successful logins
Failed logins
Account lockouts
Password changes
Privilege changes
New user accounts
Deleted user accounts
Security policy changes
Unexpected service activity
Repeated application errors
Unauthorized access attempts
The exact events depend on the system and organization.
6. Types of Logs
Common log categories include:
System Logs
Operating system events
Service events
Startup events
Errors
Authentication Logs
Login attempts
Logout events
Authentication failures
Account lockouts
Application Logs
Application errors
Requests
Exceptions
Business events
Security Logs
Access events
Permission changes
Security alerts
Policy changes
Network Logs
Connections
Firewall events
DNS events
Traffic metadata
7. A Simple Logging Architecture
APPLICATION
│
▼
SYSTEM LOGS
│
▼
LOG COLLECTION
│
▼
CENTRALIZED STORAGE
│
▼
ANALYSIS
│
▼
ALERTS
│
▼
SECURITY TEAM
Centralized logging can make investigation easier.
8. What Makes a Good Security Log?
A useful log should provide enough context.
Example:
Timestamp
Event Type
System
User or Process
Source
Result
Relevant Context
Conceptually:
WHO
+
WHAT
+
WHEN
+
WHERE
+
RESULT
9. Never Log Sensitive Secrets
Security logs are useful, but they can also create risks.
Never intentionally log sensitive secrets such as:
Passwords
Private keys
API secrets
Full authentication tokens
Session secrets
MFA secrets
Password reset tokens
Instead of:
Password = MySecretPassword
Use safe logging practices such as:
Authentication attempt failed
without recording the secret.
10. Log Levels
Many applications use log levels.
Common examples:
DEBUG
INFO
WARNING
ERROR
CRITICAL
Conceptually:
DEBUG
Detailed information for development.
INFO
Normal application events.
WARNING
Potential problems.
ERROR
An operation failed.
CRITICAL
A serious issue requiring urgent attention.
Do not assume every warning is a security incident.
11. What Is an Alert?
An alert is generated when monitoring identifies an event or pattern that may require attention.
Example:
EVENT
│
▼
ANALYSIS RULE
│
▼
SUSPICIOUS PATTERN?
│
┌┴┐
▼ ▼
NO YES
│ │
▼ ▼
LOG ALERT
12. Avoid Alert Fatigue
Too many unnecessary alerts can create:
ALERT
ALERT
ALERT
ALERT
ALERT
This can cause important alerts to be overlooked.
This problem is called:
Alert Fatigue
Good monitoring should focus on meaningful signals.
13. Indicators of Suspicious Activity
Possible indicators can include:
Repeated authentication failures
Unexpected account changes
Unusual login times
Unexpected administrative actions
Unexpected service activity
Sudden increase in errors
Unexpected configuration changes
Unusual access patterns
Important:
An unusual event is not automatically proof of an attack.
Investigate the context before drawing conclusions.
14. Baselines Are Important
A security baseline describes what is considered normal.
For example:
NORMAL
│
├── 50 logins per day
├── 2 failed logins per hour
├── Application active 9 AM–9 PM
└── Known administrative accounts
Then compare:
CURRENT ACTIVITY
│
▼
COMPARE WITH BASELINE
│
▼
UNUSUAL ACTIVITY?
Understanding normal behavior helps identify anomalies.
15. What Is a SIEM?
SIEM stands for:
Security Information and Event Management
A SIEM can help:
COLLECT LOGS
+
NORMALIZE DATA
+
CORRELATE EVENTS
+
DETECT PATTERNS
+
GENERATE ALERTS
Conceptually:
LINUX ──────┐
WINDOWS ────┤
APPLICATION ├──► SIEM ───► ALERTS
NETWORK ────┤
CLOUD ──────┘
16. SIEM Correlation
One event may not appear dangerous.
For example:
FAILED LOGIN
But multiple related events may be more important:
FAILED LOGIN
+
FAILED LOGIN
+
FAILED LOGIN
+
ACCOUNT LOCKOUT
+
UNUSUAL LOGIN
Correlation helps analysts examine related activity.
17. Incident Response Basics
Incident response is the structured process of handling a cybersecurity incident.
A simplified lifecycle is:
PREPARE
│
▼
DETECT
│
▼
ANALYZE
│
▼
CONTAIN
│
▼
ERADICATE
│
▼
RECOVER
│
▼
LESSONS LEARNED
18. Phase 1 — Preparation
Preparation includes:
Security policies
Backups
Logging
Monitoring
Incident response procedures
Team responsibilities
Communication plans
Good preparation reduces confusion during an incident.
19. Phase 2 — Detection
Detection begins when something suspicious is identified.
Example:
ALERT
│
▼
INITIAL REVIEW
│
▼
IS THIS REAL?
Possible sources include:
SIEM alert
User report
Application monitoring
Antivirus alert
System administrator
Security researcher
20. Phase 3 — Analysis
During analysis, investigators try to understand:
What happened?
Which systems are involved?
When did it begin?
What evidence exists?
What is the potential impact?
Important principle:
Do not make assumptions without evidence.
21. Phase 4 — Containment
Containment aims to limit further damage.
Conceptually:
SUSPICIOUS SYSTEM
│
▼
CONTROLLED ISOLATION
│
▼
LIMIT FURTHER RISK
The appropriate containment action depends on the incident and organization.
Poorly planned containment can disrupt business operations, so decisions should follow authorized procedures.
22. Phase 5 — Eradication
Eradication focuses on removing the cause of the incident.
Examples may include:
Removing unauthorized changes
Fixing a vulnerability
Removing malicious files
Revoking compromised credentials
Applying security updates
Actions should be documented and authorized.
23. Phase 6 — Recovery
Recovery focuses on safely returning systems to normal operation.
This may include:
Restoring services
Monitoring systems
Verifying security controls
Confirming expected behavior
Do not assume recovery is complete without verification.
24. Phase 7 — Lessons Learned
After an incident, organizations should ask:
What happened?
What worked well?
What failed?
How can detection improve?
How can prevention improve?
What should change?
The goal is continuous improvement.
25. Evidence Preservation
During an investigation, evidence may be important.
Examples include:
Logs
Screenshots
System timestamps
Configuration details
Authorized forensic images
Incident notes
Good documentation should include:
WHEN evidence was collected
WHO collected it
WHERE it came from
HOW it was preserved
Never modify evidence unnecessarily.
26. Chain of Custody Concept
A chain of custody records how evidence was handled.
Conceptually:
EVIDENCE CREATED
│
▼
COLLECTED BY
│
▼
STORED SECURELY
│
▼
TRANSFER DOCUMENTED
│
▼
ANALYZED
This is especially important in formal investigations.
🐧 27. Linux Practical Session
Today, we will safely inspect logs on your own Linux system.
Check System Logs
On systems using systemd:
journalctl
To view recent entries:
journalctl -n 50
This displays recent log entries.
28. Linux — View System Boot Logs
You can inspect logs from the current boot:
journalctl -b
This helps you understand:
System startup
Services
Errors
Warnings
29. Linux — Follow Logs
To observe new events in real time:
journalctl -f
Press:
Ctrl + C
to stop.
Use this only to monitor systems you own or administer.
30. Linux — Check Authentication-Related Events
Depending on your Linux distribution:
sudo journalctl -u ssh
or inspect your system's authentication logs.
The exact log location differs between distributions.
Examples may include:
/var/log/auth.log
/var/log/secure
Check only logs you are authorized to access.
31. Linux — Search Logs Safely
Example:
journalctl | grep -i "failed"
This helps you learn how to search for keywords.
You can also inspect recent events:
journalctl --since "1 hour ago"
32. Linux Practical Exercise
Create your own observation table:
TIME:
________________
SERVICE:
________________
EVENT:
________________
RESULT:
________________
NORMAL OR UNUSUAL:
________________
NOTES:
________________
Analyze events without changing the system.
🪟 33. Windows Practical Session
Open:
Event Viewer
You can search for it using the Windows Start Menu.
Important categories include:
Windows Logs
├── Application
├── Security
├── Setup
└── System
34. Windows — PowerShell Event Log Analysis
Open PowerShell.
View recent system events:
Get-WinEvent -LogName System -MaxEvents 20
View recent application events:
Get-WinEvent -LogName Application -MaxEvents 20
Some Security log access requires appropriate permissions.
35. Windows — Inspect Security Events
On your own system, where authorized:
Get-WinEvent -LogName Security -MaxEvents 20
Observe information such as:
Time Created
Provider
Event ID
Event Description
Do not delete or alter security logs for practice.
36. Windows — Filter Events
Example:
Get-WinEvent -LogName System -MaxEvents 100 |
Where-Object {$_.LevelDisplayName -eq "Error"}
This filters for error-level events.
The purpose is log analysis—not system disruption.
37. Windows Practical Exercise
Record five events from your own system.
For each event, document:
TIME:
________________
SOURCE:
________________
EVENT ID:
________________
DESCRIPTION:
________________
NORMAL OR REQUIRES REVIEW:
________________
🍎 38. macOS Practical Session
macOS uses a unified logging system.
Open Terminal.
View recent logs:
log show --last 1h
Because this can produce a large amount of information, filtering is useful.
39. macOS — View Live Logs
You can observe live events with:
log stream
Press:
Ctrl + C
to stop.
Use only on your own or authorized systems.
40. macOS — Filter Logs
Example:
log show --last 1h --predicate 'eventMessage CONTAINS[c] "error"'
This helps demonstrate log filtering.
Log output varies by macOS version and system activity.
41. macOS Practical Exercise
Record several events:
TIME:
________________
PROCESS:
________________
EVENT:
________________
OBSERVATION:
________________
NORMAL / UNUSUAL:
________________
Focus on understanding the system—not modifying it.
42. Compare Linux, Windows & macOS Logging
| Operating System | Common Logging Tool |
|---|---|
| Linux | journalctl |
| Windows | Event Viewer / Get-WinEvent |
| macOS | log show / log stream |
The commands differ, but the goal remains the same:
COLLECT
↓
FILTER
↓
ANALYZE
↓
UNDERSTAND
43. Safe Log Analysis Methodology
Use this process:
1. Define the question
↓
2. Identify relevant logs
↓
3. Establish normal behavior
↓
4. Search for relevant events
↓
5. Compare timestamps
↓
6. Correlate related events
↓
7. Document observations
↓
8. Escalate if required
44. Timeline Analysis
Timelines help investigators understand event sequences.
Example:
10:00 — User logged in
10:05 — Configuration changed
10:07 — Application error
10:10 — Security alert
Conceptually:
EVENT A
│
▼
EVENT B
│
▼
EVENT C
│
▼
EVENT D
Time correlation is an important investigation skill.
45. Burp Suite and Logging
For your own web application, Burp Suite can help you understand:
Requests
Responses
HTTP status codes
Cookies
Headers
Application behavior
Example safe workflow:
YOUR TEST APPLICATION
│
▼
SEND REQUEST
│
▼
OBSERVE RESPONSE
│
▼
COMPARE WITH APPLICATION LOG
This can help developers understand how client activity relates to server-side logging.
46. Safe Web Application Logging Exercise
Use a local application you own.
Perform a normal action such as:
Login
View Profile
Update Test Data
Logout
Then inspect your application logs.
Ask:
Was the event logged?
Does the log contain useful context?
Did the application expose any secrets?
Can events be correlated by time?
47. Laravel Logging
Laravel provides logging functionality through its logging system.
Application logs may be configured through:
config/logging.php
A simple example concept:
use Illuminate\Support\Facades\Log;
Log::info('User performed an authorized action.');
For errors:
Log::error('Application error occurred.');
Do not log sensitive data unnecessarily.
48. Laravel Security Logging Principles
Consider logging:
Authentication events
Authorization failures
Important administrative actions
Application errors
Security-relevant configuration changes
Avoid logging:
Passwords
Tokens
Secrets
Sensitive personal information without a legitimate need
49. Laravel Monitoring Checklist
☐ Logging is enabled
☐ Logs are protected
☐ Sensitive secrets are excluded
☐ Errors are monitored
☐ Important security events are recorded
☐ Log retention is defined
☐ Production debug settings are reviewed
☐ Alerts exist for critical failures
50. Spring Boot Logging
Spring Boot commonly uses a logging framework through its application configuration.
Example:
private static final Logger logger =
LoggerFactory.getLogger(MyService.class);
logger.info("Application service started");
Error example:
logger.error("Unexpected application error occurred");
Do not include secrets in log messages.
51. Spring Boot Security Logging Principles
Monitor relevant events such as:
Authentication failures
Authorization failures
Application exceptions
Important administrative events
Unexpected service failures
Review:
Log levels
Log storage
Log rotation
Access to logs
Sensitive data exposure
52. Secure Logging Architecture
APPLICATION
│
▼
SECURITY EVENTS
│
▼
STRUCTURED LOGGING
│
▼
CENTRALIZED COLLECTION
│
▼
MONITORING
│
▼
CORRELATION
│
▼
ALERT
│
▼
AUTHORIZED RESPONSE
53. Common Logging Mistakes
❌ Mistake 1 — Logging Passwords
Never intentionally record passwords.
❌ Mistake 2 — Ignoring Logs
Collecting logs without reviewing important events provides limited security value.
❌ Mistake 3 — Too Much Noise
Logging everything without structure can make investigation difficult.
❌ Mistake 4 — No Time Synchronization
Incorrect timestamps make event correlation difficult.
Organizations should maintain appropriate time synchronization.
❌ Mistake 5 — Logs Accessible to Everyone
Logs may contain sensitive operational information.
Access should be controlled.
❌ Mistake 6 — No Log Retention Strategy
Organizations should define how long different logs need to be retained based on operational, legal, and security requirements.
❌ Mistake 7 — Assuming Every Alert Is an Attack
Always investigate evidence and context.
54. Day 30 Main Practical Challenge
Perform this exercise only on your own computer.
Step 1 — Generate Normal Activity
Perform normal actions such as:
Log in
Open an application
Create a test file
Close the application
Step 2 — Inspect Logs
Linux
journalctl -n 50
Windows
Get-WinEvent -LogName System -MaxEvents 20
macOS
log show --last 1h
Step 3 — Find Relevant Events
Try to identify:
Timestamp
Application or process
Event
Result
Step 4 — Create a Timeline
Example:
TIME EVENT
────────────────────────────
10:00 AM System started
10:05 AM Application opened
10:07 AM Test action performed
10:10 AM Application closed
Step 5 — Document Your Findings
SYSTEM:
________________
LOG SOURCE:
________________
EVENT:
________________
TIMESTAMP:
________________
PROCESS:
________________
NORMAL OR UNUSUAL:
________________
ACTION REQUIRED:
________________
55. Incident Response Simulation
Imagine your monitoring system reports:
MULTIPLE FAILED LOGINS
Use this safe analysis workflow:
ALERT
│
▼
VERIFY THE LOG
│
▼
CHECK TIMESTAMPS
│
▼
CHECK RELATED EVENTS
│
▼
COMPARE WITH NORMAL BASELINE
│
▼
ASSESS IMPACT
│
▼
FOLLOW AUTHORIZED RESPONSE PROCEDURE
Do not automatically assume:
FAILED LOGIN = SUCCESSFUL ATTACK
Evidence must support conclusions.
56. Professional Incident Report Template
Use the following structure for an authorized incident:
INCIDENT TITLE:
____________________________
DATE AND TIME DETECTED:
____________________________
REPORTED BY:
____________________________
AFFECTED SYSTEM:
____________________________
INCIDENT DESCRIPTION:
____________________________
INITIAL INDICATOR:
____________________________
TIMELINE:
____________________________
EVIDENCE:
____________________________
VERIFIED IMPACT:
____________________________
CONTAINMENT ACTION:
____________________________
RECOVERY STATUS:
____________________________
RECOMMENDATIONS:
____________________________
LESSONS LEARNED:
____________________________
Never include passwords or unnecessary secrets in reports.
57. Day 30 Assignment
Answer the following questions:
What is security monitoring?
What is security logging?
What is the difference between logging and monitoring?
Why are security logs important?
Name five important security events.
What information should a useful log contain?
Why should passwords never be logged?
What are log levels?
What is an alert?
What is alert fatigue?
What is a security baseline?
What is a SIEM?
What is event correlation?
What are indicators of suspicious activity?
What is the first phase of incident response?
What happens during incident detection?
What is incident analysis?
What is containment?
What is eradication?
What is recovery?
Why are lessons learned important?
What is evidence preservation?
What is chain of custody?
Which tool can be used to inspect logs on Linux?
Which Windows tool can be used to view system events?
Which macOS commands can be used to inspect unified logs?
Why is timeline analysis useful?
How can Laravel log security-relevant events?
Why should application logs be protected?
Why should security conclusions be based on evidence?
🏆 Day 30 Challenge
Create a security monitoring design for a small ERP application.
Include:
USERS
│
▼
WEB APPLICATION
│
├── Authentication Logs
├── Authorization Logs
├── Application Errors
└── Admin Activity
│
▼
LOG COLLECTION
│
▼
CENTRAL STORAGE
│
▼
MONITORING
│
▼
ALERTS
│
▼
INCIDENT RESPONSE
Answer:
What events should generate an alert?
Consider:
Repeated authentication failures
Unexpected administrator account changes
Critical application errors
Unexpected permission changes
Important configuration changes
The exact rules should be appropriate for the organization.
🔐 Day 30 Golden Rules
Rule 1
You cannot effectively defend what you cannot see.
Rule 2
Logging records events. Monitoring analyzes them.
Rule 3
Never intentionally log passwords, secrets, or sensitive authentication tokens.
Rule 4
Establish a baseline before deciding what is unusual.
Rule 5
An alert is not automatically proof of an attack.
Rule 6
Follow a structured incident response process.
Rule 7
Preserve evidence and document important actions.
Rule 8
Practice only on systems and environments you own or are authorized to access.
📚 Day 30 Summary
Today you learned:
Security monitoring
Security logging
Types of logs
Important security events
Secure logging principles
Log levels
Alerting
Alert fatigue
Suspicious activity indicators
Security baselines
SIEM concepts
Event correlation
Incident response lifecycle
Preparation
Detection
Analysis
Containment
Eradication
Recovery
Lessons learned
Evidence preservation
Chain of custody concepts
Linux log analysis
Windows Event Viewer and PowerShell
macOS Unified Logs
Timeline analysis
Safe application monitoring
Laravel logging
Spring Boot logging
Professional incident documentation
🎓 Ethical Hacking Course Completion
Congratulations! 🎉
You have completed the 30-Day Ethical Hacking Learning Series.
Throughout this course, you have explored important cybersecurity concepts including:
ETHICAL HACKING FUNDAMENTALS
↓
NETWORKING
↓
LINUX
↓
WINDOWS
↓
macOS
↓
WEB SECURITY
↓
AUTHENTICATION
↓
ACCESS CONTROL
↓
SECURITY MONITORING
↓
INCIDENT RESPONSE
Remember:
Ethical hacking is not about attacking systems without permission.
A responsible cybersecurity professional works to:
UNDERSTAND
↓
IDENTIFY
↓
VERIFY
↓
DOCUMENT
↓
HELP FIX
↓
IMPROVE SECURITY
🏅 Final Ethical Hacking Principles
1. Always Get Authorization
Never test a system without permission.
2. Define the Scope
Know exactly what systems and activities are authorized.
3. Practice in a Safe Lab
Use:
Your own computer
Virtual machines
Deliberately vulnerable applications
Dedicated training platforms
Authorized test environments
4. Protect Sensitive Data
Security testing should not unnecessarily expose private information.
5. Document Your Work
Record:
Scope
Method
Evidence
Findings
Impact
Recommendations
6. Keep Learning
Cybersecurity constantly evolves.
Continue learning:
Networking
Linux
Web Security
Cloud Security
Secure Coding
Digital Forensics
Incident Response
Security Architecture
🛡️ Final Message
The goal of ethical hacking is not simply to find vulnerabilities.
The real goal is:
FIND
↓
UNDERSTAND
↓
VERIFY SAFELY
↓
REPORT RESPONSIBLY
↓
FIX
↓
SECURE
🛡️ LEARN → PRACTICE SAFELY → ANALYZE → DOCUMENT → DEFEND
⚠️ LEARNING PURPOSE ONLY
This entire 30-day Ethical Hacking series is designed only for educational, ethical, and defensive cybersecurity learning purposes.
All practical exercises must be performed only on:
Systems you own
Applications you developed
Intentionally vulnerable training labs
Dedicated practice environments
Systems where you have explicit authorization
Never use these concepts to gain unauthorized access, disrupt services, steal information, or harm others.
Be curious. Be responsible. Be ethical.

No comments:
Post a Comment