• Save
Time based security for cloud computing
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Time based security for cloud computing



The risks and threats associated with today's cloud computing and applying Time Based Security TBS principles to measure the effectiveness of security

The risks and threats associated with today's cloud computing and applying Time Based Security TBS principles to measure the effectiveness of security



Total Views
Views on SlideShare
Embed Views



3 Embeds 20

http://www.linkedin.com 11
https://www.linkedin.com 5
https://twitter.com 4



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Attackers changed – Why it matters? Because nation states and organized crime know what to do with stolen property. Previously a hacker may have been able to break into a network. But what will they really do with RSA source code?
  • CEOs and the technologists who work for them like to say the applications they rely on— especially the kind custom-written by specialists at banks and investment companies with fortunes behind them—are safe as houses.And they are, if you're talking about houses in Louisiana when the Gulf starts lashing hurricanes and tarballs.Almost 60 percent of all the applications brought to security testing and risk-analysis companyVeracode during the past 18 months couldn't meet the minimum standards for acceptable security, even when the criteria were dialed down to accommodate applications that don't pose a great security risk, according to Samskriti King, vice president of product marketing at the company. Web-based apps carry their own special set of risks."There are far more people on Web projects because they're often easier to develop; many components are already available so you can stand up Web applications very easily," King says. "Developer education usually focuses on applications generated and used in one place, but Web applications could touch many places, so a vulnerability in one component could manifest in many places if it's reused."Unfortunately, developers trained with software that's generated and used in one location with a single set of servers often don't understand the precautions needed for Web applications that take code, data, and elements of the interface from many servers, she says.[ For more background on securing Web-based apps, see 5 Problems with SaaS Security . ]The typical number of security flaws, especially in legacy or other homegrown software, must be taken into account by cloud-computer service providers, says Thomas Kilbin, CEO of cloud and hosted-server provider Virtacore Systems. After all, he says, customers who want on-demand compute capacity don't want to rewrite all their applications just to run in an environment designed to save money and add convenience."Our customers are taking apps they had running in their back office and moving them to private clouds for the most part," Kilbin says. "They are not developing any apps geared towards only working in a cloud IaaS/SaaS model. We secure these apps via a number of methods, traditional firewalls, app specific firewalls from Zeus, etc."Keeping Web-based apps secure can be particularly tough for smaller IT teams."The cloud model is more threat-rich than the shared hosting model, mainly because in shared hosting the core OS and apps—php, perl, mysql—are kept updated by the service provider," Kilbin says. "In the cloud, the customer has to keep the core OS updated, along with the application stacks, in addition to their code."Most customers don't have the expertise or the time to do so, Kilbin says.Some 2,922 applications were examined by Veracode in the past 18 months, with the results detailed in the company's recently released State of Software Security Report: The Intractable Problem of Insecure Software.Some of the applications sent to Veracode for testing come from ISVs or corporate programmers in the last stages of development. Another big chunk comes from developers who have to present certifications or risk analyses before closing a deal with government agencies or heavily regulated industries.Old App Flaws Revealed Before Web MovesIncreasingly, however, Veracode is testing software that clients have used for a long time or are very confident in, but are now migrating to a cloud or Web-based service environment. The requests often come from corporate IT executives who turn out to be wrong in believing that their secure, homegrown applications are either homegrown or secure, especially when they're moved into multi-site environments for the first time.Both commercial and open-source applications failed Veracode's tests more often than homegrown—at 65 percent and 58 percent respectively. Homegrown applications failed 54 percent of the time, Veracode reports.Software written by outsourcing firms missed the mark an astonishing 93 percent of the time, Veracode says.Even applications being used by banks and financial service companies failed 56 percent of the time on initial submission, though the criteria are tougher for those applications, because problems in those apps would create more havoc than, say, in an internally developed server-monitoring application, King says.Internal developers shouldn't be comparatively complacent, however, King says. Though internal apps are generally assumed to be made of 70 percent homegrown code, reuse of code, objects and procedures is so common that between 30 percent and 70 percent of the code in homegrown applications actually came from commercial software.Internal developers are also unaccountably unaware of the most common exploits likely to be used against Web-fronting applications, resulting in an 80 percent failure rate for Web applications, which are tested against the list of 10 most-common security threats published and publicized by the the Open Web Application Security Project (OWASP), King says."At that point it just comes down to developer education," King says.Cross-site scripting is the most common security flaw in all the types of software Veracode tests, but is most noticeable in Web- and cloud-based software, King says.But the time it takes to fix problems and get an application to an acceptable level of security has dropped drastically from 30 to 80 days a year or two ago to only 16 days now, mainly because developers of all stripes are putting greater emphasis on security, software quality, and shortening their time to market, King says.There aren't any shortcuts, but Veracode does have some suggestions for IT teams to counter the most consistent app security problems:1. Design apps assuming they'll link cross-site; secure those links and the processes that launch them.Cross-site scripting (XSS) accounts for 51 percent of all vulnerabilities, according to Veracode. Apps written in .net have an abnormally high number of XSS issues because many .net controls don't automatically encrypt data before sending or storing it. Check and encrypt all points of output. Inadequate or absent encryption in non-.net applications also created problems, but are easy to fix once the source of in-the-clear data broadcasts are identified.2. Focus your efforts on the greatest source of vulnerabilities.You can assume software from any provider is likely to have vulnerabilities, but put extra Q/A and security analysis effort into code from outsourced programming services, ISVs and components from either of those that find their way into homegrown applications.3. Verify security of the application itself in a cloud or SaaS environment.Whether the customer or the service provider supplies the application, check it for flaws or vulnerabilities in a realistic cloud/SaaS/shared-resource environment, not just in a workgroup on a LAN. Security in the cloud platforms is still evolving, and the skills to write secure code for them is not widespread. Stick extra red flags on this part of your project plan.4. Location is irrelevant. New criteria are impact, impact, impact.A printer-management application with a flaw that allows hackers to draft a LaserJet into a bot army can cause headaches. An accounting, customer-data-management or cashflow-automation app with a backdoor can put you out of business. Use Level of Risk as a multiplier to determine how important a particular app is to evaluate, and how much time or money you should spend getting it fixed.5. Don't ignore the basics.The 10 most common attacks on Web applications are listed here by OWASP. The 25 most significant security errors that appear in applications are listed here. They're easy to read and come with extra help to fix or avoid errors already known by everyone who might want to hack your systems.

