Database Attacks, How to protect the corporate assets


Published on

1 Comment
1 Like
  • how to install ??
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Data security used to be simple. (click) A Large Mainframe stored in a glass house manipulated data stored in a Winchester array. If someone tried to steal that data, you saw them through the window, (click) pulled the Halon fire supression lever, and watched them pass out.
  • It’s gotten a lot more complicated. (click) The demand for pervasive Access (read slide) has lead to (clock) increasingly focused attacks (read slide) (click) which in turn has created a whole new set of compliance needs.
  • A couple of preliminaries. This is a network we’ll use throughout this talk. Please note we’ve got firewalls, and web proxies, and encrypted channels, and all the good stuff to NETWORK security. Today we’re going to talk about APPLICATION security. We will show how the two are complimentary, but different.
  • As the environment evolved so has the threat.
  • This is Jack’s FUD slide. Data is a valuable resource in your company. You, of course, are the most valuable resource. And People want to steal that data. If you believe attacks are coming only from 18 year olds sitting up all night sucking down Red Bull, you’re sadly vulnerable. Those kids have grown up. But they’ve now got spouses and kids of their own. They need to earn a living. For the most part, we won’t hire them because they’re disaffected. Those that didn’t become ethical hackers, revert to what they did in college, and we make it easy for them.
  • Here’s a little evidence that the bad guys have moved up the stack. Scarcely a week goes by that were not reading about a personal privacy breach. Here are ten of the biggest we’ve seen, just since the beginning of the year. Nearly 50 million customers privacy invaded. So what? Choicepoint’s stock tumbled 15% the day after their breach was disclosed and hasn’t recovered. Card Systems went out of business as Visa and MasterCard will no longer do business with them.
  • So let’s summarize the top 5 issues with Application level security. (Read bullet points)
  • Second, is a depiction typical web enabled enterprise application. Web Front End; Application Specific middle ware; and a database back end. The database has the good stuff. We’ll talk about how this this application can be attacked at each of the component levels.
  • Databases, actually, any complex software is riddled with vulnerabilities. Software makers are under pressure to make their products easy to use. Ease of use and security are somewhat opposed concepts. Let’s look at a very simple vulnerability Default and Weak Passwords. Databases have their own user accounts and passwords.
  • Databases, actually, any complex software is riddled with vulnerabilities. Software makers are under pressure to make their products easy to use. Ease of use and security are somewhat opposed concepts. Let’s look at a very simple vulnerability Default and Weak Passwords. Databases have their own user accounts and passwords.
  • Like any software, databases ship with a default user name and password. Oracle uses a little obfuscation by having over 200 different defaults for different versions, but that doesn’t really cause the bad guy much of a problem. Here’s a list a some of the defaults…everyone knows them.
  • Notice the Microsoft default. SA BLANK! Remember that MSDE is a Microsoft SQL server. MSDE has this same default. So any application, like a Blackberry Mail Server, or a Cisco Network Manager, that uses MSDE has this same default user….until you change it.
  • Without account lockout, I can just try every password I can think of, or run a script. We’ll look at this a little later.
  • Let’s talk for a minute about Denial of Service and Buffer overflow attacks
  • So what’s a denial of service? We know what that is in a network. Applications have the same issues. READ THE SLIDE Here are common DOS vulnerabilities in these popular databases.
  • And Buffer Overflows. READ the Slide We’ll talk more about the RESOLUTION STACK buffer overflow later. They all have them.
  • A third tranche of vulnerabilities deal with misconfigurations. Databases are complex beasts. You know you can’t just fire them up and let ‘em rip.
  • These are some common problem areas in databases. We’ll look at how to get in through a default HTTP server in an Oracle database later. How many of you know Oracle has a built in web server? Check your port 7777. IBM DB2 CREATE_NOT_FENCED privilege granted This privilege allows logins to create stored procedures that run in the address space of the database. These stored procedures can execute malicious code under the privileges of the database manager. MySQL Permissions on User Table (mysql.user) This table contains password hashes as well as a list of privileges for a user.
  • A third tranche of vulnerabilities deal with misconfigurations. Databases are complex beasts. You know you can’t just fire them up and let ‘em rip.
  • So let’s get inside the head of one of those folks looking to take something from you. How do they plan an attack? It’s much like a Special Operations mission. [REVIEW the Slide] What types of issues will we look to exploit?
  • We simply start writing our own extended SQL commands using a UNION to inject the valid command that we’re using for malicious purposes. In this example, here we select passwords out of the DBA User’s Table. In this specific example we will pull out the hashed password for “SYSTEM” in an Oracle database.
  • When we hit “Submit”, and it returns the Password Hash as the Customer Address. And to answer the earlier rhetorical question, we only need refer to any or a number of publicly available hash dictionaries to back into the cleartext password.
  • Here we have an Oracle HTTP Server running on port 7778 – somebody could have created a web application using the Oracle HTTP Server which can exist on an any port even on port 80. The things to be aware of are the following: This application which comes standard with the installation of the Oracle HTTP Server can be used as a way into the database, and eventually into the host operating system or other trusted systems. The hackers can attack the database using a SQL Injection exploit.
  • This is the demo application that ships with the server. It is susceptible to SQL Injection: demo/sql/jdbc/JDBCQuery.jsp The first step in using SQL Injection to see where we can penetrate. We use the “connStr” command to connect to target any Oracle database in the network.
  • Here we Union the command to ask for the database name using SQL Injection.
  • And that command conveniently displays the database name within the browser.
  • Let’s try another command. The Sys.login should return the user name the web server uses to login to the database. As an aside, how often is this ever changed in your networks?
  • … and here are the results showing that the web server uses “Scott” to login to the database.
  • Here we are going to use an existing buffer overflow in Oracle in our SQL Injection attack for whatever we’d like to do. There’s exploit code taking advantage of this buffer overflow on the Internet available for you to look up and see all of the various exploits. A buffer overflow exists in the built-in function NUMTOYMINTERVAL. This buffer overflow may allow an attacker to overwrite the stack and execute arbitrary code under the security context of the database server. NUMTOYMINTERVAL is a built-in function and as such permissions to execute this function are granted to all database users.
  • Here we inject the buffer overflow attack and it crashed the database.
  • Here’s a simple one.
  • I wonder what this search might return?
  • So what do you do about this stuff? Diligence to the application is required. Security is an ongoing process. [READ Slide]
  • Hackers want to steal from you. Your valuable assets are in your databases. Doesn’t it just make sense to protect them?
  • Use the industry best practices.
  • Note we modified #2. Seriously, MBSA is ok for O/S level attacks but at the application layer you probably want an independent third party looking at the app.
  • AppDetective performs 4 basic functions: Application Discovery Penetration Testing Security Auditing Advanced Reporting A mature product, AppDetective includes many enterprise-class features…
  • Database Attacks, How to protect the corporate assets

    1. 1. Database Attacks, How to protect the corporate assets Presented by: James Bleecker
    2. 2. Agenda <ul><li>Introduction </li></ul><ul><ul><li>Landscape </li></ul></ul><ul><ul><li>Database Vulnerabilities Are The New Front-Lines </li></ul></ul><ul><li>Attacking Where the Data Resides </li></ul><ul><ul><li>Planning an Attack </li></ul></ul><ul><ul><li>Attacking Database Vulnerabilities </li></ul></ul><ul><li>How Do You Protect Your Database? </li></ul><ul><li>What is Application Security direction/Vision? </li></ul>
    3. 3. Old Data Processing Environment Winchester IMS Array Glass House Halon Release Switch CICS Controller BIG IRON Hyperchannel Halon
    4. 4. New Data Processing Requirement <ul><li>Increasingly Focused Attacks </li></ul><ul><li>Directly on applications (75%!) </li></ul><ul><li>Including insiders (80+%!) </li></ul><ul><li>As perimeter crumbles </li></ul><ul><li>Demand for Pervasive Access </li></ul><ul><li>By anyone </li></ul><ul><li>To any application </li></ul><ul><li>Increasingly direct </li></ul><ul><li>Compliance Requirements </li></ul><ul><li>Info ultimately in Db apps: </li></ul><ul><ul><li>Privacy / confidentiality </li></ul></ul><ul><ul><li>Integrity </li></ul></ul><ul><li>Compliance must be: </li></ul><ul><ul><li>Repeatable </li></ul></ul><ul><ul><li>Demonstrable </li></ul></ul>Stored Data
    5. 5. Typical Network Landscape
    6. 6. Database Vulnerabilities <ul><li>A decade ago, databases were </li></ul><ul><ul><li>Physically secure </li></ul></ul><ul><ul><li>Housed in central data centers – not distributed </li></ul></ul><ul><ul><li>External access mediated </li></ul></ul><ul><ul><li>Security issues rarely reported </li></ul></ul><ul><li>Now, databases are externally accessible </li></ul><ul><ul><li>Suppliers directly connected </li></ul></ul><ul><ul><li>Customers directly connected </li></ul></ul><ul><ul><li>Customers and partners directly sharing data </li></ul></ul>
    7. 7. Database Vulnerability Exploitation <ul><li>A decade ago, attacks were </li></ul><ul><ul><li>Broad based </li></ul></ul><ul><ul><li>Launched by disaffected “Hackers” </li></ul></ul><ul><ul><li>Intended to disrupt, gain respect / notoriety in the community </li></ul></ul><ul><li>Now, attacks are </li></ul><ul><ul><li>Targeted against specific resources </li></ul></ul><ul><ul><li>Launched by sophisticated professionals </li></ul></ul><ul><ul><li>Intended to bring monetary gain to the attacker </li></ul></ul><ul><li>Data is a valuable resource in your company </li></ul><ul><ul><li>Value increases with greater integration and aggregation </li></ul></ul><ul><ul><li>But so does the threat of data theft, modification, or destruction </li></ul></ul>
    8. 8. Databases Are Under Attack <ul><li>106 Incidents in 2005 </li></ul><ul><li>Flurry of new data breaches disclosed : More than 190 such incidents have been reported since February 2005, Jaikumar Vijayan and Todd Weiss; June 19, 2006 (Computerworld) </li></ul><ul><li>We’re not Winning! </li></ul>
    9. 9. Recent Incidents 22-May-06 1500 Department of Energy’s nuclear weapons 15-Feb-06 350,000 Dept of Agriculture 5-Mar-06 41,000 Georgetown University 9-Feb-06 200,000 Misc retail debit card compromise (OfficeMax?) Source: Privacy Rights Clearinghouse, ~50,000,000+ # of customers affected Etc, etc, etc . 15-Feb-05 145,000 ChoicePoint 19-Apr-05 200,000 Ameritrade 9-Mar-05 310,000 LexisNexis 25-Feb-05 1,200,000 Bank of America 8-Mar-05 1,400,000 DSW Shoe Warehouse 6-Jun-05 3,900,000 Citigroup 17-Jun-05 40,000,000 Card Systems Date of Initial Disclosure # of Affected Customers Company/Organization
    10. 10. Top 5 Issues in Enterprise Security <ul><li>Attackers have gone pro </li></ul><ul><ul><li>Want personal data they can sell – Personal data like credit card and social security numbers are relatively easy to monetize </li></ul></ul><ul><li>Attacks are moving to the source </li></ul><ul><ul><li>Why pull a single credit card via compromising the network? It's relatively hard with a meager pay off. Instead, take over the corporate database and get them ALL </li></ul></ul><ul><li>The perimeter provides little defense </li></ul><ul><ul><li>Insiders don't go through the firewall thus perimeters provide no protection from this growing source of risk </li></ul></ul><ul><li>Inside the perimeter, enterprises have little-to-no protection </li></ul><ul><ul><li>Beyond anti-virus, enterprises are only just now getting started to build a layered defense. For example, how does a largely signature-based security solution protect you from an insider that doesn't need to run a vulnerability against a system to get access? They've got plenty of privileges already ;-) </li></ul></ul><ul><li>Everyone is watching </li></ul><ul><ul><li>Everyone is very-much clued in to the increased threats against personal data. Any mistakes are likely to be very public </li></ul></ul>
    11. 11. How Do You Secure Apps? Key Components of Enterprise Applications Vulnerabilities exist within each of these components
    12. 12. Database Vulnerabilities: <ul><li>Default & Weak Passwords </li></ul><ul><li>Denial of Services (DoS) & Buffer Overflows </li></ul><ul><li>Misconfigurations & Resource Privilege Management Issues </li></ul>
    13. 13. Database Vulnerabilities: Default & Weak Passwords <ul><li>Databases have their own user accounts and passwords </li></ul>Oracle Microsoft SQL Server Sybase Default & Weak Passwords MySQL IBM DB2     
    14. 14. Database Vulnerabilities Default Passwords <ul><li>Oracle Defaults (Over 200 of them) </li></ul><ul><ul><ul><li>User Account: internal / Password: oracle </li></ul></ul></ul><ul><ul><ul><li>User Account: system / Password: manager </li></ul></ul></ul><ul><ul><ul><li>User Account: sys / Password: change_on_install </li></ul></ul></ul><ul><ul><ul><li>User Account: dbsnmp / Password: dbsnmp </li></ul></ul></ul><ul><li>IBM DB2 Defaults </li></ul><ul><ul><ul><li>User Account: db2admin / Password: db2admin </li></ul></ul></ul><ul><ul><ul><li>User Account: db2as / Password: ibmdb2 </li></ul></ul></ul><ul><ul><ul><li>User Account: dlfm / Password: ibmdb2 </li></ul></ul></ul>
    15. 15. Database Vulnerabilities Default Passwords <ul><li>MySQL Defaults </li></ul><ul><ul><ul><li>User Account: root / Password: null </li></ul></ul></ul><ul><ul><ul><li>User Account: admin / Password: admin </li></ul></ul></ul><ul><ul><ul><li>User Account: myusername / Password: mypassword </li></ul></ul></ul><ul><li>Sybase Defaults </li></ul><ul><ul><ul><li>User Account: SA / Password: null </li></ul></ul></ul><ul><li>Microsoft SQL Server Defaults </li></ul><ul><ul><ul><li>User Account: SA / Password: null </li></ul></ul></ul>
    16. 16. Database Vulnerabilities Weak Passwords <ul><li>It is important that you have all of the proper safeguards against password crackers because: </li></ul><ul><ul><ul><li>Most databases do not have Account Lockout </li></ul></ul></ul><ul><ul><ul><li>Database Login activity is seldom monitored </li></ul></ul></ul><ul><ul><ul><li>Scripts and Tools for exploiting weak identification control mechanisms and default passwords are widely available </li></ul></ul></ul>
    17. 17. Database Vulnerabilities: Denial of Services (DoS) & Buffer Overflows <ul><li>Databases have their own DoS’s & Buffer Overflows </li></ul>Oracle Microsoft SQL Server Sybase Denial of Services & Buffer Overflows Default & Weak Passwords MySQL IBM DB2          
    18. 18. Denial of Services Databases Have Their Own Class of DoS Attacks <ul><li>Category of attacks that could result in the database crashing or failing to respond to connect requests or SQL Queries. </li></ul><ul><li>Significant Database Denial of Services: </li></ul><ul><ul><li>Oracle8i: NSPTCN data offset DoS </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Oracle9i: SNMP DoS </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Microsoft SQL Server: Resolution Service DoS </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>IBM DB2: Date/Varchar DoS </li></ul></ul><ul><ul><li> </li></ul></ul>
    19. 19. Buffer Overflows Databases Have Their Own Buffer Overflows <ul><li>Category of vulnerabilities that could result in an unauthorized user causing the application to perform an action the application was not intended to perform. </li></ul><ul><li>Most dangerous are those that allow arbitrary commands to be executed by authenticated users. </li></ul><ul><ul><ul><li>No matter how strongly you’ve set passwords and other authentication features. </li></ul></ul></ul><ul><ul><li>Significant Database Buffer Overflows: </li></ul></ul><ul><ul><ul><li>Oracle9i: TZ_OFFSET buffer overflow </li></ul></ul></ul><ul><ul><ul><li>Microsoft: pwdencrypt buffer overflow / Resolution Stack Overflow </li></ul></ul></ul><ul><ul><ul><li>Sybase: xp_freedll buffer overflow </li></ul></ul></ul>
    20. 20. Database Vulnerabilities Misconfigurations & Resource Privilege Management Issues <ul><li>Misconfigurations can make a database vulnerable </li></ul>Oracle Microsoft SQL Server Sybase Misconfigurations & Resource Privilege Management Denial of Services & Buffer Overflows Default & Weak Passwords MySQL IBM DB2               
    21. 21. Misconfigurations & Resource Privileges Misconfigurations Can Make a Database Vulnerable <ul><li>Oracle </li></ul><ul><ul><li>External Procedure Service </li></ul></ul><ul><ul><li>Default HTTP Applications </li></ul></ul><ul><ul><li>Privilege to Execute UTL_FILE </li></ul></ul><ul><li>Microsoft SQL Server </li></ul><ul><ul><li>Standard SQL Server Authentication Allowed </li></ul></ul><ul><ul><li>Permissions granted on xp_cmdshell and xp_regread </li></ul></ul><ul><li>Sybase </li></ul><ul><ul><li>Permission granted on xp_cmdshell </li></ul></ul><ul><li>IBM DB2 </li></ul><ul><ul><li>CREATE_NOT_FENCED privilege granted </li></ul></ul><ul><ul><ul><li>This privilege allows logins to create stored procedures </li></ul></ul></ul><ul><li>MySQL </li></ul><ul><ul><li>Permissions on User Table (mysql.user) </li></ul></ul>
    22. 22. Database Vulnerabilities Wrap-up Oracle Microsoft SQL Server Sybase Misconfigurations & Resource Privilege Management Denial of Services & Buffer Overflows Default & Weak Passwords MySQL IBM DB2               
    23. 23. Planning an Attack <ul><li>Create a Map </li></ul><ul><ul><li>What does the network look like? </li></ul></ul><ul><li>Reconnoiter </li></ul><ul><ul><li>Collect information about the layout of the target </li></ul></ul><ul><ul><li>What looks intere$ting? </li></ul></ul><ul><li>Probe, Progress, Plot </li></ul><ul><ul><li>What can we do? </li></ul></ul><ul><ul><li>Build the springboard for further activity </li></ul></ul><ul><ul><li>Plan the strike </li></ul></ul><ul><li>Retreat and Re-attack </li></ul>
    24. 24. How are search engines used for attacks? <ul><li>First thing an attacker needs is information </li></ul><ul><ul><li>Where to attack </li></ul></ul><ul><ul><li>What a site is vulnerable to </li></ul></ul><ul><li>Search engine is a large repository of information </li></ul><ul><ul><li>Every web page in your application </li></ul></ul><ul><ul><li>Every domain on the Internet </li></ul></ul><ul><li>Search engines provide an attacker: </li></ul><ul><ul><li>Ability to search for attack points on the Internet </li></ul></ul><ul><ul><li>Ability to search for an attack point in a specific website </li></ul></ul><ul><ul><li>Ability to look for specific URLs or files </li></ul></ul><ul><li> </li></ul>
    25. 25. Example – looking for iSQL*Plus <ul><li>Oracle HTTP Servers </li></ul><ul><ul><li>Provides a way to run queries on database using an HTTP form </li></ul></ul><ul><ul><li>Accessed using the URL /isqlplus </li></ul></ul><ul><ul><li>By default runs on any Oracle HTTP server installed with: </li></ul></ul><ul><ul><ul><li>Oracle Applications Server </li></ul></ul></ul><ul><ul><ul><li>Oracle Database Server </li></ul></ul></ul><ul><li>Search can be performed on Google or Yahoo </li></ul><ul><ul><li>looking for Oracle HTTP servers </li></ul></ul><ul><ul><li>Using the “allinurl” advanced search feature </li></ul></ul>
    26. 26. Using Google Advanced Search
    27. 27. Results of Google Advanced Search
    28. 28. Yahoo! Advanced Search Works Too…..
    29. 29. Connect with default username/password
    30. 30. Attacker can execute any query
    31. 31. Example – SQL Injection in demo applications <ul><li>Oracle HTTP Servers </li></ul><ul><ul><li>Provided default web applications </li></ul></ul><ul><ul><li>/demo/sql/jdbc/JDBCQuery.jsp </li></ul></ul><ul><ul><li>/demo/sql/tag/sample2.jsp </li></ul></ul><ul><li>Contains SQL Injection </li></ul><ul><ul><li>Google search value of “allinurl:JDBCQuery.jsp” </li></ul></ul>
    32. 32. Vulnerable Oracle HTTP Servers
    33. 33. <ul><li>Oracle </li></ul>X’ UNION SELECT password FROM dba_users WHERE username=‘SYSTEM Oracle Example
    34. 34. Password Hash Returned Customer address: EED9B65CCECDB2E9
    35. 35. SQLINJECTION1
    36. 36. SQLINJECTION1 <ul><li>7778/demo/sql/jdbc/JDBCQuery.jsp </li></ul>
    37. 37. SQLINJECTION2 sys.database_name
    38. 38. SQLINJECTION3
    39. 39. SQLINJECTION4 sys.login_user
    40. 40. SQLINJECTION5
    42. 42. SQLINJECTION7
    43. 43. Hackers Can Find Credit Cards <ul><li>Recent posting to security newsgroups </li></ul><ul><ul><li>To: [email_address] Subject: New google's top query? </li></ul></ul><ul><ul><li>Instructions on finding credit cards on the Internet </li></ul></ul><ul><ul><ul><li>Involves using Numrange searches in Google </li></ul></ul></ul><ul><ul><ul><ul><li> </li></ul></ul></ul></ul><ul><ul><ul><li>Can focus in on a single domain </li></ul></ul></ul><ul><ul><ul><li>Can focus in on a single person </li></ul></ul></ul><ul><ul><ul><li>“ Numrange can be used to specify that results contain numbers in a range you set. You can conduct a numrange search by specifying two numbers, separated by two periods, with no spaces. Be sure to specify a unit of measure or some other indicator of what the number range represents.” </li></ul></ul></ul>
    44. 44. Google Advanced Search Page
    45. 45. How Do You Address These Vulnerabilities? <ul><li>Stay Patched </li></ul><ul><ul><li>Stay on top of all the security alerts and bulletins </li></ul></ul><ul><li>Defense in Depth </li></ul><ul><li>Multiple Levels of Security </li></ul><ul><ul><li>Regularly perform audits and penetration tests on your database </li></ul></ul><ul><ul><li>Encryption of data-in-motion / data-at-rest / data-in-use </li></ul></ul><ul><ul><li>Monitor database activity log files </li></ul></ul><ul><ul><li>Implement application layer intrusion detection </li></ul></ul><ul><ul><ul><li>Especially if you can’t stay patched! </li></ul></ul></ul>
    46. 46. How Do You Address These Vulnerabilities? <ul><li>“I’m running auditing, vulnerability assessment, and IDS tools for the network/OS. Am I secure?” </li></ul><ul><ul><li>NO!!!! </li></ul></ul><ul><li>Databases are extremely complex beasts </li></ul><ul><li>Databases store your most valuable assets </li></ul><ul><li>Significantly more effort securing databases is necessary </li></ul><ul><ul><li>“If your workstation gets hacked, that’s bad. But if your database gets hacked, you’re out of business.” </li></ul></ul><ul><ul><ul><ul><li> </li></ul></ul></ul></ul>
    47. 47. Best Practices Provided by Database Vendors & Notable Third Parties <ul><li>Oracle </li></ul><ul><ul><li>Oracl9i Security Checklist </li></ul></ul><ul><li>SANS Institute (SysAdmin, Audit, Network, Security) </li></ul><ul><ul><li>Oracle Database Checklist </li></ul></ul><ul><li>Microsoft </li></ul><ul><ul><li>10 Steps to Secure SQL Server </li></ul></ul><ul><li> </li></ul><ul><ul><li>SQLSecurity Checklist </li></ul></ul>
    48. 48. Oracle9i Security Checklist A Security Checklist for Oracle9i <ul><li>Install Only What is Required </li></ul><ul><li>Lock and Expire Default User Accounts </li></ul><ul><li>Change Default User Passwords </li></ul><ul><li>Enable Data Dictionary Protection </li></ul><ul><li>Practice Principle of Least Privilege </li></ul><ul><li>Enforce Access Controls Effectively </li></ul><ul><li>Restrict Network Access </li></ul><ul><li>Apply Security Patches and Workarounds </li></ul>
    49. 49. 10 Steps to Secure SQL Server 2000 AppDetective Compliance Capabilities 10) Audit connections to SQL Server 9) Delete or secure old setup files 8) Use the most secure file system 7) Disable SQL Server ports on your firewall 6) Limit privilege level of SQL Server Services 5) Assign a strong password 4) Isolate your server and back it up regularly 3) Use Windows Authentication Mode 2) Assess your server’s security with Microsoft Baseline Security Analyzer ((We’d suggest AppDetective!!)) 1) Install the most recent service pack
    50. 50. Database Security Resources <ul><li>SQL Server Security </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul><ul><li>Oracle Security </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul><ul><li>Database Security alerts </li></ul><ul><ul><li> </li></ul></ul><ul><li>Database Security Discussion Board </li></ul><ul><ul><li> </li></ul></ul>
    51. 51. How Do You Secure Apps? Apply the vulnerability management lifecycle... <ul><li>Determine risk and prioritize based on vulnerability data, threat data, asset classification </li></ul><ul><li>High-priority vulnerabilities </li></ul><ul><li>Establish controls and eliminate root causes </li></ul><ul><li>Baseline compliance </li></ul><ul><li>Vulnerabilities </li></ul><ul><li>Threat environment </li></ul><ul><li>Establish “as is” position </li></ul><ul><li>Identify vulnerabilities </li></ul><ul><li>Develop ideal baseline </li></ul>Maintain Baseline/ Discover Prioritize Shield and Mitigate Monitor
    52. 52. Proactive Hardening Complete Database Vulnerability Assessment <ul><li>Database Discovery </li></ul><ul><li>Penetration Testing </li></ul><ul><li>Security Audit </li></ul><ul><li>Reporting </li></ul><ul><li>Remediation: Fix Scripts </li></ul><ul><li>Keep current: ASAP updates protect against latest threats </li></ul>Baseline/ Discover Prioritize Shield and Mitigate Monitor
    53. 53. Real-Time Monitor Security Alerts + Focused, Granular Monitoring <ul><li>Who, What and When </li></ul><ul><li>Activity Monitoring & Alerting </li></ul><ul><ul><li>All User Activity and System Changes </li></ul></ul><ul><ul><li>Complex Attacks and Threats </li></ul></ul><ul><ul><li>Misuse and Malicious Behavior </li></ul></ul><ul><li>Configurable Detection </li></ul><ul><ul><li>User Defined Alert Rules </li></ul></ul><ul><ul><li>User Defined Threat Signatures </li></ul></ul><ul><li>Regularly Updated </li></ul><ul><ul><li>ASAP Updates™ </li></ul></ul><ul><li>Microsoft SQL Server </li></ul><ul><li>Oracle </li></ul><ul><li>Sybase </li></ul><ul><li>IBM DB2 </li></ul>Baseline/ Discover Prioritize Shield and Mitigate Monitor
    54. 54. Last Line of Defense - Shield Usable Crypto for Production Databases <ul><li>Column-level Encryption </li></ul><ul><ul><li>Selective protection </li></ul></ul><ul><li>Built in Key Management </li></ul><ul><ul><li>Control Administrator rights </li></ul></ul><ul><li>Easy to Implement </li></ul><ul><ul><li>Clustering / Mirroring </li></ul></ul><ul><ul><li>Back up / Disaster Recovery </li></ul></ul><ul><li>Easy to Use </li></ul><ul><ul><li>Application Transparency </li></ul></ul><ul><ul><li>User Invisibility </li></ul></ul><ul><li>Cryptographically Strong </li></ul><ul><ul><li>Broad set of algorithms </li></ul></ul>Baseline/ Discover Prioritize Shield and Mitigate Monitor
    55. 55. Security Industry Direction <ul><ul><li>More focused and complex attacks </li></ul></ul><ul><ul><li>Blended attacks </li></ul></ul><ul><ul><li>Increased audit and tracking requirements </li></ul></ul><ul><ul><li>Mixed Database vendors with less resources </li></ul></ul><ul><li>Oracle </li></ul><ul><li>Microsoft SQL Server </li></ul>
    56. 56. AppSecInc Direction <ul><ul><li>Product working closer to together </li></ul></ul><ul><ul><li>Vulnerability scan feeding IDS monitoring </li></ul></ul><ul><ul><li>Reporting across functions for compliance issues </li></ul></ul><ul><ul><li>Security Change Audit tracking </li></ul></ul>Baseline/ Discover Prioritize Shield and Mitigate Monitor
    57. 57. Contact Info <ul><li>Ben Brieger – Northwest Regional Manager </li></ul><ul><ul><li>650-796-4919 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li> </li></ul></ul><ul><li>James Bleecker – Senior Systems Engineer </li></ul><ul><ul><li>949-310-4639 </li></ul></ul><ul><ul><li>jbleecker </li></ul></ul><ul><ul><li> </li></ul></ul>