Click here to close now.


Microservices Expo Authors: Elizabeth White, Carmen Gonzalez, Liz McMillan, Pat Romanski, Yeshim Deniz

Related Topics: @CloudExpo, Microservices Expo, Microsoft Cloud, Open Source Cloud, Release Management , Cloud Security

@CloudExpo: Article

Security Automation Connects Silos

The true promise of security automation

A wealth of security information exists in our networks from a variety of sources - policy servers, firewalls, switches, networking infrastructure, defensive components, and more. Unfortunately, most of that information is locked away in separate silos due to differences in products and technologies, as well as by companies' organizational boundaries. Further complicating the issue, information is stored in different formats and communicated over different protocols.

An open standard from the Trusted Computing Group (TCG) offers the capability to centralize communication and coordination of information to enable security automation. The Interface for Metadata Access Points - IF-MAP for short - is like Facebook for network and security technology, allowing real-time sharing of information across a heterogeneous environment.

IF-MAP, part of TCG's Trusted Network Connect (TNC) architecture, makes it possible for any authorized device or system to publish information to a Metadata Access Point (MAP), a clearinghouse for information about who's on the network, what endpoint they're using, how they're behaving, and many other details of the network. Systems can also search the MAP for relevant information and subscribe to any updates to that information. Just as IP transformed communications, IF-MAP revolutionizes the way systems share data.

Security automation is any part of a security system that is able to operate without - or with only limited - administrative involvement. As shown in Figure 1, a security administrator can define a unified security policy that applies to different types of protective mechanisms, such as next-generation firewalls (NGFW), intrusion prevention systems (IPS), unified threat management (UTM) systems, and more. Best-of-breed components from multiple vendors can share information using a standard information bus.

Figure 1: Effective security automation includes several protection mechanisms.

This coordination can extend beyond front-line access control products to back-end systems such as authorization databases, virtualization technology, and reputation systems. A policy server might create and modify policy based completely on the information received from other resources in the environment.

Logs from multiple sources can be collected and correlated by a security information and event management (SIEM) system, which itself acts as both a consumer of information and a provider of real-time intelligence based on that information. Security operations personnel can easily oversee activities in the network and provide human intervention in cases where full automation may not be achievable or desirable. Security automation enhances fundamental security solutions, adding dynamic, responsive, intelligent decision-making.

Establishing Network Trust
One of the basic solutions enabled by the TNC architecture is Comply to Connect, which incorporates Network Access Control (NAC) principles - an endpoint must first show its compliance with selected endpoint health requirements before being granted access to the network. Figure 2 shows a common Comply to Connect scenario.

Figure 2: The TNC architecture enables evaluation and enforcement of compliance at admission.

The endpoint, on the left, is a device attempting to access a protected network. The enforcement point is a guard that grants or denies access based on instructions from the policy server. The policy server is really the brains of the operation; it looks at the configured policy and decides what level of access should be granted. Then it informs the enforcement point, which executes those instructions.

Many enforcement options exist; the example in Figure 2 shows a wireless access point and a switch, but environments may also use a firewall or a virtual private network (VPN) gateway. Each of these has its own pros and cons; for example, a wireless access point with 802.1X can totally block unauthorized users. But while it provides admission control, it doesn't offer enforcement deeper in the network. For that reason, most NAC solutions support a combination of different enforcement points, which can be used individually or in combination.

The security policy controlling the compliance check shown in Figure 2 is quite simple: every Windows 7 endpoint on the network must have a self-encrypting drive (SED), up-to-date anti-virus protection, and a personal firewall. When a new Windows 7 endpoint comes on the network, the enforcement point will query it and then consult the policy server. If the endpoint complies with security policy, it is given access to the production network. Another endpoint that does not have an SED may be given only limited access to the network. That way, if either endpoint is lost or stolen, protected information is only on the endpoint that could store it securely on an SED.

Expanding Network Trust Evaluation
Behavior monitoring is another way to evaluate an endpoint. Many security-related sensor devices are already deployed in networks to monitor behavior: intrusion detection systems, leakage detection systems, endpoint profiling systems, and more. The TNC architecture lets users integrate those existing systems with each other and with the NAC solution by sharing information via a MAP.

