1.
CLOUD 9:<br />UNCOVERING SECURITY & FORENSICS DISCOVERY IN CLOUD<br />[CLUBHACK 2010 EDITION]<br />byManu Zacharia<br />MVP (Enterprise Security), C|EH, <br />ISLA-2010 (ISC)², C|HFI, CCNA, MCP<br />Certified ISO 27001:2005 Lead Auditor<br />Director – Information Security<br />US Based Consultancy Firm<br />“Aut viam inveniam aut faciam ” <br />Hannibal Barca<br />

2.
#whoami<br /><ul><li> I am an Information Security Evangelist

3.
For paying my bills – I work as Director – Information Security – US Based Consultancy.

4.
Awards

5.
Information Security Leadership Achievement Award from International Information Systems Security Certification Consortium - (ISC)²

6.
Microsoft Most Valuable Professional (Enterprise Security)

7.
Author of a Book – Intrusion Alert – An Ethical Hacker’s Guide to Intrusion Detection Systems

8.
President – Information Security Research Association - NPO</li></li></ul><li>#whoami<br /><ul><li> Developed an Operating System from Linux kernel – Matriux – (www.matriux.com) - Asia’s First OS for Hacking, Forensics and Security testing – Open Source & Free 

9.
Founder c0c0n – International Security & Hacking Conf

10.
Extend service to police force as Cyber Forensics Consultant</li></li></ul><li>DISCLAIMER(S)<br /><ul><li> The opinion here represented are my personal ones and do not necessary reflect my employers views.

11.
Registered brands belong to their legitimate owners.

12.
The information contained in this presentation does not break any intellectual property, nor does it provide detailed information that may be in conflict with any laws (hopefully...) :)</li></ul>4<br />

13.
REFERENCES<br /><ul><li> Information and resources from Internet (including publications from Cloud Security Alliance) were extensively used for the creation of this presentation.</li></ul>5<br />

14.
AGENDA<br />INTRO & CLOUD ARCHITECTURE<br />CLOUD SECURITY & RISK ASSESSMENT FRAMEWORK<br />EXPLOITING CLOUD & FORENSICS<br />CONCLUSION<br />6<br />

15.
INTRODUCTION<br />7<br />

16.
QUESTION<br /><ul><li> So what is Cloud Computing?

17.
Do you know what is EC2 and S3?

18.
What is SPI Model?</li></ul>8<br />

19.
WHY THIS TALK?<br /><ul><li> cloud is loud

20.
Headline stealer

21.
Everybody is concerned about Cloud Security</li></ul>9<br />

22.
WHY CLOUD IS DIFFERENT?<br /><ul><li> Why handle cloud differently?

23.
Simple – power of cloud</li></ul>10<br />

24.
TIGR - ??????<br /><ul><li>Barack Obama's Technology Innovation and Government Reform Team (TIGR) describe the use of cloud computing as "one of the most important transformations the federal government will go through in the next decade." </li></ul>11<br />

25.
CLOUD POWER<br /><ul><li> A 64 node Linux cluster can be online in just five minutes

26.
Forget about those sleepless nights in your data centers</li></ul>12<br />

27.
EC2<br /><ul><li> Amazon Elastic Compute Cloud (Amazon EC2)

28.
A web service that provides resizable compute capacity in the cloud</li></ul>13<br />

29.
EC2 - WIKIPEDIA<br /><ul><li> Allows users to rent computers on which to run their own computer applications.

30.
A user can boot an Amazon Machine Image (AMI) to create a virtual machine, which Amazon calls an "instance", containing any software desired.</li></ul>14<br />

31.
EC2 - WIKIPEDIA<br /><ul><li> A user can create, launch, and terminate server instances as needed, paying by the hour for active servers, hence the term "elastic".</li></ul>15<br />

32.
S3<br /><ul><li> Amazon S3 (Simple Storage Service) is an online storage web service offered by Amazon Web Services.

33.
Provides unlimited storage through a simple web services interface</li></ul>16<br />

34.
S3<br /><ul><li> $0.15 per gigabyte-month

35.
102 billion objects as of March 2010</li></ul>17<br />

36.
POWER OF CLOUD<br /><ul><li> The New York Times - Amazon EC2 and S3 - PDF's of 15M scanned news articles.

37.
NASDAQ uses Amazon S3 to deliver historical stock information.</li></ul>18<br />

38.
CLOUD<br /><ul><li> Cloud separates:

39.
application and information resources from the underlying infrastructure, and

40.
the mechanisms used to deliver them.</li></ul>19<br />

41.
CLOUD<br /> Use of a collection of<br /><ul><li> services,

42.
applications,

43.
information, and

44.
infrastructure </li></ul> comprised of pools of compute, network, information, and storage resources.<br />20<br />

45.
CLOUD<br /><ul><li> Components can be

46.
rapidly orchestrated,

47.
provisioned,

48.
implemented & decommissioned, and

49.
scaled up or down

50.
Provide an on-demand utility-like model.</li></ul>21<br />

51.
CLOUD CONFUSION<br /><ul><li> From an architectural perspective; there is much confusion

52.
How cloud is both similar to and different from existing models of computing? </li></ul>22<br />

53.
CLOUD CONFUSION<br /><ul><li> How these similarities and differences impact the

54.
organizational,

55.
operational, and

56.
technological approaches </li></ul>to network and information security practices.<br />23<br />

