1-Introduction
Last updated
Last updated
The whole principle is to avoid Theft, Tampering and Disruption of the systems through CIA Triad (Confidentiality, Integrity and Availability).
Confidentiality Keeping systems and data from being accessed, seen, read to anyone who is not authorized to do so. Information is accessible only to the autorized personnel.
Integrity TRUSTWORTHINESS OF DATA OR RESOUCES: Protect the data from modification or deletion by unauthorized parties, and ensuring that when authorized people make changes that shouldn't have been made the damage can be undone.
Availability ACCESSIBLE WHEN REQUIRED BY AUTHORIZED USERS: Systems, access channels, and authentication mechanisms must all be working properly for the information they provide and protect to be available when needed.
Authenticity Refers to the characterstic of a communication, document, or any data that ensures the quality of being geniune.
Note: In addition, other properties, such as authenticity, accountability, non-repudiation and reliability can also be involved. (ISO/IEC 27000:2009)
Auditing & Accountability Basically keep tracking of everthing, like, who's been logging in when are they loggin in whose access this data.
Non-Repudiation Non-repudiation is the assurance that someone cannot deny the validity of something. Non-repudiation is a legal concept that is widely used in information security and refers to a service, which provides proof of the origin of data and the integrity of the data.
There is an inter dependency between these three attributes. When security goes up, usability and functionality come down. Any organization should balance between these three qualities to arrive at a balanced information system.
Black Hat - Hackers that seek to perform malicious activities.
Gray Hat - Hackers that perform good or bad activities but do not have the permission of the organization they are hacking against.
White Hat - Ethical hackers; They use their skills to improve security by exposing vulnerabilities before malicious hackers.
Script Kiddie / Skiddies - Unskilled individual who uses malicious scripts or programs, such as a web shell, developed by others to attack computer systems and networks and deface websites.
State-Sponsored Hacker - Hacker that is hired by a government or entity related.
Hacktivist - Someone who hacks for a cause; political agenda.
Suicide Hackers - Are hackers that are not afraid of going jail or facing any sort of punishment; hack to get the job done.
Cyberterrorist - Motivated by religious or political beliefs to create fear or disruption.
Hack value - Perceived value or worth of a target as seen by the attacker.
Vulnerability - A system flaw, weakness on the system (on design, implementation etc).
Threat - Exploits a vulnerability.
Exploit - Exploits are a way of gaining access to a system through a security flaw and taking advantage of the flaw for their benefit.
Payload - Component of an attack; is the part of the private user text which could also contain malware such as worms or viruses which performs the malicious action; deleting data, sending spam or encrypting data.
Zero-day attack - Attack that occurs before a vendor knows or is able to patch a flaw.
Daisy Chaining / Pivotting - It involves gaining access to a network and /or computer and then using the same information to gain access to multiple networks and computers that contains desirable information.
Doxxing - Publishing PII about an individual usually with a malicious intent.
Enterprise Information Security Architecture (EISA) - determines the structure and behavior of organization's information systems through processes, requirements, principles and models.
Network Threats
Information gathering
Sniffing and eavesdropping
DNS/ARP Poisoning
MITM (Man-in-the-Middle Attack)
DoS/DDoS
Password-based attacks
Firewall and IDS attack
Session Hijacking
Host Threats
Password cracking
Malware attacks
Footprinting
Profiling
Arbitrary code execution
Backdoor access
Privilege Escalation
Code Execution
Application Threats
Injection Attacks
Improper data/input validation
Improper error handling and exeception management
Hidden-field manipulation
Broken session management
Cryptography issues
SQL injection
Phishing
Buffer Overflow
Information disclosure
Security Misconfigurations
Path by which a hacker can gain access to a host in order to deliver a payload or malicious outcome
APT - Advanced Persistent Threats
An advanced persistent threat is a stealthy threat actor, typically a nation state or state-sponsored group, which gains unauthorized access to a computer network and remains undetected for an extended period; Typically uses zero day attacks.
Cloud computing / Cloud based technologies
Flaw in one client's application cloud allow attacker to access other client's data
Viruses, worms, and malware
Viruses and worms are the most prevalent networking threat that are capable of infecting a network within seconds.
Ransomware
Restricts access to the computer system's files and folders and demands an online ransom payment to the attacker in order to remove the restrictions.
Mobile Device threats
Botnets
Huge network of compromised systems used by an intruder to perform various network attacks
Insider attacks
Disgruntled employee can damage assets from inside.
Huge network of compromised hosts. (used for DDoS).
Phishing attacks
Web Application Threats
Attacks like SQL injection, XSS (Cross-site scripting)...
IoT Threats
Attacks targeting OS flaws or security issues inside such as guest accounts or default passwords.
Vectors: Buffer overflows, Protocol Implementations, software defects, patch levels, authentication schemes
Attacks on programming code and software logic.
Vectors: Buffer overflows, Bugs, XSS, DoS, SQL Injection, MitM
Attack takes advantage of systems that are misconfigured due to improper configuration or default configuration.
Examples: Improper permissions of SQL users; Access-list permit all
Act of exploiting holes in unpatched or poorly-configured software.
Examples: Software defect in version 1.0; DEfect in example CGI scripts; Default passwords
CVSS - Common Vulnerability Scoring System [+]
Places numerical score based on severity
CVE – Common Vulnerabilities and Exposures [+]
Is a list of publicly disclosed vulnerabilities and exposures that is maintained by MITRE.
NVD - National Vulnerability Database [+]
is a database, maintained by NIST, that is fully synchronized with the MITRE CVE list; US Gov. vulnerabilities repository.
Misconfiguration - improperly configuring a service or application
Default installation - failure to change settings in an application that come by default
Buffer overflow - code execution flaw
Missing patches - systems that have not been patched
Design flaws - flaws inherent to system design such as encryption and data validation
Operating System Flaws - flaws specific to each OS
Default passwords - leaving default passwords that come with system/application
Pre-Attack Phase - Reconnaissance and data-gathering.
Attack Phase - Attempts to penetrate the network and execute attacks.
Post-Attack Phase - Cleanup to return a system to the pre-attack condition and deliver reports.
⚠️ For the exam, EC-Council brings his own methodology and that's all you need for the exam; you can check another pentesting methodologies here if you are interested; In case you are studying to become a professional pentester besides certification content, I recommend the OSSTMM (Open Source Security Testing Methodology Manual).
Gathering evidence about targets; There are two types of Recon:
Passive Reconnaissance: Gain information about targeted computers and networks without direct interaction with the systems.
e.g: Google Search, Public records, New releases, Social Media, Wardrive scanning networks around.
Active Reconnaissance: Envolves direct interaction with the target.
e.g: Make a phone call to the target, Job interview; tools like Nmap, Nessus, OpenVAS, Nikto and Metasploit can be considered as Active Recon.
Obtaining more in-depth information about targets.
e.g: Network Scanning, Port Scanning, Which versions of services are running.
Attacks are leveled in order to gain access to a system.
e.g: Can be done locally (offline), over a LAN or over the internet.
e.g(2): Spoofing to exploit the system by pretending to be a legitimate user or different systems, they can send a data packet containing a bug to the target system in order to exploit a vulnerability.
Can be done using many techniques like command injection, buffer overflow, DoS, brute forcing credentials, social engineering, misconfigurations etc.
Items put in place to ensure future access.
e.g: Rookit, Trojan, Backdoor can be used.
Steps taken to conceal success and intrusion; Not be noticed.
e.g: Clear the logs; Obfuscate trojans or malicious backdoors programs.
Annoyance
Involves tracking a hacker and leading him into a fake server, wasting his time — and making him easy to detect.
Attribution
Identify an attacker; Uses tools to trace the source of an attack back to a specific location, or even an individual hacker.
Attack
That is most controversial. To “hack back,” a company accesses an alleged hacker’s computer to delete its data or even to take revenge. Both of these steps are considered illegal.
Refers to the assurance of the Integrity, Availability, confidentiality, and authenticity of information and information systems during usage, processing, storage and transmission of information.
Processes that help achieving IA:
Developing local policy, process, and guidance.
Designing network and user authetication strategy.
Identifying network vulnerabilities and threats (Vulnerability assessments outline the security posture of the network).
Idenfitying problems and resource requirements.
Creating plan for identified resource requirements.
Applying appropriate IA controls.
Performing C&A (Certification and Accreditation) process of information systems helps to trace vulnerabilities, and implement sa fety measures.
Providing information assurance training to all personnel in federal and private org.
Combination of policies, processes, procedures, standards, and guidelines to establish the required level of information security.
Designed to ensure the business operates in a state of reduced risk.
It encompasses all organizational and operational processes and participants relevant to information security.
⚠️ IA focus on risk assessment, mitigation side of things; ⚠️ InfoSec focus on actually implementing security measures to safeguard systems.
Set of requirements, process, principles, and models that determines the structure and behavior of an organization's information systems.
Goals of EISA:
Help in monitoring and detecting network behaviors
Detect and recover from security breaches
Prioritizing resources of an organization
Help to perform risk assessment of an organization's IT assets.
Cost prospective when incorporated in security provisions such as incident response, disaster recovery, event correlation, etc.
Preventive control: Deters the actor from performing the threat.
e.g: Fence, Server Locks, Mantraps, etc.
Detective control: Recognizes an actor's threat.
e.g: Background check, CCTV.
Deterrent control: Deters the actor from attempting the threat.
e.g: Warning Sign.
Recovery: Mitigates the impact of a manifested threat.
e.g: Backups.
Compensating control: Provides alternative fixes to any of the above functions.
Most of security controls are preventive phase controls.
⚠️ Defense in Depth: Multiple layers of security controls; Provides redundancy in the event of a control failure. (e.g.: image below)
Physical
Guards, lights, cameras, fire extinguishers, flood protection
Administrative
Training awareness, policies, procedures and guidelines to infosec
Technical
IDS/IPS, Firewall, Encryption, Smart cards, Access control lists
Preventative
authentication, alarm bells
Detective
audits, backups
Corrective
restore operations
Risk can be defined as a probability of the occurrence of a threat or an event that may damage, or cause loss or have other negative impact either from internal or external liabilities.
A risk matrix is used during risk assessment to define the level of risk by considering the category of probability or likelihood against the category of consequence severity.
This is a simple mechanism to increase visibility of risks and assist management decision making.
Is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.
Risk Identification
Identifies the sources, causes, consequences of the internal and external risks.
Risk Assessment
Assesses the org. risk and provides an estimate on the likelihood and impact of the risk
Risk Treatment
Selects and implements appropriate controls on the identified risks
Risk Tracking
Ensures appropriate control are implemented to handle risks and identifies the chance of a new risk occurring
Risk Review
Evaluates the performance of the implemented risk management strategies
Is a risk assessment approach for analyzing the security of an application by capturing, organizing and analyzing all the information that affects the security of an application.
Identify Objectives
Helps to determine how much effort needs to be put on subsequent steps
Application Overview
Identify the components, data flows, and trust boundaries
Decompose Application
Find more relevant details on threats
Identify Threats
Identify threats relevant to your control scenario and context using the information obtained in steps 2 and 3
Identify Vulnerabilities
Identify weaknesses related to the threats found using vulnerability categories
Policies - High-level statements about protecting information; Business rules to safeguard CIA triad; Security Policies can be applied on Users, Systems, Partners, Networks, and Providers.
Common Security Policies examples:
Password Policy
Meet the password complexity requirements.
e.g: Minimum 8 char length, upper and lower case and alphanumerical.
Wireless Security Policy
AUP - Acceptable Use-Policy
How to properly use company's assets
e.g: "Do's and Dont's" with company's computer.
Data Retention Policy
e.g: Keep the data for X time.
Access Control Policies
e.g: Accessing servers; Firewalls
Procedures - Set of details steps to accomplish a goal; Instructions for implementation
Guidelines - Advice on actions given a situation; Recommended, not mandatory
Access Control Policy
This defines the resources being protected and the rules that control access to them
Remote Access Policy
This defines who can have remote access and defines access medium and remote access security controls.
Firewall Management Policy
This defines access, management and monitoring of firewalls in an organization.
Network Connection Policy
This defines who can install new resources on the network, approve the installation of new devices, document network changes etc.
Password Policy
This defines guidelines for using strong password protection on available resources.
User Account Policy
This defines the account creation process, authority, rights and responsibility of user accounts.
Information Protection Policy
This defines the sensitivity levels of information, who may have access, how it is stored and transmitted, and how it should be deleted from storage media etc.
Special Access Policy
This defines the terms and conditions of granting special access to system resources.
Email Security Policy
This policy is designed to govern the proper usage of corporate email.
Acceptable Use Policy
This defines the acceptable use of system resources.
Promiscuous Policy - This policy usually has no restrictions on usage of system resources.
Permissive Policy - This policy begins wide open and only know dangerous services/attacks or behaviors are blocked. This type of policy has to be updated regularly to stay effective.
Prudent Policy - This policy provides maximum security while allowing known but necessary dangers. This type of policy will block all services and only safe/necessary services are enabled individually. Everything is logged.
Paranoid Policy - This policy forbids everything. No Internet connection or severely restricted Internet usage is allowed.
Perform a Risk Assessment
Use security Standards and Frameworks as guide
Get Management and Staff input
Enforce the policy. Use penalties for non-compliance
Publish final draft to entire org.
Have all staff read/sign that they understood policy
Employ tools to help enforce policy
Staff training
Review and update regularly
An incident is an event that could lead to loss of, or disruption to, an organization's operations, services or functions.
Incident management is a term describing the activities of an organization to identify, analyze, and correct hazards to prevent a future re-occurrence.
Preparation: Select people, assign rules, define tools to handle the incident.
Detection & Analysis: Determine an incident has ocurred (IDS, SIEM, AV, Someone reporting, etc).
Classification and Prioritization:
Notification: Identify minor and major incident; who and how to notify an incident.
Containment: Limit the damage; Isolate hosts; Contact system owners.
Forensic Investigation: Investigate the root cause of the incident using forensic tools; System logs, real-time memory, network device logs, application logs, etc;
Eradicate & Recovery: Remove the cause of incident; Patch if needed. Recovery: get back into production; Monitor affected systems.
Post-incident Activities: Document what happened and why; Transfer knowledge.
Managing security issues by taking a proactive approach towards the customer's security vulnerabilities
Developing or reviewing processes and procedures that must be followed
Managing the response to an incident and ensuring that all procedures are followed correctly in order to minimize and control the damage
Identifying and analyzing what has happened during an incident, including impact and threat
Providing a single point of contact for reporting seucirty incidents and issues
Reviewing changes in legal and regulatory requirements to ensure that all processes and procedures are valid
Reviewing existing controls and recommending steps and technologies to prevent future incidents
Establishing relationship with local law enforcement agency, gov. agencies, key partners and suppliers
Collects data points from network, including log files, traffic captures, SNMP messages, and so on, from every host on the network. SIEM can collect all this data into one centralized location and correlate it for analysis to look for security and performance issues, as well negative trends all in real time.
Aggregation: Collecting data from disparate sources and organizing the data into a single format. Any device within a SIEM system that collects data is called collector or an aggregator.
Correlation: Is the logic that looks at data from disparate sources and can make determinations about events taking place on your network. (Could be in-band or out-of-band, depending on the placement of the NIDS/NIPS).
Alerts - For notification if something goes bad.
Triggering - Exceeding thresholds.
Normalization: Will actually create multiple tables / organize in such a way that the data can become more efficient and allows our analysis and reports tools to work better.
WORM - Write Once Read Many: The concept being is that log files are precious, and a lot of times you might want to look at them in an archival way, so that we can use optical media like WORM drives to store them.
Most Popular SIEM Tools:
Identification, Authentication, Authorization, and Accounting work together to manage assets securely.
The information on credentials identifies the user.
Example:
Your name, username, ID number, employee number, SSN etc.
“Prove you are the legitimate User". – Should always be done with Multifactor Authentication!
Authentication Factors:
Something you know (e.g. - password)
Something you have (e.g. - smart card)
Something you are (e.g. - fingerprint)
Something you do (e.g. - android pattern; manual signature)
Somewhere you are (e.g. - geolocation)
🛑 Multi-factor authentication generally uses two of this examples (e.g. - Something you Know(1) and Something you Have(2), never on same category
What are you allowed to access – We use Access Control models, what and how we implement depends on the organization and what our security goals are.
Permissions:
Applied to resources
Rights / Privileges:
Assign at system level
Authorization strategies:
Least privileged
Separation of Duties
Trace an Action to a Subjects Identity:
Prove who/what a given action was performed by (non-repudiation); Logging
Mandatory Access Control (MAC):
Every object gets a label
Confidential, secret, top secret, etc
The administrator decides who gets access to what security level; Users cannot change these settings
Used on old systems (e.g. Top Secret Gov. information)
Discretionary Access Control (DAC):
Used in most OS
Owner of the data defines access
Very flexible access control; Very weak security
Role-based Access Control (RBAC):
Access to resources is defines by a set of rules defined by a role in your organization/job function (Manager, Director etc)
Administrators provide access based on the role of the user
Rights are gained implicity instead of explicity
In Windows, use Groups to provide role-based access control
e.g. Admin Groups --> Rights and Perms,
Sales Group --> Rights and Perms
⚠️ Access is defined by ACL, Access Control List. ⚠️ Implicity deny prevents access unless specifically permitted.
Data Loss Prevention (DLP) is the practice of detecting and preventing data breaches, exfiltration, or unwanted destruction of sensitive data. Organizations use DLP to protect and secure their data and comply with regulations.
The DLP term refers to defending organizations against both data loss and data leakage prevention.
Organizations typically use DLP to:
Protect Personally Identifiable Information (PII) and comply with relevant regulations
Protect Intellectual Property critical for the organization
Achieve data visibility in large organizations
Secure mobile workforce and enforce security in Bring Your Own Device (BYOD) environments
Secure data on remote cloud systems
Data backup plays a crucial role in maintaining business continuity by helping org. recover from IT disasters, security breaches, application failures, human error, etc.
All regulatory compliance such as COBIT, SSAE, SOCII, PCI-DSS, HIPPA, SOX, FINRA, FISMA, GDPR, etc. require business to maintain data backups of critical data for specified duration.
Identifying the critical business data
Selecting the backup media
Selecting a backup technology
Selecting the appropriate RAID levels
Selecting an appropriate backup method
1. Cold backup 🔵
Empty site, no hardware, no data, no people
It takes weeks to bring online
Basic office spaces (e.g building, chairs, AC...)
No operational equipment
Cheapest recovery site
2. Warm backup 🟡
Somewhere between cold and hot - Just enough to get going (Big room with rack space, you bring the hardware)
Hardware is ready and waiting - you bring the software and data
It takes days to bring online
Operational equipment but little or no data
3. Hot backup 🔴
Exact replica of production systems
Applications and software are constantly updated
Flip a switch and everyting moves
It take hours to bring online
Real-time synchronization
Almost all data ready to go - often just a quick update
Very expensive
This topic will be covered with details in Chapter 14 - Pentesting.
A penetration test, colloquially known as a pen test, pentest or ethical hacking, is an authorized simulated cyberattack on a computer system, performed to evaluate the security of the system.
⚠️ Not to be confused with a vulnerability assessment.
Clearly defined, full scale test of security controls
Phases
Preparation - Contracts and team determined
Assessment - All hacking phases (reconnaissance, scanning, attacks, etc.)
Post-Assessment - Reports & conclusions
Types
Black Box - Done without any knowledge of the system or network.
White Box - When the attacker have complete knowledge of the system provided by the owner/target.
Gray Box - When the attacker has some knowledge of the system and/or network
Criminal - Laws that protect public safety and usually have jail time attached.
Civil - Private rights and remedies.
Common - Laws that are based on societal customs.
"Open Source Security Testing Methodology Manual" maintained by ISECOM , defines three types of compliance.
Legislative - Deals with government regulations (Such as SOX and HIPAA).
Contractual - Deals with industry / group requirement (Such as PCI DSS).
Standards based - Deals with practices that must be followed by members of a given group/organization (Such as ITIL ,ISO and OSSTMM itself).
OSSTM Controls
OSSTM Class A - Interactive Controls
Authentication - Provides for identification and authorization based on credentials.
Indemnification - Provided contractual protection against loss or damages.
Subjugation - Ensures that interactions occur according to processes defined by the asset owner.
Continuity - Maintains interactivity with assets if corruption of failure occurs.
Resilience - Protects assets from corruption and failure.
OSSTM Class B - Process Controls
Non-repudiation - Prevents participants from denying its actions
Confidentiality - Ensures that only participants know of an asset
Privacy - Ensures that only participants have access to the asset
Integrity - Ensures that only participants know when assets and processes change
Alarm - Notifies participants when interactions occur
"Payment Card Industry Data Security Standard" Standard for organizations handling Credit Cards, ATM cards and other POS cards.
This International Standard has been prepared to provide requirements for establishing, implementing, maintaining and continually improving an information security management system.
Based on BS799 but focuses on security objectives and provides security controls based on industry best practice.
"Health Insurance Portability and Accountability Act" a law that set's privacy standards to protect patient medical records and health information shared between doctors, hospitals and insurance providers.
"Sarbanes-Oxley Act" Law that requires publicly traded companies to submit to independent audits and to properly disclose financial information.
"The Digital Millennium Copyright Act" is a 1998 United States copyright law that implements two 1996 treaties of the World Intellectual Property Organization. It criminalizes production and dissemination of technology, devices, or services intended to circumvent measures that control access to copyrighted works.
"Federal Information Security Modernization Ac Of 2002" A law updated in 2004 to codify the authority of the Department of Homeland Security with regard to implementation of information security policies. (For GOV. agencies)
Catalogs security and privacy controls for federal information systems, created to help implementation of FISMA.
"Federal Information Technology Acquisition Reform Act" A 2013 bill that was intended to change the framework that determines how the US GOV purchases technology.
"Control Object for Information and Related Technology" IT Governance framework and toolset, created by ISACA and ITGI
"U.S Gramm-Leach-Bliley Act" Law that protects the confidentiality and integrity of personal information that is collected by financial institutions.
"Computer Security Incident Response Team" CSIRT provided a single point of contact when reporting computer security incidents
"Information Technology Infrastructure Library" - An operational framework developed in the '80s that standardizes IT management procedures
The OSI Model we just looked at is just a reference/logical model. It was designed to describe the functions of the communication system by dividing the communication procedure into smaller and simpler components.
The TCP/IP model is a concise version of the OSI model. It contains four layers, unlike seven layers in the OSI model.
7
Gateway
Application
Application
Application
HTTP, FTP, POP, SMTP, DNS, RIP
Data
6
-
Presentation
Application
Application
HTTP, FTP, POP, SMTP, DNS, RIP, MIME
Data
5
-
Session
Application
Application
HTTP, FTP, POP, SMTP, DNS, RIP, SCP
Data
4
-
Transport
Transport
Transport
TCP/UDP
Segments
3
Router
Network
Internet
Network
IP, ARP, ICMP, IGMP
Packets
2
Switch/bridge
Data Link
Link
Data Link
Ethernet, Token Ring
Frames
1
Hubs/Repeater
Physical
Link
Physical
Ethernet, Token Ring
Bits
The Three-way handshake
✅ TCP Connection establishment process
Host A sends out a SYN (synchronize) packet with proposed initial sequence number to Host B.
Host B receives SYN message, it returns a packet with both SYN and ACK flags (SYN-ACK) set in the TCP header.
Host A receives the SYN-ACK, it sends back ACK (Acknowledgment) packet.
Host B receives ACK and at this stage the connection is ESTABLISHED.
❌ TCP Connection termination
Host A sends a FIN (finish) flag, indicating that is has finished sending the data.
Host B who receives the FIN, doest not terminate the connection but enters into a "passive close" (CLOSE_WAIT) state and sends the ACK for the FIN back to the Host A.
Host A enters into a (TIME_WAIT) state, and sends an ACK back to the Host B.
Host B gets the ACK from the Host A and closes the connection.
⚠️ Sequence numbers increase on new communication. Example is computers A and B. A would increment B's sequence number. A would never increment it's own sequence.
SYN
Synchronize
Set during initial communication. Negotiating of parameters and sequence numbers
ACK
Acknowledgment
Set as an acknowledgement to the SYN flag. Always set after initial SYN
RST
Reset
Forces the termination of a connection (in both directions)
FIN
Finish
Ordered close to communications
PSH
Push
Forces the delivery of data without concern for buffering
URG
Urgent
Data inside is being sent out of band. Example is cancelling a message
Internet Assigned Numbers Authority (IANA) - maintains Service Name and Transport Protocol Port Number Registry which lists all port number reservations
Ranges
Well-known ports - 0 - 1023
Registered ports - 1024 - 49,151
Dynamic ports - 49,152 - 65,535
20/21
FTP
TCP
22
SSH
TCP
23
Telnet
TCP
25
SMTP
TCP
53
DNS
TCP/UDP
67
DHCP
UDP
69
TFTP
UDP
80
HTTP
TCP
110
POP3
TCP
135
RPC
TCP
137-139
NetBIOS
TCP/UDP
143
IMAP
TCP
161/162
SNMP
UDP
389
LDAP
TCP/UDP
443
HTTPS
TCP
445
SMB
TCP
514
SYSLOG
UDP
A service is said to be listening for a port when it has that specific port open
Once a service has made a connection, the port is in an established state
Netstat command:
Shows open ports on computer
netstat -an displays connections in numerical form
netstat -b displays executables tied to the open port (admin only)
IPv4 Main Address Types
Unicast - acted on by a single recipient
Multicast - acted on by members of a specific group
Broadcast - acted on by everyone on the network
Limited - delivered to every system in the domain (255.255.255.255)
Directed - delivered to all devices on a subnet and use that broadcast address
Subnet mask - determines how many address available on a specific subnet
Represented by three methods
Decimal - 255.240.0.0
Binary - 11111111.11110000.00000000.00000000
CIDR - x.x.x.x/12 (where x.x.x.x is an ip address on that range)
If all the bits in the host field are 1s, the address is the broadcast
If they are all 0s, it's the network address
Any other combination indicates an address in the range
ELK - Elastic Search, Log Stash and Kibana (Open Source)
