Facultad De Ingeniería De Sistemas

Total Page:16

File Type:pdf, Size:1020Kb

Facultad De Ingeniería De Sistemas ESCUELA POLITÉCNICA NACIONAL FACULTAD DE INGENIERÍA DE SISTEMAS ANÁLISIS DE RIESGOS Y VULNERABILIDADES DE LA INFRAESTRUCTURA TECNOLÓGICA DE LA SECRETARÍA NACIONAL DE GESTIÓN DE RIESGOS UTILIZANDO METODOLOGÍAS DE ETHICAL HACKING PROYECTO PREVIO A LA OBTENCIÓN DEL TÍTULO DE INGENIERO EN SISTEMAS INFORMÁTICOS Y DE COMPUTACIÓN OSWALDO ANDRÉS ACOSTA NARANJO [email protected] DIRECTOR: ING. CESAR GUSTAVO SAMANIEGO BURBANO [email protected] Quito, Marzo 2013 DECLARACIÓN Yo, Oswaldo Andrés Acosta Naranjo, declaro bajo juramento que el trabajo aquí descrito es de mi autoría; que no ha sido previamente presentada para ningún grado o calificación profesional; y que he consultado las referencias bibliográficas que se incluyen en este documento. A través de la presente declaración cedo mis derechos de propiedad intelectual correspondientes a este trabajo, a la Escuela Politécnica Nacional, según lo establecido por la Ley de Propiedad Intelectual, por su Reglamento y por la normatividad institucional vigente. __________________________ Oswaldo Andrés Acosta Naranjo CERTIFICACIÓN Certifico que el presente trabajo fue desarrollado por Oswaldo Andrés Acosta Naranjo, bajo mi supervisión. _______________________ Ing. Gustavo Samaniego DIRECTOR DE PROYECTO AGRADECIMIENTOS Agradezco a Dios, por haberme guiado desde el principio de mi vida personal y académica, quien me permitió llegar a concluir esta etapa de mi carrera. Agradezco principalmente a mi padre Oswaldo Acosta y a mi madre Teresa Naranjo, por estar presentes durante todos los años de estudio, por su incansable apoyo y por enseñarme que las metas se cumplen con esfuerzo y sacrificio propio. Agradezco profundamente a mis hermanas Catalina, Silvia, Evelin, Ivon y Mariatere, por el apoyo incondicional que me brindaron para la culminación de mi carrera . Agradezco a mis cuñados y a mis sobrinas, que me brindaron su total apoyo y que de una u otra forma han contribuido a la culminación de mis estudios. Agradezco especialmente a mi novia Andreita, por su amistad, cariño e incondicional amor, por el apoyo durante la realización de este proyecto y porque siempre creyó en mí. A los amigos, Edgar, Sociedad y a todos aquellos y aquellas con los cuales he compartido momentos agradables durante mis estudios y que siempre han estado allí. Andrés Acosta DEDICATORIA Dedico especialmente este trabajo a mis padres que siempre me apoyaron, y por haberme dado las bases de sacrificio y honestidad para culminar mis estudios. A mis hermanas, cuñados y sobrinas que siempre estuvieron presentes con su apoyo y consejos en cada momento de mi vida estudiantil. A mi novia que siempre me apoyo desde el inicio hasta el fin de este proyecto. Andrés Acosta 1 CONTENIDO DECLARACIÓN ....................................................................................................... I CERTIFICACIÓN .................................................................................................... II AGRADECIMIENTOS ............................................................................................ III DEDICATORIA ...................................................................................................... IV CONTENIDO ........................................................................................................... 1 ÍNDICE DE TABLAS ............................................................................................... 4 ÍNDICE DE FIGURAS ............................................................................................. 6 RESUMEN .............................................................................................................. 7 PRESENTACIÓN .................................................................................................... 8 1 CAPÍTULO: CARACTERIZACIÓN DE LA INSTITUCIÓN ............................ 10 1.1 INFORMACIÓN DE LA SECRETARIA NACIONAL DE GESTIÓN DE RIESGOS ............................................................................................... 10 1.1.1 ESTRUCTURA ORGÁNICA POR PROCESOS ............................. 11 1.2 DIRECCIÓN DE TECNOLOGÍAS DE INFORMACIÓN Y COMUNICACIONES .............................................................................. 13 1.2.1 PROCESOS Y SERVICIOS DE TIC ............................................... 13 2 CAPÍTULO: ANÁLISIS DE RIESGOS Y VULNERABILIDADES ................. 15 2.1 DETERMINACIÓN DE LA METODOLOGÍA DE ETHICAL HACKING A UTILIZAR ............................................................................................... 15 2.1.1 DESCRIPCIÓN DE LA METODOLOGÍA OSSTMM ....................... 15 2.1.1.1 METODOLOGÍA OSSTMM ............................................................... 17 2.1.1.2 ANÁLISIS Y EVALUACIÓN DE RIESGOS CON OSSTMM ............... 18 2.1.2 DESCRIPCIÓN DE LA METODOLOGÍA ISSAF ............................. 20 2.1.2.1 METODOLOGÍA ISSAF .................................................................... 20 2.1.2.2 ANÁLISIS Y EVALUACIÓN DE RIESGOS CON ISSAF .................... 24 2.1.3 SELECCIÓN DE LA METODOLOGÍA ............................................ 26 2.2 IDENTIFICACIÓN DE RIESGOS .......................................................... .27 2.2.1 IDENTIFICACIÓN DE ACTIVOS .................................................... .27 2.2.1.1 IDENTIFICACIÓN DEL DISEÑO DE ARQUITECTURA DE RED ..... .28 2.2.2 IDENTIFICACIÓN Y BÚSQUEDA DE VULNERABILIDADES ........ 32 2.2.2.1 RECOPILACIÓN DE INFORMACIÓN .............................................. 32 2 2.2.2.1.1 SELECCIÓN DE LA HERRAMIENTA DE RECOPILACION INFORMACIÓN .................................................................... 33 2.2.2.2 MAPEO DE RED .............................................................................. 41 2.2.2.2.1 SELECCIÓN DE LA HERRAMIENTA DE MAPEO DE RED .. 41 2.2.2.2.2 IDENTIFICACIÓN DE PUERTOS Y SERVICIOS................... 42 2.2.2.2.3 IDENTIFICACIÓN DEL SISTEMA OPERATIVO .................... 50 2.2.2.2.4 IDENTIFICACIÓN DEL PERÍMETRO DE RED ...................... 54 2.2.2.3 SEGURIDAD EN LAS CONTRASEÑAS ........................................... 56 2.2.2.4 SEGURIDAD DE LOS SWITCH........................................................ 57 2.2.2.5 SEGURIDAD DEL ROUTER ............................................................. 57 2.2.2.6 SEGURIDAD DEL FIREWALL .......................................................... 59 2.2.2.7 SEGURIDAD DEL SISTEMA DE DETECCIÓN DE INTRUSOS ........ 61 2.2.2.8 SEGURIDAD DEL SISTEMA ANTI-VIRUS ........................................ 62 2.2.2.9 SEGURIDAD EN LA RED DE ÁREA DE ALMACENAMIENTO ......... 63 2.2.2.10 SEGURIDAD EN LA RED INALÁMBRICA ...................................... 64 2.2.2.11 SEGURIDAD DEL SERVIDOR WEB ............................................... 65 2.2.2.12 SEGURIDAD DE LAS APLICACIONES WEB ................................. 66 2.2.2.12.1 SELECCIÓN DE LA HERRAMIENTA DE ANALISIS DE APLICACIONES WEB ......................................................... 66 2.2.2.13 SEGURIDAD DE USUARIOS DE INTERNET ................................. 71 2.2.2.14 SEGURIDAD FÍSICA ...................................................................... 72 2.3 ANÁLISIS DE RIESGOS ........................................................................ 73 2.3.1 VERIFICACIÓN DE VULNERABILIDADES .................................... 74 2.4 EVALUACIÓN DE RIESGOS ................................................................. 76 2.4.1 VALORACIÓN DEL RIESGO ......................................................... 77 2.4.2 ANÁLISIS DE IMPACTO ................................................................. 79 2.4.2.1 ANÁLISIS DE IMPACTO TÉCNICO ................................................... 79 2.4.2.2 ANÁLISIS DE IMPACTO DE NEGOCIO ............................................ 82 3 CAPÍTULO: TRATAMIENTO DE LOS RIESGOS ......................................... 86 3.1 PLAN DE MITIGACIÓN DE RIESGOS EN BASE A LOS ANÁLISIS DE IMPACTO ............................................................................................... 86 3.1.1 CONTRAMEDIDAS PARA LAS ENTIDADES DE EVALUACIÓN ... 86 3.1.2 PLAN DE MITIGACIÓN DE RIESGOS ........................................... 91 3 3.2 PRESENTACIÓN DE CONCLUSIONES Y RECOMENDACIONES PARA MITIGAR LOS RIESGOS ....................................................................... 96 4 CAPÍTULO: CONCLUSIONES Y RECOMENDACIONES ............................ 99 4.1 CONCLUSIONES ................................................................................... 99 4.2 RECOMENDACIONES ........................................................................ 100 BIBLIOGRAFÍA .................................................................................................. 102 ANEXOS ............................................................................................................. 104 ANEXO 1: Módulos del Mapa de Seguridad de OSSTMM versión 2.2 ............... 104 ANEXO 2: Entidades de Evaluación de ISSAF versión 0.2.1 .............................. 106 ANEXO 3: Registro de números de Puerto TPC y UDP ...................................... 107 ANEXO 4: Puertos usados por Troyanos ............................................................ 108 ANEXO 5: Vulnerabilidades de la SNGR ............................................................ 109 4 ÍNDICE DE TABLAS TABLA 2-1: Valores de Evaluación de Riesgos de OSSTMM ............................... 19 TABLA 2-2: Comparación de Metodologías ........................................................... 26 TABLA 2-3: Áreas de Alcance ..............................................................................
Recommended publications
  • La Sécurité Informatique Edition Livres Pour Tous (
    La sécurité informatique Edition Livres pour tous (www.livrespourtous.com) PDF générés en utilisant l’atelier en source ouvert « mwlib ». Voir http://code.pediapress.com/ pour plus d’informations. PDF generated at: Sat, 13 Jul 2013 18:26:11 UTC Contenus Articles 1-Principes généraux 1 Sécurité de l'information 1 Sécurité des systèmes d'information 2 Insécurité du système d'information 12 Politique de sécurité du système d'information 17 Vulnérabilité (informatique) 21 Identité numérique (Internet) 24 2-Attaque, fraude, analyse et cryptanalyse 31 2.1-Application 32 Exploit (informatique) 32 Dépassement de tampon 34 Rétroingénierie 40 Shellcode 44 2.2-Réseau 47 Attaque de l'homme du milieu 47 Attaque de Mitnick 50 Attaque par rebond 54 Balayage de port 55 Attaque par déni de service 57 Empoisonnement du cache DNS 66 Pharming 69 Prise d'empreinte de la pile TCP/IP 70 Usurpation d'adresse IP 71 Wardriving 73 2.3-Système 74 Écran bleu de la mort 74 Fork bomb 82 2.4-Mot de passe 85 Attaque par dictionnaire 85 Attaque par force brute 87 2.5-Site web 90 Cross-site scripting 90 Défacement 93 2.6-Spam/Fishing 95 Bombardement Google 95 Fraude 4-1-9 99 Hameçonnage 102 2.7-Cloud Computing 106 Sécurité du cloud 106 3-Logiciel malveillant 114 Logiciel malveillant 114 Virus informatique 120 Ver informatique 125 Cheval de Troie (informatique) 129 Hacktool 131 Logiciel espion 132 Rootkit 134 Porte dérobée 145 Composeur (logiciel) 149 Charge utile 150 Fichier de test Eicar 151 Virus de boot 152 4-Concepts et mécanismes de sécurité 153 Authentification forte
    [Show full text]
  • A Toolkit for Detecting and Analyzing Malicious Software
    A Toolkit for Detecting and Analyzing Malicious Software Michael Weber, Matthew Schmid & Michael Schatz David Geyer Cigital, Inc. [email protected] Dulles, VA 20166 g fmweber, mschmid, mschatz @cigital.com Abstract the virus or Trojan horse performs malicious actions unbe- knownst to the user. These programs often propagate while In this paper we present PEAT: The Portable Executable attached to games or other enticing executables. Analysis Toolkit. It is a software prototype designed to pro- Malicious programmers have demonstrated their cre- vide a selection of tools that an analyst may use in order ativity by developing a great number of techniques through to examine structural aspects of a Windows Portable Ex- which malware can be attached to a benign host. Several ecutable (PE) file, with the goal of determining whether insertion methods are common, including appending new malicious code has been inserted into an application af- sections to an executable, appending the malicious code ter compilation. These tools rely on structural features of to the last section of the host, or finding an unused region executables that are likely to indicate the presence of in- of bytes within the host and writing the malicious content serted malicious code. The underlying premise is that typi- there. A less elegant but effective insertion method is to cal application programs are compiled into one binary, ho- simply overwrite parts of the host application. mogeneous from beginning to end with respect to certain Given the myriad ways malicious software can attach to structural features; any disruption of this homogeneity is a benign host it is often a time-consuming process to even a strong indicator that the binary has been tampered with.
    [Show full text]
  • Regrun? Regrun Is an Excellent Tool Kit for Protecting Your Computer Against Viruses Or Trojans/Spyware/ Adware Parasites Or Rootkits
    What is RegRun? RegRun is an excellent tool kit for protecting your computer against viruses or Trojans/Spyware/ Adware parasites or Rootkits. The RegRun uses the newest technology in the world. Fight with the bad guys by the most powerful weapon. What you should know about RegRun? RegRun is not an antivirus in a common sense. It does not scan your disk and detect/cure using signature database. There are a lot of antiviral programs that you can choose. RegRun checks all Windows startup holes and it can detect and remove any UNKNOWN virus. The modern viruses spreads to the millions computers in the world for a pair days. First, a virus kills an antivirus and disables a way to update the antiviral databases. RegRun prevents a virus auto start. Later you can clean your computer by antivirus to remove virus according files and registry records. RegRun resolves three main tasks: 1. Makes backups of the registry and important files. Restores a computer even if it does not boot. 2. Detects a virus in your computer. 3. Removes a virus from your computer. Hope you enjoy it! Who needs RegRun? If you are a user who is exposed to sources of viruses and Trojans (e.g. you are an Internet surfer, E-mail recipient, one who buys "safe" software on CD's, or one who receives data on floppy disks), or if you are an experienced user who needs to adjust your startup configuration as a function of testing and debugging new software, you need RegRun. RegRun is the best choice for users who wants to get maximum security, for power users and computer professionals.
    [Show full text]
  • Hacking Windows95/98 Andme
    Color profile: GenericHacking CMYK/ Hackingprinter profile Exposed: Network Security Secrets & Solutions / McClure, Scambray, Kurtz / 222742-7 / Chapter 4 Composite Default screen CHAPTER 4 Hacking Windows 95/98 and Me 129 P:\010Comp\Hacking\742-7\ch04.vp Thursday, January 30, 2003 10:32:23 AM Color profile: GenericHacking CMYK/ Hackingprinter profile Exposed: Network Security Secrets & Solutions / McClure, Scambray, Kurtz / 222742-7 / Chapter 4 Composite Default screen 130 Hacking Exposed: Network Security Secrets & Solutions he most important thing for a network administrator or end user to realize about Windows 95/95B/98/98SE and their updated counterpart Windows Millennium TEdition (hereafter Win9x/Me, or the “DOS Family”) is that their architecture was not designed to incorporate security from the ground up like Microsoft’s other Windows lineage, the Windows NT Family. Throughout this book, we use the phrase “NT Family” to refer to all systems based on Microsoft’s New Technology (NT) platform, including Win NT 3.x–4.x, Windows 2000, Windows XP, and Windows .NET Server (see Chapter 5). Where necessary, we will differentiate between desktop and server versions. In contrast, we will refer to the Microsoft DOS/Windows 1.x/3.x/9x/Me lineage as the “DOS Family.” In fact, it seems that Microsoft went out of its way in many instances to sacrifice secu- rity for ease of use when planning the architecture of Win9x/Me. This becomes double jeopardy for administrators and security-unaware end users. Not only is Win9x/Me easy to configure, but the people most likely to be configuring it are also unlikely to take proper precautions (such as good password selection).
    [Show full text]
  • Back Orifice Download Hacker
    Back Orifice Download Hacker 1 / 4 Back Orifice Download Hacker 2 / 4 3 / 4 Surely you've heard the news already: Back Orifice 2000 (BO2K) is floating ... never download software from unknown vendors or software authors; don't let .... The program BO2K was written by DilDog of the hacking and phreaking group Cult of the Dead Cow and was based on the previous BO codes of SirDystic released in August '98 (also a cDc member). They provide this program absolutely free to download at their website www.bo2k.com.. Download: R.A.T, Crypter, Binder, Source Code, Botnet.... Back Orifice 2000 is a new version of the famous Back Orifice backdoor trojan (hacker's remote access tool). It was created by the Cult of Dead Cow hackers .... 1999-0660 "A hacker utility or Trojan Horse installed on a system… ... An intruder can download files from a Back Orifice system by sending a.. "Back Orifice" is a hacker's dream, and a Netizen's nightmare. ... It has reportedly been downloaded by well over 100,000 people since then.. Some hackers download files and steal passwords. ... Several RATs are frequently found in the wild, including Back Orifice, NetBus, Subseven, and DeepThroat.. Back Orifice - Windows Remote Administration Tool, by the cDc. ... The controversial Windows Remote Administration/Hacking Tool/Trojan has been ported ... tags | trojan: MD5 | 83e687476c2db91023c227524a676781: Download | Favorite .... I also downloaded the code of Back Orifice 2000. Even though these codes are called the Hacker Tool, it is very interesting to me about Internet code like socket, .... ... Thomas Cook's currency exchange site Microsoft: Back-door hack no threat to ..
    [Show full text]
  • Certified Ethical Hacker Version 8 Study Guide
    ffirs.indd 2 22-07-2014 17:23:44 CEHv8 Certified Ethical Hacker Version 8 Study Guide ffirs.indd 1 22-07-2014 17:23:44 ffirs.indd 2 22-07-2014 17:23:44 CEHv8 Certified Ethical Hacker Version 8 Study Guide Sean-Philip Oriyano ffirs.indd 3 22-07-2014 17:23:44 Senior Acquisitions Editor: Jeff Kellum Development Editor: Richard Mateosian Technical Editors: Albert Whale and Robert Burke Production Editor: Dassi Zeidel Copy Editors: Liz Welch and Tiffany Taylor Editorial Manager: Pete Gaughan Vice President and Executive Group Publisher: Richard Swadley Associate Publisher: Chris Webb Media Project Manager I: Laura Moss-Hollister Media Associate Producer: Marilyn Hummel Media Quality Assurance: Doug Kuhn Book Designer: Judy Fung Proofreader: Sarah Kaikini, Word One New York Indexer: Ted Laux Project Coordinator, Cover: Patrick Redmond Cover Designer: Wiley Cover Image: ©Getty Images Inc./Jeremy Woodhouse Copyright © 2014 by John Wiley & Sons, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-1-118-64767-7 ISBN: 978-1-118-76332-2 (ebk.) ISBN: 978-1-118-98928-9 (ebk.) No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions.
    [Show full text]
  • Chapter 10 Phase 4: Maintaining Access
    Chapter 10 Phase 4: Maintaining Access Trojan Horses ♦ Software program containing a concealed malicious capability but appears to be benign, useful, or attractive to users Backdoor ♦ Software that allows an attacker to access a machine using an alternative entry method ♦ Installed by attackers after a machine has been compromised ♦ May Permit attacker to access a computer without needing to provide account names and passwords ♦ Used in movie “War Games” ♦ Can be sshd listening to a port other than 22 ♦ Can be setup using Netcat Netcat as a Backdoor ♦ A popular backdoor tool ♦ Netcat must be compiled with “GAPING_SECURITY_HOLE” option ♦ On victim machine, run Netcat in listener mode with –e flag to execute a specific program such as a command shell ♦ On attacker’s machine run Netcat in client mode to connect to backdoor on victim Running Netcat as a Backdoor on Unix Note: on attacker’s machine, run “nc victim 12345” Running Netcat as a Backdoor on WinNT/2000 Trojan Horse Backdoors ♦ Programs that combine features of backdoors and Trojan horses – Not all backdoors are Trojan horses – Not all Trojan horses are backdoors ♦ Programs that seem useful but allows an attacker to access a system and bypass security controls Categories of Trojan Horse Backdoors ♦ Application-level Trojan Horse Backdoor – A separate application runs on the system that provides backdoor access to attacker ♦ Traditional RootKits – Critical operating system executables are replaced by attacker to create backdoors and facilitate hiding ♦ Kernel-level RootKits – Operating
    [Show full text]
  • Security Power Tools.Pdf
    www.dbebooks.com - Free Books & magazines SECURITY POWER TOOLS ® Other computer security resources from O’Reilly Related titles Security Warrior SSH, The Secure Shell: The Snort Cookbook™ Definitive Guide Practical Unix and Internet TCP/IP Network Security Administration Essential System Network Security Hacks™ Administration Security Books security.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center security and related technologies, including sample chapters and code examples. oreillynet.com is the essential portal for developers interested in open and emerging technologies, including new platforms, pro- gramming languages, and operating systems. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today for free. SECURITY POWER TOOLS ® Bryan Burns, Jennifer Stisa Granick, Steve Manzuik, Paul Guersch, Dave Killion, Nicolas Beauchesne, Eric Moret, Julien Sobrier, Michael Lynn, Eric Markham, Chris Iezzoni, and Philippe Biondi Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Security Power Tools® by Bryan Burns, Jennifer Stisa Granick, Steve Manzuik, Paul Guersch, Dave Killion, Nicolas Beauchesne, Eric Moret, Julien Sobrier, Michael Lynn, Eric Markham, Chris Iezzoni, and Philippe Biondi Copyright © 2007 O’Reilly Media, Inc.
    [Show full text]
  • The Gateway Trojan
    THE GATEWAY TROJAN Volume 1, Version 1 TABLE OF CONTENTS About This Report ....................................................................................................................................1 Why This Malware?..................................................................................................................................2 The Basic Questions About RATs..........................................................................................................2 Different Breeds of RATs ........................................................................................................................5 Symantec’s Haley Subcategories of RATs .........................................................................................6 Dissecting a RAT .......................................................................................................................................7 Category II: Common RATs ....................................................................................................................9 Back Orifice ...........................................................................................................................................9 Bifrost ................................................................................................................................................. 10 Blackshades ....................................................................................................................................... 11 DarkTrack .........................................................................................................................................
    [Show full text]
  • Taint Analysis for Automatic Malware Detection and Analysis
    Whole-system Fine-grained Taint Analysis for Automatic Malware Detection and Analysis Heng Yin Dawn Song [email protected] [email protected] College of William and Mary Carnegie Mellon University Abstract or bundled-ware containing spyware or adware. More surprisingly, even software provided by reputable ven- As malware is becoming increasingly sophisticated and dors could contain code that performs undesired actions stealthy, effective techniques for malware detection and such as leaking users’ private data. For example, Google analysis are imperative. Previous detection mechanisms Desktop, a popular local file system search tool, has are insufficient. Signature-based detection cannot detect been reported to send users’ private information back to new malware, and watch-point based behavioral detec- Google’s servers [15]. In another example, SONY Me- tion can be evaded by stealthier design. Most previous dia Player has been reported to send users’ listening be- analysis mechanisms are too coarse-grained to capture havior such as which songs the user has listened to back malware behavior and fail to address kernel-level attacks. to SONY [35]. Thus, as users and computers cannot We propose whole-system fine-grained taint analysis for live in isolation from the rest of the Internet and for- automatic malware detection and analysis, and build a eign code gets downloaded and installed unknowingly or prototype called TaintQemu. By tainting data from hard- knowingly to the local system all the time, the users and ware inputs and monitoring its propagation, TaintQemu computers are completely oblivious to what code is ac- generate taint graphs. The taint graph represents how in- tually installed on the local system and whether they will formation propagates during the system execution.
    [Show full text]
  • Remote Administration Software Attacks on Systems Using Public Key Security with and Without Smart Cards
    Remote administration software attacks on systems using public key security with and without smart cards I. INTRODUCTION user more control of the remote Windows system than the person at the keyboard of that machine.” Public key technology is increasingly used to protect (Back Orifice web site, www.cultdeadcow.com/ against a wide range of potential security attacks on tools). The most satisfying, or the most frightening, data and data transmissions and to prevent identity thing about these claims is that they are absolutely theft. At the same time, remote administration tools true. are becoming increasingly popular for centralized administration and troubleshooting. Remote Using Back Orifice or other remote control programs administration tools offer both considerable savings as administration or trouble-shooting tools is ideal. for enterprises as well as considerable potential for They allow an administrator to take complete control bypassing security systems such as public key- of a computer. The flip side of full control is that an enabled systems. improperly motivated individual can do essentially anything that the legitimate user can do. This has a This white paper investigates the potential security serious impact on security that we will address in impacts on public key enhanced security systems by the remainder of this paper. remote administration tools. The general product class name was used, rather than specific vendor Back Orifice also advertises that it can get detailed names, because the issues investigated are related to system information, including: the technology and not to any particular vendor’s implementation. The evaluation of the interaction • Current user of these two technologies was done using several • CPU type remote administration applications, principally Back •Windows version Orifice, and an application from a PKI solutions • Memory usage provider.
    [Show full text]
  • This Is a Plain-Text List of Port Numbers, Names, and Descriptions. 'The List Should Be Kept in Ascending Numeric Sequence
    'This is a plain-text list of port numbers, names, and descriptions. 'The list should be kept in ascending numeric sequence. 'At present, the maximum number of entries is 8192. One line/port. 'Format: portnumber TAB portname TAB description ' portnumber: required. Range is 0 to 65535 ' TAB: a tab character (X'09'). The tabs are required even when ' fields between them are omitted. They are the delimiters. ' portname: optional. Common ports have standardized uses/names, ' but most other ports do not have names. Try to keep the ' names short, as they appear within the 'port' columns of ' the Events List. ' description: optional. This is a list of legitimate and/or malware. ' Legitimate use(s) come first, immediately following the TAB. ' These are the normal, non-threatening uses of the port. When ' a port has several uses, separate them with vertical bars. ' Spaces on either side of the bars make the list more readable. ' Malware (Worms, viruses, Trojans, etc.) appear after the ' legitimate uses. The Malware list begins with a Tilde (~). ' When there are several malwares, separate them with vertical ' bars. 'Look at some of the existing entries for examples. 'Lines beginning with an apostrophe, and blank lines, are ignored. 'Please send updates and corrections to [email protected] 0 ~REx 1 tcpmux TCP Port Service Multiplexer~Sockets des Troie 2 compressnet Compression Process~Death 3 compressnet compressnet 4 echo Appletalk echo Protocol 5 rje Remote Job Entry~yoyo 7 echo echo 8 ~Ping Attack 9 discard sink null 11 systat Active Users~Skun
    [Show full text]