57.
CLOUD SECURITY – DIFFERENT?<br />Marcus Ranum - Same old, <br />Same old <br />24<br />

58.
CLOUD SECURITY – DIFFERENT?<br />Same Client / Server paradigm from Mainframe days – Bruce Schneier<br />25<br />

59.
So what is this cloud?<br />26<br />

60.
CLOUD ARCHITECTURE<br />27<br />

61.
CLOUD<br /><ul><li> NIST (U.S. National Institute of Standards and Technology) defines cloud computing by describing:

62.
five essential characteristics,

63.
three cloud service models, and

64.
four cloud deployment models.</li></ul>28<br />

65.
CLOUD CHARACTERISTICS<br /><ul><li> Five essential characteristics

66.
On-demand self-service

67.
Broad network access

68.
Resource pooling

69.
Rapid elasticity

70.
Measured service</li></ul>29<br />

71.
CLOUD CHARACTERISTICS<br /><ul><li> On-demand self-service

72.
Unilaterally provision computing capabilities as needed automatically, without requiring human interaction with a service provider.

73.
Computing capabilities include server time and network storage </li></ul>30<br />

74.
CLOUD CHARACTERISTICS<br /><ul><li> Broad network access

75.
Available over the network and accessed through standard mechanisms</li></ul>31<br />

76.
CLOUD CHARACTERISTICS<br /><ul><li> Can be accessed through heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs) as well as other traditional or cloud based software services.</li></ul>32<br />

77.
CLOUD CHARACTERISTICS<br /><ul><li> Resource pooling

78.
The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model,

79.
Different physical and virtual resources dynamically assigned and reassigned according to consumer demand.</li></ul>33<br />

80.
CLOUD CHARACTERISTICS<br /><ul><li> Degree of location independence - customer has no control or knowledge over the exact location of the provided resources

81.
Customer may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). </li></ul>34<br />

82.
CLOUD CHARACTERISTICS<br /><ul><li> Examples of resources include:

83.
storage,

84.
processing,

85.
memory,

86.
network bandwidth, and

87.
virtual machines.</li></ul>35<br />

88.
CLOUD CHARACTERISTICS<br /><ul><li> Rapid elasticity

89.
Capabilities can be

90.
rapidly and elastically provisioned to quickly scale out ; and

91.
rapidly released to quickly scale in.

92.
In some cases this is done automatically.</li></ul>36<br />

93.
CLOUD CHARACTERISTICS<br /><ul><li> Measured service.

94.
Metering capability at some level of abstraction appropriate to the type of service

95.
Resource usage can be monitored, controlled, and reported — providing transparency for both the provider and consumer of the service.</li></ul>37<br />

96.
CLOUD CHARACTERISTICS<br /><ul><li> Example:

97.
storage,

98.
processing,

99.
bandwidth,

100.
active user accounts</li></ul>38<br />

101.
MYTHS - CLOUD CHARACTERISTICS<br /><ul><li> Myths about Cloud Computing Essential Characteristics

102.
Virtualization is mandatory

103.
Answer is No

104.
Cloud services are often but not always utilized in conjunction with, and enabled by, virtualization technologies</li></ul>39<br />

105.
MYTHS - CLOUD CHARACTERISTICS<br /><ul><li> There is no requirement that ties the abstraction of resources to virtualization technologies

106.
In many offerings virtualization by hypervisor or operating system container is not utilized.</li></ul>40<br />

107.
MYTHS - CLOUD CHARACTERISTICS<br /><ul><li>Multi-tenancy as an essential cloud characteristic

108.
Multi-tenancy is not called out as an essential cloud characteristic by NIST but is often discussed as such.</li></ul>41<br />

109.
CLOUD SERVICE MODELS<br /><ul><li> Divided into three archetypal models.

110.
The three fundamental classifications are known as the SPI Model.

111.
Various other derivative combinations are also available.</li></ul>42<br />

112.
CLOUD SERVICE MODELS<br /><ul><li> Cloud Service Models

113.
Cloud Software as a Service (SaaS).

114.
Cloud Platform as a Service (PaaS).

115.
Cloud Infrastructure as a Service (IaaS).</li></ul>43<br />

116.
CLOUD SERVICE MODELS - SaaS<br /><ul><li> The client use the software / applications running on a cloud infrastructure.

117.
Accessed through thin client interface such as a browser.</li></ul>44<br />

118.
CLOUD SERVICE MODELS - SaaS<br /><ul><li> User does not manage or control the underlying cloud infrastructure including:

119.
network,

120.
servers,

121.
operating systems,

122.
storage, or

123.
even individual application capabilities</li></ul>45<br />

124.
CLOUD SERVICE MODELS - SaaS<br /><ul><li> Possible exception - limited user specific application configuration settings.</li></ul>46<br />

125.
CLOUD SERVICE MODELS - PaaS<br /><ul><li> User can deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider.</li></ul>47<br />

126.
CLOUD SERVICE MODELS - PaaS<br /><ul><li> The consumer does not manage or control the underlying cloud infrastructure including

127.
network,

128.
servers,

129.
operating systems, or

130.
storage,</li></ul>48<br />

131.
CLOUD SERVICE MODELS - PaaS<br /><ul><li> Has control over the deployed applications and possibly application hosting environment configurations.</li></ul>49<br />

132.
CLOUD SERVICE MODELS - IaaS<br /><ul><li> The user can provision

133.
processing,

134.
storage,

135.
networks, and

