Don't like ads? PRO users don't see any ads ;-)
Guest

Untitled

By: a guest on Jun 27th, 2012  |  syntax: None  |  size: 99.03 KB  |  hits: 24  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1.  
  2. Introduction to Security+ 2008    
  3.  
  4.         6 domains
  5.         open standard
  6.         derived from J.T.A   job task analysis
  7.     Domains...............
  8.     Systems Security
  9.     Network Infrastructure
  10.     Access Control
  11.     Cryptography
  12.     Organizational Security
  13.     OSI Model  http://www.freesoft.org/CIE/Topics/15.htm https://secure.cbtnuggets.com/it-training-videos/series/411/4679
  14.  
  15.  
  16.  
  17. Evaluating Common Security Threats
  18.  
  19.     Privilege Escalation
  20.         increasing permissions beyond those allowed by the security policy
  21.     Malware
  22.         intentional threats
  23.         unintentional threats
  24.         internal  60%
  25.         external
  26.     Viruses
  27.         primarily spread by email
  28.         polymorphic, can modify to avoid detection
  29.         mutation, can encrypt itself to avoid detection
  30.         stealth, hides by masking itself, fake file size
  31.         retrovirus attacks antivirus software
  32.         multipartite, attacks in multiple ways, common target MS Word
  33.         armored is hard to analyse, covered with protected code
  34.         companion, attaches to programs, games, shareware and change extension
  35.         phage, alter and modify other apps and dbs, apps have to be reinstalled
  36.         macro, runs in MS Office apps and runs mini programs
  37.     Worms
  38.         doesn’t need to attach to existing app
  39.         usually consumes resources, doesn’t modify files
  40.         some are only designed to spread
  41.         common payload is to install to a backbone for a DDOS attack
  42.         has 3 parts:
  43.             enabling vulnerability
  44.             propogation mechanism
  45.             payload has an attack using local exploit
  46.     NSP-SEC Response  (network service provider security forum incident response team)
  47.         Prepare:  resources needed to respond to attacks
  48.     Identify:  identify the worm or virus
  49.     Classify:  classify the type it is
  50.     Traceback:  trace it back to its origin
  51.     React:  isolate and repair the affected system
  52.     Document:  document to process for future repairs
  53.  
  54. Trojan Horses
  55.  
  56.         Malware that looks desirable like a game, anti virus or device driver
  57.         Love Bug was a good example of a trojan horse virus and a worm propogated using email address book
  58.  
  59. System hardening,  turn off systems and services you don’t need and turning on ones that help like Firewall or Phishing filters
  60.  
  61. Spam  can be a DDOS, junk email, safe list (whitelist)
  62.  
  63. Rootkits, software exploitation,  database, other apps (office, macro), doesn’t show in taskmanager or netstat, exploits the OS, can be a trojan as well
  64.  
  65. Botnets, automatic software robots on internet, zombie hosts, installed by worms & trojan horses, controlled by remote server (usually in Windows), uses buffer overflows often
  66.  
  67. Logic Bombs, launched when conditions are met.  April fools day, 911
  68.  
  69. Spyware and Adware
  70.  
  71.         spyware can take control, monitor, redirect
  72.         collect personal info, surfing habits, redirect browsers to bad sites
  73.         spyware can change configs
  74.         adware auto displays ads and popups
  75.         most adware is legit, some are spyware
  76.             adobe reader, aim, yahoo, mess, smiley, zango, kazaa
  77.         ad-aware and spybot are tools for removal
  78.         browsers have popup blocker settings and filter levels
  79.  
  80.  
  81.     Risks to hardware and peripherals
  82.  
  83.         exploit cpu microcode errors
  84.         USB devices are todays floppies
  85.         any removable storage
  86.         dvd rw:  a virus can write to a dvd buffer called ‘eek’
  87.         cell phones:  security protocols WTLS (wireless transport layer security), ECC  Eliptic Curve Cryptography
  88.         nas: network attached storage
  89.         san:  storage area network
  90.         connects to sever farms or large data centers using high speed
  91.         DDOS (distributed denial of service) would spread quickly here
  92.         IPSEC solution provides encryption and authentication and data integrity between devices.
  93.         Routers or servers can use IPS (intrusion prevention services) based on signature, pattern matching or anomaly detection.        
  94.  
  95.        
  96.  
  97. Operating System Hardening
  98.     Service Packs and Hotfixes, not all can be rolled back
  99.  
  100.     Patches and Patch Management
  101.  
  102.             patch is a small bit of code to fix problems or applications
  103.             updates can be time based or event based (new attack)
  104.             schedule when the happen, weekends, friday night etc
  105.             test the patch in a similar setup
  106.             change Management, performing the update, tracking the update, testing, documentation, committee, contigency/backout plans for failure, based on the ITIL
  107.             Audit and Assessment, quarterly, audit to make sure the process is being done properly.  What systems have to be patched and how often.
  108.             Documentation, surveys, whitepapers, reports, display success and failures
  109.  
  110.  
  111.     Group Policy & Security Templates
  112.  
  113.         Microsoft NT/2000/2003/2008 feature
  114.         Centralized mgmt / config via active directory
  115.         controls: registry, ntfs security, audit and security policy, software installation, scripts, app settings (IE),  Use SMS or RIS for installing OSs.
  116.         GP uses Admin & Security Templates
  117.         Create / Edit …..Link.....Apply,  GPO (group policy object) gets linked to a site, domain or organizational unit.... inheritance applies and you can block it too and apply without
  118.         Policies might be account lock policy, security policy, computer policy, user policy
  119.         All stored in Active Directory database
  120.  
  121.  
  122.     Configuration Baselines
  123.  
  124.  
  125. Application Security
  126.  
  127.     Active X, Authenticode uses certs, require confirmation for download using Authenticode
  128.     JAVA, from SUN,  can allow attackers to exploit unsafe applets, solutions include blocking java applets at the firewall using IDS and IPS, intrusion detection services and intrusion protection services, application firewalls can keep these applets from running.  Manually disable in IE under Security tab / custom level
  129.     Scripting, small chunks of code that deliver functionality, cgi scripts can be problematic, javascript is more secure, JS can’t read/write files, interact with other pages in the same frameset from same site, JS can’t access cookies.
  130.     Cookies
  131.     XSS, cross site scripting, over 80% of documented security vulnerabilities, Allow code injection into web pages, also does phishing attacks and browser exploits, attack often transparent to user, XSS written in several languages, many XSS atack since 1990s, Three kinds of XSS:  dom-base (type 0), non-persistent (type 1, most common, data is provided by a web client and is used by server side scripts to place bad code in the results page), persistent (type 2, when data is offered by a user and is stored on a server and is later displayed on a web page),  prevent by: eliminating all scripts or on a domain basis, Input validation forms prevents sql injection, cookie security can tie session cookie to the IP of user
  132.     Buffer Overflows, DOS (denial of service), 2nd most common attack, app receives more data than expected, program terminates or writes beyond its memory addresses, may leave system vulnerable, could be innocently from program errors or it could be from malicious code, Code Red and SQL Slammer worms are examples
  133.     SMTP Open Relays: SMTP email server that permits third party relay of email messages, AKA insecure relay or third party relay, malicious senders can send large volumes of spam, server owner who misconfigures is often unaware, can lead to system crashes, equipment damage and loss of business, M.A.P.S (mail abuse prevention system blacklist) is now owned by TrendMicro
  134.     P2P File Sharing, morpheus, kazaa, emule, bittorrent, takes bandwidth, copyright issues, adware, spyware, viruses
  135.     Instant Messaging, can reduce productivity, clear-text, send files, gets around policies, view webcam, has additional applets that can be vulnerable,  if company uses IPSEC to encrypt data that can be more safe, can be picked up with wireless users, uses specific TCP and UDP ports
  136.     Email Phishing:   mimic companies websites like paypal, ebay, facebook to get confidential data, check the url that is supposed to be the real site, spear phishing appears to come from someone you know like your employer
  137.  
  138.    
  139. Implementing Security Applications
  140.  
  141.     HIDS/HIPS, host based intrusion detection and preventions systems.
  142.         IDS (reactive), analyzes copies of the data, doesn't’ affect throughput, will allow some mal traffic into nets/systems, needs up to date signatures.
  143.         IPS (proactive), inline solution monitors Layer 2 through 7, must be able to handle network traffic, stops malicious traffic from entering nets/ systems, needs up to date signatures.
  144.         ISO OSI Model:
  145.             7-application, dns smtp
  146.             6-presentation, translation to ascii text, encryption
  147.             5-session, allow ftp, muliple browsers, IM, telnet, remote desktop working together
  148.             4-transport, TCP and UDP operate
  149.             3-network, routed protocols
  150.             2-data link, nics, frame relay
  151.             1-physical, turns into zeros and ones, encoding
  152.         Host Based solution is installed on target laptops, know as Defense in Depth or Layered Solution
  153.         HIPS chqaracteristics
  154.             software installed on hosts, not hw
  155.             audits log files, files systems, resources
  156.             provides individual host detection (HIDS) / prevention (HIPS)
  157.             can be centrally manager (cisco MARS, NAC, NAP)
  158.             stop attacks in real time, anomaly detection
  159.             some HIPS combine best features of A/V, personal FW, and App FWs (doing deep applicatino inspection) in one.  cisco CSA (cisco security agent) can do this.
  160.             Policy groups define your policies for different groups,  HIPS intercepts operating system and application calls
  161.             HIPS is both signature based and signature based
  162.     Personal Firewalls: zone alarm, HIPS, mcafee, norton protection center, microsoft live one care.  You can block at application level, port, protocol level & network connections
  163.     Anti-Virus, quarantine, schedule updates, scans, exclude files, virus definition file
  164.     Anti-Spam
  165.     Anti-Spyware & Popup blockers, phishing settings are in advanced tab of Internet Options in IE
  166.  
  167.    
  168.  
  169.  
  170. Network Infrastructure Attacks (Part 1)
  171.  
  172.     Legacy Protocols, old unix programs, telnet should use ssh instead which encrypts creating a vpn, https => SSL/TLS cert based, get rid of NTP, instead use NTP.V3, SNMP, instead use SNMP.V3 using 3DES and AES encryption, disable protocols and services not used in OSs, routers and other HW devices.
  173.     TCP/IP Hijacking: is a type of Session Hijacking.  Scripts can create IP sequence numbers to help with hijacking.
  174.     Null Sessions: windows biggest vulnerability, SMB (server message block) communication for file/print sharing, gives the mal user the ability to connect to unsecured IPC$ share (net use), once established, many tools can be used. windows xp, vista, 2003, 2008 are safe, unpatched NT4 & 2000 machines are rampant, need most recent updates or upgrade
  175.     Spoofing: can occur at different network layers.  ARP at layer 2 (address resolution protocol) bad mac address, IP at layer 3,  uses a false source address (mac at layer 2 or ip at layer 3) to hide identity, spoofing mac addresses lets you create rogue dhcp servers or rogue wireless access points.  DNS service servers can get unrequested replies that cache bad information that get applied to valid requests for DNS.  RFC 1918 allocates private address space.  10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, 192.168.0.0 - 192.168.255.255.  
  176.     Man in the middle: attacker is between client and server (two network communicating devices), sometimes a switch or router, most try to impersonate the server
  177.     replay:  when attacker captures data with a packer sniffer, retransmits for malicious purposes, credentials, financial data, privacy data, CHAPv2 protocol will mitigate and so will IPSEC implementation
  178.     DOS and DDOS (Availability attacks): action against availability, falure of systems and services, includes botnets, DOS, DDOS, TCP SYN & ICMP Floods etc.  Botnets are often put on free hosting and fast university networks.  They aim to overwhelm servers and bandwidth.  DDOS use Handler systems to find other Agent systems that are loaded with the attack software.  DOS Flood Attacks:  TCP SYN flood starts a tcp 3 way handshake and keeps flooding as they server trys to respond.  The handshake never completes.  Limit the number of half open sessions.  Use firewall services.  Source address is typically spoofed or forged.  ICMP is used often for diagnostic tools and is used for attacks like the Ping of Death: ICMP fragments are too large and brings down the server or router, ICMP fragmentation: fills up reassembly buffers on servers or routers, Smurf attack: uses spoofed broadcast ping to get a huge number of responses.  The ping will exploit the echo request packets directed at IP broadcast addresses from remote sites.
  179.  
  180.  
  181. Network Infrastructure Attacks (Part 2)
  182.  
  183.     Domain Name Kiting:  coined by Bob Parsons of Godaddy.com, scam involving a few domain name registrars who purchase many well indexed expired domains.  Temporary web sites host these domains loaded with paid as link via search engines, domains are then dropped before 5 day grace periods, domains are perpetually trapped in scheme and unavailable to the public, ICANN presently allows this practice.
  184.  
  185.     DNS Poisoning: DNS works at the application level.  Problem since early days of DNS.  A.K.A DNS Cache poisoning, poisons with data w/ non-authoritative origins.   DNS Poisoning can be unintentional like from a misconfigured DNS servers or buggy code.  Malicious users poison a DNS with their IP and reroute you to their malicious site.  
  186.         Redirecting NS (name service) of attacking domain to target
  187.         Redirecting NS of another unrelated Domain
  188.         DNS Forgery, beats the real response before the legitimate server can, can use DNSSEC to add certs to DNS in Active Directory
  189.         Pharming is a related vulnerability.  Done by exploiting DNS vulnerabilities or by changing the client’s ‘hosts’ file.  A hacker redirects traffic to a bogus website.
  190.     ARP Poisoning:  
  191.         How ARP works:  Computer A asks who has this IP address.  Computer B says I have that IP and here is my MAC address additionally.  The switch in between them stores it in it’s CAM table.
  192.         With Reverse ARP, Computer A says who has this MAC address.  Computer B says I have that MAC and here is my IP additionally.
  193.         Some devices accept ARP replies without a request allowing a switch, client or server to be poisoned.  CAM tables get flooded with a ton of entries.
  194.         ARP operates at level 2 and 3 of the OSI model,  you can poison the ARP Cache on a server or workstation, you can poison the CAM tables  on switches, you can poison routing tables that have dynamic routing protocols like RIPv2 and OSPF.
  195.         Poisons memory buffers (layer 2 MAC addresses).
  196.         MAC Address Flood: port security commands limit the number of MAC addresses on a port.
  197.         VLANs: Virtual Area Networks, configure ports to a subnet/broadcast domain.  You can hop from one VLAN to another.
  198.         Spoofing: masquerading the DHCP protocol,  STP (spanning tree protocols) which provides loop prevention on those switches,  MACOF, ARP
  199.         DHCP snooping: listen to ports and only allow DHCP servers on specific ports, thereby limiting rogue dhcp servers.  DHCP has a field in the header that is 8 bits with 255 options that can be changed and spoofed (what domain, wins server, mail server).
  200.         Telnet sends clear text, use SSH VPN instead with Putty or Teraterm
  201.         Bad: sniffing, spoofing,  Good: snooping
  202.         HTTP GUI to manage switches for example, need HTTPS
  203.         Switches operate at layer 2
  204.     Weak Passwords:  10 or greater chars, uppercase, lowercase, numbers and symbols.  Account locked after 3 or 5 times failure, password history so you can’t reuse passwords for x new passwords.  Use mnemonic to memorize a passphrase.
  205.     Back Doors:  programs: Subseven, backorrifice, netbus, master paradise.  Programs allowing unauth remote access to system, attacker can steal, damage, excalate or deply other programs like DDOS or logic bomb...etc.  Backdoors are often planted via Trojan Horses, freeware and shareware, phishing and pharming.  Need up to date anti-virus / anti-spyware apps.  Multiple levels of programs.  They can also be code that is written into a program that allows the compromise.
  206.     Default Accounts:  Disable Wireless lan accounts or change the name and password used. Disable Guest accounts and any predefined user accounts.  Administrator account:  don’t share the admin account.  Should work as a basic user and only RUN AS administrator as needed.
  207.  
  208.  
  209. Network Design Elements and Components
  210.  
  211.     DMZ: Demilitarized Zones (aka Screened Subnets or Security Zones),  has servers on the perimeter of your network for public servers,  HTTP, SMTP, DNS, Ecommerce and FTP servers in their own security zone, protected by a firewall.  You typically have limited access from inside hosts being able to manage them.  They are being exposed to the internet or extranet partners.  It’s typically for the untrusted network (internet).  You can setup a Private Zone, Public Zone and DMZ.  Some use ZFW, zone based firewalls.  They can prevent traffic from unsafe protocols like http, imap, pop3, esmtp, rpc, peer to peer file sharing, Instant messengers.  
  212.         3 armed firewall used in small to medium sized businesses, goes into a single firewall appliance with a Public arm, Private arm and DMZ.    You can make multiple zones in the DMZ in their own VLAN or Private VLAN which prevents communicating or limited to certain rules.
  213.         Medium to Enterprise size business go further with something like a Screened Subnet which has a perimeter router with access control filters and security, then a firewall, then a switch (layer 2 or layer 3) that feeds the DMZ and then another firewall which feeds your inside corporate network.
  214.     VLANS: Virtual Lan.  A VLAN is the capability on a layer 2 switch to create a virtual or simulated network or subnetwork in the same way that routers do.  They can all be a member of the same broadcast domain.
  215.     NAT: Network Address Translation, allows us to hide internal IP addresses from outside network.   PAT (port address translation) translates internal IP/port data to “sockets” that go out over the external network.  This way the NAT device knows what IP/port to reply to by linking IP packets each socket.  This allows many internal IPs to be mapped to a single external IP address.  NAT is not a security mechanism.
  216.     NAC: Network Admission Control, sponsored by CISCO, Microsoft has NAP (NAC-NAP), enforces policy compliance on all devices using servers and agents running on trusted endpoint devices, part of defense-in-depth/layered security, works to proactively defend agains malware attacks enforcing security compliance.
  217.     Telephony: VOIP (voice over IP), phone conversations sharing wired & wireless media, leveraging inexpensive channels over the untrusted internet, VOIP introduces over 175 unique vulnerabilities to AVAYA, CISCO & Nortel,  Attacker using variety of attack methods up and down TCP/IP stack ( app, transport, internet, physical)
  218.  
  219.  
  220. Network Security Tools
  221.  
  222.     NIDS/NIPS:
  223.         Network Intrusion Detection Systems, detect and alert but allow traffic through
  224.         Network Intrusion Prevention Systems, detect and alert inline and prevent traffic through, provides detailed traffic inspection in real time.  Signature based compares against a known database.  Anomaly based looks for changes in network characteristics like change in traffic patterns.  
  225.             An NIPS can:
  226.                 Deny attackers based on IP
  227.                 Deny, attacker services based on port/protocols
  228.                 Isolate a Victim and then can deny traffic from the victim to prevent DDOS
  229.                 Deny connections
  230.                 Deny individual packets
  231.                 Do logging of attacker packets, victims packets
  232.                 Modify packets on the fly
  233.                 Produce alerts to management software
  234.                 Produce verbose alerts (memory dump)
  235.                 Create requests to block connections and individual hosts
  236.                 Rate limiting, throttling of bandwidth for a channel to stop a DOS
  237.                 Request SNMP trap information
  238.                 Reset TCP connections
  239.     FW (Firewalls):  HW and or SW solution to enforce network access security policy,  modern FWs do: access controls, terminate vpn tunnels and vpn services (IPSEC), QoS (with rate limiting) and redundancy - even IDS/IPS (intrusion detection/prevention) for total C.I A (confidentiality, integrity, availability) .  The first step towards defense-in-depth even for hosts,  hardware zone-based FW’s are superior because software based depends on the OS which adds vulnerabilities.  Some models provide multiple virtual firewalls (security contexts).  This allows you to have a firewall for a DMZ and each security zone can be managed with separate firewalls.  If you are an ISP you can have each customer have a security context.
  240.     Honeypots:  A trap to deflect, detect and counteract attacks, typical a computer, subnet, data or site which is isolated, unprotected (various degrees) & logged, for surveys, early-warning of attacks, capturing, trapping, some are designed to counteract spam for example, honeyd can simulate a large network on one host.  Honeynet connects Honeypots,  Collection of Honeypot tools is a Honeyfarm
  241.     Proxy Servers:  Gateway or Intermediary device between networks to provide a variety of services, Firewall proxies Intercept all packets and reprocesses them, NAT is a form of a Proxy Service because it represents a public IP and does translation to private addresses.  Web Server Proxies and other Application are gateways and can provide translation services.  Web Proxies can serve as a gateway for translation of XML for business servers, caching of web pages for internal users for performance, filtering and inspection for policy enforcement (no bad web sites) or apps like P2P file sharing.  Operates at several layers of the OSI model.
  242.     Protocol Analyzers: Monitors networks for capacity planning, growth, optimization, adherence to security policies and file transfer policies, but also for security but is also a vulnerability for security.  Task Manager is a basic Protocol Analyzer.  Wireshark is a free analyzer for wired and Aeropeek for wireless.   Can show from layer 1 all the way to the application layer.  These are also called packet sniffers, so they can be a vulnerability if someone installs one.
  243.     Penetration Testing: Is more of a process.  Used for evaluating security, doing risk assessment and risk management.  It’s part of the auditing process and part of the initial process of creating a security policy to see where you have risks and are vulnerable.  Checks to see if your Defense-in-depth is sufficient.  White hat hackers or crackers probe the security of systems.  Vigorously attempts to breach system.  They think like hackers and provide a regular auditing assessment of the organization’s state.
  244.  
  245.  
  246. Wireless Network Security
  247.  
  248.     Weak Encryption = WEP (wired equivalent privacy),  early standard of authentication was Open System that let anyone to connect.  Shared Key is where you put in a password on your laptop and the admin puts in one on the wireless point (WEP key).  WEP is nowhere as secure as ethernet.  The encryption uses RC4 which is good.  WPA is better because it has per user/per frame keying (generated password for each), sequence counters, larger initialization vectors.  WPA uses 48 bit IV. TKIP message integrity code(MIC) checks integrity of frame.  WPA2 is the new standard using 802.11i  (RSNA, robust security network associations)
  249.     SSID Broadcast:  is like a workgroup name.  Change it to a unique name and don’t broadcast it.  Using Aeropeek it can find out hidden SSIDs.  802.11g is one of the best choices for profile.
  250.     802.1x authentication: sits on top of ethernet and 802.11 wireless.  Can work for wired and wireless environment.   Wireless router sends credentials from a laptop to a “radius” server for authentication.   In your wireless router you can add Firewall rules.  Can also authenticate with MAC Addresses
  251.     MAC Filtering: Allows you to set a wireless router to ONLY allow a list of specific MAC addresses.  This is not secure because MAC addresses can be spoofed.
  252.     Rogue Access Points: is any device that is unauthorized.
  253.     WAR Driving:  WAR Driving with Aeropeek software shows people with no authentication, people with WEP and default SSIDs or weak WEP keys like SSID or company name.  WAR Chalking puts symbols to tell people the SSID and other credentials.
  254.     Blue Jacking:  Sending unwanted spam messages over Bluetooth.  PAN (personal area network).  Uses Bluetooth OBEX protocol.  Typically harmless guerilla marketing but now becoming vulnerable to trojan horses.  Bluesnarfing is illegal hacking of a mobile phone.
  255.     BlueSnorting:  is a free open source NIDS/NIPS for packet logging of bluetooth wireless .
  256.  
  257.  
  258. Access Control (Part 1)
  259.  
  260.     Subjects: users, systems, applications and they access objects.
  261.     Objects:  data, peripheral devices, files
  262.     Best Practices
  263.         Defence-in-Depth
  264.         Attack Surface, minimize and understand all physical, logical, electronic points of entry and exit
  265.         Least Privilege, only giving required privileges.  Add privileges granularly as needed.  Limit web page functionality by user or group.
  266.         Implicit Deny,  all access is denied by default.
  267.         Separation of Duties:  only certain people have certain permissions and get jobs rotated.
  268.         Job Rotation
  269.     Access Control Models
  270.         MAC: Mandatory Access Control.  Predefined file permission on server managed by admins.  Good for military.  Subjects get a clearance label, objects get a classification label and they get mapped.
  271.         DAC: Discretionary Access Control.  Allows an object owner to grant access to other users and applications.  Is vulnerable to trojan horses.   Labels are not mandatory.
  272.         RBAC, Role Based Access Control: Combination of MAC and DAC
  273.             Can simulate both MAC and DAC
  274.             Roles are created for various job functions and then permissions are assigned for the roles
  275.             Permission are assigned to roles
  276.             Users are not assigned access directly
  277.             RBAC is not an ACL method!  It’s a whole different application.  This is saying “What can people do”.  This person has the role of doing this particular action to a medical record.
  278.             Introduces Role Hierarchy and constraints.  A constraint places a restrictive role on inheritance of permissions from opposing roles.   You create formulase
  279.                 S (subject: person, system, service), can have more than one role
  280.                 R (role, job function or job title), can have multiple subjects and permissions
  281.                 P (permissions: approvals of certain type of access to an object or resource), can be assigned to many roles
  282.                 SE (session is a mapping of a subject, role or permission)
  283.                 SA: subject assigmnent
  284.                 PA: permission assignment
  285.             RBAS is considered an industry best practice
  286.         Rule Based Access Control
  287.             Doesn’t use RBAC acronym
  288.             A combo form of MAC and DAC
  289.             Access to resources is based on administratively defined rules.  Only admins define rules.
  290.             Access properties are stored in ACL’s (access control lists) that have rules contained in them.
  291.             Like MAC, users can’t change access controls, only system admins can
  292.         Applying Access Controls, they can be applied on a domain by domain basis using built-in accounts or admin defined.  Then groups like Domain Users can be nested in a Universal group, then a Domain Local group.
  293.         Access Control List is simply a list of permissions attached to an object and then assigned to a user.  ACLs can be used on firewalls, routers and multi layer switches to control access.  They can filter out IP address or entire networks, tcp/udp applications
  294.     Logical Access Controls
  295.     Authentication Models
  296.         Single Factor is something you know or something you have.  Enter a username/password or a PIN number.  If you have a badge you flash that’s single factor.
  297.         Two Factor: combines something you know with something you have, or something you have with something you are.
  298.             something you know.  PIN number
  299.             something you have.  ATM card, smart card
  300.         Three Factor
  301.             something you know.  PIN number
  302.             something you have.  ATM card, smart card or smart token
  303.             something you are.  biometrics, facial scan, fingerprint scan, iris scan
  304.         Single Sign On allows you to sign on one time be granted a “ticket” and get access to everything you should be able to get to.
  305.  
  306.  
  307.  
  308. Access Control (Part 2)
  309.  
  310.     Authentication Components and Protocols:  protocol is run on servers to create centralization of access management between authenticating devices and another resource.  They can store their info on back end databases.  These control access from Switches, Firewalls, Routers and NAS. TACACS+
  311.         RADIUS:     Uses UDP.  Everyone supports RASIUS.  RADIUS is used by Microsoft and encrypts just the password.  Used by Microsoft’s IAS “internet authentication service”.  Uses Unidirectional CHAP (Challenge Handshake Authentication Protocol).   Has better accounting features for hot spots to track timed usage like if you are paying for an hour of usage.  A RADIUS accounting server is a good choice.  RASIUS is more often used with 802.1x IEEE
  312.         TACACS+:  Uses TCP.  TACACS+ is more secure encrypting the entire communication and is used with 802.1x IEEE.    Separates the Authentication and Authorization features.   The Authorization server can provide access to objects, systems, services and applications.  Uses Bidirectional CHAP (Challenge Handshake Authentication Protocol), authenticating the network device and the TACACS+ server.
  313.         802.1x + EAP(extensible authentication protocols):  Has port based Access Control.  Works on top of 802.3 for a switch or 802.11 for a WAP.  Laptop is called supplicant and sends a request to get on the network by authenticators like a Switch that forwards the request to a RADIUS/TACACS server.
  314.         EAP-TLS will let you use certificates and public key infrastructure technique.
  315.     RRAS: Routing and Remote Access.  Combines hardware and Software running on a server to allow users remote access.  Supports Dialup networks, VPN using PPT/MPPE (tunneling/encryption) or VPN using L2TP/IPSEC
  316.     LDAP:  Lightweight Directory Access Protocol
  317.     KERBEROS: Runs on Active Directory, KDC (key distribution center), TGS (ticket granting server).  As users log into the RRAS server it talks over LDAP protocol to the Active Directory server and tickets are used to prove the users identity.  It can also serve as a SIngle Sign On solution because the get granted tickets for each server, app, partition, os they need access to.  Kerberos is built on “symmetric key cryptography” PKI.
  318.     Policies are network and connectivity settings for users:  time of day they can log on, for how long, filtering of IP/TCP/UDP.
  319.     PAP:  Password Authentication Protocol.  Sent in clear text.
  320.     CHAP: Challenge Handshake Authentication Protocol.  Very popular and works with ppp.   One way hash is done against password and is sent to the networks access server.    Provides protection against playback attacks.  Microsoft has MS-CHAP.  and CHAP has CHAPv2.  CHAPv2 has the ability to authenticate the server too.
  321.     EAP: Extensible Authentication Protocol used in 802.1X
  322.     VPN extends your network to a larger network.  Could be someone dialing up or over an external network.
  323.     Identification vs Authentication:  Identification can be done on two endpoint devices with a shared user name/id, system name or router name.  Authentication is about challenging the claim by who provided the identification which might use Fingerprint, Facial or Iris scans.
  324.     Physical Access Security Methods
  325.         Access logs/lists
  326.         Hardware Locks on workstations and laptops,  lock USB ports with software locks.  Use the fingerprint scanner on the pc.
  327.         ID Badges can have tokens like RFID you can pass in front of a sensor
  328.         Door Access Systems,  Fail secure locks when power goes out.  Fail safe lock unlocks when power fails.  Can add biometric sensors with locks.
  329.         Man-Trap, 2 door system
  330.         Video Surveillance, cameras to watch.  Keep aware of diversion techniques and piggybacking.
  331.  
  332.  
  333. Assessments and Audits (Part 1)
  334.  
  335.     Risk Assessment
  336.         Key component of security strategy (threat analysis comes first)
  337.         Includes process of anticipating risk
  338.         Will govern steps to take in addressing vulnerabilities and threats
  339.         Asset ID & Valuation → Risk (threat/vulnerability) → Controls & Counter Measures → Evaluation Auditing → Action Plan → Residual Risk  →  (back to Asset ID & Evaluation)
  340.         Controls include kerberos, authentication systems, physical security, vpns
  341.         Counter measures include intrusion detection, intrusion prevention, firewalls, honeypots
  342.         Evaluation includes evaluating the effectiveness by doing some pilot testing and staging and auditing  the of the counter measures and controls on our existing security posture
  343.         Action Plan:  decides what need to be purchased or configured.
  344.         Residual Risk:  the risk you are willing to accept or get insurance for
  345.     Qualifying Risk:
  346.         Exposure Factor is a % that indicates how much damage an incident can cause on a specific asset.  You have to do it for each asset.
  347.         Annualized Rate of Occurence is how often an incident occurs per year, based on information gathering statistics, historical data, case studies or information from insurance companies.
  348.         Asset Value x Exposure Factor (EF) = Single Loss Expectancy (SLE)
  349.         SLE x Annualized Rate of Occurence (ARO) = Annual Loss Expectancy (ALE)
  350.         Assign risk levels 5 high........2 low, 1 none, used for logical assests, good will, forumulas, intellectual property.
  351.     Defining Risks
  352.         Origin: is the risk an internal structured attack or internal unstructured (an accident, poor planning, lack of enforcement of security policies) or is it external structured attack or just a bot working our perimeter routers.  Hostile employees, consultants, people not properly trained.  Is your risk being defined by HIPPA or Sarbanes Oxley.
  353.         Activity or Event:   Somebody stealing confidential data, power failures, DOS attacks
  354.         Consequences: results, impacts, unavailability of ecommerce servers, losing market share, having legal authorities coming into your facility, reduction of good will
  355.         Specific Causes: Floods, human error, design error, hurricanes, human intervention, failure to plan.
  356.         Lack of Protective Mechanisms: no firewall, no security suites on laptops
  357.         Time and Place: Are you in the wrong place at the wrong time, vulnerable to environmental disasters.
  358.     Major Risk Management Strategies
  359.         Accept the risk: we have valued our assets and a specific risk is too expensive to address
  360.         Mitigate the risk:  spend the money and time on people, physical security, controls and counter measures (IDS, IPS, VPN, IPSEC internal and external solution, CIA, FWs, ACLs, honeypot)
  361.         Transfer the risk:  if we have an incident we will charge more and pass it to the customer or insure the risk
  362.         Cease and Desist:  stop doing whatever causes the risk
  363.     Vulnerability Assessment: is done after you have a prepared team of people with a knowledge of threats.  Get information about known vulnerabilities.
  364.         Port scanners: nmap, shows ports used and open, nmap.org, insecure.org
  365.         Ping scanners (net mapping)
  366.         Protocol Analyzers
  367.         Password Crackers
  368.         Oval - Open Vulnerability Assessment Software: sponsored by NCSD (national cyber security division of homeland security) and provides it’s content to US-CERT and others.  It is a common language to look for vulnerabilities.  Provides formats in XML and SQL.  Provides baseline CVE (common vulnerabilities and exposures).  Characteristics include: OS, Software apps, Registry settings, Config files, Files system attributes and more.  So you want OVAL compliant tools so you are standardized.
  369.         Wireless Analyzers
  370.     Mitigation: Controls and Countermeasures:  
  371.         Technical: Access control mechanisms, identification schemes, authentication mechanisms, encryption, intrusion detection software.
  372.         Non-Technical:  Operational controls (written security policies), policies and procedures,  best practices, operational procedures, personal security, physical security and environmental security.
  373.         Preventative Controls:  stops attempts to violate security policy C.I.A.
  374.         Detective Controls:  IDS, IPS, Alerts, Auditing, checksums at layer 2,3,4 of OSI model
  375.         Corrective Controls: after the fact, Incident management, remediate vulnerabilities, backup procedures, IPS that works with firewalls to block ports and processes.
  376.         Compensatory:  they compensate for increased risk by adding additional control steps to mitigate risk.  You might add a challenge / response to weak access controls.  You might add another factor to authentication. Single for Two factor, might add a Third factor.
  377.         Deterrent:  things to deter hackers.  Offering a reward to identify hackers.
  378.     Penetration Testing Overview:   evaluates the security of an organization, a server or a service
  379.         Evaluating security by simulating an attack
  380.         Proactive analysis for vulnerabilities
  381.         Determines feasibility of attack and BIA (business impact analysis), what would be the impact.
  382.         Leads to GAP analysis then Action plan,  finds gaps / holes in security.  Penetration testing and Security gap analysis are part of a full blown audit process.
  383.         Black Box vs. White Box Penetration, black box has no prior knowledge of the system, white box has all the infrastructure data.
  384.         Full Disclosure: you know services available and the entire configuration , Partial: you know what the services / apps and security policy are but not configuration specifics, Blind Tests
  385.         OSSTMM (open source security testing methodology manual)
  386.         NIST (national institutes of standards and technology)  OSSTMM is more comprehensive.
  387.         ISSAF (Information system security assessment framework)
  388.  
  389.  
  390. Assessments and Audits (Part 2)
  391.  
  392.     Monitoring and Analysis Tools: AiroPeek, iNetTools, can be used as an attack if you run continuous ping.  Ping Scan scans an address range for information gathering and risk assessment.  Trace Route shows the hops through the network.  DNS Lookup, Name to IP Scan, Name lookup.  Port scan shows what ports are open on TCP/UDP ports. Service scanning looks for services by port.  Finger (name protocol) uses TCP port 79 to show if a user is logged on, email address, files in users home dir.  Finger is very insecure as shown by the Morris Worm.  Whois shows who owns a domain name.  Throughput shows speed of data on network.  
  393.         Certificate templates, shows all templates and security templates that can be used for certificate services using PKI
  394.         Event Viewer
  395.             Security log has success audits
  396.         IAS (radius server)
  397.         IP Security Monitor Tool to view IPSEC VPN traffic
  398.         Performance Logs and Alerts
  399.         Routing and Remote Access for Dialup access
  400.         Security Configuration and Analysis tools
  401.         Security Templates, predefined domain security template
  402.         Wireless Monitor
  403.         Reliability and Performance Monitor:  shows reliability and availability for hardware, app, windows and misc failures.
  404.         Windows Firewall:  Monitoring of domain profile, private profile, public profile, log location.
  405.     IDS (intrusion detection systems) Detection / Monitoring Methodologies
  406.         Signature Based:  defined signatures used to detect attacks or vulnerabilities, compares data in the network traffic against a database of known signature.
  407.         Anomaly Based: Monitors the network for a departure in “normal” baseline behaviour.  When norms are deviated, they can trigger an anomaly.  Statistical Anomaly Detection checks baseline statistics and compares with current activitiy..  Non-statistical has predefined definition of known behaviour.  They can find if routing protocols originated from an end user workstation or a TCP packet where the source and destination address/port are the same or IPX traffic where only TCP traffic is used.  On a wireless device it could find a rogue DHCP server.
  408.         Behaviour Based (policy): triggers on violation of policy or configured behaviour.  It must have a clear view of what the expected behaviour or security policy is.  Typically very reliable and focused.  Can make custom signatures with XML.  Takes a good amount of work up front.
  409.     Logging Procedures: Event Viewer: Application log, Security log, System log,   IPSEC log.  Syslog server is third party to log events.  Syslog is a popular protocol.  Kiwi is a free syslog server.  Logging is a proactive process.
  410.         SDEE (Security Device Event Exchange), proposed by the ICSA (international computer security association): secure standard to replace syslog and defines the format of messages to communicate between security devices.
  411.     SNMP:  Simple Network Management Protocol.  SNMP can manage servers, routers, switches, hubs, vpn concentrators.... etc.  One or more systems can manage them.  Agents send data to the managing systems using SNMP protocol.  This has a security hole because it passes a lot of data.  The passwords use “community strings” in clear text (read only or read/write).  SNMP is a WEAK protocol.
  412.         SNMP v3 is the current standard in 2004 and has 3 important features:
  413.             Authentication
  414.             Encryption with 3DES, AES or DES
  415.             Access Control mechanisms
  416.  
  417.  
  418. General Cryptography Concepts
  419.  
  420.     Cryptography Defined
  421.         Cryptography is where you develop and use codes.  Cryptanalysis is where you break the codes.
  422.         Cryptography is used mainly for encryption & authentication
  423.         Cryptography is the process of rendering data unreadable
  424.         Cryptography uses authentication and can be applied to the involved parties (users or systems) to verify they are who they say they are.
  425.         Cryptography can also be applied to the message contents to improve the integrity of the data so it doesn’t change in transit.
  426.         Encryption changes clear text to cipher text
  427.         Hashing takes the original message and runs it through an algorithm and getting a result which is appended to the message and compared by the receiver.
  428.         Caesar Cipher: is a substitution cipher that substitutes letters of the alphabet.
  429.             Keying variable:  tells you how vulnerable you are.  Like if you have just 26 letters it’s easier for a brute force attack.
  430.             Crypto Algorithm:  how the letters are being substituted.
  431.             Plain Text:  the text being ciphered
  432.     Symmetric vs Asymmetric:
  433.         Overview
  434.             Desirable attributes include:
  435.             Resist cryptographic attacks
  436.             Support variable and long key lengths (password used in the process)
  437.             Be scalable
  438.             Import / Export the keys
  439.             Avalanche effect (changing a few 0’s and 1’s) should cause the result (cipher text) to completely change.
  440.             Sym algo: means you have the same key you encrypt with to decrypt with
  441.             Asym algo:  uses different keys to encrypt and decrypt the data.  PKI: public key, private key
  442.             Key + Algo + Data
  443.         Symmetric key algorithms:  
  444.             sender has the same key as the receiver.  
  445.             Key range from 40 bit to 256 bit.
  446.             DES-56 (cracked already), 3DES-112,   AES - (128, 192, 256), IDEA -128, Blowfish 32 to 448, RC2, RC4 (used by WEP wireless), RC5, RC6 - 40 to 256 bit keys
  447.             Commonly use techniques are block ciphers (blocks of data), stream ciphers (streams of data), message authentication codes (MACs) used for the hashing process.
  448.             Symmetric algorithms are speedy and can be accelerated by hardware easily.
  449.             Key management is a drawback since they have the same key at both ends.
  450.             Diffie Helmen is a key management algorithm for key exchange
  451.         Asymmetric Encryption Algorithms
  452.             A.K.A. Public Key Algorithms,  encrypt/decrypt keys are different
  453.             Key lengths 512 - 4096 bits
  454.             Good for digital signatures and setting up secure channels where encrypted data can later be sent.
  455.             Much slower than symmetric and good for low volume exchanges.
  456.             RSA, ElGamal, Elliptic curves and DH (Diffie Helman)
  457.  
  458.     C.I A.N: Confidentiality, Integrity, Availability/Authenticity, Non-Repudiation
  459.         Confidentiality:  protect information so only accessed by authorized users and only when there is a need.
  460.         Integrity:  means the data cannot be created, modified or deleted without authorization.  Data stored in one part of a data system is going to have agreement with other data in other parts of the system.  $2500 transaction should agree from source to destination.
  461.         Availability: system uses the right controls to keep data available and functioning properly when needed.  Like to prevent a DOS
  462.         Authenticity: verifies that the user, object or system is genuine and have not been forged or spoofed.
  463.         Non-Repudiation:  One party cannot deny having received a transaction, nor can the other deny having sent a transaction.
  464.  
  465.     Algorithm Comparision:
  466.         Block:   Block cipher transforms a fixed length block of text data to a block of cipher data of the same length.  DES uses an 8 byte block size.  Cipher text is longer than plain text usually.  DES, 3DES AES IDEA, Blowfish, Skipjack
  467.         Stream:  Operate on bits 0s and 1’s.  The size of the message won’t typically change.  Transformation of smaller plain text units will vary depending on when they are encountered in the encryption.   DES, 3DES in output feedback mode (OFM) or cipher feedback mode (CFM), RC4, SEAL,
  468.             RSA & DH are considered trusted
  469.         DES is no longer trusted.  Does the algo provide enough protection against a brute force attack.  AES is highly recommended.
  470.         The longer the key the more processing overhead.
  471.  
  472.     Trusted Platform Module (TPM):  used to authenticate hardware devices.  It’s a spec for software written to firmware.   provides secure generation of cryptographic keys and hardware pseudo random number generator.  The hardware has an RSA key burned into it.
  473.         Remote attestation:  creates a nearly unforgeable hash key summary of hardware and software configuration.
  474.         Supports full disk encryption,  example:  bitlocker
  475.         Supports digital rights management, software license protection and enforcement, password protection
  476.  
  477.  
  478. Cryptography Algorithms and Protocols
  479.  
  480.     First battle won by cryptographic failure: Tanenberg.  Russians sent out communications in clear and Germans intercepted it.
  481.     Hashing concepts and protocols, used to secure passwords on network devices, or in authentication protocols like CHAP (for 2 devices or 2 users), or to provide data integrity when sent over the wire.  Based on one way mathematical functions.  Fixed length hash is known as a digest or fingerprint.  Hashing is similar to a CRC checksum that’s done in basic layer 2 communications with frames but it’s much stronger.
  482.         It’s almost impossible to reverse a one way hash to the original text.  With CHAP it can pass a hash over the network and not the username and password.
  483.         Rainbow Crack is a list of hashes that can match captured hashes with a database.
  484.         On a Cisco router you can run ‘service password-encryption’ and it hashes all existing paswords on the system.  It is not as safe as MD5 which comes from “enable secret” command.
  485.         SNMP V3 uses HMAC with MD5 or SHA protocol to authenticate the devices.
  486.         Hashing algorithms: used to generate one time and one way responses to challenges and authentication protocols like CHAP.  Also used with EAP (extensible access protocol) in wired and wireless environment specifically with EAP MD5.  Hashing can also be used to provide data integrity with file integrity checkers with digitally signed contracts and public key infrastructure certificates.  It can also provide proof of authenticity when used with symmetric secret authentication keys such as in an IPSEC environment.  Routing protocols also use it to authenticate routers to one another.
  487.             SHA (secure hash algorithm), designed by NSA (national security agency), published in the NIST(national institute of standards and technology).  Types include  SHA1 and SHA2(224,256,384, 512).  SHA1 gives a message digest 160 bits in length and is the most used.  SHA3 is coming.  It’s used in SSL/TLS, PGP, SSH, SMIME and IPSEC
  488.             MD5:  Message Digest Algorithm 5,  widely used but not completely secure.  Uses 128 bit.  Designed by Ron Rivest in 1991.   Used worldwide for integrity mechanisms.  Fileservers often provide them for file downloads.  Popular in Unix and in Cisco.
  489.                 It’s used in SSL/TLS, PGP, SSH, SMIME and IPSEC
  490.             Lanman:  obsolete in Microsoft Windows pre NT.  Was used to store windows passwords.  Is a block cipher based on DES and easily cracked.
  491.             NTLM:  (NT LanManager) Used with SMB (Server Message Block protocol), (has been replaced by Microsoft with CIFS and refers to MS-CHAP.  Use with remote access protocols. MS-CHAP1 and MS-CHAP2 are widespread.  NTLM V2  was introduced in Windows NT SP4 and is used most often.  Kerberos (designed by MIT) is now preferred in Active Directory domains replacing NTLM.
  492.                 NTLM is used when clients authenticate to a server with an IP, or if a user authenticates to server that belongs to a different active directory forest or a server that has no domain at all (workgroup or peer to peer network).  NTLM is also used if a firewall restricts the ports that Kerberos needs.
  493.     Encryption Algorithms Revisited
  494.         DES: obsolete with 56 bit key size, designed by IBM
  495.         3DES:  much more secure, approved by NIST through 2030
  496.         RSA:  used for PKI digital signatures.  Widely used in electronic commerce protocols.
  497.         PGP:  Pretty Good Privacy.  An application that provides cryptographic privacy and authentication.  Used for signing, digital signatures for users, applications, drivers, hardware.  Use for emails to encrypt and decrypt.  Follows Open PGP standard and is an asymmetric solution with private and public keys.   Uses public key cryptography.   It also supports message authentication and integrity checking (using a hash or message digest from the plain text and then creates a digital signature from that hash using the sender’s private keys).  PGP3 is the latest version and is widely used.
  498.         Elliptic Curve:  (ECC)  For handheld wireless devices.   Diffie Helmen group 7 uses ECC.
  499.         AES / AES 256:  The defacto standard recommended by the US government.  Uses a substitution permutation method.  AES is fast in hardware and software and easy to implement. Doesn’t use much memory and is very popular.  Used for winzip, pkzip, full disk encryption, Open SSL, Secure FTP.  AES is now an option for an IPSEC implementation.
  500.         One Time Pad:  OTP.  Original plain text gets grouped up with a pad / random key and is only used one time.   It is used for perfect secrecy.
  501.     Additional Protocols:  
  502.         SSL/TLS:   SSL (secure socket layer).   TLS (transport layer security) is the successor to SSL.  Used to provide secure communications over untrusted networks like the internet and is used for things like: faxing, email, instant messaging, web browsing and data transfers.  They are essentially the same protocols.  Current browsers are using TLS.  It provides endpoint authentication and privacy using cryptography.    When a TLS connection starts, the following happens:
  503.             Peer negotiation for support of different algorithms
  504.             Key exchange and authentication process
  505.             Symmetric cipher encryption and message authentication
  506.             Typically they use public key algorithms or preshared TLS keys.  
  507.             Typical algorithms used for the key exchange process are RSA, Diffie Helman, PSK (pre shared key).  
  508.             For authentication typically you use RSA, DSA, RC3, 3DES, AES or IDEA
  509.             For the hashing function typically you use  HMAC MD5 or HMAC SHA which is stronger
  510.         S/MIME: Secure Multipurpose Internet Mail Extensions.  Open standard for public key encryption and is used to digitally sign email that is in the MIME protocol.  Developed by RSA Data Security.
  511.             Provides cryptographic security for email applications including privacy and data security through encryption, authentication, message integrity and non-repudiation.  All email apps and browsers have it.   It’s a PKI technology using certificate authorities like Verisign or Thawte.
  512.         PPTP:  Point to Point Tunneling Protocol works with Point to Point protocol by sending a regular PPP session to it’s peer within the generic routing GRE protocol.  PPTP is PPP in a GRE tunnel.    Was the first protocol supported by Microsoft’s dial up networking.
  513.             Authentication:  PPTP does the tunneling for VPNs but connections are validated with MS-CHAP v2 or EAP-TLS (extensible authentication protocol)
  514.             Encryption:  MPPE (Microsoft Point to Point Encryption protocol as defined in RFC 3078)
  515.         HTTPS:   Hypertext transfer protocol over Secure Sockets Layer, secures web traffic on port 443 using SSL or more commonly TLS, adds a layer of encryption and authentication between HTTP and TCP layer 4.  Designed by Netscape.  
  516.         SHTTP:  Alternative, Used for ecommerce but not used often.  Pretty much dead.
  517.         L2TP:    Layer 2 Transport Protocol,  VPN tunneling at Layer 2.  Born from Ciscos Layer 2 Forwarding and Microsofts PPTP.  L2TP version 3 adds additional security, improved encapsulation and the ability to  transfer data links other than simply PPP over an IP network, the familiar things like Frame Relay, Ethernet and ATM.  L2TP acts and performs like an OSI Layer 2 protocol for tunneling network traffic between two endpoints over untrusted networks like the Internet.  Its actually a Layer 5 session layer protocol and it uses UDP (User Datagram Protocol)  on port 1701.  It’s very common to carry PPP sessions over an L2TP tunnel.  It doesn’t provide confidentiality or strong authentication.  It’s really a tunneling protocol that is combined with IPSEC to secure the L2TP packets.
  518.         IPSEC:   Internet Protocol Security framework.  Provides confidentiality, authentication and integrity.  Is a suite of protocols to provide secure IP communications by authenticating and encrypting each packet in the data stream.   It also provides cryptographic key establishment which is why it is used in a Public Key infrastructure. IPSEC is a Layer 3 protocol, the network layer of the OSI model, whereas SSL, TLS and SSH operate at layers 4 through 7 of the OSI model.  IPSEC is more flexible and can protect layer 4 protocols that include TCP and UDP.  IPSEC is superior over SSL and TLS because the applications don’t have to be designed to use IPSEC.  It uses the IKE (Internet Key Exchange) protocol to handle the negotiation between the two peers.  It negotiates the protocol and algorithms based on security associations and policies.
  519.         SSH:   Secure Shell.  Creates a secure channel to exchange data on a network.  Started in Unix/Linux and is used to replace the insecure Telnet.  SSH uses public key cryptography to authenticate the remote computer and let the remote computer authenticate the user optionally.  SSH server listens on port 22.  SSH can secure FTP, synchronization, SCP, SSH login.  SSH can be a full VPN using Putty or TeraTerm.
  520.  
  521. Public Key Infrastructure (PKI)
  522.  
  523.     Key Management:  strength of key is based almost entirely on the length of the key.  3DES or AES can only be broken with brute force and is theoretically impossible.  The number of bits depends on the level of sensitivity of the information.  Longer keys have a bigger hit to performance through routers, servers or firewalls.
  524.         Generation: typically automated by good random number generators
  525.         Verification: makes sure weak keys can’t be used in generation
  526.         Storage: store on highly available system, with fault tolerance on a secure system, private keys need to be kept private.
  527.         Exchange: need a secure channel to distribute and exchange keys.
  528.         Revocation:  need a way to revoke outdated, invalid keys that may have expired certificates.
  529.         Destruction: erases keys so malicious hackers can’t get to them.
  530.     Digital Signatures: provide unique proof of data source generated by a single party.  They can authenticate users by using the private key of that user and a signature that private key generates.  They can prove authenticity and integrity of PKI certificates.  They provide a secure timestamp.  They provide the same functionality of a handwritten signature.
  531.         provides authenticity of digitally signed data
  532.         provides integrity of digitally signed data
  533.         provides non-repudiation of digitally signed data
  534.     Asymmetric Encryption Revisited:  deals with a public key / private key.  They have two main goals:  confidentiality and authentication.  They offer non-repudiation and integrity of a secure channel. Think RSA for the digital signature.    Symmetric encryption on the other hand is used to encrypt large chunks of data or email messages.  
  535.         a user uses a signature algorithm with her signature key or private key.  Based on the input of the private key into the signature algorithm the output becomes her digital signature.  
  536.             The sending device will attach the digital signature to her original message resulting in a digitally signed message.  The receiving device verifies the signature with her public key.  The sender and receiver are relying on some CA (certificate authority) to issue these keys.  
  537.             The receiving device is going to input the message, the digital signature and the public key into the signature algorithm and it will check the validity of the signature.  If successful the it is a verified signature and the document has integrity and was originated by the user.
  538.             They can also be used to authenticate code or device drivers to verify integrity and the source.
  539.             They are built on extremely complex mathematical formulas.
  540.             Great for exchanging symmetric keys when the symmetric algorithm has no facility to exchange keys like to exchange private shared keys.  The asymmetric encryption can  protect the channel for exchange.
  541.             Uses key pairs (public & private):  both keys can encrypt but
  542.                 if you encrypt with the private key, then the public key decrypts the data.
  543.                 if you encrypt with the public key, then the private key decrypts the data.
  544.                 only one host has the private key, thereby validating the authenticity of the sender.
  545.             Also known as Public Key Encryption
  546.             RSA, DSA, DH, ElGamal, ECC (elliptic curve technology for hand helds)
  547.                 RSA is the most common (Rivest, Shamir and Adleman),  in the public domain.  Easiest to understand an implement.  It’s very flexible because it has variable key lengths that allow you to trade off speed for security if necessary.  512 to 2048 bits range.  RSA is based on the difficulty of factoring extremely large numbers.  Typically used for the long haul, are changed regularly and can be renewed after months or years.  RSA signatures are at the core of PKI.
  548.             512 to 4096 bits (1024 + are trusted)
  549.         DH Key Exchange (Diffie Hellman):     With symmetric encryption we know there is a shared secret key between both parties.  Diffie Hellman is at the foundation of most modern key exchange methodologies.  The IKE protocol and IPSEC and VPN use Diffie Hellman extensively to give us a reliable and trusted methodology for exchanging keys over untrusted channels.  DH can generate keying material and also provides key management for other algorithms like 3DES and AES.
  550.             Provices secure key exchange over untrusted channels like the internet.
  551.             Once exchanged, those keys can be used to generate other keys that can be used for IPSEC for example.
  552.             Establishes secret keys taht can be used for Symmetric Encryption like 3DES or AES or to generate the secret keys used for hashing like data integrity and HMAC’s like MD5 and SHA1.
  553.             DH is in RFCs 2409 and 3526.
  554.     PKI Principles, Standards, and Roles:
  555.         Framework to support large scale public key based technologies
  556.         Set of Tech, Org and Legal components to establish C.I.A.N. (confidentiality, integrity, authenticity, and non-repudiation)  through public key cryptography (ASYMM key cryptography).
  557.         Certificate: Digital doc that binds entity name and public key signed by certificate authority.  It also defines the protocol used.  The CA is the trusted third party that signs the public keys of the players in the PKI based system.  The certificate of a user will always be signed by a CA.  Every CA has its own certificate that contains its public key that is self signed.  This is called a self-signed CA certificate.
  558.         PKI Areas: CA’s, PKI Users (people, companies, devices, vpn concentrators, firewalls and servers), Storage and Protocols, LRA’s (local registration authorities), Supporting Legal Framework
  559.         CA’s: Verisign, Thawte, Entrust, RSA, CyberTrust, Microsoft, Novell
  560.             Root CA that generates directly to users is not scalable but can be used for a segregated authority like Microsoft might for it’s inside employees.
  561.             Multiple CAs is more scalable.  Top level CA can generate certs to subordinate CAs.  This has better scalability, managability and you can distribute trust decisions down to smaller branches or sub organizations.  A large multi national corporation might have a Root CA that generates certificates to level 2 CAs who put the certs out to the end users.  Every cert has a path (chain) that leads back to the Root CA.  
  562.             Cross Certifying:  Multiple flat single root CA’s that have trust relationships horizontally by cross certifying their own certificates.  
  563.                 Usage Keys:  some PKIs’ require the user to have 2 key pairs.  
  564.                     One pair is for encryption only using 3DES with a short key length for example.
  565.                     The other pair is for signing only using RSA for example with 1024 to 2048 bit lengths.
  566.             Certificate Authorities
  567.                 X.509 format is often used.  X509.3 is the most widely used and is found in secure web servers using SSL and TLS, used in web browsers with SSL and TLS, used with S/MIME, PGP, used in IPSEC VPNs and specifically the IKE protocol
  568.                 PKI requires interoperability with other standards and protocols like the X.500, the PKCS (public key cryptography standard) and LDAP
  569.                     PKCS defines of algorithms, application protocol interfaces and data formats that are used in PKI.  There are many standards:  
  570.                         PKCS1 is the RSA standard
  571.                         PKCS3 is the Diffie Hellman key exchange standard
  572.                 IETF is responsible for the PKI standards
  573.                 public keys are used for authentication
  574.                 trusted third party certs provide scalability
  575.                 Certs are also used in an 802.1X environment which includes 802.3 which is Ethernet and 802.11 which is wireless using EAP.TLS (extensible authentication protocol).
  576.                 CAs are the most scalable, global authentication solution and X.509 format is the most ubiquitous format
  577.  
  578.  
  579. Organizational Security (Part 1)
  580.  
  581.     Alternate Disaster Recovery Sites
  582.         Hot Sites:  offsite facility with redundant systems so you can simply move over to that location in an emergency.  Hot Site is also called the “Active Backup Model”.  This allows the fastest way to get back up in an emergency.
  583.         Warm Sites:  similar to hot site but requires some level in installation, setup and administration in and emergency. Bringing systems online, restoring data etc.  Some companies create Reciprocal Agreements to share the costs of a warm site.  Should be outside your common geographic area.  Requires advance planning, testing and access to media for recovery.  
  584.         Cold Sites:  have no configuration, might be an empty warehouse with electricity.  Might be a wireless network environment.  Used when you might be there for a long time.  They are least expensive but require the most planning, pilot testing and the most resources to get going. Cold sites might not have security either.
  585.  
  586.     Redundancy Planning:
  587.         Single Points of Failure: can occure in all mission critical devices, email server, routers, switches, IPS sensors, Sharepoint, Kerberos in a Windows 2003 environment, file servers.   A cluster of servers might be represented by one IP but behind it you have a wide variety of devices, using network load balancing, round robin techniques, a cluster using active active clustering.  If one device goes down, the other can take over transparently.  The goal is 99.999 % uptime.  Duplicates !
  588.         RAID (redundant array of independent disks): use for redundancy of data using inexpensive arrays of disks.  Keep spare drives to rebuild arrays.
  589.         Redundant Servers / ISP / Conns:
  590.         U.P.S.:  uninteruptible power supply
  591.         Backup Generators:
  592.         Spare Parts:  you need to have spares to keep things going.  Drives, power supplies, memory.
  593.     Redundancy Components:
  594.     Disaster Recovery Procedures:
  595.         Non Disaster: business is unavailable for a few hours either intentionally or not.  It’s simply a non disaster.
  596.         Disasters:  loss of operability for over 24 hours.  Doesn’t mean total distruction.  It makes the facility unstable.
  597.         Catastrophes:   Destroys the entire facility,  fire earthquake or other man made or natural disasters.
  598.         Disaster Recover Objectives:
  599.             Protecting People
  600.             Protecting the Goodwill or name of company, shareholders, competitive advantage.
  601.             Protecting Data
  602.             Resuming of Business Functions: get back in a timely manner
  603.             Minimize Decision Making During Disaster:  comes from good planning, documentation, clear thinking from leaders.
  604.             Rehearsed Plans and Procedures
  605.         Requires Planning, Exercises, Backup and Storage (offsite) and Restoration
  606.     Incident Response:  often under Incident Manager role.
  607.         Incident response defined:  an occurance that has caused damage or has the potential to cause damage.  Incident response is about a teams capability to respond to unexpected events to control or limit damage and to maintain or restore normal operations.  A plan must be in place to define the responses.  AIW (acceptable interuption window).
  608.         Forensics:
  609.             AAA:  
  610.                 Acquire: gather information on disks, usb keys, ram and system logs
  611.                 Authenticate:  making sure evidence presented is the actual evidence collected in the investigation.
  612.                 Analyze:  
  613.             Investigation procedures includes:  Identification, Preservation, Collection, Examination, Analysis, Presentation and Decision
  614.         Chain of Custody: is a log or diary of the chain that evidence was collected
  615.             Who collected it, How and Where was it taken?
  616.             Who took possession w/ date and timestamp
  617.             How was it transported
  618.             How was it stored and protected while there.
  619.             Who removed it from storage and why ?
  620.             if it’s compromised it’s “tainted” evidence.
  621.             www.sans.org has several pages dedicated to this activity,  SCORE (security consensus operational readiness evaluation)
  622.         First Responders: these are the incident response handlers and must have good communications to everyone in the company and outside authorities like police and fire departments.
  623.         Damage / Loss Controls:  Damage Controls describes actions necessary to deal with any problem that could jeopardize a particular project or endeavor or security implementation process.  Loss Controls deal with retail industries like shoplifting and losing of inventory to your own workers and can even be losing information or data to our own employees.  Involves monitoring and auditing of our own employees to make sure they are not installing company software on their own computers or taking company devices home.
  624.  
  625.  
  626. Organizational Security (Part 2)
  627.  
  628.     Secure Disposals:
  629.         Info storage and retention policy:  must be able to downgrade information and limit the amount of time that information is going to be retained or reviewed or hardware and storage is going to be retained.  Review on a regular basis if information is going to be retained or removed.  It be mandated by DOD or some other organization like Sarbanes Oxley or HIPAA.
  630.         Disposition workflow:  determining when data is being created how long it will be retained so someone is messaged to start a workflow process.
  631.         Information Destruction Policy:  should include shredding or incineration.
  632.         Re-Sale of Systems:  drives should be zeroed out and degaussed (disk wiping).  Low level format. Windows systems can use debug command to do a low level format.  Licensed software must be removed or it violates EULA.
  633.     AUP (acceptable use policy): deal with computers provided by an organization and lays out what activities are allowed and prohibited on the equipment.  It could say they are for company business only.  I might cover usage policies for: web, email, private usage.  Also information and procedures regarding telephone system usage.  How to deal with questions for grey areas.  Might have to call HR or IT.
  634.     Mandatory Vacations: they create opportunities for cross training of duties (rotation of duties).   Helps prevent single point of failure and cuts down on fraud.
  635.     PII (personally identifiable info):  OPPA (online privacy protection act).  This makes forensics more difficult.
  636.     Due Care and Diligence: the process of learning all the risks that are known, weaknesses in the code.  Can tie into risk assessment and analysis when looking at other companies and their security or someone to become a strategic partner
  637.     Due Process: a person has a right to be notified and be heard in an orderly proceding to protect their own rights.  If you are going to terminate someone and try to prosecute them in a court of law, you need to follow the concepts and principles of due process giving individuals the ability to enforce their rights.
  638.     SLA (service level agreement):
  639.         Agreement between service provider / vendor and you or your company
  640.         May be security or availability related
  641.         Outline contractual obligations and deliverables
  642.         May even exist inter-department internally
  643.         Also known as maintenance contracts
  644.         MTBF (mean time between failure)  vs  MTTR (mean time to repair).  MTTR doesn’t often include the time to get the part.
  645.     Security Aware HR:
  646.         Hiring and termination, process based on voluntary or involuntary, locking accounts
  647.         Training and awareness
  648.         Ethics Policies: CPSR (Computer Professionals for Social Responsibility)
  649.         Background Checks
  650.         Privacy (HIPAA)
  651.  
  652.  
  653. Organizational Security (Part 3)
  654.  
  655.     Environmental Controls:  used to control heat and humidity, fire suppression, the three components of a fire are heat, fuel and oxygen (trilogy of fire).  Shielding with a faraday cage can prevent EMI (electromagnetic interference) and RFI (radio frequency interference).  Lights and motoers can cause EMI so make sure all signal lines are shielded and grounded properly.  Things that generate EMI should be as physically separated from cabling as possible.
  656.     Social Engineering:  
  657.         teaching how Phishing can be presented in email,  instant messaging
  658.         Hoaxes,  a person claims to be an IT admin and need credentials or personal info.  Someone describing themselves as a janitorial service, maintenance worker, pest control trying to get information.
  659.         Someone piggybacking into a secure area.
  660.         Shoulder surfing, looking over someone’s shoulder, using telescopes or binaculars
  661.         Have admin timeout so inactivity logs  people out.
  662.         Make sure users know to logoff or lock OS when not in use
  663.         Dumpster divers looking for information, don’t throw old hard drives away until zeroed out.
  664.         End user education and awareness training should be happening constantly quarterly or semi-annually.
  665.     Survey of Security + Acronyms
  666.         3DES — Triple Digital Encryption Standard
  667.         ACL — Access Control List
  668.         AES - Advanced Encryption Standard
  669.         AES256  — Advanced Encryption Standards 256bit
  670.         AH - Authentication Header
  671.         ALE - Annualized Loss Expectancy
  672.         ARO - Annualized Rate of Occurrence
  673.         ARP - Address Resolution Protocol
  674.         AUP - Acceptable Use Policy
  675.         BIOS — Basic Input/Output System
  676.         BOTS — Network Robots
  677.         CA — Certificate Authority
  678.         CAN - Controller Area Network
  679.         CCTV - Closed-circuit television
  680.         CHAP — Challenge Handshake Authentication Protocol
  681.         CRL— Certification Revocation List
  682.         DAC — Discretionary Access Control
  683.         DDOS — Distributed Denial of Service
  684.         DES— Digital Encryption Standard
  685.         DHCP — Dynamic Host Configuration Protocol
  686.         DLL - Dynamic Link Library
  687.         DMZ — Demilitarized Zone
  688.         DNS — Domain Name Service (Server)
  689.         DOS - Denial of Service
  690.         EAP - Extensible Authentication Protocol
  691.         ECC - Elliptic Curve Cryptography
  692.         FTP - File Transfer Protocol
  693.         GRE - Generic Routing Encapsulation
  694.         RIDS- Host Based Intrusion Detection System
  695.         HIPS - Host Based Intrusion Prevention System
  696.         HTTP - Hypertext Transfer Protocol
  697.         HTTPS - Hypertext Transfer Protocol over SSL
  698.         HVAC - Heating, Ventilation Air Conditioning
  699.         ICMP - Internet Control Message Protocol
  700.         ID - Identification
  701.         IM - Instant messaging
  702.         IMAP4 - Internet Message Access Protocol v4
  703.         IP - Internet Protocol
  704.         IPSEC - Internet Protocol Security
  705.         IRC - Internet Relay Chat
  706.         ISP - Internet Service Provider
  707.         KDC - Key Distribution Center
  708.         L2TP - Layer 2 Tunneling Protocol
  709.         LANMAN - Local Area Network Manager
  710.         LDAP - Lightweight Directory Access Protocol
  711.         MAC - Mandatory Access Control Media Access Control
  712.         MAC - Message Authentication Code
  713.         MAN - Metropolitan Area Network
  714.         MD5 - Message Digest 5  
  715.         MSCHAP - Microsoft Challenge Handshake Authentication  Protocol
  716.         S/MIME - Secure.' Multipurpose Internet Mail Extensions
  717.         SCSI - Small Computer System Interlace
  718.         SHA - Secure Hashing Algorithm
  719.         SHTTP - Secure Hypertext Transfer Protocol
  720.         SLA - Service Level Agreement
  721.         SLE - Single Loss Expectancy
  722.         SMTP - Simple Mail Transfer Protocol
  723.         SNMP - Simple Network Management Protocol
  724.         SPIM - Spam over Internet Messaging
  725.         SSH - Secure Shell
  726.         SSL - Secure Sockets Layer 550- Single Sign On
  727.         SIP - Shielded Twisted Pair
  728.         TACACS - Terminal Access Controller Access Control System
  729.         TCRIP - Transmission Control Protocol Internet Protocol
  730.         TKIP - Temporal Key Integrity Protocol
  731.         TKIP - Temporal Key Interchange Protocol
  732.         TLS - Transport Layer Security
  733.         TPArt- Trusted Platform Module
  734.         UPS - Uninterruptible Power Supply
  735.         UR L - Universal Resource Locator
  736.         USE - Universal Serial Bus
  737.         UTP - Unshielded Twisted Pair
  738.         VLAN Virtual LOCal Area Network
  739.         VolP - Voice over IP
  740.         VPN - Virtual Private Network
  741.         WEP - Wired Equivalent Privacy
  742.         WPA - Wi-Fi Protected Access
  743.  
  744.  
  745. Network Security Domain Update
  746.  
  747.     All In One Security Applicances:
  748.         Firewall device
  749.         Can inspect traffic and make sure protocols are operating properly.  
  750.         Can do url  filtering with white/black lists.  
  751.         Threat detection to look for scanners on traffic.  
  752.         Anti-spoofing.  
  753.         Can be a certificate server and manage certificates.  
  754.         Can be a concentrator or gateway for different types of VPNs.  
  755.         Even includes virtual appliances.
  756.         Modular lets you add IPS module
  757.         Content Security:  anti spam, spyware, virus, url filtering, anti-phishing
  758.     Layer 2 Security: consider what devices are connected to each port.  Can people do VLAN hopping attacks or VLAN double tagging attacks.  Make sure latops, ip phones, pcs, workstations, biz hubs and printers are hard coded as access ports.  Ports that connect to other switches carrying VLANs are trunk ports.  Set the switchport mode to nonegotiate and not dynamic.  Set switchport to protected.  That isolates the port from communicating with other protected ports.  Port security maximum 3 only allows 3 mac addresses on that port.  Prevents flooding of CAM or MAC address table.  Hard code the mac addresses that can connect.  Use port based authentication.  Violation determines the consequences of rules: protect, restrict or shutdown the port.  Set aging policy for how long mac addresses stay in the table based on time or inactivity. Don’t forget about 802.1X (whatever that means).
  759.     Virtualization and Cloud Computing: Virtualization is a security problem because people can easily install virtual servers and virtual software on a machine and make rogue servers, dhcp, dns, default gateways or routers.  We can also virtualize firewalls and IPS sensors.  Desktop Managers can deny access if a client has a host being emulated with a VM.  They can also check for keystroke loggers.  Some backend servers like a URL filtering service could be performed by someone like TrendMicro in the cloud who would provide the black lists of bad URLs.
  760.     IPv4 vs IPv6:   www.ipv6vsipv4.com   ipv6 has 128 bits, ipv4 has 32 bits.  
  761.         Both have most of the same threats - IPv6 closes some doors but opens others
  762.         Coexistence and Migration = Vulnerability
  763.         Reconnaissance:  early attack used to gather information, using port scanners, ip scanners and sniffers.  Scanning with ipv6 isn’t feasible because the address space is so big.
  764.         Viruses and Worms:  in both version but worms that do random addresses are not as big of a risk
  765.         Unauth Access:  ipv6 has new extension headers that open new attack vectors.
  766.         Mobile lP:  is embedded in ipv6 with some new security.
  767.         Header Manipulation: ipv6 has new extension headers that open new attack vectors.
  768.         Sniffing:  works in both ipv4 and ipv6 and is countered using cryptographic measures to convert the information to cypher text.
  769.         Fragmentation:  is a big problem in ipv4, ipv6 doesn’t have as much a problem
  770.         Application Layer Attacks:  IPSEC increases security
  771.         Spoofing:  still a problem in ipv6 since you still have tunneling.
  772.         Rogue Devices:  big problem in ipv4.  in ipv6 we can use IPSEC to use 802.1X port based authentication to block unauthorized devices from connecting.
  773.         Resolution Attacks:  still has dhcp vulnerabilities but using stateless autoconfiguration in ipv6 instead of ARP so it is an improvement.
  774.         Man-In-the-Middle Attacks:  using a good key management strategy with IPSEC will help out.  Make sure your keys are protected.
  775.         Smurf Attacks:  a broadcast amplification attack and not in ipv6
  776.         Flooding Attacks: new types of traffic in IPv6 does open up some vulnerabilities.
  777.         Routing Attacks:  native support for IP security will countermeasure these.
  778.     Wireless Security Enhancements
  779.         WPA2 (WiFi Protected Access):  Based on 802.11i (RSN, robust security networks) and is the next generation of  WPA which was an interim solution for WEP.   WPA2 is the WiFi Alliance delivery or version of the 802.11i.  There is WPA2 Personal or WPA2 Enterprise.    WPA2 Personal uses weak preshared keys and passphrases which is a vulnerability.   Risks:  Encryption keys are compromised or network resources are placed at risk.  Crackers get the passphrase by using social engineering or an offline brute force dictionary attack.  WPA2 Corporate uses CCMP/AES for Confidentiality and 802.1X/EAP for Authenticity and Integrity
  780.         EAP (Extensible Authentication Protocol):   Is the original extension of PPP - now 802.1X (3748).  Very flexible - 1 way or 2 way Authentication,    
  781.             Messages sent with EAPOL (EAP Over Lan) from supplicant to authenticator
  782.             Messages sent from authenticator to back end (AAA) server is RADIUS
  783.         LEAP:  weak EAP protocol, do not use. Was easy to deploy, used static WEP encryption.  ASLEAP is a tool that can compromise (crack / exploit)LEAP.  EAP-FAST uses PACs (protected access credentials) which are like certificates.
  784.         PEAP:  an extension of LEAP.  Considered a strong EAP extension.  Uses encrypted TLS tunnels.  Most common widely supported EAP method.  Flavors of PEAP:  uses EAP MS-CHAPv2, uses SSL/TLS, EAP-GTC (supports token based authentication)
  785.         TKIP (Temporal Key Integrity Protocol):  Meant to replace WEP.
  786.             Firmware upgrade to improve security.
  787.             Still uses RC4 like WEP but adds:
  788.                 temporal keys (dynamically generated temporary keys)
  789.                 sequencing: sequences the protocol data units and drops TKIP data units if out of order
  790.                 key mixing: complex 2 step cryptographic mixing process that generates stronger seeding material for RC4 as opposed to WEP that had that weak 24 bit initialization vector
  791.                 better data integrity from MIC (message integrity code/check) which defeats bit flipping and forgery attacks that were used against the WEP protocol
  792.         CCMP:  Counter mode with cipher block message authentication code protocol
  793.             802.11i replacement for WEP and TKIP
  794.             Uses AES block instead of RC4 stream
  795.             Usually needs new hardware
  796.             Has many components, different key sizes because of AES.  
  797.             Any new wireless security implementation will be using CCMP as your Confidentiality, Authenticity and Integrity mechanism.
  798.         Antenna Placement:  place antennas so you don’t have interference from other neighbors and don’t extend too far from your building where outside people can sniff.
  799.         Power Controls:  If boosting power, consider the radiation pattern and if it goes too far.
  800.  
  801.  
  802. Compliance and Operational Security Domain Update
  803.  
  804.     Handling Risk
  805.         Risk management vs. Risk Avoidance
  806.             Reduce to acceptable levels  or Ignore the risk
  807.             Basic yet difficult or Insure the risk level
  808.             Put together the best practices or Offload to a third party consulting firm
  809.  
  810.             Will management traffic like Telnet, SSH, SSL/TLS or SNMP on it’s own VLAN or In Band with your data traffic.  Will you use IPSEC or SSL/TLS
  811.             Will you use secure version of time servers like NTPv3 to synchronize ?
  812.             Do you have a strict password policy, badges, do you allow piggybacking ?
  813.             Do you have a wireless production network ?  Is it secure.
  814.             Are you using SNMP v2c and are you using read/write community strings ?  Use Read Only.
  815.             E-banking: requires identifying the threats, performing a risk assessment and risk analysis and implement risk management.  
  816.     Basic Forensics Procedures
  817.         Introduction:  IOCE (international organization on computer evidence), SWDGE (scientific working group on digital evidence)
  818.         Basics of forensics:  MOM (motive, opportunity & means)
  819.             motive, who did the crime and why did they do the crime
  820.             opportunity, where, when of cybercrime, exploit of a vulnerability, AUP, holes in firewall, unpatched servers, no anti-virus, spam
  821.             means, capabilities to successfully perform an exploit or attack, admin access, weak password policy
  822.             network analysis: analyze all ingress/egress points, dialup networks, wan/lan connections, choke points where routers/firewalls are, be able to analyze logs in servers, firewalls or IPS,  need to use path tracing back to the source of an incident
  823.             media analysis: be able to image disks and pull info off disks and how disks can be cleaned and how to extract data after cleaning.  Steganography.  
  824.             software analysis: can it be reverse engineered, is your software protected with digital signatures, review and look for malicious code on your systems, look for potential exploits using penetration testing.
  825.         Investigative Phases:
  826.             Identification: detect events, listen to complaints, do monitoring and auditing, do profile detection
  827.             Preservation: involves chain of custody, have a proper system to maintain evidence, time synchronization
  828.             Collection: collection of evidence
  829.             Examination: taking the basic facts and information gathering
  830.             Analysis:  analyzing the data
  831.             Presentation: presentation to law enforcement, stake holders, steering committees
  832.             Decision: how to act, may involve law enforcement or internal discipline
  833.         Anti-forensics: works around forensics
  834.             hiding data: by obfuscation or encrypting the data or using steganography, using slackspace in memory
  835.             artifact wiping: eliminating files or file systems, data remanence, also programs can do the wiping and then delete themselves
  836.             trail obfuscation: confuses examiners, cleaning up logs, using layer 2 or 3 spoofing, misinformation, fake accounts, trojan commands,  TimeStomp is a tool that lets you modify files
  837.         Standards of Evidence:
  838.             Best: signed contract, not oral, video
  839.             Secondary: not as reliable, like oral evidence or copies of documents
  840.             Direct: can prove facts by itself to prove a point, typically from a witness
  841.             Conclusive: irrefutable and uncontradictable evidence
  842.             Circumstantial: can prove intermediate fact, can be used to deduce or assume the existence of another existing fact.
  843.             Corroborative: supports other evidence like circumstantial or secondary evidence
  844.             Hearsay: oral or written evidence from 2nd hand information. similar to circumstantial evidence
  845.         Tools of the Trade:
  846.             tags and labels
  847.             forms and documentation
  848.             gloves & anti-static bands
  849.             pliers, screwdrivers, tweezers, cutters
  850.             evidence bags, tape, ties, markers & pens
  851.             magnifier glass
  852.             recorder, laptop to mp3 files
  853.             experience
  854.     Security Awareness and Training
  855.         ATE: Awareness Training and Education
  856.             Awareness, WHAT, informational, retaining information about how to be the best most secure employee you can, teach through videos, posters, newsletters.  Is a short term thing.  Bring up in Bi-monthly meetings
  857.             Training: is the HOW, it’s the knowledge/skillset, through lectures, case studies, hands on practice, CBT nuggets, problem solving, recognition of attacks. Intermediate time frame
  858.             Education is the WHY and is long term deep understanding, reading and study, seminars and discussions, degrees, certifications.
  859.         Review user habits: sometimes force user habits with NAC (network admission control) or NAP (network access policy) software to force updates.  Is the desk clean and free of sensitive information and that passwords are not on sticky notes.  Limit personally owned devices in the office.  Do you have a strict password policy and procedures for handling data?  USB keys or external portable devices.  Policies on piggybacking.
  860.         Compliance:  DOD, Sarbanes Oxley, HIPAA, C.E. continuing education
  861.         Threat awareness system: send out global emails on intranet for attack problems from IDS and IPS
  862.         Social Networking and P2P: Twitter, Facebook, P2P file sharing, distributing Youtube videos, should be part of a security policy defining what level if any these can be used.  Send all traffic through headquarters where you can provide URL filtering, or proxy services or content services.
  863.     Risks of Virtualization, pros and cons
  864.         Pros: consolidation, energy efficient, resource utilization, management, enhanced provisioning of virtual servers, load balancing, automation, cloud support, DRP (disaster recovery planning), VDI (virtual desktop infrastructure)
  865.         Cons:  Another vulnerable OS, traditional IDS/IPS have problems (hard to place sensors inline between servers), malware is virtual aware, data confidentiality (exploit of one server could escalate to another in the same box), outsourcing challenges (do they know how to work with VMs)
  866.     Risks of Cloud Computing
  867.         public cloud computing - how safe is your data really
  868.             using same passwords is bad, use unique ones for a cloud
  869.         data deletion is not controllable
  870.         loss of control - access, housing, mgmt, maintenance
  871.         corporate security policy include Cloud Computing / SLA’s
  872.         Reputation / Marketing over Research, you have to research and test with the companies
  873.         Compliance Issues: is there any conflict with destruction or disposition policies with Sarbanes Oxley or HIPAA requirements
  874.  
  875.  
  876. Threats and Vulnerabilities Domain Update
  877.  
  878.     Phishing:  Delivery of email messages, phone calls that try to steal information/money.  False links in emails, threats (account will be disabled) using a popular company.  Look for bad grammar.  
  879.     SPIM (spam over instant messaging):  launched most often by bots, harvest IM screen / profile names, usually contains link to website, A.K.A ‘instant span’ or IM Marketing, SPIMMER is the sending entity.  A firewall is the main source of defense.
  880.     Vishing: (SPIT is voip spam)  Voice Phishing, intercept voice mail messages, change hold music, denial of service, eavesdropping
  881.     Pharming: Hacker's attack intended to redirect a website's traffic to another, bogus site
  882.     DNS/ARP Poisoning: improperly formatted packets, weakness in headers, packet that depends on the receiving device processing it improperly.  DNS Cache poisoning via tcp sequence numbers, spoofing DNS query response, or through vulnerable DNS servers.  Layer 2 ARP poisoning can be done by poisoning the MAC addresses.  The CAM tables can be flooded with MACOF which forces the switch to be a HUB.
  883.     Application Attacks:  defended with limiting commands, number of connections,  timeouts, limits how apps can be accessed
  884.     Assessment Types & Techniques:  
  885.         Risk: the likelihood a threat or threat agent will implement a particular exploit or attack
  886.         Threat: looking at individual exploits or agents that can take advantage of a vulnerability.  Like in house developed software.
  887.         Vulnerability: finding weaknesses in systems, design, implementation, vpns, protocol limitations, configurations of routers, firewalls, devices etc...
  888.         Assessment Techniques
  889.             Baseline reporting: reference for anomalies from a knowledge base
  890.             Code review: is code tested, digitally signed with a PKI
  891.             Determine attack surface:  access control rules on routers, switches etc so only certain hosts and vlans can control the devices, reducing footprint of wireless transmission.
  892.             Architecture:  will you use SSL VPN or PKI and what is your compliance.
  893.             Design reviews:  are there improvements we can make to move from IPSEC to SSL full tunnel, move from pre shared keys to PKI or token based or one time passwords for authentication / authorization.
  894.  
  895.  
  896. Application, Data, and Host Security Domain Update
  897.  
  898.     Fuzzing
  899.         A.K.A fuzz testing - black box software testing
  900.         Find bugs using automated malformed data injection
  901.         Developed in 1989 at U of Wisc Madison
  902.         Automatic bug finding to locate software faults
  903.         Programs are called “fuzzers”
  904.             numbers, chars, metadata, binary sequences
  905.     Cross-Site Scripting (XSS):  very common exploit for public facing server, vulnerability found in web applications where code can be injected into a web page (html or client side scripts).  Can bypass “same origin” policy which allows access to pages and variables from the same site.
  906.         Cracker finds an XSS hole in Site A
  907.         Good guy hits site A and sends many requests to Site B (victim) via a META refresh to hide the referrer without his knowledge
  908.         Good guy sends many requests to Site B and eventually finds a hole which is then sent to site C without his knowledge.
  909.         Good guy sends successful attempts to hack site B to site C which are logged so that Bad Guy can view them at a later date (done without Good guys knowledge)
  910.         Bad guy checks Site C for successful hack attempts against Site B to launch further attacks having never visited Site B (the victim)
  911.         Web master of victim Site B never sees Site A (origin of XSS attack) in his logs and never sees Bad guy in his logs (and will think Good Guy is to blame)
  912.     XSRF: Cross Site Request Forgery.  Esoteric obscure offshoot of XSS.  Can force your pc to go to banking, brokerage sites and modify account info.  Is very devastating but not hard to counter measure.  One example is an image tag that has the source of a server in the src attribute.  Always close your browser window when leaving a site like a bank or broker.
  913.     Mobile Device Security
  914.         Should be in written policy,  AUP (acceptable use policy) w/enforcement
  915.         Personal or Provisioned (should be tightly managed and controlled)
  916.         Risks: What is stored and sent on the device.
  917.         Risks: infected apps, identity/content theft, lost/stolen device, banking, pharming
  918.         Rapid deployment with poorly tested devices.
  919.     Hardware Based Encryption
  920.         HW encry/decr is much faster than software
  921.         HMAC hashed message authentication, adds a hash to detect changes in data.
  922.         Secret keys on hardware are not as vulnerable due to exposure; fewer brute force attacks
  923.         Often part of organizational policy
  924.         Downside is it has to be replaced to be upgraded usually.
  925.  
  926.  
  927. Access Control and Identity Management Domain Update
  928.  
  929.     AAA services:  often use RADIUS / TACACS (+) / LDAP servers
  930.         Authentication Review: is identification and authenticating a peer or a device.
  931.         Authorization Review:  is what you can do,  what protocols, actions, services can you take ONCE you are authenticated.
  932.         Accounting:  is when did you start, finish and for how long.  Used for billing, auditing and reporting.
  933.         802.1x is port based authorization and allows you to authenticate devices like a nic on a laptop
  934.  
  935.  
  936. Cryptography Domain Update
  937.  
  938.     Additional Cryptosystems
  939.         RIPEMD has 160 bits is most widely used
  940.             Race Integrity Primitives Evaluation Message Digest
  941.             Message Digest provides Authenticity and Integrity because it comes from a shared secret key and the matching hash guarantees Integrity..
  942.             Avalanche effect happens if a single bit is different creates a hugely different result.
  943.             RIPEMD - 160 is European Message Digest Crypto Hash
  944.             128-256-320 bit version also exist
  945.             Developed in open academic community - no patents
  946.             Closest alternative is SHA-1 but is slightly faster than SHA-1
  947.         PGP/GPG: Nice way for users to secure email and files over untrusted internet.  Early version was from Phillip Zimmerman in 1991.  Some version are free.  GPG is the new open source version.  Uses public keys and private keys.  Each user has one of each.  Typically the public key encrypts the message and the private key decrypts them.  PGP adds a trusted introduction concept where a User can provide an introduction to another user to establish a trust relationship to exchange public keys.  PGP can be used in a PKI for more sophisticated uses.
  948.         GPG, an infrastructure like IPSEC and PKI
  949.             Free version of OPEN PGP Standard RFC 4880
  950.             Encrypt & Digitally sign data and communication and messages
  951.             Versatile Key management - S/MIME Support
  952.             Can replace PGP; more functionality and is enhanced.
  953.             Decrypts / Verifies PGP 5,6 & 7
  954.             Multi Algorithm and Multi Language like ElGmal, (uses DSA & RSA for key pair generation),  for symmetric encryption it can use AES, 3DES, Blowfish, TwoFish, CAST5.  For hashing and integrity it can use MD5, SHA-1, RIPEMD 160 and TIGER
  955.             Check out gnupg.org
  956.             Is extensible to add new modules
  957.             Supports many languages besides english
  958.         Whole Disk Encryption
  959.             There are many disk encryption softwares that encrypts the entire hard disk or volume
  960.             Bit Locker, Drive Sentry, File Vault, PGPDisk, SafeGuard, TrueCrypt, Kryptos, SecuBox and many others
  961.             Protects all data in storage like confidential information like Sarbanes Oxley and HIPAA, customer data and partner data.
  962.             They can encrypt user data files, swap files (memory files), system files, hidden files.
  963.             Uses Variety of Cryptosystems
  964.             Most often automated key management, recovery, Muti-platform support, rapid depoloyment, Defense-In-Depth
  965.         TwoFish
  966.             Free, unpatented, open source, no copyright
  967.             Heavily crypto-analyzed
  968.             Highly Efficient, runs fast, works on smart cards, smart tokens and hardware
  969.             is a Block cipher
  970.             Created by Bruce Schneier
  971.             128 bit block cipher, keys of 128, 192, 256
  972.     SSL/TLS Operations
  973.         used in browsers, web based protected access to devices
  974.         gives endpoint authentication for client and server, can authenticate the server to the client and vice versa
  975.         gives data encryption, data encryption, data authentication, and data integrity.
  976.         creates a TLS tunnel for protection of application data and / or UDP flows or TCP connections
  977.         Session establishment phase where you negotiation parameters and do peer authentication.  Use RSA or DH as the key exchange method.  One way or two way authentication
  978.         Data transfer phase that offers a protected path between the client and server Both phases occur in the SSL/TLS record protocol.  
  979.     PKI Advanced Topics
  980.         Revocation Methods: CRL, OCSP, AAA  identifes certificates that are not valid
  981.         Connect Users with Mapping.  Apply a policy based on contents of a users certificate
  982.         AAA servers for per-user settings
  983.     Review of Acronyms