Thursday, 18 March 2010

Musings on security architecture

Time for something a little more intellectual than usual. Here's a list of Do's and Don'ts when it comes to Security Architecture. Purely personal opinion. Feel free to argue. Feel free to agree. Feel free to ignore.

Do collect all of your security requirements from your business stakeholders, your regulatory environment, your wider enterprise and industry standards

Don't present me with an endless list of requirements saying the same thing but in slightly different ways. Consolidate your requirements set but maintain traceability by stating where your consolidated requirements originated

Do obtain sign-off from the relevant business stakeholders that the requirements are correct

Don't tell me that the Head of Security has approved the requirements and so we're good to go...

Do perform a comprehensive risk assessment of the system/service in question

Don't come back with a set of risks so abstract as to be useless - "An attacker may gain unauthorised access to my data" - well yes, but what's the business impact? What's the data? Who is the attacker? And are you talking physical or logical access? And are there any relevant attack vectors available to the threat actors you're worried about?

Do obtain business sign-off that the risk assessment is valid and caters for the risks that they care about

Don't tell me that the Head of Security has approved the risk assessment and so we're good to go...

Do define a set of security services based on your requirements and your risk assessment

Don't give me any services that cannot be traced back to a requirement or a risk. We're not doing this for the sake of it... It may be 'best practice' but do you need 'best practice' or is what you have good enough?

Do consider how your security services interact and how they are used by the relevant actors

Don't get bogged down with fully elaborating a security architecture - mental masturbation may be fun, but it's not productive. Do what you need to do to validate that your architecture is appropriate and is as complete as it needs to be.

Do consider any wider enterprise architectures that you are operating within. Your work may just be a view on a wider architecture

Don't simply assume re-use of existing services defined in a wider architecture without validating that they meet your requirements and are available for your use

Do tell other people about your work - an architecture is worthless unless it's used to influence design, build and run. Don't lock yourself away in an ivory tower and then complain that you're being ignored.

Don't exaggerate the importance of your work - architecture is a tool, sometimes a piece of art as well, but most importantly a tool.

Do remember that you're working in the real world. Whatever you're working on most likely has to be deliverable and affordable.

Don't be precious. This is just a general comment :-).

Well, that's my quick brain dump of do's and don'ts typed up as I sit here on a train heading home. I've probably missed lots of really important stuff - I may even have got some stuff wrong. In your opinion. Let me know.

Friday, 12 March 2010

Web-cast musings

Was it great? No.

Was it utterly cringe inducing? No.

Better than expected? Probably.

What am I wittering on about? I did my second BrightTALK web-cast yesterday which was all about trying to show how cloud security need not sit (and indeed should not) apart from wider enterprise security frameworks. Given the topic I was expecting half of my audience to 'get it' and the other half to absolutely hate it; as it turned out the feedback was mostly positive albeit there was one member of the audience who only gave the presentation 1 star out of 5. But as I say, I was probably expecting more mixed ratings than I received and a number of 5 star ratings means it's currently standing at a 4.2/5 rating - which I'd certainly have taken before the gig! Main lesson for me is to try and not fit a 60 minute presentation into 40 minutes as I was aware that I was rushing through the content...

The really nice thing about BrightTALK is the ability to ask the audience to vote on questions of your choice. One of my questions gave a really interesting outcome - the question was around which service model the audience viewed as the most complex to secure. Both IaaS and SaaS scored 44% with PaaS only scoring 12%. I found this particularly interesting being as I was about to go on and say how I felt that PaaS was actually the most complex model to secure! Perhaps I should have run the vote again after the webcast... Now, I believe the low score for PaaS is probably because it's the model that's the least well understood - it's not as straightforward to understand as either IaaS or SaaS - rather than my audience believing it to be intrinsically more secure. But I could be wrong. Any comments out there? Do we need to expand more on what PaaS actually is?

Monday, 8 February 2010

Cloud and Enterprise Security Architecture

So, I let myself get volunteered to do another web-cast for BrightTALK.

I'm giving the first presentation at their 3rd Cloud Security Summit on the 11th of May. My last web-cast was a fairly generic overview of the security risks associated with cloud computing. My next presentation is a bit more ambitious... I'm aiming to try and bring cloud computing security within the context of wider enterprise architecture. It's either going to be great or one of the more cringe-inducing web-casts on the Interweb :-)