136.
other fundamental computing resources</li></ul>50<br />

137.
CLOUD SERVICE MODELS - IaaS<br /><ul><li> The consumer is able to deploy and run arbitrary software, which can include operating systems and applications.

138.
The consumer does not manage or control the underlying cloud infrastructure</li></ul>51<br />

139.
CLOUD SERVICE MODELS - IaaS<br /><ul><li> Has control over

140.
operating systems,

141.
storage,

142.
deployed applications, and

143.
possibly limited control of select networking components (e.g., host firewalls).</li></ul>52<br />

144.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Regardless of the service model, there are four cloud deployment models:

145.
Public Cloud

146.
Private Cloud

147.
Community Cloud

148.
Hybrid Cloud</li></ul>53<br />

149.
CLOUD DEPLOYMENT MODELS<br /><ul><li> There are derivative variations that address specific requirements.</li></ul>54<br />

150.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Public Cloud

151.
The cloud infrastructure is made available to the general public or a large industry group

152.
Owned by an organization providing cloud services.</li></ul>55<br />

153.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Private Cloud

154.
The cloud infrastructure is operated solely for a single organization.

155.
It may be managed by the organization or a third party, and may exist on-premises or off-premises.</li></ul>56<br />

156.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Community Cloud

157.
The cloud infrastructure is shared by several organizations

158.
Supports a specific community that has shared concerns</li></ul>57<br />

159.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Examples:

160.
mission,

161.
security requirements,

162.
policy, or

163.
compliance considerations</li></ul>58<br />

164.
CLOUD DEPLOYMENT MODELS<br /> It may be managed by the:<br /><ul><li> organizations or

165.
a third party </li></ul>and may exist <br /><ul><li> on-premises or

166.
off-premises.</li></ul>59<br />

167.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Hybrid Cloud

168.
Composition of two or more clouds (private, community, or public)

169.
They remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability </li></ul>60<br />

170.
CLOUD DEPLOYMENT MODELS<br /><ul><li> Example - Hybrid Cloud

171.
Cloud bursting for load-balancing between clouds.</li></ul>61<br />

172.
CLOUD BURSTING<br /><ul><li> New twist on an old concept :)

173.
Bursting into the cloud when necessary, or

174.
using the cloud when additional compute resources are required temporarily</li></ul>62<br />

175.
CLOUD BURSTING<br /><ul><li> Example - used to shoulder the burden of some of the application's processing requirements.

176.
How it is done?

177.
Basic application functionality could be provided from within the cloud</li></ul>63<br />

178.
CLOUD BURSTING<br /><ul><li> More critical (e.g. revenue-generating or mission critical) applications continue to be served from within the controlled enterprise data center.</li></ul>64<br />

179.
CLOUD BURSTING<br /><ul><li> How it is different from the traditional bursting?

180.
Traditionally been applied to resource allocation and automated provisioning / de-provisioning of resources

181.
Historically focused on bandwidth.</li></ul>65<br />

182.
CLOUD BURSTING<br /><ul><li> In the cloud, it is being applied to resources such as:

183.
servers,

184.
application servers,

185.
application delivery systems, and

186.
other infrastructure…</li></ul>66<br />

187.
CLOUD BURSTING<br /><ul><li> …required to provide on-demand computing environments that expand and contract as necessary, without manual intervention.</li></ul>67<br />

188.
CLOUD BURSTING<br /><ul><li> Without manual intervention means?

189.
We generally call it - automation

190.
But is automation sufficient for cloud? or is it the right thing for cloud?</li></ul>68<br />

191.
CLOUD ORCHESTRATION<br /> Orchestration describes the automated<br /><ul><li> arrangement,

192.
coordination, and

193.
management of </li></ul>complex computer systems, middleware, and services.<br />69<br />

194.
CLOUD ORCHESTRATION<br /><ul><li> Generally used in the context of:

195.
Service Oriented Architecture,

196.
virtualization,

197.
provisioning, and

198.
dynamic datacenter topics.</li></ul>70<br />

199.
DERIVATIVE - DEPLOYMENT MODELS<br /><ul><li> Derivative cloud deployment models are emerging due to the maturation of market offerings and customer demand.

200.
Example

201.
Virtual Private Clouds</li></ul>71<br />

202.
VIRTUAL PRIVATE CLOUDS<br /><ul><li> Public cloud infrastructure in a private or semi-private manner

203.
By interconnecting these resources to the internal resources of a consumers’ datacenter, usually via virtual private network (VPN) connectivity.</li></ul>72<br />

204.
CLOUD SERVICE BROKERS<br /><ul><li> Providers that offer intermediation, monitoring, transformation/portability, governance, provisioning, and integration services.

205.
They also negotiate relationships between various cloud providers and consumers.</li></ul>73<br />

206.
CLOUD SERVICE BROKERS<br /><ul><li> They take advantage of the incompatibility issues prevailing and provide an interface for customers.

207.
Acts as proxy (middle man)</li></ul>74<br />

208.
OPEN AND PROPRIETARY API<br /><ul><li> Open and proprietary APIs are evolving which seek to enable things such as

209.
management,

210.
security and

211.
inter-operatibility</li></ul>for cloud.<br />75<br />

212.
OPEN AND PROPRIETARY API<br /><ul><li> Open Cloud Computing Interface Working Group,

213.
Amazon EC2 API,

214.
VMware’s DMTF-submitted vCloud API,

