Basic Networking, TCP/IP and Security

Published: Nov 25, 2018   |   4885 words with about 27 minutes reading time   |   ©2022 by Bob Smith
Category: Technology   |   Tags: Black hat Pentest Pineapple

CYBER SECURITY BASICS

EXTREME NETWORK BASICS IN 12 CONCEPTS

Down the Rabbit Hole We Go

A Matter of Trust

Hardware

TCP/IP NETWORKING - SO WHAT

Why

Layered Anatomy of A Network Device

     -------- COMPUTER ---------   CLIENT OR SERVER  
    |                           |
    |         browser           |
    |   email   |    facetime   |  APPLICATIONS
    |      |    |        |      |
    |    25|  80|   16393|      |  ports
    |   ...\ | /.....\ | /...   |
    |      -----     -----      |
    |     | TCP |   | UDP |     |  PROTOCOL MODULES  
    |      -----     -----      |  
    |         \      /          |  
    |          ------           |  
    |         |  IP  |          |  ROUTING  
    |          --*--- 10.0.0.2  |  IP addr
    |           /               |
    |   ----  /                 |  
    |  |ENET|                   |  MEDIA ACCESS CONTROLLER (MAC)
    |   --@- 08-00-39-00-2F-C3  |  MAC addr
    |      \                    |
     -------\-------------------
             |
           --o----------          ROUTER
----------o  SWITCH/AP  o-------  ETHERNET OR WIFI NETWORK
           ------o------
                 |  GATEWAY
                  -----X========  ISP

Ethernet

WiFI 802.11

Protocol Speeds (Mbit/s) Range Band Year
802.11b 2.4-11 35 m 2.4g 1999
802.11a 5 - 54 35 m 5g 1999
802.11g 2.4 - 54 38 m 2.4g 2003
802.11n 2.4 - 600 70 m 2.4/5g 2009
802.11ac 5 - 3,466.8 35 m 5g 2013
802.11ax up to 10,530 10 m 2.4/5g 2019
802.11ay up to 20,000 10 m 2.4/5g 2020

Internet Protocol (IP)

Main functions

IP Addressing

IPv4 (1981)

IPv6 (2017)

User Datagram Protocol (UDP)

Transmission Control Protocol (TCP)

Ports

Network Configuration Commands

PUBLIC WIFI HYGIENE

The Essentials

A Pineapple You Can Trust

Take-aways

  1. Use only trusted networks
  2. Don’t use the same credentials for anything
  3. Insist on multi-factor authentication

The Rest of the Story

White is the New Black

Distributed Denial of Service (DDOS)

Doesn’t Discriminate

Hacking Through the Wall

Social Engineering

Getting Ready For A Much Larger Picture

MAC Spoofing

Network injection

Caffe Latte attack

Defeats WEP. It is not necessary for the attacker to be in the area of the network using this exploit. By using a process that targets the Windows wireless stack, it is possible to obtain the WEP key from a remote client. By sending a flood of encrypted ARP requests, the assailant takes advantage of the shared key authentication and the message modification flaws in 802.11 WEP. The attacker uses the ARP responses to obtain the WEP key in less than 6 minutes.

802.11 Security

CONFIGURING ROUTERS

Configuration

Hardware

Software

Increase Wireless Performance

PUBLIC KEYS INFRASTRUCTURE (PKI) AND ENCRYPTION

Hashing Cryptography

Two Keys Are Better Than One

Hashcash Proof of Work

Block Chain (Distributed Ledgers)

Domain Name System - a “Root” of all Evils

Secure Sockets Layer (SSL)

OAUTH 2.0 (OA)

How it Works

Convenience

Here are the steps taken to establish an OA link:

  1. OpenTable registers with Google to activate site to site OA functionality.
  2. User establishes desire to link Google and OpenTable with permitted functions
  3. Google distributes user specific keys to OpenTable and user for secure handshake and data transfer

Vulnerabilities

Best Practices

For Users

  1. Verify site secure by the address starting with HTTPS and indicated in browser by key or lock icons
  2. Use free browser and site check tools from Semantic and Qualys SSL Labs

For Providers

  1. Private information including resources, credentials, authorization codes, access and refresh tokens transmit across encrypted TLS tunnels.
  2. Load balancing servers terminates the tunnel short of the resource server leaving a vulnerable gap. IETF draft OAuth 2.0 Security: Going Beyond Bearer Tokens recommends app-to-app encryption
  3. Use latest TLS and cipher suites as recommended by NIST FIPS SP 140-2, Annex A
  4. Use only the RFC 6749 Authorization Code Grant Model (sec 4.1)
    • enable authentication direct to authorization server eliminating shared client credentials
    • authorization server transmits access token direct to client removing browser from exposure
    • *support direct application access and refresh token exchange
  5. Use signed JSON Web Tokens for authorization and authentication requests [RFC7523](https://tools.ietf.org/html/rfc7523
  6. Limit access token time-to-live and number of access token requests reducing brute force attacks
  7. Use signed JSON Web Tokens for authorization and authentication requests