Password Security Module 8. Objectives Explain Authentication and Authorization Provide familiarity with how passwords are used Identify the importance.

Slides:



Advertisements
Similar presentations
Point3r$. Password Introduction Passwords are a key part of any security system : –Work or Personal Strong passwords make your personal and work.
Advertisements

Password Cracking Lesson 10. Why crack passwords?
Password Security An overview. We need your help The IT department uses the latest technology and techniques to maintain the highest level of security.
Two-Factor Authentication & Tools for Password Management August 29, 2014 Pang Chamreth, IT Development Innovations 1.
COEN 350: Network Security Authentication. Between human and machine Between machine and machine.
CS426Fall 2010/Lecture 81 Computer Security CS 426 Lecture 8 User Authentication.
CS 483 – SD SECTION BY DR. DANIYAL ALGHAZZAWI (7) AUTHENTICATION.
Module 4: Implementing User, Group, and Computer Accounts
1 Chapter 11: Authentication Basics Passwords. 2 Establishing Identity Authentication: binding of identity to subject One or more of the following –What.
Tom Parker Project Manager Identity Management Team IT Security Group.
11 SUPPORTING LOCAL USERS AND GROUPS Chapter 3. Chapter 3: Supporting Local Users and Groups2 SUPPORTING LOCAL USERS AND GROUPS  Explain the difference.
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 4 Profiles, Password Policies, Privileges, and Roles.
Lesson 9-Securing a Network. Overview Identifying threats to the network security. Planning a secure network.
CSCI 530 Lab Authentication. Authentication is verifying the identity of a particular person Example: Logging into a system Example: PGP – Digital Signature.
7-Access Control Fundamentals Dr. John P. Abraham Professor UTPA.
Nothing is Safe 1. Overview  Why Passwords?  Current Events  Password Security & Cracking  Tools  Demonstrations Linux GPU Windows  Conclusions.
Air Force Association (AFA) 1. 1.Access Control 2.Four Steps to Access 3.How Does it Work? 4.User and Guest Accounts 5.Administrator Accounts 6.Threat.
Windows This presentation is an amalgam of presentations by Mark Michael, Randy Marchany and Ed Skoudis. I have edited and added material. Dr. Stephen.
Password Management PA Turnpike Commission
IS 302: Information Security and Trust Week 7: User Authentication (part I) 2012.
Guide to Operating System Security Chapter 4 Account-based Security.
Managing User Accounts, Passwords and Logon Chapter 5 powered by dj.
Hands-On Microsoft Windows Server Security Enhancements in Windows Server 2008 Windows Server 2008 was created to emphasize security –Reduced attack.
Managing Network Security ref: Overview Using Group Policy to Secure the User Environment Using Group Policy to Configure Account Policies.
CIS 450 – Network Security Chapter 8 – Password Security.
Database Security DB0520 Authentication and password security Authentication options – strong, weak Review security environment - Sys Admin privileges.
Fall 2011 Nassau Community College ITE153 – Operating Systems Session 22 Local Security Polcies 1.
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 4 Profiles, Password Policies, Privileges, and Roles.
Microsoft ® Virtual Academy Module 3 Understanding Security Policies Christopher Chapman | Content PM, Microsoft Thomas Willingham | Content Developer,
Profiles, Password Policies, Privileges, and Roles
Mark Shtern. Passwords are the most common authentication method They are inherently insecure.
1 Chapter Overview Configuring Account Policies Configuring User Rights Configuring Security Options Configuring Internet Options.
8.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 8: Planning.
Chapter 13 Users, Groups Profiles and Policies. Learning Objectives Understand Windows XP Professional user accounts Understand the different types of.
Identification and Authentication University of Sunderland COM380 Harry R. Erwin, PhD.
Passwords. Outline Objective Authentication How/Where Passwords are Used Why Password Development is Important Guidelines for Developing Passwords Summary.
Breno de MedeirosFlorida State University Fall 2005 Windows servers The NT security model.
1 Chapter 11: Authentication Basics Passwords. 2 Establishing Identity Authentication: binding of identity to subject One or more of the following –What.
All Input is Evil (Part 1) Introduction Will not cover everything Healthy level of paranoia Use my DVD Swap Shop application (week 2)
 Access Control 1 Access Control  Access Control 2 Access Control Two parts to access control Authentication: Are you who you say you are? – Determine.