215.
Sun’s Open Cloud API,

216.
Rackspace API, and

217.
GoGrid’s API,</li></ul>76<br />

218.
OPEN AND PROPRIETARY API<br /><ul><li> Play a key role in cloud portability and interoperability as well as common container formats such as the DMTF’s Open Virtualization Format (OVF).

219.
DMTF - Distributed Management Task Force </li></ul>77<br />

220.
MULTI-TENANCY IN CLOUD<br /><ul><li> Not an essential characteristic of Cloud Computing in NIST’s model.

221.
Generally identified as an important element of cloud.</li></ul>78<br />

222.
MULTI-TENANCY IN CLOUD<br /><ul><li> Implies a need for

223.
policy-driven enforcement,

224.
segmentation,

225.
isolation,

226.
governance,

227.
service levels, and

228.
chargeback/billing models for different consumers. </li></ul>79<br />

229.
CLOUD<br />80<br />

230.
CLOUD CUBE<br />81<br />

231.
CLOUD REFERENCE MODEL<br />82<br /><ul><li> Understanding the relationships and dependencies between Cloud Computing models is critical to understanding Cloud Computing security risks.</li></li></ul><li>CLOUD REF MODEL<br />83<br /><ul><li>IaaS is the foundation of all cloud services, with PaaS building upon IaaS, and SaaS in turn building upon PaaS

232.
As the capabilities are inherited, so are information security issues and risk.</li></li></ul><li>CLOUD REF MODEL<br />84<br />

233.
CLOUD SECURITY<br />85<br />

234.
CLOUD – WHAT COULD BE TARGETTED?<br /><ul><li> From an attackers point of view:

235.
The boxes,

236.
Storage,

237.
Applications</li></ul>86<br />

238.
WHY CLOUD SECURITY IS DIFFERENT?<br /><ul><li> With any new technology comes new risks

239.
New vectors - that we need to be aware of

240.
Confusion exists - how cloud is both similar to and different from existing models of computing</li></ul>87<br />

241.
SECURITY ISSUES<br /><ul><li> Cloud based security issues, also commonly know as Cloud Based Risk – CRISK</li></ul>88<br />

242.
SECURITY ISSUES<br />Lock-in<br /><ul><li> When a cloud user decides to migrate (due to various reasons including poor SLA) to another cloud service provider or to in-house IT

243.
Different cloud service providers use different API – not compatable with each other for migrating the data </li></ul>89<br />

244.
SECURITY ISSUES<br />Lack of:<br /><ul><li> Tools,

245.
Procedures,

246.
Standard data formats, and

247.
Interfaces,</li></ul>can considerably delay or prevent a successful migration.<br />90<br />

248.
SECURITY ISSUES<br />Shared Service Consequences<br /><ul><li> Any kind of intentional and un-intentional malicious activity carried out or executed on a shared platform may affect the other tenants and associated stake holders.</li></ul>91<br />

249.
SECURITY ISSUES<br />Examples - Shared Service Consequences:<br /><ul><li>Blocking of IP ranges

250.
Confiscation of resources as part of an investigation - the availability is in question.</li></ul>92<br />

251.
SECURITY ISSUES<br />Examples - Shared Service Consequences: <br /><ul><li> The diversity of application running on the cloud platform and a sudden increase in the resource usage by one application can drastically affect the performance and availability of other applications shared in the same cloud infrastructure.</li></ul>93<br />

252.
SECURITY ISSUES<br />Sudden Acquisitions and Take-overs<br /><ul><li> Cloud is upcoming and promising domain for organizations to venture and expand.

253.
Sudden take over can result in a deviation from the agreed Terms of Use & SLA which may also lead to a Lock-In situation.</li></ul>94<br />

254.
SECURITY ISSUES<br />Run-on-the-cloud<br /><ul><li> Similar to the conventional run on the bank concept.

255.
Bankruptcy and catastrophes does not come with an early warning.</li></ul>95<br />

256.
SECURITY ISSUES<br /><ul><li> What happens if the majority clients withdraw the associated services from a cloud infrastructure?</li></ul>96<br />

257.
SECURITY ISSUES<br /><ul><li> The cloud service providers may try to prevent that move through direct and indirect methods – which may include a lock-in also.</li></ul>97<br />

258.
SECURITY ISSUES<br />Maintaining Certifications & Compliance<br /><ul><li> Organizations need to ensure that they can maintain the same when moving to cloud.

259.
ToU prohibits VA/PT

260.
This may introduce security vulnerabilities and gaps

261.
Result – Loose your certification.</li></ul>98<br />

262.
SECURITY ISSUES<br />Example - Maintaining Certifications:<br /><ul><li> In general scenario, the PCI DSS compliance cannot be achieved with the Amazon EC2/S3 cloud service.

263.
Major downfall in performance and quality metrics may affect your certifications.</li></ul>99<br />

264.
SECURITY ISSUES<br />Technical and Procedural Vulnerability<br /><ul><li> Vulnerabilities applicable to the conventional systems & networks are also applicable to cloud infrastructure.

265.
Lack of could based security standards and non-adherence to procedures may affect the CIA of customer data. </li></ul>100<br />

266.
SECURITY ISSUES<br />Confidentiality is @ Risk<br /><ul><li> The information deleted by the customer may be available to the cloud solution provider as part of their regular backups.

267.
Insecure and inefficient deletion of data where true data wiping is not happening, exposing the sensitive information to other cloud users.</li></ul>101<br />