Time based security for cloud computing Presentation Transcript

  • 1. Time Based SecurityForCloud ComputingJorge Sebastiaohttp://linkedin.com/in/sebastiao1`Day Tuesday 11-12-12Session 4: Cyber Security8:30-10:00Using Time Based SecurityJorge Sebastiao, VP AdvancThreats and Challenges inNiraj Mathur, BDM ServiCyber Security and Impact
  • 2. Modern Hackers2
  • 3. Too many layers to defend
  • 4. Too many APIs
  • 5. Our systems are too complex
  • 6. Our policies can not be used?
  • 7. 2012 attack motivations
  • 8. Motivation is money
  • 9. Are your passwords aretimeless?
  • 10. Also Government sponsored?
  • 11. 2012 attack techniques
  • 12. Modern APT StructureInfection PersistenceCommunicationControlSocialMediaConfigurationFilesEXEUpdatesRemoteExploits HiddenTrafficCustomMalwareRootkits Backdoors Anti-AVEncryptionProxies&EvasionsFastFlux
  • 13. APTs around the clock attackReconInitialintrusionBackdoors& malwareAdvancementMaintenance
  • 14. Mobile Malware up1,200% Q1 2012
  • 15. Android wipeout
  • 16. 1.7Mil Apps High Risk
  • 17. Mobility put risk every where.
  • 18. Attacks will be everywhereMainframeMinicomputerPCDesktop/InternetMobileInternet1101001000100001000001000000100000001950 1960 1970 1980 1990 2000 2010 2020 2030Devices/Users(millions)YearRef: ITU, Morgan Stanley Research, 2009- Smartphone- Tablets- Car Electronics-- Mobile Medicine-- Payment Systems-- Mobile Banking- GPS/Navigation- Mobile Video- Home Entertainment- Games- Home Appliances
  • 19. Cloud DimensionsSource: NIST Definition of Cloud Computing v153 Service Models4 Deployment Models5 EssentialCharacteristics
  • 20. Cloud Architecture Issues 1
  • 21. Cloud Architecture Issues 2
  • 22. Mobile Cloud Computing - logical evolutionhttp://twitter.com/4jorge/status/227380945404178432
  • 23. Cloud Loss of Connectivity
  • 24. Cloud Control
  • 25. Cloud Issues & Threats#1: Abuse and Nefarious Use of Cloud Computing#2: Insecure Interfaces and APIs#3: Malicious Insiders#4: Data Loss or Leakage#5: Account or Service Hijacking#6: Unknown Risk Profile#7: Alternative to Botnets – Brute Force#8: New Vulnerabilities#9: Fait Sharing – FBI / Interpol Raid#10: Auditability
  • 26. Many Apps Flunk Security CheckBefore Move to the Cloud
  • 27. “Big Failures…”
  • 28. Its all about time…
  • 29. You don’t have time torespondSQL Slammer Wormscanned 55million host /sec
  • 30. Wrong Skills?
  • 31. Wrong Assumptions?
  • 32. Broken tools?Firewall IDS Anti-VirusAttack
  • 33. Ineffective barriers?
  • 34. Modeling Risk is not enoughThreats VulnerabilitiesControls Risks AssetsSecurityRequirementsBusinessImpactexploitexposeincreaseincreaseincrease haveprotect againstmet by indicatereduce
  • 35. Risks even higher in cloud environment
  • 36. Think outside the box3
  • 37. Time to combine securityTotal SecurityPhysicalSecurityManagementICTSecurityManagement
  • 38. A5 - ProcessBusiness RiskControlsMaturity
  • 39. Defense in depth
  • 40. Leverage Standards & CertificationSecurity MetricsKey Performance IndicatorsCoBiT, ComplianceITILISO20000ISMSISO27001BCMSISO22301Time Based Security
  • 41. Knowledge BaseResponseBuild IntelligenceMultiple SourcesIntelPartners,Vendors,CERT ,…InternalSecurityResearchInternet,Mailing listsand othersources Automatic Incidence Response
  • 42. Continuous DetectionResponseIncident ResponseAnalyseContainEliminateRestoreLessonsPolicy Refine PolicyContinuous MonitoringT-1 T 0 T 1 T 1 T 3 T 4 T NCommunicate
  • 43. Big Data is key
  • 44. Moving Fast
  • 45. TBS- Time Based SecurityProtectionDetectionResponseSECURITYP>D+RAnti-virusVPNFirewall, IPSAccess ControlGrid Time ResponsePatch MgmtIncidence ResponseDisaster RecoveryVulnerability TestingSIEMLog CorrelationCCTV, Access Control
  • 46. TransformAssess ArchitectImplementing TBS
  • 47. http://linkedin.com/in/sebastiao`Day Tuesday 11-12-12Session 4: Cyber Securi8:30-10:00Using Time Based SecurJorge Sebastiao, VP AdvThreats and ChallengesNiraj Mathur, BDM SeCyber Security and Imp