Australian Data Centre Strategy Summit 2015

Screenshot 2015-03-16 19.32.29

Last week I was fortunate to attend the Australian Data Centre Strategy Summit that was located on the Gold Coast – a very nice location for a very serious conference! The conference focus was about, yes, you guessed it, Data Centres, and the decisions businesses are making when it comes to hosting their infrastructure in the ‘cloud’. The reality of any ‘cloud’ service is that these are bricks and mortar data centres, located in physical locations both in Australia and overseas. For an organisation, you are making decisions to have infrastructure hosted elsewhere and your employees/students will be pulling data down from these data centres to your physical location. Think Google Apps for Education. Similar concept, but that is software as a service (SAAS) whereas infrastructure hosted in a data centre is infrastructure as a service (IAAS).

I do feel a need to point out that I was one of five female attendees (I was counting, and it wasn’t difficult to spot the women in the room). C’mon girls – we need your presence at IT conferences, and as participants rather than as organisers of the event. There were quite a few pretty young things handing out materials, but I did almost cheer when I saw Australia Post’s general manager for service integration and operations Claire Bourke enter the room. She delivered a presentation about Australia Post’s switch to active-active data centres using the Melbourne Next DC facility and Fujitsu’s Noble Park facility. If you’re interested, you can read about their motivation for this transition here. 

There were only two schools present. Toorak College, and St. Luke’s Anglican School in Bundaberg, ably represented by Mitch Miller, their IT Manager who has done some groundbreaking work in his school to move infrastructure to Amazon Web Services. The school’s approach has been the subject of an Amazon Web Services case study and I’d encourage IT Managers in schools to take a read.

You can access my Storify of all of my tweets from the conference here. 

Some highlights for me (other than Mitch’s presentation, which was specific to school environments, but more than applicable to business operations too).

Mark Thiele’s presentation about the impact of the Internet of Things on the Data Centre. Mark made some really salient points about the need to seek out talent for IT in your organisation to enable innovation to flourish. His article about Innovation vs Cost Center in relation to IT is a must read for anyone heading up IT, as is another written by Mark exploring the ‘IT Hero and Firefighter Mentality‘ that can pervade organisations. Really worthwhile reads that give you much to contemplate and work with.

Chris Taylor, CTO at Qantas, delivered a fantastic presentation that I wasn’t permitted to tweet. However, their cloud strategy has been explored in an IT News article that is well worth reading. I did take notes, and I think there are aspects of it that I can share as a lot of it is spelled out in the IT News article. Chris stated, “Cloud is the best thing to happen to IT systems”.  Some great points he made regarding a shift to utilising the benefits of the computational processing power of cloud services were:

Innovation and agility

Simplification

Speed to value and business outcomes

Cultural transformation

Speed is life – to get speed you need to take complexity out

Respect your customers – they want better service

Fail fast. Cloud allows you to do this

Test – learn -pivot – redo

Glenn Gore is Senior Manager, Technology Solutions at Amazon Web Services and he ran a workshop outlining AWS and their security, something I was keen to explore. This was very interesting, especially considering this was an ‘I am the only woman in this room’ session, and the fact that Glenn asked participants to say who they were and why they were there. I was ever so slightly intimidated as I realised I was surrounded by CIOs from major corporations and Government agencies, and I had to say that I was from an Independent Girl’s School in Victoria! Nonetheless, I was not deterred and asked quite a few questions. Some key takeaways from Glenn’s session (for me, anyway):

There is cooperation between tier one telcos to try and combat attacks that are becoming more frequent.

People are moving to encryption of data when it rests in data centres (and as it travels there). Key management becomes critical – rolling keys updating every hour etc to secure the management layer you are responsible for when storing in what is considered the ‘public cloud’.

AWS will encrypt on a vendor’s behalf if you want that.

Businesses/corporations should be using 2 factor authentication to secure data.

AWS use real time security frameworks – they use algorithms that flag when patterns of activity change allowing them to identify suspicious activity. They often flag sites and check with owners of data to see if there may be reasons for changes in activity level.

AWS have a shared responsibility model – AWS manages infrastructure. Hacks are happening at apps level. No attacks coming through infrastructure level. Here’s some info from their security page:

Because you’re building systems on top of the AWS cloud infrastructure, the security responsibilities will be shared: AWS has secured the underlying infrastructure and you must secure anything you put on the infrastructure or connect to the infrastructure. The amount of security configuration work you have to do varies depending on how sensitive your data is and which services you select.

 

AWS does not publicly display roadmaps and dates -this is part of their security profile. They don’t care about delays to their roadmap because security is the main priority.

AWS security engineering team- develop their own patents to deal with protecting their infrastructure

Duty of care – will note suspicious traffic vectors and send out calls to check.

AWS will Scan for open ports.

You as the user of the system, have to protect your encryption keys and access to systems – don’t lose sight of this.

AWS are the first cloud provider to meet IRAP in Australia. Now this impressed me. Here’s what that means:

Amazon Web Services was audited by an independent assessor from the Information Security Registered Assessors Program (IRAP). The assessment examined the security controls of Amazon’s people, process and technology to ensure that they met the needs of the Australian Signals Directorate (ASD)Information Security Manual (ISM).

One of my questions to Glenn was, “Who do you see as your closest competitor”, because, quite frankly, after all of my reading I can’t see anyone who gets close to what AWS can do in terms of understanding data centre cloud storage and the security necessary to run it. Here’s where they sit in Gartner’s magic quadrant:

Screenshot 2015-03-16 22.48.53

Glenn’s answer: he sees their competitors as the people thinking they can build their own data centres and protect it adequately. I think he was referring to people with the mindset that is fearful of the ‘public cloud’ who have limited understanding of the security offerings a company like AWS can provide. (If anyone reads this who was in the room and who thinks I misinterpreted this, feel free to correct me).

All in all, a really worthwhile event for a woman from an Independent School in Melbourne to attend. 😉

Here’s a few links to information regarding security and AWS for those of you interested in reading a bit more.

http://www.asd.gov.au/infosec/irap/irap_assessments.htm

http://aws.amazon.com/compliance/aws-irap-information-security-registered-assessors-program-australia/

http://d0.awsstatic.com/whitepapers/compliance/AWS_Australian_Signals_Directorate_Cloud_Computing_Security_Considerations_Oct14.pdf

http://d0.awsstatic.com/whitepapers/compliance/Using_AWS_in_the_context_of_Australian_Privacy_Considerations.pdf

http://aws.amazon.com/compliance/

 

 

Moving to the Cloud? What should you consider?

This year our school has adopted Google Apps for Education. Sounds simple, huh?

Not so. Decisions to move your staff and students into Cloud Computing solutions are complex and in my view, require thoughtful planning and consideration. When I became Director of ICT and eLearning at the start of 2013, my first job was to implement a new Learning Management System. That was pretty big and was the main focus for much of 2013, but the early stages of that project coincided with planning starting around the possibility of a move into the Google Apps space.

Why Google Apps? Plenty of reasons, but here are just a few.

The collaborative nature of the docs – the way students can work together and co-create. The visibility of works in progress when shared with teachers. The ability to provide feedback and formative assessment easily at point of need, when students are in the process of writing. The cloud storage provided to users – 30GB for each user when you’re a Google Apps for Education school. Providing staff with a cloud storage option that sits within your domain, instead of having staff opening their own cloud storage accounts eg: Dropbox, and sharing school docs outside of a school domain. I’ll elaborate further on my reasoning in another post (and I promise I’ll get to it!!).

But before any decisions could be made, I needed to familiarise myself with issues surrounding Cloud Computing so that I could evaluate whether or not a move in this direction was right for my school. What did this involve? Reading, and plenty of it. I looked at Gartner and Forrester research and followed links shared on Twitter to business blogs like Harvard Business Review and Forbes. I needed to see where business was heading and explore speculation about the future of work and what might be required. I read countless articles about cloud storage and privacy concerns. And through all this, I was linking what I was reading to the education system and analysing how what applies in business translates to school environments.

Coming across Data Sovereignty and the Cloud: A Board and Executive Officer’s Guide , published by the Cyberspace Law and Policy Centre, UNSW Faculty of Law was fortuitous. The report was sponsored by  NEXTDCBaker & McKenzie and Aon. NEXTDC is a data centre company, looking to become the biggest cloud data centre storage service in Australia. I have visited their Port Melbourne location, taking a tour through what is an impressive facility. Baker and McKenzie are a law firm and Aon is a global provider of risk management services. When you look at recent changes to Australian Privacy Laws you can see why organisations like this are interested in supporting research and policy reports of this nature. Australian Privacy Principle 8 deals with cross border disclosure of personal information – an area affecting schools and businesses if you use a cloud computing solution where the data is stored in overseas data centres.

The report raised many questions for me, and led to a 90 minute phone conversation with David Vaile, one of the authors of the report. Even at the end of that, I was no closer to firm resolve around the issues surrounding cloud computing and privacy. Within the report is reference to the Australian Signals Directorate’s (Defence Force) Cloud Computing considerations. Their discussion paper provides the following:

“…assists agencies to perform a risk assessment and make an informed decision as to whether cloud computing is currently suitable to meet their business goals with an acceptable level of risk.”