268.
SECURITY ISSUES<br />Lack of transparency in cloud<br /><ul><li>The service provider may be following good security procedures, but it is not visible to the customers and end users.

269.
May be due to security reasons.

270.
But end user is finally in the dark.</li></ul>102<br />

271.
SECURITY ISSUES<br />Lack of transparency in cloud<br /><ul><li> End user questions remains un-answered:

272.
how the data is backed up,

273.
who back up the data,

274.
whether the cloud service provider does it or has they outsourced to some third party, </li></ul>103<br />

275.
SECURITY ISSUES<br /><ul><li> how the backup is transferred to a remote site as part of the backup policy,

276.
is it encrypted and send,

277.
is the backup properly destroyed after the specified retention period or</li></ul>104<br />

278.
SECURITY ISSUES<br /><ul><li> is it lying somewhere in the disk,

279.
what kind of data wiping technologies are used.

280.
The lists of questions are big and the cloud users are in dark</li></ul>105<br />

281.
SECURITY TESTING<br /><ul><li> Problems testing the cloud?

282.
Permission

283.
How do you get permission to test your application running on Amazon EC2 when the results of your testing could show you data from another client completely?</li></ul>106<br />

284.
SECURITY TESTING<br /><ul><li> Getting black hole or getting kicked-off

285.
"In networking, black holes refer to places in the network where incoming traffic is silently discarded (or "dropped"), without informing the source that the data did not reach its intended recipient." - From Wikipedia</li></ul>107<br />

286.
SECURITY TESTING<br /><ul><li> How do you track version?

287.
How do you do regression testing?

288.
How do you know what version of the search engine google is currently running on?</li></ul>108<br />

289.
SECURITY TESTING<br /><ul><li> If you test an application today and find it vulnerable or not vulnerable, how do you know that the app you testing tomorrow is the same one that you tested yesterday? - You don't</li></ul>109<br />

290.
Then why we move?<br /> If its not good, safe or not even new, then why cloud adoption happening?<br />110<br />

291.
FEW TOP REASONS<br /><ul><li> Management by in-flight magazines

292.
Management version – something new and promising – let’s try it out

293.
Geek version – It’s really cool

294.
There is nobody to put a break when these two people join together.</li></ul>111<br />

295.
Other reasons<br /><ul><li> Poor uptime and service delivery experience from IT department.

296.
Economical factors

297.
Multi-tenancy means cost sharing</li></ul>112<br />

298.
Other reasons<br /><ul><li> Cost saving makes it attractive during recession.

299.
Cloud computing allows you to move from CAPEX to OPEX.

300.
Save 30% of IT Operational Cost</li></ul>113<br />

301.
Other reasons<br /><ul><li> Variable cost subscription model – rapidly scale up and scale down.

302.
Go Green or Green IT also influenced many.

303.
Powerful - A 64 node Linux cluster can be online in just five minutes - forget about those sleepless nights in your data centers</li></ul>114<br />

304.
ADDRESSING SECURITY ISSUES IN CLOUD – RISK ASSESSMENT FRAMEWORK FOR CLOUD<br />115<br />

305.
ADDRESSING CLOUD SECURITY<br /><ul><li>Adopt a risk based approach

306.
Evaluate your tolerance for moving an asset to cloud

307.
Have a framework to evaluate cloud risks.</li></ul>116<br />

308.
RA FRAMEWORK FOR CLOUD<br /><ul><li> Identify the asset for cloud.

309.
Evaluate the asset

310.
Map the asset to cloud deployment models

311.
Evaluate cloud service models & providers

312.
Sketch the potential data flow</li></ul>117<br />

313.
1 - IDENTIFY THE ASSET<br /><ul><li> Two types of assets are supported by cloud:

314.
Data

315.
Applications/Functions/Processes

316.
Either partial functions or full applications</li></ul>118<br />

317.
1 - IDENTIFY THE ASSET<br /><ul><li> In cloud, we do not need data and application to reside at the same location.

318.
We can shift parts of functions to the cloud.</li></ul>119<br />

319.
1 - IDENTIFY THE ASSET<br /><ul><li> Example:

320.
Host the main application and data in our own data-centre.

321.
Outsource a portion of its functionality to the cloud through Platform as a Service (PaaS).</li></ul>120<br />

322.
1 - IDENTIFY THE ASSET<br /><ul><li>First step in evaluating risk for the cloud - determine exactly what data or function is being considered for the cloud.

323.
Include potential use of the asset once it moves to the cloud</li></ul>121<br />

324.
1 - IDENTIFY THE ASSET<br /><ul><li> This will help you account for scope creep

325.
Data and transaction volumes are often higher than expected.</li></ul>122<br />

326.
1 - IDENTIFY THE ASSET<br /><ul><li> What is scope creep?

327.
Also known as

328.
focus creep,

329.
requirement creep,

330.
feature creep,

331.
function creep</li></ul>123<br />

332.
1 - IDENTIFY THE ASSET<br /><ul><li> Refers to uncontrolled changes in a project's scope.

333.
Can occur when the scope of a project is not properly defined, documented, or controlled.</li></ul>124<br />

334.
2 - EVALUATE THE ASSET<br /><ul><li> Determine how important the data or function is to the organization.

335.
A detailed valuation is recommended only if the organization has an existing process for that. </li></ul>125<br />

336.
2 - EVALUATE THE ASSET<br /><ul><li> If not, a rough assessment of the following is recommended:

