Skip to main content

Cloud Computing will be all about GRC!

3. Data Regulations: Each jurisdiction around the world has slightly different approaches to the regulation of data privacy and the Australian Law Reform Commission has recently released a report suggesting significant strengthening of Australia's data privacy regime. Therefore it is important that customers understand where their data will ultimately be stored and by whom so that they can ensure compliance with Australian privacy and also record retention regulations.

Many SaaS providers work on the basis of centralised infrastructure that is not based in Australia. The customer must ensure that contractually the provider is bound to comply with Australian privacy laws before allowing the data to be exported. The issue is further compounded if the SaaS provider then uses a third party to do the storage of the data.

Such is the complexity that EMC announced recently that it is having difficulty choosing a location to build the data centres to run its storage-as-a-service offering because of differing privacy laws across the world.

4. Data Security: The customer needs to get comfortable with the level of security provided by the SaaS provider and the process in the event of data leakage.

Further, laws in other countries can allow the governments and intelligence agencies of those countries access to the customer's data. For example the US Patriot Act requires US companies to hand over all customer data held by that US company upon request by the relevant US agency.

5. Liability: Generally speaking the providers of free SaaS applications do not accept any liability for any errors in or losses caused by the service. It is important to review the terms and conditions carefully on this point. In the case of paid services, the providers generally will accept some degree of liability. Sometimes this is limited to credits which can be applied against future fees due.



Source

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op