1656 lines
No EOL
44 KiB
Markdown
1656 lines
No EOL
44 KiB
Markdown
NAVY INFORMATION OPERATIONS COMMAND MARYLAND
|
||
NETWARCOM
|
||
|
||
# NIOC MARYLAND ADVANCED COMPUTER NETWORK OPERATIONS COURSE
|
||
|
||
Coordinated by
|
||
|
||
[REDACTED]
|
||
|
||
NAVIOCOM Maryland
|
||
|
||
Center of Excellence for Non-Kinetic Options
|
||
1
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Title
|
||
|
||
* Content
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
2
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## WHY ARE WE TEACHING THIS?
|
||
|
||
* 5 Pillars of IO:
|
||
* OPSEC
|
||
* MILDEC
|
||
* MISO
|
||
* EW
|
||
* CNO
|
||
* The next major conflict will start in cyberspace
|
||
* Whether we recognize the signs is another matter
|
||
* Recent conflicts have already shown the importance of CNO (Russia/Georgia)
|
||
* Think China will make a move on Taiwan without bringing down their communications networks?
|
||
* As IW officers (or IDC) – we are expected to know and understand CNO and communicate with decision makers
|
||
* Recently announced plans from Command in Chief and Pentagon officials emphasize cyber space operations
|
||
* Basic 1810/IDC quals are a good foundation, but CO/XO want you to know more about CNO
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
3
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Course Overview
|
||
|
||
Wednesday, April 11th
|
||
Location: OPS2B
|
||
2B4118-1
|
||
|
||
| Time | Topic | Briefer |
|
||
| :---------- | :--------------------------- | :------------------------------------ |
|
||
| 0730-0900 | CNO Intro/ TAO Overview | LT [REDACTED] / CTN1 |
|
||
| | | CTN1 [REDACTED] / CTN2 |
|
||
| 0900-1000 | Analysis | CTN1 [REDACTED] / CTN1 |
|
||
| 1000-1100 | EAO | [REDACTED] |
|
||
| 1100-1200 | Lunch | [REDACTED] |
|
||
| 1200-1300 | IOD/Scanning | CTN1 [REDACTED] |
|
||
| 1300-1400 | DNT | ENS [REDACTED] |
|
||
| 1430-1500 | TAO Brief/Tour | ENS [REDACTED] |
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
4
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Course Overview
|
||
|
||
Thursday, April 12th
|
||
Location: OPS2B 2B4118-3
|
||
|
||
| Time | Topic | Briefer |
|
||
| :-------- | :--------------------- | :----------------------------------------------------------------- |
|
||
| 0800-0900 | CND Intro/Threat Brief | LTJG [REDACTED] / LTJG [REDACTED] (S: [REDACTED] U: [REDACTED]) |
|
||
| 0900-1000 | Red Team Brief | CTN2 [REDACTED] / CTN2 [REDACTED] (S: [REDACTED] U: [REDACTED]) |
|
||
| 1000-1030 | Blue Team Brief | LCDR [REDACTED] (S: [REDACTED]; U: [REDACTED]) |
|
||
| 1030-1100 | JCMA Brief | CTR1 Brown/ CTR1 [REDACTED] (S: [REDACTED] U: [REDACTED]) |
|
||
| 1100-1130 | Hunt Brief | CTN2 [REDACTED] (S: [REDACTED]; U: [REDACTED]) |
|
||
| 1130-1300 | Lunch | [REDACTED] |
|
||
| 1300-1400 | Tutelage Brief | |
|
||
| 1400-1530 | NTOC Brief/Walkthrough | CTN2 [REDACTED] (S: [REDACTED] U: [REDACTED]) POC: LCDR [REDACTED] |
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
5
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Course Overview
|
||
|
||
Friday, April 13th
|
||
Location: OPS2B
|
||
2B4118-3
|
||
|
||
| Time | Topic | Briefer |
|
||
| :---------- | :--------------------------- | :---------------------------------- |
|
||
| 0800-0900 | POD | CTN2 [REDACTED] |
|
||
| 0900-1000 | OCO | LTJG [REDACTED] |
|
||
| 1000-1100 | Legal Authorities | LT [REDACTED] / MAJ [REDACTED] |
|
||
| 1100-1200 | Lunch | [REDACTED] |
|
||
| 1200-1400 | PKC/PKI (Asymmetric Encryption) | LT [REDACTED] |
|
||
| 1400-1430 | Debrief/Discussion | LT [REDACTED] |
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
6
|
||
|
||
---
|
||
|
||
## USCYBERCOM LOO's
|
||
|
||
* CNO
|
||
* CND
|
||
* CNA
|
||
* CNE
|
||
|
||
* Who: TAO
|
||
* Where: ROC
|
||
|
||
Class I
|
||
* Automated
|
||
|
||
Class II
|
||
* Interactive
|
||
|
||
Human-enabled
|
||
* Proximal Access
|
||
* Physical Interdiction
|
||
* Multi-Staged
|
||
|
||
* USCYBERCOM LOO'S
|
||
* Offensive Cyber Operations (OCO) Who: CYBERCOM Where: ROC
|
||
* CNA-OPE (intent)
|
||
* Conducted by US Military Personnel or DoD Civilians with UCMJ Waivers
|
||
* Defensive Cyber Operations (DCO)
|
||
* NTOC: TUTELAGE (.mil) NCDOC: HAWKEYE (.navy.mil) DHS: EINSTEIN (.gov)
|
||
* Response-Action Timely & Proportional
|
||
* DoD Global Information GIG Operations (DGO)
|
||
* Proactive Network Operations (PNO)
|
||
* Information Assurance (IA)
|
||
|
||
FLTCYBERCOM / C10F
|
||
★★★ U.S. FLEET CYBER COMMAND / U.S. TENTH FLEET ★★★
|
||
|
||
---
|
||
|
||
## DoD Global Information Grid Operations (DGO)
|
||
|
||
* DGO operations consist of aspects of NetOps directing operation of the GIG
|
||
* Goal: support efforts to build, configure, secure, operate, maintain and sustain DoD networks
|
||
* Desired end-state: enable pillars of Information Assurance
|
||
* Achieved via Proactive Network Operations (PNO)
|
||
* DISA operates the GIG, but USCYBERCOM ensures operation and availability
|
||
|
||
Pillars of Information Assurance
|
||
* Confidentiality
|
||
* Integrity
|
||
* Availability
|
||
* Non-Repudiation
|
||
* Authentication
|
||
|
||
Responsible Organizations:
|
||
* USCYBERCOM
|
||
* NSANet: IAD & NTOC
|
||
* JWICS: DIA
|
||
* navy.mil
|
||
* Navy Cyber Defense Operations Command (CTF 1020)
|
||
* NAVNETWARCOM (CTF 1010)
|
||
|
||
FLTCYBERCOM /C10F
|
||
★★★ U.S. FLEET CYBER COMMAND / U.S. TENTH FLEET ★★★
|
||
8
|
||
|
||
---
|
||
|
||
## Defensive Cyberspace Operations (DCO)
|
||
|
||
DCO:
|
||
* Direct and synchronize actions to detect, analyze, counter and mitigate cyber threats and vulnerabilities
|
||
|
||
Goal:
|
||
* Protect critical missions, enable freedom of action in cyberspace
|
||
|
||
Dynamic Network Defense Operations:
|
||
* Flexible response, incorporating Title 10 and Title 50 authorities, to defend the GIG
|
||
|
||
Responsible Organizations:
|
||
* USCYBERCOM: .mil
|
||
* NTOC uses SIGINT
|
||
* NCDOC: navy.mil
|
||
* HAWKEYE
|
||
* DHS: .gov
|
||
* EINSTEIN
|
||
|
||
FLTCYBERCOM /C10F
|
||
★★★ U.S. FLEET CYBER COMMAND / U.S. TENTH FLEET ★★★
|
||
9
|
||
|
||
---
|
||
|
||
## Offensive Cyberspace Operations (OCO)
|
||
|
||
OCO:
|
||
* Enabling and attack effects in cyberspace
|
||
|
||
Goal:
|
||
* Support national and CCDRs' objectives via cyber actions
|
||
|
||
Who:
|
||
* Remote Operations Center, civilians and military personnel
|
||
|
||
Supports DCO:
|
||
* Enables active defense against cyber actors/adversaries
|
||
|
||
ROC Relationships:
|
||
* Remote Operations Center
|
||
* USCYBERCOM tasks
|
||
* NSA/CSS controls
|
||
* Navy's Role:
|
||
* Force Provider
|
||
|
||
FLTCYBERCOM /C10F
|
||
★★★ U.S. FLEET CYBER COMMAND / U.S. TENTH FLEET ★★★
|
||
10
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
NAVY INFORMATION OPERATIONS COMMAND MARYLAND
|
||
U.S. TENTH FLEET
|
||
|
||
NAVY INFORMATION OPERATIONS COMMAND MARYLAND
|
||
NETWARCOM
|
||
|
||
## 10 Department
|
||
## NIOC Maryland
|
||
|
||
## Computer Network Operations
|
||
|
||
REQUIREMENTS & TARGETING
|
||
Missions for Today, Opportunities for Tomorrow
|
||
|
||
ROC
|
||
|
||
ACCESS TECHNOLOGY & OPERATIONS
|
||
DETEGO ATQUE OSUAR
|
||
|
||
mission infrastructure
|
||
TECHNOLOGIES
|
||
|
||
DATA NETWORK TECHNOLOGIES
|
||
NOTHING BUT NET
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
11
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Outline
|
||
|
||
* TAO Overview
|
||
* Mission Aligned Cells (MAC)
|
||
* Manning / Placement
|
||
* Department Operations
|
||
* Summary
|
||
* Examples: Russia & Lebanon
|
||
* Joint Cyber Attack Team
|
||
* NCAT Vision
|
||
* Afloat CNO
|
||
* Discussion Topics
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
12
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## TAO Organization
|
||
|
||
* Requirements & Targeting
|
||
* Manage ops requirements Perform target development
|
||
|
||
* Remote Operations Center
|
||
* Conduct On-net ops (exploit, collect, geo-locate)
|
||
|
||
* Data Network Technologies
|
||
* Develop operational concepts and software implants to exploit computer networks
|
||
|
||
* Telecommunications Network Technologies
|
||
* Develop operational concepts and software implants to exploit phone switches Develop network warfare capabilities Network shaping
|
||
|
||
* Access Technologies & Operations
|
||
* Conduct physical-access (off-net) operations Conduct expeditionary CNO Develop hardware and firmware implants to access isolated or complex networks
|
||
|
||
* Mission Infrastructure Technologies
|
||
* Design, development and delivery of the end-to end infrastructure that supports GENIE operations
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
FVEY
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Mission Aligned Cells (MACs)
|
||
|
||
Concept:
|
||
* TAO recently completed a major effort to align resources from R&T, ROC, DNT and MIT into mission focused teams.
|
||
* Mission Aligned Cells
|
||
* Teams composed of operators, analysts and developers working together to focus on a specific target set.
|
||
* Allows TAO to efficiently resources on high-priority projects and targets.
|
||
|
||
Current MAC's:
|
||
* China/North Korea (NSAW, NSAH)
|
||
* Iran (NSAW, NSAG)
|
||
* Russia (NSAW, NSAH)
|
||
* Cyber Counterintelligence (CCI) (NSAW, NSAG, NSAT, NSAH)
|
||
* Counterterrorism (CT) (NSAW, NSAG)
|
||
* Target Service Provider (TSP) (NSAW, NSAT)
|
||
* Regional Targets (RT) (NSAW, NSAT)
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
14
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## TAO – Front Office (S32)
|
||
|
||
* TAO
|
||
* Requirements & Targeting
|
||
* Remote operations Center
|
||
* Data Network Technologies
|
||
* Telecommunications Network Technologies
|
||
* Access Technologies & Operations
|
||
* Mission Infrastructure Technologies
|
||
|
||
Leadership Positions:
|
||
* RDML [REDACTED]
|
||
* Deputy Chief, TAO
|
||
* CAPT [REDACTED]
|
||
* TAO Cyber Operations Integrated Lead (COIL)
|
||
* Principle advisor to TAO leadership for operational cyber issues
|
||
|
||
S32:
|
||
* Staff (2/2/0)
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
15
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Requirements & Targeting (S327)
|
||
|
||
|
||
* TAO
|
||
* **Requirements & Targeting**
|
||
* Remote operations Center
|
||
* Data Network Technologies
|
||
* Telecommunications Network Technologies
|
||
* Access Technologies & Operations
|
||
* Mission Infrastructure Technologies
|
||
|
||
Leadership Positions:
|
||
* LCDR [REDACTED]
|
||
* D/Chief, CT & Afghanistan
|
||
* LCDR [REDACTED]
|
||
* In training – slated for Hard Targets Division, DPRK Branch
|
||
* LT [REDACTED]
|
||
* CNO Coordinator – China/DPRK Branch
|
||
|
||
S327:
|
||
* R&T Influence (8/6/0)
|
||
* Endpoint Exploitation (57/35/0)
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
16
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Remote Operations Center (S321)
|
||
|
||
|
||
* TAO
|
||
* Requirements & Targeting
|
||
* **Remote operations Center**
|
||
* Data Network Technologies
|
||
* Telecommunications Network Technologies
|
||
* Access Technologies & Operations
|
||
* Mission Infrastructure Technologies
|
||
|
||
Leadership Positions:
|
||
* CAPT [REDACTED]
|
||
* Deputy Chief, ROC
|
||
* LCDR [REDACTED]
|
||
* D-Chief, STO
|
||
* LT [REDACTED]
|
||
* Chief, Iran MAC (IMAC)
|
||
* CTNCS [REDACTED]
|
||
* ROC SER
|
||
* LCDR [REDACTED]
|
||
* Chief, Cyber Operations Branch
|
||
* LTJG [REDACTED]
|
||
* Tech Lead, Cyber Operations Branch
|
||
|
||
S321:
|
||
* ROC Influence (9/9/0)
|
||
* Lead (3/3/0)
|
||
* Interactive Operator (49/26/0)
|
||
* Production Operator (25/14/0)
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
17
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Data Network Technologies (S323)
|
||
|
||
* TAO
|
||
* Requirements & Targeting
|
||
* Remote operations Center
|
||
* **Data Network Technologies**
|
||
* Telecommunications Network Technologies
|
||
* Access Technologies & Operations
|
||
* Mission Infrastructure Technologies
|
||
|
||
Leadership Positions:
|
||
* LT [REDACTED]
|
||
* Chief, Cyber Technologies Branch
|
||
* LT [REDACTED]
|
||
* Chief, Engineering Services Division
|
||
|
||
S323:
|
||
* Development (Officer) (2/2/0)
|
||
* Development (Enlisted) (16/6/0)
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
18
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Access Technologies & Operations (S328)
|
||
|
||
|
||
* TAO
|
||
* Requirements & Targeting
|
||
* Remote operations Center
|
||
* Data Network Technologies
|
||
* Telecommunications Network Technologies
|
||
* **Access Technologies & Operations**
|
||
* Mission Infrastructure Technologies
|
||
|
||
Leadership Positions:
|
||
* LT [REDACTED]
|
||
* Chief, Operations Branch
|
||
* LT [REDACTED]
|
||
* D-Chief, EAO
|
||
|
||
S328:
|
||
* ATO (Officer) (4/4/0)
|
||
* ATO (Enlisted) (23/15/1)
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
19
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Remaining Personnel / Summary
|
||
|
||
S325 - Mission Infrastructure Technologies:
|
||
* Infrastructure (Enlisted) (7/1/0)
|
||
|
||
S352 – Global Access Operations:
|
||
* Global Access (Officer) (0/1/0)
|
||
* Global Access (Enlisted) (1/1/1)
|
||
|
||
10 Dept Summary:
|
||
* Officers**
|
||
* 28 BA / 26 COB = 93%
|
||
* Enlisted
|
||
* 182 BA / 101 COB = 55%
|
||
|
||
\** 2/9 CS P-coded officer billets filled; need M.S. Computer Science personnel
|
||
|
||
[Billet Description (BA/COB/Deployed)]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
20
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Operations Summary
|
||
|
||
### Weekly Interactive CNE operations
|
||
|
||
**ALL**
|
||
|
||
| | Operators | | Ops Conducted | |
|
||
| :------- | :-------- | :-------- | :------------ | :-------- |
|
||
| All | 208 | 100.00% | 2588 | 100.00% |
|
||
| CIV | 70 | 33.65% | 1059 | 40.92% |
|
||
| NAVY | 52 | 25.00% | 674 | 26.04% |
|
||
| AF | 44 | 21.15% | 343 | 13.25% |
|
||
| ARMY | 29 | 13.94% | 376 | 14.53% |
|
||
| USMC | 11 | 5.29% | 108 | 4.17% |
|
||
| USCG | 2 | 0.96% | 28 | 1.08% |
|
||
|
||
**NAVY**
|
||
|
||
| | Operators | | Ops Conducted | |
|
||
| :------- | :-------- | :-------- | :------------ | :-------- |
|
||
| NAVY | 52 | 100.00% | 674 | 100.00% |
|
||
| NIOC-M | 28 | 53.85% | 292 | 43.32% |
|
||
| NIOC-T | 10 | 19.23% | 133 | 19.73% |
|
||
| NIOC-G | 8 | 15.38% | 107 | 15.88% |
|
||
| NIOC-H | 6 | 11.54% | 142 | 21.07% |
|
||
|
||
### Target Sets - R&T Analysts
|
||
|
||
* China
|
||
* Russia
|
||
* Iran
|
||
* Afghanistan
|
||
* Pakistan
|
||
* India
|
||
* Iraq
|
||
* Counterterrorism
|
||
* Cyber Counterintelligence (CCI)
|
||
|
||
Supporting Roles
|
||
|
||
* ROC Senior Watch Officers
|
||
* Development
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
21
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Target Example: [REDACTED] MAC
|
||
|
||
Team [REDACTED]
|
||
|
||
* MAC: Mission Aligned Cell – puts analysts and operators together to increase target familiarity and efficiency of operations
|
||
* Joint military and civilian entity
|
||
|
||
[REDACTED]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
22
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Target Example: [REDACTED] (NSA-G)
|
||
|
||
* Current TAO Targets
|
||
* Political
|
||
* [REDACTED] leadership to include Ministry of Interior, Parliament Members, and Presidential Palace
|
||
* Military
|
||
* Former Commander of [REDACTED] Common Border Force
|
||
* Col. [REDACTED] IT Directorate
|
||
* Gen. [REDACTED] Medical Command
|
||
* Gen. [REDACTED] (affiliation unknown)
|
||
* Col. [REDACTED] Instructor, Army Staff and Command College
|
||
* Lt. Col. [REDACTED] – Defense Ministry
|
||
* Recent Reporting
|
||
* [REDACTED] Armed Forces Reviewed Personnel Issues Regarding Retirement, Communications, and Health Care
|
||
|
||
[REDACTED]
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
23
|
||
|
||
---
|
||
|
||
TOP SECRET//COMINT//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## CTU 1060.1.1 - NROC
|
||
|
||
### FLEET FOCUS
|
||
|
||
Framework and support for Navy requirements
|
||
|
||
Provides structure to develop holistic Navy capability
|
||
|
||
CTU CDR [O-6]
|
||
* D/CDR [O4-5]
|
||
* Chief of Operations [O-3]
|
||
* Technical Director [Civilian]
|
||
|
||
Support five (5) Combined Task Elements
|
||
* CTE 1060.1.1.1
|
||
* CTE 1060.1.1.2
|
||
* CTE 1060.1.1.3
|
||
* CTE 1060.1.1.4
|
||
* CTE 1060.1.1.5
|
||
|
||
* CND-RA 1020.6.1
|
||
|
||
### JOINT FOCUS
|
||
|
||
Navy support to joint priorities
|
||
|
||
Structure supports manning requirements levied on Navy
|
||
|
||
### CTE Manning
|
||
|
||
Unix and Windows Operators:
|
||
* Exploiter Qualified (Minimum Requirement)
|
||
* Router and Firewall Operators: May shift between CTE's depending on operator specialty and mission requirement
|
||
|
||
CTE Mission Commander
|
||
* 2 Windows Operators
|
||
* 2 Basic Operators
|
||
* 2 Unix Operators
|
||
* 1 Infrastructure Operator
|
||
* 14 R&T Analyst
|
||
|
||
### Mission Alignment
|
||
|
||
* NCAT
|
||
* Service-led JCAT
|
||
* JCAT Support
|
||
* Service CNE Support
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Joint Cyber Attack Team (JCAT)
|
||
|
||
### JCAT Concept of Operations:
|
||
* Assembled for Title 10 execution support
|
||
* Mission Commanders and Operators provide full-time support to CNE operations outside of JCAT
|
||
|
||
### Current Navy Participation:
|
||
* Mission Commanders:
|
||
* LTJG [REDACTED]
|
||
* Qualification based on JQS administered by the Cyber Operations Branch
|
||
* Five (5) additional officers in training
|
||
* Operators:
|
||
* Working to certify all qualified Interactive Operators for JCAT
|
||
* Requires LOAC/ROE Briefing and Tool Training
|
||
|
||
### Requirements:
|
||
* CAUI Support
|
||
* 1 Mission Commander
|
||
* 2 CNA Operators
|
||
* TASKORD 11-0335
|
||
* 3 Mission Commanders
|
||
* 10 CNA Operators
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
---
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Afloat Computer Network Operations
|
||
|
||
AUTEC testing with USS Annapolis. 18 NOV 2011
|
||
|
||
* Interactive Operations
|
||
* Connection via:
|
||
* NEPTUNETHUNDER,
|
||
* BLINDDATE/HAPPYHOUR
|
||
* Successful exploits at 4, 6, and 8 NM with 4 watt Access Point (AP).
|
||
* Predict max connection distance to standard 100 mw AP to be 4 NM.
|
||
* Man On the Side Operations
|
||
* Inject using:
|
||
* BLINDDATE/NITESTAND
|
||
* Successful inject at 4 NM to 100 mw client computer.
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
Information Technology Directorate (ITD)
|
||
|
||
## Afloat Computer Network Operations
|
||
|
||
```
|
||
CYPHER TEXT
|
||
|
||
GW:
|
||
NETMASK:
|
||
VLAN:
|
||
|
||
PLAIN TEXT
|
||
IP: 172.31.255.x
|
||
GW: 172.31.255.14
|
||
NETMASK: 255.255.255.240
|
||
VLAN: 441
|
||
|
||
FIRST MILE GATEWAY SERVER
|
||
IP: 172.31.255.14
|
||
GW: 172.31.255.1
|
||
NETMASK: 255.255.255.240
|
||
VLAN: 441-456,588
|
||
|
||
MATCHCRIMP
|
||
WAITAUTO
|
||
|
||
SIPRNET
|
||
|
||
FLEET COMMS
|
||
|
||
IP:
|
||
GW:
|
||
NETMASK:
|
||
VLAN:
|
||
|
||
USS ANNAPOLIS SSN 760
|
||
ROUTER
|
||
|
||
PLAIN TEXT
|
||
IP:
|
||
GW:
|
||
NETMASK:
|
||
VLAN:
|
||
|
||
CYPHER TEXT
|
||
IP:
|
||
GW:
|
||
NETMASK:
|
||
VLAN:
|
||
|
||
OMNIDIRECTIONAL ANTENNA (#2 Scope)
|
||
|
||
DIRECTIONAL ANTENNA (Mission Configurable Mast)
|
||
|
||
RFDU
|
||
|
||
PASSIVE SEGMENT WIRELESS ADAPTOR
|
||
ACTIVE SEGMENT WIRELESS ADAPTOR
|
||
|
||
BLINDDATE
|
||
IP:
|
||
GW:
|
||
NETMASK:
|
||
VLAN:
|
||
|
||
ENCRYPTED NETWORK
|
||
UNENCRYPTED NETWORK
|
||
RECEIVE ONLY
|
||
TRANSMIT AND RECEIVE
|
||
|
||
NROC COLLECTION POST
|
||
ROC / TAO
|
||
|
||
NODE:
|
||
SECRET
|
||
TITLE:
|
||
NAVY BLINDDATE SYSTEM
|
||
NO: 1
|
||
```
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
---
|
||
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Questions?
|
||
|
||
NAVY INFORMATION OPERATIONS COMMAND MARYLAND
|
||
U.S. TENTH FLEET
|
||
|
||
TAO.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
TOP SECRET//SI//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
28
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
NAVY INFORMATION OPERATIONS COMMAND MARYLAND
|
||
U.S. FLEET CYBER COMM
|
||
UNITED STATES TENTH FLEET
|
||
|
||
## Network Operations - Overview
|
||
|
||
Overall classification of this brief is:
|
||
|
||
* Derived From: NSA/CSSM 1-52
|
||
* Dated: 20070108
|
||
* Declassify On: 20350101
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Describe the following network component/terms:
|
||
* Proxy Server:
|
||
* An intermediary computer that completes application network requests on behalf of a host.
|
||
* Router
|
||
* A layer 3 device used to route traffic between networks
|
||
* File Server
|
||
* A server dedicated to the hosting and sharing of files.
|
||
* Perimeter Network
|
||
* The network segment located between LAN and Internet, used to place Internet facing services like Web and Mail Servers.
|
||
* Internet
|
||
* The aggregate of publicly connected networks implementing the IP addresses
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
30
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Describe the following network component/terms:
|
||
* Intranet
|
||
* A private network not normally accessible through the internet.
|
||
* Firewall
|
||
* A mechanism to filter network traffic using rules based on attributes like source, destination, packet type, port, and session status.
|
||
* IDS (Intrusion Detection System):
|
||
* Network traffic analyzer that uses patterns to detect malicious activity.
|
||
* TACACS (Terminal Access Controller Access Control System).
|
||
* Provides authentication, authorization, and accounting control to network devices via central server.
|
||
* RADIUS (Remote Authentication Dial In User Service)
|
||
* Authentication protocol for remote users to access network resources via network access methods like Dial-in, VPN, DSL, and WAP.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
31
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Define the following cross domain solutions:
|
||
* High Assurance Guards
|
||
* Connects networks operating within different security domains. Filters traffic like a firewall but operates on all levels of the TCP/IP stack.
|
||
* SABI (Secret and Below Interoperability)
|
||
* Connection of Secret Security Domain to Security Domains of lesser classification levels.
|
||
* TSABI (Top Secret and Below Interoperability)
|
||
* Connection of Top Secret Security Domain to domains of lesser classification levels.
|
||
* Bastion Host
|
||
* A host on an internal network that is also publicly exposed to the Internet or another public network. Usually used for service hosting (web, email, etc) or as part of a firewall solution.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
32
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Describe the location of the following components in a simple networked environment:
|
||
* a. Proxy Server
|
||
* b. Router
|
||
* c. Firewall
|
||
* d. Workstation
|
||
* e. DMZ
|
||
* f. Switch
|
||
|
||
```
|
||
DMZ Segment
|
||
Internal Network
|
||
Internet
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
33
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Wireless Networking
|
||
|
||
* Define wireless networking to include the following aspects:
|
||
* Wireless Access Point
|
||
* Wired to Wireless bridging.
|
||
* 802.11 Protocols
|
||
* The set of layer 1 & 2 protocols defining the RF physical layer and media access control.
|
||
|
||
| STANDARD | Frequency Range | Modulation Method | Bit Rate |
|
||
| :-------- | :-------------- | :---------------- | :------- |
|
||
| 802.11a | 5.0 GHz | OFDM | 54 Mbps |
|
||
| 802.11b | 2.4 GHz | DSSS | 11 Mbps |
|
||
| 802.11g | 2.4 GHz | OFDM | 54 Mbps |
|
||
| 802.11n | 2.4 or 5 GHz | SDM | 600 Mbps |
|
||
|
||
* Other wireless technologies in the 2.4 GHz range include Bluetooth (802.15), cordless phones, microwaves, baby monitors, etc...
|
||
* MAC Filtering
|
||
* Only defined hardware addresses can connect to network
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
34
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Define the following application protocols/services and identify their port numbers:
|
||
* Telnet: TCP 23
|
||
* NTP (Network Time Protocol): TCP/UDP 123
|
||
* NetBEUI (NetBIOS Extended User Interface): Non routable transport protocol used in pre-WinXP LAN's.
|
||
* Net BIOS (Network Basic Input/Output System): TCP/UDP 139
|
||
* FTP (File Transfer Protocol): TCP 21
|
||
* POP3 (Post Office Protocol 3): TCP 110
|
||
* RPC (Remote Procedure Call):
|
||
* SUN/UNIX: TCP 111, 32771
|
||
* WIN: TCP/UDP 135
|
||
* HTTP (Hypertext Transfer Protocol): TCP 80
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
35
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Define the following application protocols/services and identify their port numbers (continued...) :
|
||
* SMTP (Simple Mail Transfer Protocol): TCP 25
|
||
* DNS (Domain Name System): TCP/UDP 53
|
||
* SNMP (Simple Network Management Protocol): UDP 161
|
||
* SSL (Secure Socket Layer): Presentation Layer protocol for use by applications to secure communications
|
||
* SSH (Secure Shell): TCP 22
|
||
* TFTP (Trivial FTP): UDP 69
|
||
* HTTPS (HTTP Secure): TCP 443
|
||
* FTPS ():
|
||
* DHCP (Dynamic Host Configuration Protocol): UDP 67
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
36
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Network Layer Protocols
|
||
|
||
* Define the following network layer protocols to include their relationship to TCP/IP:
|
||
* IP
|
||
* Layer 3 (Network) used for network addressing and routing
|
||
* TCP
|
||
* Layer 4 (Transport) used for application session and reliable delivery
|
||
* UDP
|
||
* Layer 4 (Transport) used for application communication.
|
||
* ARP
|
||
* Layer 2 (Link) used for Mapping IP addresses to MAC Addresses
|
||
* RARP
|
||
* Layer 2 (Link) used for Mapping MAC addressees to IP Addresses
|
||
* ICMP
|
||
* Layer 3 (Network) used for Network Diagnostics
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
37
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## OSI Model
|
||
|
||
* List and describe the 7 layers of the OSI Model:
|
||
|
||
```
|
||
Encapsulation
|
||
Data
|
||
TCP Header DATA
|
||
IP Header Data
|
||
LLC Header Data FCS
|
||
MAC Header Data FCS
|
||
1100101011010
|
||
|
||
Layer Name
|
||
Application
|
||
Presentation
|
||
Session
|
||
Segment Transport
|
||
Packet Network
|
||
Frame Data Link
|
||
Physical
|
||
|
||
Routers
|
||
Switches
|
||
Cabling
|
||
|
||
| Layer No. | Function | Examples |
|
||
| --------- | -------------------------------------------------------------- | ---------------- |
|
||
| Layer 7 | User Interface | Telnet HTTP |
|
||
| Layer 6 | Encryption and Other Processing | JPEG ASCII7 |
|
||
| Layer 5 | Manages Multiple Applications | OS Scheduling |
|
||
| Layer 4 | Provides Reliable and Unreliable Delivery and Error Correction | TCP UDP |
|
||
| Layer 3 | Provides Logical Addressing Used by Routers | IP IPX |
|
||
| Layer 2 | Access Endpoints with MAC Address Error Detection Correction | 802/3 HDLC |
|
||
| Layer 1 | Specifies Voltage, Wire Speed, and Pin-Out Cables | EIA/TIA 232 V.35 |
|
||
|
||
De-Encapsulation
|
||
Data
|
||
TCP Header Data
|
||
IP Header Data
|
||
LLC Header Data FCS
|
||
MAC Header Data FCS
|
||
1100101011010
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
38
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## TCP/IP Model
|
||
|
||
* List and describe the 4 layers of the TCP/IP Model to include how they relate to the OSI Model:
|
||
* The TCP/IP model combines the Session and Presentation layers with the Application layer. It is assumed if a program has need of layer 5 or 6 functionality, then the program will have to provide it.
|
||
|
||
```
|
||
TCP IP
|
||
APPLICATIONS
|
||
Transport Layer TCP and UDP
|
||
Network Layer IP
|
||
Data Link Layer
|
||
Physical Layer
|
||
|
||
OSI
|
||
Application Layer 7
|
||
Presentation Layer 6
|
||
Session Layer 5
|
||
Transport Layer 4
|
||
Network Layer 3
|
||
Data Link Layer 2
|
||
Physical Layer 1
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
39
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## TCP 3-Way Handshake
|
||
|
||
* Define and illustrate the TCP 3-Way Handshake
|
||
|
||
* The 3-Way handshake is the method that all TCP sessions use to initialize connections and session parameters. It follows the sequence SYN, SYN-ACK, ACK. Application data can begin sending with the final ACK packet.
|
||
|
||
```
|
||
A
|
||
Computer A sends a synchronize message to B containing a sequence number; seq=100.
|
||
|
||
B
|
||
Computer B acknowledges that it received the message by incrementing the sequence number (called an "ACK"). It also sends its own sequence; ack=101,syn=300.
|
||
|
||
Computer A receives the Ack it expects and the connection is now established. All communication will now send incremented syns and acks to ensure a good connection; syn=102,ack=301.
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
40
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## TCP Flags
|
||
|
||
* Define and briefly describe the use of the following TCP flags:
|
||
* SYN: Used to initialize the TCP by setting the packet sequence number
|
||
* ACK: Used to acknowledge receipt of all package sequences up the number indicated
|
||
* PSH: Indicates that that all data already received should be given to the application as soon as possible. Flushes the buffer.
|
||
* URG: Urgent Data. Commonly used for interrupts.
|
||
* FIN: Indicates there is no more data to send from that end of the connection. Session closes after both ends acknowledge FINs
|
||
* RST: Immediate termination of connection. Commonly used to indicate unavailable service.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
41
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Protocol Headers
|
||
|
||
* Define and describe the structure of the following protocol headers:
|
||
* IP
|
||
|
||
```
|
||
0 15 16 31
|
||
+-------+-------+---------------+---------------------+ ^
|
||
| 4-bit | 4-bit | 8-bit type of | 16-bit total | |
|
||
|version| header| service (TOS) | length (in bytes) | |
|
||
| | length| | | |
|
||
+-------+-------+---------------+-------+-------------+ |
|
||
| | 3-bit | 13-bit | |
|
||
| 16-bit identification | flags | fragment | |
|
||
| | | offset | |
|
||
+---------------+---------------+-------+-------------+ |
|
||
| 8-bit time | | | | 20 bytes
|
||
| to live | 8-bit protocol| 16-bit header | |
|
||
| (TTL) | | checksum | |
|
||
+---------------+---------------+---------------------+ |
|
||
| | |
|
||
| 32-bit source IP address | |
|
||
| | |
|
||
+-----------------------------------------------------+ |
|
||
| | |
|
||
| 32-bit destination IP address | |
|
||
| | v
|
||
+-----------------------------------------------------+
|
||
/ \
|
||
| options (if any) |
|
||
\ /
|
||
+-----------------------------------------------------+
|
||
/ \
|
||
| data |
|
||
\ /
|
||
+-----------------------------------------------------+
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
42
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Protocol Headers
|
||
|
||
* Define and describe the structure of the following protocol headers:
|
||
* TCP
|
||
|
||
```
|
||
0 15 16 31
|
||
+-----------------+-------------------+ ^
|
||
| 16-bit source | 16-bit destination| |
|
||
| port number | port number | |
|
||
+-----------------+-------------------+ |
|
||
| | |
|
||
| 32-bit sequence number | |
|
||
| | |
|
||
+-------------------------------------+ |
|
||
| | |
|
||
| 32-bit acknowledgment number | | 20 bytes
|
||
| | |
|
||
+------+----------+-+-+-+-+-+-+-------+ |
|
||
|4-bit | |U|A|P|R|S|F| | |
|
||
|header| reserved |R|C|S|S|Y|I| 16-bit| |
|
||
|length| (6 bits) |G|K|H|T|N|N| window| |
|
||
| | | | | | | | | size | |
|
||
+------+----------+-+-+-+-+-+-+-------+ |
|
||
| 16-bit TCP | 16-bit urgent | |
|
||
| checksum | pointer | |
|
||
+-----------------+-------------------+ v
|
||
/ \
|
||
| options (if any) |
|
||
\ /
|
||
+-------------------------------------+
|
||
/ \
|
||
| data (if any) |
|
||
\ /
|
||
+-------------------------------------+
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
43
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Protocol Headers
|
||
|
||
* Define and describe the structure of the following protocol headers:
|
||
* UDP
|
||
|
||
```
|
||
0 15 16 31
|
||
+-----------------+-------------------+ ^
|
||
| 16-bit source | 16-bit destination| |
|
||
| port number | port number | |
|
||
+-----------------+-------------------+ | 8 bytes
|
||
| 16-bit UDP | 16-bit UDP | |
|
||
| length | checksum | |
|
||
+-----------------+-------------------+ v
|
||
/ \
|
||
| data (if any) |
|
||
\ /
|
||
+-------------------------------------+
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
44
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## MAC Addressing
|
||
|
||
* Discuss the following as it pertains to MAC Addressing:
|
||
* LENGTH OF MAC ADDRESS IN BITS: 48
|
||
* DISPLAY OF MAC ADDRESS: Hexadecimal Format 00:8e:f0:59:31:ae
|
||
* LOCATION OF MAC ADDRESS: First 48 bits in message
|
||
* MANUFACTURER SPECIFIC BITS: First 3 Octets
|
||
* HOST SPECIFIC BITS: Last 3 Octets
|
||
|
||
```
|
||
OUI
|
||
_________________________________
|
||
/ \
|
||
1st octet 2nd octet 3rd octet 4th octet 5th octet 6th octet
|
||
+------------+-------------+-------------+-------------+-------------+-------------+
|
||
| 10111101 | 01110101 | 11001111 | 01011111 | 01000101 | 01111010 |
|
||
+--------+-+-+-------------+-------------+-------------+-------------+-------------+
|
||
| |
|
||
| +--- G/I (group/individual) bit
|
||
|
|
||
+----- G/L (global/local) bit
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
45
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## ARP
|
||
|
||
* Discuss the following as it pertains to ARP:
|
||
* ADDRESS RESOLUTION:
|
||
* ARP (Address Resolution Protocol) facilitates the mapping between hardware addresses (MAC Address) and logical network addresses (IP Addresses). This mapping can be stored in a file or can determined through ARP broadcast requests on a local network.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
46
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## ICMP
|
||
|
||
* Discuss the following as it pertains to ICMP:
|
||
* ICMP is a protocol that defines a collection of message types commonly used for network diagnostics.
|
||
* Layer of the OSI model: ICMP (usually) consists of Layer 3 (Network) messages transported by IP.
|
||
* Ping: Message Type 8 (request) and 0 (reply). Used to determine if a device is active on the network.
|
||
* Traceroute: Uses a combination of the IP time-to-live (TTL) field and the ICMP messages 11 (time exceeded) and 3.3 (port unreachable) to determine the route a packet takes through the network.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
47
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Routing Table
|
||
|
||
* Discuss the routing table as it pertains to the router:
|
||
* The Routing Table Stores what networks are reachable through each interface along with metadata about that route.
|
||
|
||
```
|
||
10.1.0.0
|
||
E0 A S0
|
||
| Network | Interface | Metric |
|
||
| :------- | :-------- | :----- |
|
||
| 10.1.0.0 | E0 | 0 |
|
||
| 10.2.0.0 | S0 | 0 |
|
||
| 10.3.0.0 | S0 | 1 |
|
||
| 10.4.0.0 | S0 | 2 |
|
||
|
||
10.2.0.0
|
||
S0 B S1
|
||
| Network | Interface | Metric |
|
||
| :------- | :-------- | :----- |
|
||
| 10.2.0.0 | S0 | 0 |
|
||
| 10.3.0.0 | S1 | 0 |
|
||
| 10.4.0.0 | S1 | 1 |
|
||
| 10.1.0.0 | S0 | 1 |
|
||
|
||
10.3.0.0 10.4.0.0
|
||
S0 C E0
|
||
| Network | Interface | Metric |
|
||
| :------- | :-------- | :----- |
|
||
| 10.3.0.0 | S0 | 0 |
|
||
| 10.4.0.0 | E0 | 0 |
|
||
| 10.2.0.0 | S0 | 1 |
|
||
| 10.1.0.0 | S0 | 2 |
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
48
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## IP Addressing
|
||
|
||
* Discuss the following as it pertains to ranges of IP addressing:
|
||
* Classful networks were the original method of distributing address groups to organizations.
|
||
* Class A: First 8 bits for Network ID and the last 24 bits for Host ID.
|
||
* 126 Networks : 16,277,214 Hosts/net
|
||
* Class B: First 16 bits for Network ID and the last 16 bits for Host ID.
|
||
* 16,384 Networks : 65,534 Hosts/net
|
||
* Class C: First 24 bits for Network ID and the last 8 bits for the Host ID.
|
||
* 2,097,152 Networks : 254 Hosts/net
|
||
|
||
```
|
||
/ \
|
||
/ \
|
||
( First ) --- 0 ---> [ Class A Address ]
|
||
\ Bit? /
|
||
\ /
|
||
|
|
||
1
|
||
|
|
||
v
|
||
/ \
|
||
/ \
|
||
( Second) --- 0 ---> [ Class B Address ]
|
||
\ Bit? /
|
||
\ /
|
||
|
|
||
1
|
||
|
|
||
v
|
||
/ \
|
||
/ \
|
||
( Third ) --- 0 ---> [ Class C Address ]
|
||
\ Bit? /
|
||
\ /
|
||
|
|
||
1
|
||
|
|
||
v
|
||
/ \
|
||
/ \
|
||
( Fourth) --- 0 ---> [ Class D Address ]
|
||
\ Bit? /
|
||
\ /
|
||
|
|
||
1
|
||
|
|
||
v
|
||
[ Class E Address ]
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
49
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## TCP/IP
|
||
|
||
* Discuss the following as it pertains to TCP/IP:
|
||
* Number of bits in an IP address: 32
|
||
* Number of octets contained in an IP address: 4
|
||
|
||
|
||
```
|
||
0 8 16 24 32
|
||
+-------+---------------+---------------+---------------+
|
||
|0| Network ID | Host ID | Class A Address
|
||
| | (bits 2-8) | (24 bits) |
|
||
+-+-------------+---------------+---------------+-------+
|
||
|1 0| Network ID | Host ID | Class B Address
|
||
| | (bits 3-16) | (16 bits) |
|
||
+---+---------------------------+---------------+-------+
|
||
|1 1 0| Network ID |Host ID| Class C Address
|
||
| | (bits 4-24) |(8 bits|
|
||
+-----+-----------------------------------------+-------+
|
||
|1 1 1 0| Multicast Group Address | Class D Address
|
||
| | (28 bits) |
|
||
+-------+-----------------------------------------------+
|
||
|1 1 1 1| Experimental Address ID | Class E Address
|
||
| | (bits 5-32) |
|
||
+-------+-----------------------------------------------+
|
||
```
|
||
|
||
* IPv6 has 128 bits, roughly a 300 trillion 300 trillion more
|
||
* 90,000,000,000,000,000,000,000,000,000 times the space of IPv4
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
50
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Networking Fundamentals
|
||
|
||
* Discuss the following as it pertains to the following protocols:
|
||
* TCP
|
||
* UDP
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
51
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## IP Subnets
|
||
|
||
* Discuss the following as it pertains to IP Subnets:
|
||
* Number of bits used in a subnet mask.
|
||
* How the subnet mask identifies the network portion of the of the IP address.
|
||
* Borrowing bits from the host portion of the address.
|
||
* Benefits of subnetting.
|
||
|
||
```
|
||
0 8 16 24 32
|
||
+-------+---------------+---------------+---------------+
|
||
| 200 | 13 | 94 | Host ID | Class C Network
|
||
| | | | (8 bits) | 200.13.94.0
|
||
+-------+---------------+---------------+---------------+
|
||
|
||
+---------------------------------------+---------------+ 0 Subnet ID Bits
|
||
|1 1 1 1 1 1 1 1|1 1 1 1 1 1 1 1|1 1 1 1 1 1 1 1|0 0 0 0 0 0 0 0| 8 Host ID Bits
|
||
+---------------+---------------+---------------+---------------+ (1 Subnet,
|
||
| 255 | 255 | 255 | 0 | 254 Hosts)
|
||
+---------------+---------------+---------------+---------------+
|
||
|
||
+---------------------------------------+-+-------------+ 1 Subnet ID Bit
|
||
|1 1 1 1 1 1 1 1|1 1 1 1 1 1 1 1|1 1 1 1 1 1 1 1|1|0 0 0 0 0 0 0| 7 Host ID Bits
|
||
+---------------+---------------+---------------+-+-------------+ (2 Subnets,
|
||
| 255 | 255 | 255 | 128 | 126 Hosts Each)
|
||
+---------------+---------------+---------------+---------------+
|
||
```
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
52
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## TELNET
|
||
|
||
* Discuss the following as it pertains to TELNET:
|
||
* Use: Create a Network Virtual Terminal session on a [REDACTED]
|
||
* Type of connection: TELNET uses TCP as the s[REDACTED]
|
||
* Default port number: 23
|
||
|
||
# DO NOT USE EVER!!!
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
53
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## References
|
||
|
||
1. Authorized Self-Study Guide Interconnecting Cisco Network Devices, Part 2 (ICND2): (CCNA Exam 640-802 and ICND Exam 640-816) by Steve McQuerry. Publisher: Cisco Press. Pub Date: February 13, 2008. Print ISBN-10: 1-58705-463-9.
|
||
2. Cisco Networking Simplified, Second Edition by Jim Doherty; Neil Anderson; Paul Della Maggiora. Publisher: Cisco Press. Pub Date: December 18, 2007. Print ISBN-10: 1-58720-199-2.
|
||
3. TCP/IP Guide, 1st Edition by Charles M. Kozierok. Publisher: No Starch Press. Pub Date: October 4, 2005. Print ISBN-13: 978-1-593-27047-6.
|
||
4. TCP/IP Illustrated, Volume 1: The Protocols by W. Richard Stevens. Publisher: Addison-Wesley Professional. Pub Date: December 31, 1993. Print ISBN-10: 0-201-63346-9.
|
||
5. Building Internet Firewalls, 2nd Edition by Elizabeth D. Zwicky: Simon Cooper: D. Brent Chapman. Publisher: O'Reilly Media, Inc. Pub Date: 2000/06/26.
|
||
6. Intelipedia Articles.
|
||
7. NSA Wiki Articles.
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
54
|
||
|
||
---
|
||
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
## Questions
|
||
|
||
* Questions?
|
||
|
||
NAVIOCOM Maryland
|
||
Center of Excellence for Non-Kinetic Options
|
||
SECRET//REL TO USA, AUS, CAN, GBR, NZL
|
||
|
||
55 |