337.
how sensitive an asset is, and

338.
how important an application / function / process is.</li></ul>126<br />

339.
2 - EVALUATE THE ASSET<br /><ul><li> How do we do it?

340.
For each asset, ask the following questions:

341.
How would we be harmed if the asset became widely public and widely distributed?</li></ul>127<br />

342.
2 - EVALUATE THE ASSET<br /><ul><li> How would we be harmed if an employee of our cloud provider accessed the asset?

343.
How would we be harmed if the process or function were manipulated by an outsider?</li></ul>128<br />

344.
2 - EVALUATE THE ASSET<br /><ul><li> How would we be harmed if the process or function failed to provide expected results?

345.
How would we be harmed if the information/data were unexpectedly changed?</li></ul>129<br />

346.
2 - EVALUATE THE ASSET<br /><ul><li> How would we be harmed if the asset were unavailable for a period of time?</li></ul>130<br />

347.
2 - EVALUATE THE ASSET<br /><ul><li> What are we doing basically with the above process?

348.
Assessing confidentiality, integrity, and availability requirements for the asset; and

349.
how those are affected if all or part of the asset is handled in the cloud.</li></ul>131<br />

350.
3 – MAP THE ASSETS<br /><ul><li> Step 3 - Map the asset to potential cloud deployment models

351.
Determine which deployment model is good for the organizational requirement.</li></ul>132<br />

352.
3 – MAP THE ASSETS<br /><ul><li> Decide whether the organization can accept the risks implicit to the various deployment models (private, public, community, or hybrid); and hosting scenarios (internal, external, or combined).</li></ul>133<br />

353.
3 – MAP THE ASSETS<br /><ul><li> For the asset, determine if you are willing to accept the following options:

354.
Public.

355.
Private, internal/on-premises.

356.
Private, external (including dedicated or shared infrastructure).

357.
Community

358.
Hybrid</li></ul>134<br />

359.
3 – MAP THE ASSETS<br /><ul><li> End of this phase you should have answer to the following:

360.
Deployment models and locations that fits your security and risk requirements.</li></ul>135<br />

361.
4 – EVALUATE MODELS & PROVIDERS<br /><ul><li> Focus on the degree of control you’ll have at each SPI tier to implement any required risk management.</li></ul>136<br />

362.
5 – SKETCH DATA FLOW<br /><ul><li> Map out the data flow between:

363.
your organization,

364.
the cloud service, and

365.
any customers/other nodes.</li></ul>137<br />

366.
5 – SKETCH DATA FLOW<br /><ul><li> High-level design can be adopted for the same.

367.
Absolutely essential to understand whether, and how, data can move in and out of the cloud before finalizing.</li></ul>138<br />

368.
RA - CONCLUSION<br /><ul><li> You should have a clear understanding of the following:

369.
the importance of what you are considering moving to the cloud,

370.
risk tolerance,</li></ul>139<br />

371.
RA - CONCLUSION<br /><ul><li> which combinations of deployment and service models are acceptable, and

372.
potential exposure points for sensitive information and operations.</li></ul>140<br />

373.
RA - CONCLUSION<br /><ul><li> For low-value assets you don’t need the same level of security controls

374.
Can skip most of the recommendations — such as on-site inspections, discoverability, and complex encryption schemes.

375.
A high-value regulated asset might entail audit and data retention requirements.</li></ul>141<br />

376.
EXPLOITING CLOUD for iw / attacks<br />142<br />

377.
DO YOU KNOW THIS?<br />143<br />

378.
INFORMATION WARFARE<br /><ul><li> Clue:

379.
Kendo (kumdo in korean)</li></ul>144<br />

380.
INFORMATION WARFARE<br />風 - Swift as the wind<br />林 - Quiet as the forest<br />火 - Conquer like the fire<br />山 - Steady as the mountain<br />145<br />

381.
INFORMATION WARFARE<br /><ul><li>Battle strategy and motto of Japanese feudal lord Takeda Shingen( 武田信玄 )(1521–1573 A.D.).

382.
Twenty-Four Generals - famous groupings of battle commanders

383.
(Takeda Nijūshi-shō )武田二十四将</li></ul>146<br />

384.
INFORMATION WARFARE<br /><ul><li> Came from the Art of War by Chinese strategist and tactician Sun Tzu (Sunzi)

385.
A sort of abbreviation to remind officers and troops how to conduct battle</li></ul>147<br />

386.
INFORMATION WARFARE<br /><ul><li> This is what we need in information warfare or when launching an attack</li></ul>148<br />

387.
EXPLOITING CLOUD<br /><ul><li> Sample Task

388.
Break PGP passphrases

389.
Solution

390.
Brute forcing PGP passphrases</li></ul>149<br />

391.
EXPLOITING CLOUD<br /><ul><li>Try – ElcomSoft Distributed Password Recovery (with some patches to handle PGP ZIP)

392.
Two elements - EDPR Managers & EDPR Agents</li></ul>150<br />

393.
EXPLOITING CLOUD<br /><ul><li> Dual core Win7 box - 2100 days for a complex passphrase.

394.
Not acceptable – too long

395.
Lets exploit the cloud.</li></ul>151<br />

396.
EXPLOITING CLOUD<br /><ul><li> First things first – Create an Account on Amazon. Credit Card Required 

397.
Install Amazon EC2 API Tools on your linux box.</li></ul>sudo apt-get install ec2-api-tools<br />152<br />

