DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software security issues.
[slides] @SerenaSoftware Infomercial | @CloudExpo #Cloud #ITaaS #BigData
Leading cloud-centric IT organizations are establishing core capabilities to improve productivity, control costs and provide a highly responsive end-user experience. Key steps along this journey include creating an end-user cloud services catalog, automating workflows and provisioning, and implementing IT showback and chargeback. In his session at 19th Cloud Expo, Mark Jamensky, executive vice president of Products at Embotics, walked attendees through an in-depth case study of enterprise IT management products provider Serena Software and its journey to enhancing ITaaS and IT cost visibility capabilities. The session shared best practices, lessons learned and key technologies used along the way.
Holiday Cooking with AllRecipes.com on the Cloud
Are you one of those people who want to make something special during the holiday season for your near and dear ones? Well, in that case, you’re sure to have browsed recipes from AllRecipes.com – one of the most popular and comprehensive database of food recipes for any season. This holiday season got even better as AllRecipes.com has turned to Microsoft Azure, a popular cloud platform, for sharing its recipes with millions of visitors like you.
AllRecipes.com is a food site owned by Meredith Corp, and has been in operation since 1997. Over these two decades, it has transformed the way people search for recipes, and in fact, has helped billions of people around the world to make any kind of dish. If you translate this to numbers, it services more than 1.5 billion people every year, and these visitors view about 95 recipes per second. Over the last few years, 66 percent of its visitors connect to it through their mobile device. These numbers are growing as more people around the world are exploring food beyond their comfort zone.
Typically, traffic to AllRecipes.com is cyclical. For example, the number of visitors on a Sunday afternoon is almost 60 percent more when compared to Monday morning. Likewise, traffic peaks during Thanksgiving and Christmas season as more people look for recipes to serve their family. A detailed study of its traffic pattern shows that eight weeks in November and December, especially during the holidays and the day before the Super Bowl generate the maximum traffic.
Since it’s traffic is cyclical and predictable, it makes sense for AllRecipes.com to move to the cloud. This way, it can choose a scalable plan that will handle its traffic during the peak season, and will expand during the off-seasons to help the company save some money. Without the cloud, this company would have to invest in large infrastructure, which would have not just cost not just a ton more money, but would also be underused during the off season. With cloud, AllRecipes.com has the option to expand or scale back, according to its needs.
Another important reason to move to the cloud is the expected responsiveness. Most chefs who visit the site are looking for ideas while dropping their kids at soccer practice or while shopping at the grocery stores. Sometimes, they may be at a place where the network is not great, and yet they may want to have an idea of what to make for dinner once they’re back. To cater to these customers, who incidentally form the largest customer base, it’s important that the site is fast, responsive, and takes as little data as possible. Again, this can be best achieved on a cloud platform like Microsoft Azure rather than on a data center that could be located miles away from the visitor’s location.
So, why did the company choose Azure, and not anything else? The simple answer is this site is built on C#, so Azure was the natural choice!
All this means is you’re sure going to spend a lot less time waiting for the site to load, and a lot more time cooking and having fun with your family and friends.
Merry Christmas!
The post Holiday Cooking with AllRecipes.com on the Cloud appeared first on Cloud News Daily.
Security through visibility: Seeing into virtual and cloud networks