I would like to take a little time to explain the philosophy behind this upcoming presentation. I’ve been thinking for a while now that those of us working in the cloud space need to work harder to bring the technologies into the mainstream – whilst the hype around cloud computing was really useful in bringing it to the forefront, I fear it is now counterproductive to mainstream adoption. By treating cloud as somehow different, or apart from traditional IT delivery, all we are doing is making it appear scarier than it need be to potential consumers. After all, it
is human nature to be wary of things that are different or unknown. What I aim to do is to show that we can bring cloud computing into the wider architecture context of an enterprise – yes cloud brings some unique opportunities and unique challenges, just not necessarily more so than other means of IT delivery. In-house, traditional out-sourcing, cloud – all have their own quirks and are all unique in their own special ways…

So please, tune in to http://www.brighttalk.com/webcasts/8490/attend on the 11th and see whether I manage to pull it off or fall flat on my face!

Friday, 22 January 2010

It really is true!

After years of saying that security is a genuine enabler to business and not just a blocker (or speedbump) on the way, I was fortunate enough to get some proof of my statements recently.

I'm currently working on an information sharing solution between various disparate organisations - most of these organisations have now agreed to share more, particularly sensitive, information (of immense business value) based on their confidence in the security model. Result!

Only a short post today but I thought I ought to have something a bit more positive up here than my last post - especially if it's going to be a while til the next one :-)

Thursday, 7 January 2010

Is it just me?

As much as I would have liked to start 2010 with a nice positive post, I'm going to have to start with a bit of a whinge. What is it about the subject of security that means that everybody working in IT believes that they know how to do it? I rarely see non-DBAs telling their DBAs how their databases should be partitioned but I'll regularly see non-security types discussing security with great authority but little in the way of informed opinion!

So, I'm happy to accept the charge that part of the brief of the security professional is to educate the masses - but I do find it incredibly frustrating that the masses seem pre-programmed with the belief that they already understand security and risk management...

Is it just me?

Tuesday, 1 December 2009

Amusing vulnerability

I came across one of the more entertaining recent vulnerability announcements this morning - take a look at http://www.kb.cert.org/vuls/id/261869. I think it falls into the "well it's obvious now I think about it" category however I hadn't really thought about it... In summary, the way that clientless VPN servers re-write URLs breaks the same origin policy - pretty obvious if you've ever used one of these products and looked at the various URLs that get returned. This means that "bad things" can happen - take a look at the advisory. I'd suggest that any organisation using these kinds of clientless VPNs to provide remote access functionality prevent Internet browsing through these servers; after all, if a user can get to the VPN server he/she has Internet access so why do they need to go through the VPN server?

Why do I view this as entertaining? Well, it's always a little ironic when security products present attack vectors and I'm a big fan of irony. I also know several organisations that make use of this technology and I can't wait to point them to the link...

Thursday, 5 November 2009

AWS in the Enterprise

I managed to get to the Amazon Web Services in the Enterprise event earlier this week. It was a well attended event, with an audience predominantly suited and enterprisey in appearance. Despite an equipment failure (dodgy projector), which necessitated some juggling around with the schedule, I think Amazon managed to get their messages across with respect to the way that their services are currently being used to generate real business value. As ever with these kinds of events, it was the customer presentations that generated the most interest as far as I am concerned. Vendor presentations are fine and dandy but I’m much more interested in what real organisations are doing and the lessons that such organisations have learned during their initial experiences. The presentation from Bob Harris of Channel 4 was particularly encouraging – especially the statement that AWS is now their default platform of choice for web facing applications; C4 projects now need to justify any decision not to use AWS. Bob also provided an interesting anecdote of a senior technical architect from a major SI making a particularly ill-informed comment regarding the security implications of using S3. Lesson here is to be even more diligent than usual when choosing your SI if working in the cloud space. I will admit to a vested interest here :-).
Overall, I think the message that most people will take away from the event is that the AWS platform is maturing and that confidence is increasing amongst enterprises that tricky issues such as compliance and security can be managed. The other message that AWS clearly wanted to get across is that early adopters are likely to obtain a substantial competitive advantage over their more timid competitors due to increased agility and speed to market. We’ll have to see how that one plays out…