Contained within it is an overview of Cloud Computing considerations you can apply to whatever platform you are looking at implementing. In my case, this was Google Apps for Education. What I did was take this list (as follows) and then read Google Security Whitepapers and information about GAFE and found the information that addressed the following considerations.

  1. Cloud computing security considerations include:
    • My data or functionality to be moved to the cloud is not business critical (19a).
    • I have reviewed the vendor’s business continuity and disaster recovery plan (19b).
    • I will maintain an up to date backup copy of my data (19c).
    • My data or business functionality will be replicated with a second vendor (19d).
    • The network connection between me and the vendor’s network is adequate (19e).
    • The Service Level Agreement (SLA) guarantees adequate system availability (19f).
    • Scheduled outages are acceptable both in duration and time of day (19g).
    • Scheduled outages affect the guaranteed percentage of system availability (19h).
    • I would receive adequate compensation for a breach of the SLA or contract (19i).
    • Redundancy mechanisms and offsite backups prevent data corruption or loss (19j).
    • If I accidentally delete a file or other data, the vendor can quickly restore it (19k).
    • I can increase my use of the vendor’s computing resources at short notice (19l).
    • I can easily move my data to another vendor or in-house (19m).
    • I can easily move my standardised application to another vendor or in-house (19m).
    • My choice of cloud sharing model aligns with my risk tolerance (20a).
    • My data is not too sensitive to store or process in the cloud (20b).
    • I can meet the legislative obligations to protect and manage my data (20c).
    • I know and accept the privacy laws of countries that have access to my data (20d).
    • Strong encryption approved by DSD protects my sensitive data at all times (20e).
    • The vendor suitably sanitises storage media storing my data at its end of life (20f).
    • The vendor securely monitors the computers that store or process my data (20g).
    • I can use my existing tools to monitor my use of the vendor’s services (20h).
    • I retain legal ownership of my data (20i).
    • The vendor has a secure gateway environment (20j).
    • The vendor’s gateway is certified by an authoritative third party (20k).
    • The vendor provides a suitable email content filtering capability (20l).
    • The vendor’s security posture is supported by policies and processes (20m).
    • The vendor’s security posture is supported by direct technical controls (20n).
    • I can audit the vendor’s security or access reputable third-party audit reports (20o).
    • The vendor supports the identity and access management system that I use (20p).
    • Users access and store sensitive data only via trusted operating environments (20q).
    • The vendor uses endorsed physical security products and devices (20r).
    • The vendor’s procurement process for software and hardware is trustworthy (20s).
    • The vendor adequately separates me and my data from other customers (21a).
    • Using the vendor’s cloud does not weaken my network security posture (21b).
    • I have the option of using computers that are dedicated to my exclusive use (21c).
    • When I delete my data, the storage media is sanitised before being reused (21d).
    • The vendor does not know the password or key used to decrypt my data (22a).
    • The vendor performs appropriate personnel vetting and employment checks (22b).
    • Actions performed by the vendor’s employees are logged and reviewed (22c).
    • Visitors to the vendor’s data centres are positively identified and escorted (22d).
    • Vendor data centres have cable management practices to identify tampering (22e).
    • Vendor security considerations apply equally to the vendor’s subcontractors (22f).
    • The vendor is contactable and provides timely responses and support (23a).
    • I have reviewed the vendor’s security incident response plan (23b).
    • The vendor’s employees are trained to detect and handle security incidents (23c).
    • The vendor will notify me of security incidents (23d).
    • The vendor will assist me with security investigations and legal discovery (23e).
    • I can access audit logs and other evidence to perform a forensic investigation (23f).
    • I receive adequate compensation for a security breach caused by the vendor (23g).
    • Storage media storing sensitive data can be adequately sanitised (23h).
    • ( Cloud Computing Security Considerations )

This took some time. There were weeks out of my life in 2013 where I was living and breathing information regarding privacy, security and cloud computing. Believe you me, if you encountered me during this time, my conversation topics were limited and suitable only for a specific audience!

But, it was worth it. I had a document I could present to my Executive that helped us come to the decision that Google Apps for Education was suitable for our school environment. What I gained from this exercise was a thorough understanding of issues surrounding Cloud Computing and the information I needed to be able to speak confidently with my school community about the move we were making.

If you’re a school looking to move into the Cloud Computing space, then measures like this are necessary. If you’re an Australian school looking for links to assist you with the process, then take a look at the following.

Defence Signals Directorate – Cloud Computing Considerations

http://www.dsd.gov.au/publications/csocprotect/cloud_computing_security_considerations.htm

Data Sovereignty and the Cloud  – a Board and Executive Officer’s Guide

http://cyberlawcentre.org/data_sovereignty/CLOUD_DataSovReport_Full.pdf

And if you’re looking to go Google, the following will help.

Google’s approach to IT Security – A Google Whitepaper

https://cloud.google.com/files/Google-CommonSecurity-WhitePaper-v1.4.pdf

Google Apps Service Level Agreement

http://www.google.com/apps/intl/en/terms/sla.html

Google Apps Documentation and Support – Security and Privacy Overview

http://support.google.com/a/bin/answer.py?hl=en&answer=60762

Google Apps for Education

http://www.google.com/enterprise/apps/education/benefits.html

Security Whitepaper: Google Apps Messaging and Collaboration Products

http://static.googleusercontent.com/external_content/untrusted_dlcp/www.google.com/en/us/a/help/intl/en-GB/admins/pdf/ds_gsa_apps_whitepaper_0207.pdf

It’s not over for me. The next thing to consider is replication of data to cloud storage. Off I am to the Amazon Web Summit next week in Sydney to explore that one a little further. 😉