Figure 3 shows an approach to check behavior. Security sensors in the network monitor behavior, and a security policy identifies acceptable behavior.

Figure 3: Behavior checking enables automated response to changes in the endpoint's activity.

Once an endpoint has connected to the network, even if it has passed authentication and compliance checks, it could behave in an unauthorized fashion. If the endpoint starts violating security policy by trying to spread a worm, that traffic is detected and stopped by an IPS sensor.

Even more important, that sensor publishes information to the MAP about the attack it stopped. The MAP notifies the policy server, which evaluates its security policy and instructs the enforcement point to move the endpoint to a remediation network until it can be addressed.

The end result is an entire network security system that is working together. Each part performs its function, and each piece is integrated with the whole using the open IF-MAP standard.

Extending Security to Mobile Devices
TNC standards have enabled NAC to evolve into a foundation technology for business requirements such as mobile security and Bring Your Own Device (BYOD). A common scenario in today's connected world occurs when a mobile user accesses the Internet and social networks on a personal device, such as a smartphone, which they also use to access their corporate network. If the smartphone inadvertently becomes infected with malware, corporate data on that device is now at risk. And it's even worse when the user connects their smartphone to the corporate network; the attacker, who has taken control of the device, can access sensitive information.

This situation occurs when a company's security team lacks the tools to accommodate employees using their own consumer devices to improve productivity. Without the appropriate technology, the IT team cannot:

  • detect malware on the mobile device
  • protect the user from cloud-based threats
  • control access based on user identity, device, and location
  • coordinate security controls to protect sensitive information

This clearly needs a new approach!

Addressing the new requirements of BYOD and providing broad protection involves flexible deployment models that can be tailored to individual environments and security context, and coordination to keep users protected against the dynamic threat landscape.

Security automation makes it possible to detect and address compromised mobile devices; protect the user from malicious sites and applications; restrict network and resource access based on user identity, device, and location; and correlate endpoint activity monitoring across the corporate network infrastructure.

Leveraging Standard Network Security Metadata
These capabilities are enabled by TNC's standardization of basic metadata for network security. Metadata is the information stored in a MAP, representing anything that is known about the network: traffic flows, scan results, user authentications, or other events. In the case above, metadata represents information about network components and applicable security policies. The MAP is a clearinghouse for metadata; MAP clients can publish metadata to it, search it for specific metadata, and/or subscribe to metadata about endpoints in the network.

These inquiries include common things that it might be helpful to know about an endpoint - the type of device, identity of the user operating the device, role assigned to that user, association between the MAC address and IP address of the endpoint, location of the endpoint, and any events related to that endpoint.

Extending Security Automation to Other Use Cases
While standard metadata is useful for out-of-box interoperability, much more information about an endpoint or a network is available. IF-MAP can be extended by creation of vendor-specific metadata, similar to Vendor-Specific Attributes (VSAs) in RADIUS, enabling anyone to publish anything that can be expressed in XML!

Imagine a manufacturing line, where a physical process is controlled by a digital component called a Programmable Logic Controller (PLC). An operator display panel, the Human Machine Interface (HMI), is typically physically remote from the actual process that needs monitoring. As changes in the process occur, the operator display updates in real-time.

Many HMIs use a legacy protocol called Modbus to poll the PLC, retrieve these process variables, and display them. Originally designed to be run over a serial connection, Modbus has been ported to TCP. One of the problems with the Modbus protocol and many others in this space is that there are zero security features in the protocol - no authentication, no authorization - which means no way of knowing whether a requestor is authorized to gain access requested, or even who is sending data the request. If an endpoint (or intruder) can ping the PLC, it can issue commands to it!

Many control systems components operate this way. Until now, they have been small islands of automation with very little interconnection to other systems. Running over a serial bus required physical serial connections - typically, the operator had to be present in front of the machine to affect it, so physical security was sufficient. And once these systems are in place, they are designed to stay in production for decades. So now these systems are getting more and more interconnected with the enterprise network - and, by extension, to external networks - and they encounter the same types of security issues as enterprise systems.