(c)iStock.com/alashi
Imagine an IT security team as a navy crew at sea. A torpedo blasts the ship’s side below the water line. As the water floods in, they can’t even see the hole, let alone fix it. Instead, everyone turns to the pumps to keep the ship afloat.
This is the state of many security programs today. Despite a plethora of point solutions, security teams lack visibility into what they’re trying to protect, their most pressing risks and the security tools at their disposal. Thus security teams operate in constant reactionary mode, while a strategic, proactive security program remains elusive.
The growing popularity of virtual networks further complicates visibility issues. Virtual machines are spun up at a moment’s notice, and security groups and tags are assigned – but not necessarily in line with broader security policies. Network security teams may have no access to management consoles and limited insight as to how changing network architectures affect their attack surface.
But with comprehensive network modeling extending into virtual networks, network security engineers can gain the needed visibility to unify security and compliance processes across their hybrid hardware and virtual environments.
Verifying access
A major challenge to policy and access verification in hybrid environments is complexity. The mixture of physical, virtual and cloud networks with their various security groups and tags, as well as traditional ACLs, makes manual comparison and analysis almost impossible. But by normalising this data and combining hybrid network policies, network access can be analysed end to end and visualised within the model.
Microsegmentation challenges
Historically, data centres have been protected by perimeter security technologies analysing north-south traffic –traffic into and out of the data centre. Traditional data centre designs assume that all east-west traffic – traveling within the data centre – occurs in trusted, well-protected zones. Recent data breaches, however, have shown that this assumption is no longer valid. Microsegmentation is capable of dividing east-west traffic within the data centre into smaller, more protected zones; but without security visibility into how microsegmentation is implemented, it’s difficult to verify policy is adhered to across the network.
By combining and modeling north-south and east-west policies network security teams can gain end-to-end access visibility throughout their hybrid network. Model-driven visibility also provides a more realistic view of applied policy at the host level rather than verifying access only at “chokepoints” or gateways to the virtual network.
Vulnerability detection in virtual networks
One added benefit of modeling virtual and cloud environments is scanless vulnerability detection. Security analytics applied to the model can deduce vulnerabilities using product configuration and version information. This can significantly decrease reliance on active or third-party scans which are harder to operate on virtual and cloud networks. Incorporating vulnerability intelligence gives a fuller picture of how these networks impact overall risk.
Visualisation
By unifying hybrid IT environments in one model and normalising their data, organisations can break down the barriers that traditionally existed between physical, virtual and cloud networks for comprehensive, streamlined security management.
This information can be further distilled into a simple picture of the organisation’s unique attack surface. Using attack surface visualisations, CISOs to “in-the-trenches” security practitioners to board members can quickly see the interconnectedness of their IT infrastructure and where their most critical security exposures lurk. Attack surface visibility gives an intuitive and deeply analytical tool to make fast, informed decisions regarding incident response, operations and security investments. It provides a common language and reference to stop reacting to symptoms and start treating root causes of security issues, creating a proactive, holistic security program.
Security through visibility: Seeing into virtual and cloud networks

(c)iStock.com/alashi
Imagine an IT security team as a navy crew at sea. A torpedo blasts the ship’s side below the water line. As the water floods in, they can’t even see the hole, let alone fix it. Instead, everyone turns to the pumps to keep the ship afloat.
This is the state of many security programs today. Despite a plethora of point solutions, security teams lack visibility into what they’re trying to protect, their most pressing risks and the security tools at their disposal. Thus security teams operate in constant reactionary mode, while a strategic, proactive security program remains elusive.
The growing popularity of virtual networks further complicates visibility issues. Virtual machines are spun up at a moment’s notice, and security groups and tags are assigned – but not necessarily in line with broader security policies. Network security teams may have no access to management consoles and limited insight as to how changing network architectures affect their attack surface.
But with comprehensive network modeling extending into virtual networks, network security engineers can gain the needed visibility to unify security and compliance processes across their hybrid hardware and virtual environments.
Verifying access
A major challenge to policy and access verification in hybrid environments is complexity. The mixture of physical, virtual and cloud networks with their various security groups and tags, as well as traditional ACLs, makes manual comparison and analysis almost impossible. But by normalising this data and combining hybrid network policies, network access can be analysed end to end and visualised within the model.
Microsegmentation challenges
Historically, data centres have been protected by perimeter security technologies analysing north-south traffic –traffic into and out of the data centre. Traditional data centre designs assume that all east-west traffic – traveling within the data centre – occurs in trusted, well-protected zones. Recent data breaches, however, have shown that this assumption is no longer valid. Microsegmentation is capable of dividing east-west traffic within the data centre into smaller, more protected zones; but without security visibility into how microsegmentation is implemented, it’s difficult to verify policy is adhered to across the network.
By combining and modeling north-south and east-west policies network security teams can gain end-to-end access visibility throughout their hybrid network. Model-driven visibility also provides a more realistic view of applied policy at the host level rather than verifying access only at “chokepoints” or gateways to the virtual network.
Vulnerability detection in virtual networks
One added benefit of modeling virtual and cloud environments is scanless vulnerability detection. Security analytics applied to the model can deduce vulnerabilities using product configuration and version information. This can significantly decrease reliance on active or third-party scans which are harder to operate on virtual and cloud networks. Incorporating vulnerability intelligence gives a fuller picture of how these networks impact overall risk.
Visualisation
By unifying hybrid IT environments in one model and normalising their data, organisations can break down the barriers that traditionally existed between physical, virtual and cloud networks for comprehensive, streamlined security management.
This information can be further distilled into a simple picture of the organisation’s unique attack surface. Using attack surface visualisations, CISOs to “in-the-trenches” security practitioners to board members can quickly see the interconnectedness of their IT infrastructure and where their most critical security exposures lurk. Attack surface visibility gives an intuitive and deeply analytical tool to make fast, informed decisions regarding incident response, operations and security investments. It provides a common language and reference to stop reacting to symptoms and start treating root causes of security issues, creating a proactive, holistic security program.
Gaining elastic visibility into your clouds – without the strain