398.
EXPLOITING CLOUD<br /><ul><li> Select an AMI

399.
Example - use a 32 bit Windows AMI - ami-df20c3b6-g</li></ul>153<br />

400.
EXPLOITING CLOUD<br /><ul><li> Start an instance from the Linux shell as follows:</li></ul>ec2-run-instances -k ssh-keypair ami-df20c3b6-g default<br />154<br />

401.
EXPLOITING CLOUD<br /><ul><li> Enumerate the instance ID & public IP:</li></ul>ec2-describe-instances<br />155<br />

402.
EXPLOITING CLOUD<br /><ul><li> Instance status change from “pending” to “running”

403.
Extract the admin password for the instance</li></ul>ec2-get-password -k ssh-keypair.pem $instanceID<br />156<br />

404.
EXPLOITING CLOUD<br /><ul><li> Configure EC2 firewall to permit inbound RDP traffic to the instance.</li></ul>ec2-authorize default -p 3389 -s $trusted_ip_address/32<br />157<br />

405.
EXPLOITING CLOUD<br /><ul><li> Configure the firewall in front of the EDPR manager system to permit TCP/12121 from anywhere.

406.
RDP into the instance & configure EDPR</li></ul>158<br />

407.
EXPLOITING CLOUD<br /><ul><li> Login using the password obtained from ec2-get-password command</li></ul>159<br />

408.
EXPLOITING CLOUD<br /><ul><li> Install EDPR Agent,

409.
Configure the Agent to connect to the Manager.

410.
3 points to configure mainly</li></ul>160<br />

411.
EXPLOITING CLOUD<br /><ul><li> Configure the public IP address or hostname of the EDPR manager you have configured.</li></ul>161<br />

412.
EXPLOITING CLOUD<br /><ul><li>Interface tab - Set the Start-up Mode to "At Windows Start-up".</li></ul>162<br />

413.
EXPLOITING CLOUD<br /><ul><li> Registry hack

414.
EDPR creates a pair of registry values which are used to uniquely identify the agent when connecting to the manager.

415.
We need to scrub these values – why?</li></ul>163<br />

416.
EXPLOITING CLOUD<br /><ul><li> If we don’t, every single instance we initiate will appear to be the same agent to the manager.

417.
Output = The job handling will be totally corrupted.</li></ul>164<br />

418.
EXPLOITING CLOUD<br />HKEY_LOCAL_MACHINEoftwarelcomSoftistributed AgentID<br /><ul><li> Set the value of the UID key to null, but DO NOT DELETE THE KEY.</li></ul>165<br />

419.
EXPLOITING CLOUD<br /><ul><li> Let’s bundle the EC2 instance.

420.
Remember in cloud, bundle is similar to creating a ‘template’ in VMware terminology.</li></ul>166<br />

421.
EXPLOITING CLOUD<br /><ul><li> Install and configure EC2 AMI Tools

422.
Command:</li></ul>ec2-bundle-instance $instance_id -b $bucket_name -p $bundle_name -o $access_key_id -w $secret_access_key<br />167<br />

423.
EXPLOITING CLOUD<br /><ul><li> Bundling process runs sysprep on the Windows instance, compress and copies the instance to S3.</li></ul>168<br />

424.
EXPLOITING CLOUD<br /><ul><li> Check the progress of the bundle task:</li></ul>ec2-describe-bundle-tasks<br />169<br />

425.
EXPLOITING CLOUD<br /><ul><li> Register the bundled AMI:</li></ul>ec2-register $bucket_name/$bundle_name.manifest.xml<br />170<br />

426.
EXPLOITING CLOUD<br /><ul><li> The register command returns AMI ID

427.
Used to spawn instances of the EDPR agent. Example:</li></ul>IMAGE ami-54f3103d<br />171<br />

428.
ACTION TIME <br /><ul><li>Start EDPR manager & configure task.

429.
to brute an password composed of uppercase letters, lowercase letters, and the numbers 0-9, with a length of between 1 to 8 characters against a PGP ZIP file.</li></ul>172<br />

430.
ACTION TIME <br />173<br />

431.
ACTION TIME <br /><ul><li> Start a single instance of our EDPR agent:</li></ul>ec2-run-instances -k $ssh-keypair ami-54f3103d -g default<br />174<br />

432.
ACTION TIME <br /><ul><li> Agent check in with the EDPR manager.</li></ul>175<br />

433.
ACTION TIME <br /><ul><li> We started it with default parameters

434.
EC2 “small” instance

435.
Trying 500K keys per second

436.
How long will it take?</li></ul>176<br />

437.
ACTION TIME <br /><ul><li>Whattt???? 3600 days? = 10 years!!!!!</li></ul>177<br />

438.
ACTION TIME <br /><ul><li> Let’s scale up – deploy 10 additional instances:</li></ul>ec2-run-instances -n 10 -k ssh-keypair ami-54f3103d -g default -t c1.medium<br />178<br />

439.
ACTION TIME <br /><ul><li> The -n 10 parameter tells EC2 to launch 10 instances.

440.
c1.medium instance = “High CPU" instance</li></ul>179<br />

441.
ACTION TIME <br />180<br />

442.
ACTION TIME <br /><ul><li> Now we have more cracking agents in the party!!!

443.
2+M keys/second

444.
So what's the time required now???</li></ul>181<br />