Overlaying Security onto Industrial Control Systems
A single manufacturing line could have hundreds, or even thousands, of these PLCs. Replacing them is out of the question, as is retro-fitting them to add on security. But what if a transparent security overlay was inserted to protect these legacy components?

Deployment and lifecycle management for such an overlay would be a huge challenge - unless there was a mechanism for provisioning certificates, communication details, and access control policies to the overlay components. That's exactly what one manufacturing company has done with IF-MAP, by using vendor-specific metadata for provisioning of certificate information and access control policy, as shown in Figure 4.

Figure 4: IF-MAP enabled security overlay protects industrial control system components.

The first step is to add the overlay protection. In this case, the enforcement points are customized components, designed for Supervisory Control And Data Acquisition (SCADA) networks, that can create an OpenHIP "virtual private LAN" on top of standard IP networks. This requires no changes to the underlying network, protects communications between SCADA devices, and is completely transparent to the protected SCADA devices.

A MAP and a provisioning client enable centralized deployment, provisioning, and lifecycle management for the myriad enforcement points. The provisioning client publishes metadata to the MAP to define the HMIs and PLCs and to specify security policies that allow them to talk to each other, but do not allow external access to them.

For example, when an HMI comes into the network and queries for a PLC, the HMI does an Address Resolution Protocol (ARP) lookup. The enforcement point receives that traffic, searches the MAP, and finds the access control policy determining whether this specific HMI can talk to that particular PLC. Enforcement points can be moved around the network without requiring manual reconfiguration or reprovisioning, since all of the provisioning is centralized via the MAP.

This is not just a neat thought experiment - it is actually in production deployment on hundreds of endpoints in critical manufacturing lines today!

The Future of Security Automation
We've barely scratched the surface of security automation. For one thing, it goes far beyond access control. Imagine...

  • A content management database (CMDB) receives notification of a new device on the network and scans the new endpoint, then updates its data store
  • An analysis engine observes some behavior on the network and requires more information about the associated endpoint, so it requests an investigation by another component such as an endpoint profiler or vulnerability scanner
  • Carrier routers redirect traffic through deep packet inspection based on suspicious user activity
  • A security administrator modifies an existing security policy, or adds a new policy, and various policy servers / sensors are notified, triggering a re-evaluation of the network's endpoints
  • An application server publishes a request for bandwidth for a particular user based on the service the user is accessing, and network infrastructure components change QoS settings for those traffic flows based on that request
  • An IF-MAP enabled OpenFlow switch controller makes packet-handling decisions based on information from other network components
  • An analysis system determines that there's an attack underway; in addition to triggering a response, it notifies security administrators of the attack taking place, populating a dashboard with information to create a "heat map" of the attack

All of these are examples of a common three-step process: sensing, analysis, and response. Security automation is enabled by the abstraction and coordination of these functions across multiple disparate components in the network.

Imagine the power gained by linking together information from all of the various infrastructure and security technologies in a network and using that information to make dynamic, intelligent, automated decisions. That's the true promise of security automation - and the realization of that promise is in its infancy.

More Stories By Lisa Lorenzin

Lisa Lorenzin is a member of the TNC Work Group at Trusted Computing Group and a Principal Solutions Architect at Juniper Networks.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
SYS-CON Events announced today that Dyn, the worldwide leader in Internet Performance, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Dyn is a cloud-based Internet Performance company. Dyn helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Through a world-class network and unrivaled, objective intelligence into Internet condit...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively.
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing syste...
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and b...
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show h...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
DevOps Summit at Cloud Expo 2014 Silicon Valley was a terrific event for us. The Qubell booth was crowded on all three days. We ran demos every 30 minutes with folks lining up to get a seat and usually standing around. It was great to meet and talk to over 500 people! My keynote was well received and so was Stan's joint presentation with RingCentral on Devops for BigData. I also participated in two Power Panels – ‘Women in Technology’ and ‘Why DevOps Is Even More Important than You Think,’ both ...
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.