(c)iStock.com/VisualCommunications
How do you see what isn’t physically there? It is emerging as a major problem facing enterprises, as cloud increasingly becomes the new normal.
On-premise networks and physical data centres are disappearing fast, with core business applications and processes being migrated to cloud architectures. The latest Cisco Global Cloud Index states that by 2020, 92% of workloads will be processed in public and private cloud data centres, and just 8% in physical data centres.
The rapid move to cloud is understandable since it is so alluring: they are elastic, cost less to operate and manage, and is scalable, enhancing business agility. But in engineering there is no such thing as getting something for nothing. You always have to give something up in order to gain something. The trick, of course, is getting something you value greatly while giving up something that does not mean as much to you. For cloud migration, these benefits are being realised at the expense of visibility and insight into those cloud environments.
When we surveyed a range of businesses on their virtualisation practices, just 37% monitored their virtualised environments with the same rigor as their physical networks. So there is a big visibility gap when it comes to the cloud. While that may seem like a good trade-off today, it may feel different if and when things go wrong. Most organisations cannot take that chance, so they need to bridge the visibility gap quickly. They need it for better control, to maintain security no matter where their data goes, and of course to ensure reliability of their core business applications.
It would seem like addressing this visibility gap could be fixed easily by inserting virtual network taps into the virtualised environment and sending the traffic to their monitoring, analytics, and security tools. Unfortunately, doing this would quickly flood these tools with data, because internal East-West traffic in virtual data centres typically represents 80% of the total traffic. It would be like connecting a lawn sprinkler to a fire hydrant. Identifying and extracting only relevant traffic is key, but how can you do that efficiently? More so, how can your virtual taps handle scaling up and down as virtual machines emerge and dissolve? Let’s take a closer look at the key requirements for visibility and monitoring in virtual environments.
Expanding your (visibility) horizon
There are four key points to consider when deploying virtual taps so you end up with meaningful, granular access to critical application traffic on virtualised networks.
Horizontal scale: Cloud environments are attractive because they can scale up and down rapidly as user demands and workloads change. When placing the virtual taps in the virtual network, you need to be sure they can scale up to accommodate rapid growth in traffic volumes as well as user numbers and data interactions. The taps should do this automatically, without needing IT intervention. Virtualisation means agility, so if an application or service expands to handle 10x or 100x the number of users, make sure the virtual tap you are using can scale elastically – without impacting application performance.
Securing in the dark: Virtualised networks are typically segmented using virtual firewalls to protect key applications and services from attack, and to prevent lateral movement in the virtualised environment that could compromise data or resources. So the virtual taps you use needs to be able to see the application and network traffic flowing between segments. With this comprehensive insight, you can ensure that the appropriate security rules and policies governing each segment are being enforced.
More containers: As virtual machine use grows, container use multiplies even faster – by as much as 10-fold or more, as each application may employ multiple containers. If your organisation is using container-based virtualisation to boost application performance, the virtual tap must be able to access traffic in the container environment.
DevOps elasticity: When your DevOps team puts out a new build – which, remember, doesn’t just cover new applications and services, but also updates to existing ones – then that update propagates across the virtual environment. Individual virtual machines, containers, and by association their hosted applications, have shorter and shorter lifespans requiring continual awareness of the actual state of the environment. It is vital that these changes not block the entire traffic path, or take the virtual tap down with it. As an example, consider how to archive and retrieve monitored traffic from a container that no longer exists. The tap is your sentinel, which has to maintain pervasive access to traffic to enable you to see what is happening on the virtual network: it must be fault-tolerant, even if the application it is monitoring fails.
These four points apply when monitoring any virtualised environment, whether public cloud, private cloud or software defined wide-area networks (SD-WANs): the virtual taps and the overall visibility solution need to be completely environment-agnostic.
Elastic visibility
Once the virtual taps have been deployed to extract traffic from the virtual machines in your environments, you are ready to start processing packets. This volume of traffic needs filtering and controlling using a network packet broker. That keeps duplicate data from overwhelming monitoring and security tools and ensures they scale up/down as needed. Data traffic should be broken up into manageable pieces using packet filtering, grooming and brokering processes, to make sure the security systems and analytics tools are seeing everything.
Elastically-scalable access is achievable for all the data crossing their virtual networks and clouds as well as intelligent distribution to analytics and compliance tools. Leaving your data unmonitored is not smart business. You do not have to give up visibility to gain cloud speed and cost advantages. With the right architecture, you can have both so you should not compromise.
Gaining elastic visibility into your clouds – without the strain

