top of page
Mike Walker

Open Group Conference Austin 2011–Keynote Coverage Day 2

The second morning at the Open Group Conference changed themes a bit. The focus shifted from Enterprise Architecture and Business Architecture to Security and Cloud. A topic that is very near and dear to my heart. There was quite a bit of discussion in these session on how we can enable Cloud solutions from an Enterprise Architecture perspective.

  1. The Digital Identity Challenge - How the US National Strategy for Trusted Identities in Cyberspace (NSTIC) Program Is Responding -- Dr Peter Alterman, Senior Advisor at National Program Office, National Strategy for Trusted Identities in Cyberspace, NIST, and Senior Advisor for Strategic Initiatives at National Institute of Health (NIH)

  2. Lessons From the Cloud: What I’ve Learned in 10 Years of Cloud Computing Brandon Dunlap, Managing Director of Research, Brightfly


Open Group Conference Austin 2011–Keynote Coverage Day 2

This was a very interesting session both from an informative perspective on the specific working group but also what the federal government is doing to protect it’s citizens. What I really liked about the session was it gave insights into the actions the Obama administration is doing to protect all of our digital identities to protect us from theft and fraud.

It was stated a few times that this administration is very sensitive to the Big Brother or George Orwell scenarios. Kudos to this team and the Obama administration. It also brings me back to a security quote from the early 1700’s that applies just as much then as it does now.

“Any society that would give up a little liberty to gain a little security will deserve neither and lose both.”

Below are the key messages from that presentation:

  1. Goal by 2016

  2. Allowing people to choose their authentication provider through an Identity Ecosystem

  3. Private sector will run this effort but the federal government will provide support

  4. Not government ran

  5. The private sector has the highest ability to execute on this vision

  6. The government will define the governance model

  7. No new standards, will align to proven security standards

  8. Tie all this back to the national security policy

  9. Protect Privacy and Civil Liberties are Fundamental

  10. Avoid a George Orwell scenario

  11. What’s being done so far?

  12. Series of workshops on privacy and governance

  13. Supporting existing eGovernment and federated identity management (SSA, IRS, Health ID, etc.)

  14. Going forward

  15. Workshops on technical, legal and attributes in the near future

  16. Establish a functioning governance entity

  17. Create governance models and standards

  18. Criteria for selecting grants

  19. Explore models for addressing liability

  20. Support adoption of attribute management architectures

  21. Prepare for pilot for grants

  22. Ensure early adoption ID’s are being distributed early and broadly.

Session 2: O-Automated Compliance Expert Working Group (O-ACEML)

The Open Group recently published the Open Automated Compliance Expert Markup Language (O-ACEML) standard. This new technical standard addresses needs to automate the process of configuring IT environments to meet compliance requirements. O-ACEML will also enable customer organizations and their auditors to streamline data gathering and reporting on compliance postures.

O-ACEML is aimed at helping organizations to reduce the cost of compliance by easing manual compliance processes. The standard is an open, simple, and well defined XML schema that allows compliance requirements to be described in machine understandable XML, as opposed to requiring humans to interpret text from documents. The standard also allows for a remediation element, which enables multiple requirements (from different compliance regulations) to be blended into a single policy. An example of where this is needed would be in password length and complexity requirements, which may differ between different regulations. O-ACEML allows for the most secure setting to be selected and applied, enabling all of the regulations to be met or exceeded.

The Need?

According to AMR Research, North American Companies are estimated to spend $29.9B on regulatory compliance and will spend $8.8B this year on technology solutions to solve their compliance requirements. The cost worldwide is huge, and the need to comply is not an option. Reducing this cost is therefore a business imperative.

How is this enabling compliance to make it action oriented

  1. Compliance is manual and complicated

  2. Solution: automated it

  3. O-ACEML is a simple way for humans to create security policies

  4. O-ACEML provides a way to have insights into environments that are complex with many end devices or computers via a standard XML structure

  5. Aid auditors in compliance checks

  6. This standard is targeted towards Compliance Organizations such as:

  7. TCG

  8. PCI

  9. NIST

  10. ISO

  11. COBIT

Solution

Create an XML based solution that can provide a common vocabulary for both Risk Management, Security and Audit functions


Mike Walker's Blog: Open Group Conference Austin 2011–Keynote Coverage Day 2
  1. As seem above O-ACEML is primarily split into three areas:

  2. O-ACEML will be used by compliance organizations to express requirements.

  3. O-ACEML will be used by compliance automation tools to implement these requirements through configuration controls upon the underlying device in a automated manner.

  4. O-ACEML will be used to form a auditable historical log which records the details of any configuration change.

  5. This solution allows for descriptive rules that specify a specific action(e.g., shut down this port)

  6. Since this is XML based it is highly dynamic and technology agnostic

  7. The XML de fines what the systems should do, how it should do it and log the result in the XML structure

  8. Below is a sample workflow of an O-ACEML


Mike Walker's Blog: Open Group Conference Austin 2011–Keynote Coverage Day 2

Next steps

  1. Looking to publish to the industry

  2. Push simple tooling

  3. Working with PCI, MITRE, NIST and others

Links

The last session talked about cloud computing risks, how to identify them and prevention.

Key Tweets


8 minutes ago via TweetDeck · Reply · View Tweet


theopengroup: Dunlap: You need to understand the business that your organization is in so you can protect it. Talk to people find their pain points #ogaus

9 minutes ago via HootSuite · Reply · View Tweet


systemsflow: @bdunlap 1st response to "InfoSec too expensive" argument - save $$ by ditching half your security app portfolio as redundant #ogaus

9 minutes ago via HootSuite · Reply · View Tweet


systemsflow: Big message from BrightFly's Brandon Dunlap: cloud providers (Dropbox, Google, 37 signals, etc.) need to publish security controls #ogaus

19 minutes ago via HootSuite · Reply · View Tweet


tinamonod: RT @omkhar: Great discussion with @ARSzakal and @HPPearsonabout #Cloud #Security at the networking event last night #ogaus

23 minutes ago via web · Reply · View Tweet


edocastro: Dunlap: Workers with a credit card are the new IT department; they are going out and procuring services that you are unable to vet #ogaus

24 minutes ago via Twitter for Windows Phone · Reply · View Tweet


theopengroup: Entertaining and interesting presentations by both our keynotes this morning! #ogaus

24 minutes ago via HootSuite · Reply · View Tweet


mikejwalker: AMR: NA companies are estimated to spend $29.9B on reg compliance and will spend $8.8B this year on technology solutions #entarch#ogaus

25 minutes ago via TweetDeck · Reply · View Tweet



SmartestITCan : RT @omkhar: Great discussion with @ARSzakal and @HPPearsonabout #Cloud #Security at the networking event last night #ogaus









1 view0 comments

Comments


bottom of page