Identification and Authentication CS432 - Security in Computing Copyright © 2005,2010 by Scott Orr and the Trustees of Indiana University.
Mitch Parks, GSEC/GCWN ITS Desktop Security Analyst
How Safe are They?. Overview Passwords Cracking Attack Avenues On-line Off-line Counter Measures.
Password Security. Overview What are passwords, why are they used? Different types of attacks Bad password practices to avoid Good password practices.
COEN 350: Network Security Authentication. Between human and machine Between machine and machine.
CNIT 124: Advanced Ethical Hacking Ch 9: Password Attacks.
Module 7: Implementing Security Using Group Policy.
1 Data Access Control, Password Policy and Authentication Methods for Online Bank Md. Mahbubur Rahman Alam B. Sc. (Statistics) Dhaka University M. Sc.
Building Structures. Building Relationships. Passwords February 2010 Marshall Tuck.
CSCI 530 Lab Authentication. Authentication is verifying the identity of a particular person Example: Logging into a system Example: PGP – Digital Signature.
CHAPTER 5 MANAGING USER ACCOUNTS & GROUPS. User Accounts Windows 95, 98 & Me do not need a user account like Windows XP Professional to access computer.
Internet2 Base CAMP Topics in Middleware: Authentication.
CSCE 201 Identification and Authentication Fall 2015.
Module 7: Designing Security for Accounts and Services.
4.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 12: Implementing Security.
CSCI 530 Lab Passwords. Overview Authentication Passwords Hashing Breaking Passwords Dictionary Hybrid Brute-Force Rainbow Tables Detection.
 Encryption provides confidentiality  Information is unreadable to anyone without knowledge of the key  Hashing provides integrity  Verify the integrity.
Password Theft By: Markie Jones. Road Map Do’s Do Not’s What can someone do with it? How do they get it? Who’s most at risk? When & Where are consumers.
Understanding Security Policies Lesson 3. Objectives.
Understanding Security Policies
Authentication and Account Management
Chapter One: Mastering the Basics of Security
Password Cracking Lesson 10.
Fun gym Cambridge Nationals R001.
Fun gym Cambridge Nationals R001.
Lesson 16-Windows NT Security Issues
Understanding Security Policies
PLANNING A SECURE BASELINE INSTALLATION
Computer Security Protection in general purpose Operating Systems
Preparing for the Windows 8. 1 MCSA Module 6: Securing Windows 8
Presentation transcript:

Password Security Module 8

Objectives Explain Authentication and Authorization Provide familiarity with how passwords are used Identify the importance of good password selection Examine why password policies are essential Develop guidelines for creating strong passwords Password Cracking Tools File Integrity

Authentication & Authorization Authentication The process of verifying the digital identity of the sender of a communication, such as a request to log in Establish a trust relationship between a provider of services and a consumer of services Authorization Permissions granted to an authenticated user Authorization follows Authentication

Authentication & Authorization Authentication methods Something you have (a token, a swipe card, etc.) Something you are (biometrics) Something you know (a password) Secure communication channel Authorization By policies of an organization or operational requirements Access control (Set of permissions granted ) Module 06: 4

How/Where Passwords are Used Controlling access to a resource Computers Cell Phones On-line Accounts Voic Medical and Benefit phone access Facility Access Automated Teller Machines (ATM) Etc.

Why Password Development is Important Passwords control access to private data and resources Attackers may capture a password file and crack it Passwords stored as hash values Cracker programs can run at their leisure Attackers may try to break into a live system If a “time-out” policy is not implemented, they could try infinite times until they succeed Many users have simple passwords or one associated with their life (profiling or social engineering can be used against them) Some systems come with default passwords

Password Cracking Techniques Brute Force – Every combination of letters, numbers, and characters possible Dictionary – Words (and combinations of words) found in a specialized dictionary Assume a password of 7 alphabet characters in length MaxCombinations = NumberAvailableChars PasswordLength MaxCombinations = 26 7 = 8,031,810,176 (8 Billion) Example: A 3GHz processor, guessing 3 million passwords per second, will take approximately 45 minutes to guess the passwords