(c)iStock.com/VisualCommunications
How do you see what isn’t physically there? It is emerging as a major problem facing enterprises, as cloud increasingly becomes the new normal.
On-premise networks and physical data centres are disappearing fast, with core business applications and processes being migrated to cloud architectures. The latest Cisco Global Cloud Index states that by 2020, 92% of workloads will be processed in public and private cloud data centres, and just 8% in physical data centres.
The rapid move to cloud is understandable since it is so alluring: they are elastic, cost less to operate and manage, and is scalable, enhancing business agility. But in engineering there is no such thing as getting something for nothing. You always have to give something up in order to gain something. The trick, of course, is getting something you value greatly while giving up something that does not mean as much to you. For cloud migration, these benefits are being realised at the expense of visibility and insight into those cloud environments.
When we surveyed a range of businesses on their virtualisation practices, just 37% monitored their virtualised environments with the same rigor as their physical networks. So there is a big visibility gap when it comes to the cloud. While that may seem like a good trade-off today, it may feel different if and when things go wrong. Most organisations cannot take that chance, so they need to bridge the visibility gap quickly. They need it for better control, to maintain security no matter where their data goes, and of course to ensure reliability of their core business applications.
It would seem like addressing this visibility gap could be fixed easily by inserting virtual network taps into the virtualised environment and sending the traffic to their monitoring, analytics, and security tools. Unfortunately, doing this would quickly flood these tools with data, because internal East-West traffic in virtual data centres typically represents 80% of the total traffic. It would be like connecting a lawn sprinkler to a fire hydrant. Identifying and extracting only relevant traffic is key, but how can you do that efficiently? More so, how can your virtual taps handle scaling up and down as virtual machines emerge and dissolve? Let’s take a closer look at the key requirements for visibility and monitoring in virtual environments.
Expanding your (visibility) horizon
There are four key points to consider when deploying virtual taps so you end up with meaningful, granular access to critical application traffic on virtualised networks.
Horizontal scale: Cloud environments are attractive because they can scale up and down rapidly as user demands and workloads change. When placing the virtual taps in the virtual network, you need to be sure they can scale up to accommodate rapid growth in traffic volumes as well as user numbers and data interactions. The taps should do this automatically, without needing IT intervention. Virtualisation means agility, so if an application or service expands to handle 10x or 100x the number of users, make sure the virtual tap you are using can scale elastically – without impacting application performance.
Securing in the dark: Virtualised networks are typically segmented using virtual firewalls to protect key applications and services from attack, and to prevent lateral movement in the virtualised environment that could compromise data or resources. So the virtual taps you use needs to be able to see the application and network traffic flowing between segments. With this comprehensive insight, you can ensure that the appropriate security rules and policies governing each segment are being enforced.
More containers: As virtual machine use grows, container use multiplies even faster – by as much as 10-fold or more, as each application may employ multiple containers. If your organisation is using container-based virtualisation to boost application performance, the virtual tap must be able to access traffic in the container environment.
DevOps elasticity: When your DevOps team puts out a new build – which, remember, doesn’t just cover new applications and services, but also updates to existing ones – then that update propagates across the virtual environment. Individual virtual machines, containers, and by association their hosted applications, have shorter and shorter lifespans requiring continual awareness of the actual state of the environment. It is vital that these changes not block the entire traffic path, or take the virtual tap down with it. As an example, consider how to archive and retrieve monitored traffic from a container that no longer exists. The tap is your sentinel, which has to maintain pervasive access to traffic to enable you to see what is happening on the virtual network: it must be fault-tolerant, even if the application it is monitoring fails.
These four points apply when monitoring any virtualised environment, whether public cloud, private cloud or software defined wide-area networks (SD-WANs): the virtual taps and the overall visibility solution need to be completely environment-agnostic.
Elastic visibility
Once the virtual taps have been deployed to extract traffic from the virtual machines in your environments, you are ready to start processing packets. This volume of traffic needs filtering and controlling using a network packet broker. That keeps duplicate data from overwhelming monitoring and security tools and ensures they scale up/down as needed. Data traffic should be broken up into manageable pieces using packet filtering, grooming and brokering processes, to make sure the security systems and analytics tools are seeing everything.
Elastically-scalable access is achievable for all the data crossing their virtual networks and clouds as well as intelligent distribution to analytics and compliance tools. Leaving your data unmonitored is not smart business. You do not have to give up visibility to gain cloud speed and cost advantages. With the right architecture, you can have both so you should not compromise.
Spreadsheets, Clouds and Finance-Owned Solutions | @CloudExpo #Cloud #FinTech
It’s that time of year again! Finance teams are putting the finishing touches on next year’s corporate budgets and teams are likely looking back on 2016 to see what to change or improve in the year ahead.
Here at Vena, we’re making our annual predictions in finance and corporate performance management for 2017. We pulled the predictions after countless conversations with customers, partners, industry analysts and more. Buckle your seatbelts, I’m sure 2017 will be a wild ride!
Six Cloud Trends to Watch in 2017 | @CloudExpo @NaviSite #Cloud #MachineLearning
While cloud may have formally entered the enterprise in 2006, it’s now a reality for nearly every company. The Cloud Era got its start with Software as a service (SaaS) offerings that paved the way for innovations in CRM and email deployments, to create new opportunities for the likes of Salesforce and Microsoft Office 365. Still in its “early stages,” cloud now encompasses legacy applications, backups, disaster recovery, security/audit log management and so much more. 2017 will be full of continued maturation and will give way to a whole new generation of cloud-native applications.
IBM and Delos to Create Healthy Indoor Environments
One of the major concerns during any winter season is the quality of indoor air. Since most of us have to shut our windows and turn on the heater to protect against the cold, the quality of indoor air suffers greatly. Such unclean air leads to an increased chance of respiratory and other illnesses during winters. To prevent these problems and to promote healthy indoor environment, cloud-giant IBM has partnered with a wellness, real estate and technology firm called Delos.
Under the terms of this partnership, Delos will tap into IBM’s Watson and its cloud infrastructure to understand the impact of indoor environment on human health. Specifically, it will create cognitive computing-based apps with Watson and Bluemix platform to give construction engineers and architects an insight into the existing problem, and may also provide solutions that can be incorporated in the design and construction of homes and offices. Through these apps, both companies want to drive home the point that a healthy indoor environment is essential for better living and working conditions. Already, many companies find it difficult to handle the low productivity and frequent sick leaves during the winter season, so they are sure to take steps to reduce this absenteeism and increase productivity.
Are you’re wondering why IBM chose Delos for this partnership? Well, for starters, Delos is already in the process of collecting massive amounts of data, to understand the relationship that exists between indoor air quality and health. So, in this sense, IBM is simply providing the right technology to help Delos make sense of the data they have collected. In many ways, it’s a natural partnership because IBM has the perfect platform and technological tools to help Delos identify the right patterns from its vast data. In addition to its own data, Delos is also tapping into the database of Mayo Clinic to fill in any gaps that may arise.
Delos has already setup a Wellness Lab in collaboration with Mayo Clinic, to simulate a wide-variety of indoor environments in real-time. it has setup sensors in homes and offices across different cities in the US to give its scientists and researchers greater access into everyday conditions. With this information, researchers can identify the impact of different aspects such as indoor light, optimal temperature, acoustics, dust levels, and more, on the health of those living in these conditions.
With IBM’s Watson and Bluemix, Delos can also look into the historical data, including the many studies that have been done in this regard. Eventually, it can combine all this information to understand what impacts indoor air, and in turn, what effect it has on human beings.
This partnership is a classic example of IT application, where the advancements we have made are used to improve our own well-being. Though this is not the first experiment of its kind, the fact that it taps into so many sources of information and uses advanced technology, makes it truly unique.
It won’t be long before we start breathing healthy air – even during winters!
The post IBM and Delos to Create Healthy Indoor Environments appeared first on Cloud News Daily.