Self-Serviced End-to-end Encryption Approaches for Applications Deployed in OpenShift

Introduction The majority of applications deployed on Red Hat OpenShift have some endpoints exposed to the outside of the cluster via a reverse proxy, normally the router (which is implemented with HAProxy). When using a router, the following options are possible: In the diagram we can see: Clear text: the connection is always unencrypted. Edge: […]
The post Self-Serviced End-to-end Encryption Approaches for Applications Deployed in OpenShift appeared first on Red Hat OpenShift Blog.
Quelle: OpenShift

Simplifying complex modernization strategies with the right tools

A few years ago, NASA found water on Mars and mountains on Pluto. The first ever self-driving cars hit the road across the country. And organizations were still building compute workloads with monolithic applications in their local, dedicated data centers with predefined support and upgrade cycles.
How far we’ve come since then. Companies are realizing the benefits of microservices and cloud deployments. They’re beginning to incorporate those technologies into their IT ecosystems.
Those organizations are now also realizing something else: Migrating an entire topology at once to a microservice ecosystem simply isn’t realistic. Most are adopting cloud technology in incremental steps, moving their easiest-to-move applications to the cloud first while leaving the more challenging workloads back in the data center.
This means some IT teams are working in traditional IT infrastructures, maintaining and supporting the applications running on physical servers. Other teams within the same company are supporting modern applications designed using microservices and deployed on clouds. Supporting these very different resources in tandem can be a challenging proposition, especially when another team in the organization uses Openstack as a standard for controlling the compute, network and storage across the entire organization.
Moving past application modernization complexity

This is a common scenario for most companies in the process of their application modernization journeys. This incremental digital transformation can create a storm of complexity. But there are three key reasons it is necessary for companies to move forward with their application modernization journeys.
1. Reliability requirements are driving application architecture.
Containerization enables organizations to adopt modern, cloud native principles, making applications highly reliable. Microservices allow for cloud portability, improve efficiency and provide unparalleled agility.
To realize these benefits, companies need next generation tools such as IBM Microclimate, to get started. Microclimate provides end-to-end, cloud-native solutions for creating, building, testing and deploying container-based microservices. It helps developers focus on application code by automating many of the tasks that require in-depth domain knowledge. With the built-in data collectors in Microclimate, developers can see real-time changes to their code before they commit and make necessary remediation to improve performance.
2. The need for speed is driving continuous delivery.
To outpace competition and meet user expectations, applications must be updated very frequently. Cloud-native, microservice-based applications can easily be updated daily or even multiple times per day. To capitalize on the agility of this, technology teams must also adopt a DevOps and continuous delivery approach, introducing automation to test, build and deploy. This approach also enables teams to use multiple pipelines and ensure the reliability of each release.
3. Cloud flexibility is driving infrastructure automation.
The versatility of modern applications creates opportunities for huge expansion in a short period of time. IT administrators are seeing a transition from supporting just the data center to now managing hybrid environments in which traditional resources are managed alongside a multicloud software infrastructure. Even the largest, most sophisticated organizations’ data centers cannot expand quickly enough to keep up with demand, so companies are using private and public clouds to fill those needs.
IBM Cloud Automation Manager helps organizations automate provisioning by deploying and configuring infrastructure and applications across any cloud environment with workflow orchestration. They can also provide governance and control through effective, enforceable governance and intelligent insights for a security-rich, compliant IT environment.
Modernizing application monitoring
The easiest way to ensure reliability is with a simple and consistent monitoring method across hybrid cloud applications. To get ahead of issues before they reach users, teams need tools that can pinpoint troubled microservices across complex hybrid environments.
New advances in monitoring, relying on site reliability engineer (SRE) golden signals and one-hop dependency are key elements for shifting management from technology-based to service-based monitoring. This approach helps the site reliability engineer realize the value of modern application portability across hybrid clouds.
IBM Cloud App Management delivers a management solution for hybrid, multicloud applications. Designed for high-scale, highly resilient applications and crafted to support cloud operations and Kubernetes, IBM Cloud App Management supports DevOps, site reliability engineers and IT ops with app-centric monitoring of microservice-based applications.
With the aim to help the companies through their modernization journey, IBM is the only vendor providing a completely integrated tool set. IBM provides an end-to-end solution to cover every aspect of an organization’s transformational journey without forcing it to rip and replace its traditional infrastructure.
The post Simplifying complex modernization strategies with the right tools appeared first on Cloud computing news.
Quelle: Thoughts on Cloud

Simplifying your environment setup while meeting compliance needs with built-in Azure Blueprints

I’m excited to announce the release of our first Azure Blueprint built specifically for a compliance standard, the ISO 27001 Shared Services blueprint sample which maps a set of foundational Azure infrastructure, such as virtual networks and policies, to specific ISO controls.

Microsoft Azure leads the industry with over 90 compliance offerings. Azure meets a broad set of international and industry-specific compliance standards, such as General Data Protection Regulation (GDPR), ISO 27001, HIPAA, PCI, SOC 1 and SOC 2, as well as country-specific standards, including FedRAMP and other NIST 800-53 derived standards, Australia IRAP, UK G-Cloud, and Singapore MTCS. Many of our customers have expressed their interest in being able to leverage and build upon our internal compliance practices for their environments with a service that maps compliance settings automatically.

To help our customers simplify the creation of their environments in Azure while successfully interpreting US and international governance requirements, we are announcing a series of built-in Blueprints Architectures that can be leveraged during your cloud-adoption journey. Azure Blueprints is a free service that helps customers deploy and update cloud environments in a repeatable manner using composable artifacts such as policies, deployment templates, and role-based access controls. This service is built to help customers set up governed Azure environments and can scale to support production implementations for large-scale migrations.

The ISO 27001 Shared Services Blueprint is already available to your Azure tenant. Simply navigate to the Blueprints page, click “Create blueprint”, and choose the ISO27001 Shared Services blueprint from the list.

The ISO 27001 blueprint is designed to help you deploy production ready, secure end-to-end solutions in one click and includes:

Hardened infrastructure resources: Azure Resource Manager templates are used to automatically deploy the components of the architecture into Azure by specifying configuration parameters during setup. The infrastructure components include Azure Firewall, Active Directory, Key Vault, Azure Monitor, Log Analytics, Virtual Networks with subnets, Network Security Groups, and Role Based Access Control definitions. Additionally, these resources can be locked by Blueprints as a security measure to protect the consistency of the defined blueprint and the environment it was designed to create.
Policy controls: Set of Azure policies that help provide real-time enforcement, compliance assessment, and remediation.
Proven virtual datacenter architectures: The infrastructure resources provided are based on the Microsoft approved virtual datacenter (VDC) architectures which take into consideration scale, performance, security, and governance.
Security and compliance controls: You still benefit from all the controls for which Microsoft is responsible as your cloud provider, and now this blueprint helps you configure a number of the remaining controls to meet ISO 27001 requirements.
Documentation: Step by step deployment guide outlining the shared services infrastructure and the policy control mapping matrix.
Migration runway: Provides a prescriptive set of instructions for deploying an Azure recommended foundation to accelerate migrations via the Azure migration center.

At Microsoft, we are committed to helping our customers leverage Azure in a secure and compliant manner. Over the next few months you will continue to see new built-in blueprints released for HITRUST, PCI DSS, UK National Health Service (NHS) Information Governance (IG) Toolkit, FedRAMP, and Center for Internet Security (CIS) Benchmark. If you would like to participate in any early previews please sign up, or if have a suggestion for a compliance blueprint, please share it via the Azure Governance Feedback Forum.

Learn more about the Azure ISO 27001 Blueprints.
Quelle: Azure