445.
ACTION TIME <br /><ul><li> Down to 122 days</li></ul>182<br />

446.
ACTION TIME <br /><ul><li> Kickoff another 89 to hit a century.</li></ul>ec2-run-instances -n 89 -k ssh-keypair ami-54f3103d -g default -t c1.medium<br />Note: Check your EDPR License.<br />183<br />

447.
ACTION TIME <br /><ul><li> Error:</li></ul>Client.InstanceLimitExceeded: Your quota allows for 9 more instance(s). You requested at least 89<br />184<br />

448.
ACTION TIME <br /><ul><li> Option 1

449.
Request to instance amazon EC2 Instance Limit - http://aws.amazon.com/contact-us/ec2-request/</li></ul>185<br />

450.
ACTION TIME <br /><ul><li> Option 2

451.
Amazon spot instances - allows us to bid on unused Amazon EC2 capacity and run those instances.</li></ul>186<br />

452.
ACTION TIME <br /><ul><li> Option 3

453.
Create custom python script to bypass this limitation</li></ul>187<br />

454.
ACTION TIME <br /><ul><li> With a couple more of instances, we can reduce it to hours

455.
A successful cloud based distributed cracking system.</li></ul>188<br />

456.
CLOUD FORENSICS<br />189<br />

457.
CLOUD FORENSICS<br /><ul><li> Mixed Responses

458.
Bad guys have started using cloud based services and infrastructure for launching attacks

459.
Cloud do provide a good platform for incidence response and forensics investigations</li></ul>190<br />

460.
CLOUD FORENSICS<br /><ul><li> By utilizing the inherent features of cloud computing, computer forensic can become an on-demand service under certain circumstances.</li></ul>191<br />

461.
CLOUD FORENSICS<br /><ul><li> Regular business and operations are not affected when a cloud environment needs to be forensically examined.

462.
Not the case with the traditional infrastructure where the equipments are seized.

463.
Cloud Example – Amazon EBS</li></ul>192<br />

464.
CLOUD FORENSICS<br /><ul><li> Cloud based forensics took a new turn when Amazon introduced Elastic Block Store (EBS) volumes

465.
Enables the user to launch an instance with an Amazon EBS volume that will serve as the root device.</li></ul>193<br />

466.
CLOUD FORENSICS<br /><ul><li> When there is a need to preserve a cloud environment, EBS can create an exact replica of the cloud instance & put it on the same cloud for forensics evaluation and examination.

467.
Since the forensic investigators will be working with another instance of the environment, the regular operations is not affected in any way.</li></ul>194<br />

468.
CLOUD FORENSICS<br /><ul><li> Replication process achieved in few minutes.

469.
Forensic evidences are invalid if they are not cryptographically hashed.

470.
This can be easily achieved using the on-demand feature of cloud.</li></ul>195<br />

471.
CLOUD FORENSICS<br /><ul><li> Replication process achieved in few minutes.

472.
Forensic evidences are invalid if they are not cryptographically hashed.

473.
This can be easily achieved using the on-demand feature of cloud.</li></ul>196<br />

474.
CLOUD FORENSICS<br /><ul><li>The cloud based hashing takes less time and is much faster when you compare it with the traditional cryptographic hashing process.

475.
Amazon Web Services is already providing a good forensic feature where it can provide a MD5 hash of every file that is on the cloud system.</li></ul>197<br />

476.
CLOUD FORENSICS<br /><ul><li> What this practically means is that when a bit by bit copy is initiated (forensic duplication), you have systems in place which can ensure that you made the exact replica and not even a bit has changed during the replication and copying process.</li></ul>198<br />

477.
CLOUD FORENSICS<br /><ul><li> Even though you have all the above services available, cloud forensics is still challenging.

478.
Virtualization of various entities like the applications and host systems, which once used to be in-house is now scattered on the cloud.</li></ul>199<br />

479.
CLOUD FORENSICS<br /><ul><li> Makes evidence gathering a challenging task

480.
Since we are acquiring data from a virtual environment, the forensic investigator should have a clear and precise understanding of how they work and what files are interesting and required to acquire.</li></ul>200<br />

481.
CLOUD FORENSICS<br /><ul><li> Near to impossible to acquire the complete hard disk due to various reasons including but not limited to:

482.
multiple data owners on the same disk,

483.
remote geographical location,

484.
jurisdictional difficulties,

485.
RAID configurations etc</li></ul>201<br />

486.
And finally<br /><ul><li> Questions also arise on the compatibility and reliability of the tools used for investigating cloud forensics - because most of the tools are meant for real time systems and not for virtualized environments.

487.
A collaborative and collective effort is required to address what we discussed.</li></ul>202<br />

488.
conclusion<br />203<br />

489.
CONCLUSION<br /><ul><li> The architectural mindset used when designing solutions has clear implications on the:

490.
future flexibility,

491.
security,

492.
collaborative capabilities, and

493.
mobility</li></ul>of the resultant solution.<br />204<br />

494.
CONCLUSION<br /><ul><li> With so many different cloud deployment and service models, and their hybrid permutations — no list of security controls can cover all these circumstances.</li></ul>205<br />

495.
GOOD SECURITY PROFESSIONAL<br />A good security professional is someone who always looks both ways before crossing a one-way street.<br />206<br />

496.
207<br />QUESTIONS??<br />Manu Zacharia<br />m@matriux.com<br />or<br />m@HackIT.co<br />or<br />

497.
thank you !<br />