Password Cracking Tools Free password cracking programs Linux & Windows Top 10 Tools - John the Ripper - ophcrack - Windows only Cain and Abel - Administrators often crack password son systems they manage to identify and change weak passwords

Guidelines for Developing Passwords Strong Passwords 8 or more characters long Have a combination of upper and lowercase letters, numbers, and special characters Changed on a regular basis Easy to remember and are not written down Passphrases: Choose a line or two from a song or poem and use the first letter of each word. For example, “It is the East, and Juliet is the Sun'' becomes Not used over and over again for different programs and websites Weak Passwords Contains your name, friends name, favorite pet, sports team, etc. Contains publicly accessible information about yourself, such as social security number, license numbers, phone numbers, address, birthdays, etc. Words found in a dictionary of any language Made of all numbers or all the same letter Never changed Written down Shared with others

Windows XP Set password policies to enforce strong passwords Click Start -> Control Panel -> Administrative Tools -> Local Security Policy Click the plus sign (+) to the left of Account Policies. You will see these 2 categories: Password Policy and Account Lockout Policy. Click on Password Policy

Windows XP Best Practices are stated below Enforce password history:5 passwords This security setting determines the number of unique new passwords that have to be associated with a user account before an old password can be reused. The value must be between 0 and 24 passwords. This policy enables administrators to enhance security by ensuring that old passwords are not reused continually. Maximum password age:30 to 90 days This security setting determines the period of time (in days) that a password can be used before the system requires the user to change it. Best practices state passwords should expire every 30 to 90 days, depending on the environment. This limits an attacker’s amount of time to crack a user's password and have access to network resources. Minimum password age:5 days This security setting determines the period of time (in days) a password must be used before it can be changed. Without a minimum password age, users can cycle through passwords repeatedly until they get to an old favorite.

Windows XP Minimum password length:8 characters This security setting determines the least number of characters a password may contain. The longer a password is, the harder it is for an attack to crack. Password must meet complexity requirements?Yes This security setting requires all passwords meet complexity requirements. For example, passwords must include special characters, capitalized, numeric, etc. The more complex a password, the harder for an attack to crack. Store password using reversible encryption for all users in the domain? Disable This setting allows applications using protocols that must have the user's clear text password for authentication purposes. These passwords are not really encrypted, but do use a hash to store them, essentially leaving them as vulnerable as plain text. This policy should never be enabled. Note: These are best practices for normal user accounts. Administrative level and Power Users may have more stringent settings.

Ubuntu Set password policies to enforce strong passwords Password values are controlled in the file /etc/pam.d/common- password Minimum Password Length – set to 8 By default, Ubuntu requires a minimum password length of 4 characters To adjust the minimum length to 8 characters add the ‘ minlen = ’ parameter to the pam_unix configuration in the /etc/pam.d/common- password file Example password required pam_cracklib.so retry=3 minlen=8 difok=3

Ubuntu Password History (reuse) Create an empty /etc/security/opasswd file for storing old user passwords Set permissions to opasswd to the same as the /etc/shawdow file Enable password history by adding the “ remember= ” to the pam_unix configuration in the /etc/pam.d/common-password file Example password required pam_unix.so md5 remember=12 use_authtok The value of the " remember" parameter is the number of old passwords to store for a user

Ubuntu Password aging parameters can be set in /etc/login.defs Password Expiration Needs a minimum and maximum password age forcing users to change their passwords when they expire PASS_MIN_DAYS – Set to 7 days Minimum number of days allowed between password changes PASS_MAX_DAYS – Set from 30 to 90 days Maximum number of days a password may be used P ASS_WARN_AGE – Set to 14 days Number of days warning given before a password expires

Password Policy Best Practices Password policies are critical to the security posture of your organization Best Practices across the board Number of times a password can be reused Passwords should not be cycled more than 3 to 5 uses Password should expire/be changed Every 90 days for user account Every 30 days for an administrator account Minimum length requirement 8 characters Complexity requirements Upper and lower case, special character and numbers All passwords should be encrypted when stored Module 06: 16

Password Policy Best Practices Educate users Communicate to users that they will never be asked for their password over the phone, by the helpdesk, etc. This helps prevent social engineering attacks Make sure users do not use the same passwords for all of their login IDs Users should not write down or share passwords Module 06: 17

List of References