The OWASP Foundation OWASP Chennai Phishing

OWASP Chennai Chapter Kick-off 2 Definition It is the act of tricking someone into giving confidential information (like passwords and credit card information) on a fake web page or form pretending to come from a legitimate company (like their bank). For example: Sending an to a user falsely claiming to be an established legitimate enterprise in an attempt to scam the user into surrendering private information that will be used for identity theft.

OWASP Chennai Chapter Kick-off 3 Examples

4 Examples

5 Examples

6 Types of Phishing  Deceptive - Sending a deceptive , in bulk, with a “call to action” that demands the recipient click on a link.

OWASP Chennai Chapter Kick-off 7 Types of Phishing  Malware-Based - Running malicious software on the user’s machine. Various forms of malware-based phishing are:  Key Loggers & Screen Loggers  Session Hijackers  Web Trojans  Data Theft

OWASP Chennai Chapter Kick-off 8 Types of Phishing  DNS-Based - Phishing that interferes with the integrity of the lookup process for a domain name. Forms of DNS-based phishing are:  Hosts file poisoning  Polluting user’s DNS cache  Proxy server compromise

OWASP Chennai Chapter Kick-off 9 Types of Phishing  Content-Injection – Inserting malicious content into legitimate site. Three primary types of content-injection phishing:  Hackers can compromise a server through a security vulnerability and replace or augment the legitimate content with malicious content.  Malicious content can be inserted into a site through a cross- site scripting vulnerability.  Malicious actions can be performed on a site through a SQL injection vulnerability.

OWASP Chennai Chapter Kick-off 10 Types of Phishing  Man-in-the-Middle Phishing - Phisher positions himself between the user and the legitimate site.

OWASP Chennai Chapter Kick-off 11 Types of Phishing  Search Engine Phishing - Create web pages for fake products, get the pages indexed by search engines, and wait for users to enter their confidential information as part of an order, sign-up, or balance transfer.

OWASP Chennai Chapter Kick-off 12 Causes of Phishing  Misleading s  No check of source address  Vulnerability in browsers  No strong authentication at websites of banks and financial institutions  Limited use of digital signatures  Non-availability of secure desktop tools  Lack of user awareness  Vulnerability in applications  … and more

OWASP Chennai Chapter Kick-off 13 Effects of Phishing  Internet fraud  Identity theft  Financial loss to the original institutions  Difficulties in Law Enforcement Investigations  Erosion of Public Trust in the Internet.

OWASP Chennai Chapter Kick-off 14 Industries affected Major industries affected are:  Financial Services  ISPs  Online retailers

OWASP Chennai Chapter Kick-off 15 Phishing Trends

OWASP Chennai Chapter Kick-off 16 Phishing Trends

OWASP Chennai Chapter Kick-off 17 How to combat phishing?  Educate application users Think before you open Never click on the links in an , message boards or mailing lists Never submit credentials on forms embedded in s Inspect the address bar and SSL certificate Never open suspicious s Ensure that the web browser has the latest security patch applied Install latest anti-virus packages Destroy any hard copy of sensitive information Verify the accounts and transactions regularly Report the scam via phone or .

OWASP Chennai Chapter Kick-off 18 How to combat phishing?  Formulate and enforce Best practices Authorization controls and access privileges for systems, databases and applications. Access to any information should be based on need-to-know principle Segregation of duties. Media should be disposed only after erasing sensitive information.

OWASP Chennai Chapter Kick-off 19 How to combat phishing? Reinforce application development / maintenance processes: 1. Web page personalization Using two pages to authenticate the users. Using Client-side persistent cookies.

OWASP Chennai Chapter Kick-off 20 How to combat phishing? 2. Content Validation Never inherently trust the submitted data Never present the submitted data back to an application user without sanitizing the same Always sanitize data before processing or storing Check the HTTP referrer header

OWASP Chennai Chapter Kick-off 21 How to combat phishing? 3. Session Handling Make session identifiers long, complicated and difficult to guess. Set expiry time limits for the SessionID’s and should be checked for every client request. Application should be capable of revoking active SessionID’s and not recycle the same SessionID. Any attempt the invalid SessionID should be redirected to the login page. Never accept session information within a URL. Protect the session via SSL. Session data should be submitted as a POST. After authenticating, a new SessionID should be used (HTTP & HTTPS). Never let the users choose the SessionID.

OWASP Chennai Chapter Kick-off 22 How to combat phishing? 4. URL Qualification Do not reference redirection URL in the browser’s URL Always maintain a valid approved list of redirection url’s Never allow customers to supply their own URL’s Never allow IP addresses to be user in URL information

OWASP Chennai Chapter Kick-off 23 How to combat phishing? 5. Authentication Process Ensure that a 2-phase login process is in place Personalize the content Design a strong token-based authentication

OWASP Chennai Chapter Kick-off 24 How to combat phishing? 6. Transaction non-repudiation To ensure authenticity and integrity of the transaction

OWASP Chennai Chapter Kick-off 25 How to combat phishing? 7. Image Regulation Image Cycling Session-bound images

OWASP Chennai Chapter Kick-off 26 Organizations  Anti-Phishing Working Group (APWG) The APWG has over members from over 1500 companies & agencies worldwide. Member companies include leading security companies such as Symantec, McAfee and VeriSign. Financial Industry members include the ING Group,VISA, Mastercard and the American Bankers Association.

OWASP Chennai Chapter Kick-off 27 What does all the above imply? It is better to be safer now than feel sorry later.

OWASP Chennai Chapter Kick-off 28References U5dhgYAJ: onsequences&hl=en&gl=in&ct=clnk&cd=7http:// /search?q=cache:-T6- U5dhgYAJ: onsequences&hl=en&gl=in&ct=clnk&cd=7 Phishing-dhs-report.pdf Report_on_phishing.pdf

OWASP Chennai Chapter Kick-off 29 Questions?

OWASP Chennai Chapter Kick-off 30 Thank You!