The Veeam Community Weekly Recap is available with incredible content and relevant information! Congratulations to Nico Losschaert, Brad Linch, Christian Eromosele, and Philippe Dupuis for the posts and articles.
Thanks so much to Madalina Cristil, Mark Boothman, and Safiya Mohamed for the opportunity to participate! I am honored.
The year has begun, and some versions of Veeam solutions will no longer be supported (end-of-life). Therefore, it is essential to plan and carry out updates now. Veeam has been working on several new features and enhancements to its solutions. For example, in the launch of Veeam Backup & Replication v12 alone, more than 100 new features were introduced, and in the recent release 23H12 (VBR 12.1), many new features related to cybersecurity and expanded support for backup methods and integrations were made available. Below is a summary of the main end-of-support dates:
February 2024:
Veeam Backup & Replication v11
Veeam ONE v11
Veeam Backup for Nutanix AHV v3
Veeam Agent for Microsoft Windows v5
Veeam Agent for Linux v5
Veeam Agent for Mac v1
March 2024:
Veeam Recovery Orchestrator v4
Veeam Backup for Microsoft 365 v3
September 2024:
Veeam Agent for Oracle Solaris v3
Veeam Agent for IBM AIX v3
VCSP software:
February 2024: Veeam Backup & Replication v11 (Cloud Connect)
Hey! Here, I present a small set of questions and answers (FAQ) to help you understand the relationship between Kubernetes and Digital Transformation in organizations. I hope this is useful, especially for those just starting their Kubernetes journey!
1) How is Kubernetes associated with Digital Transformation?
2) In which areas can Kubernetes contribute to the transformation of organizations?
3) How are organizations deploying Kubernetes?
4) Kubernetes is an open-source project. How can organizations benefit from this?
5) What is the relationship between Kubernetes, DevOps and DevSecOps?
6) Cybercrimes are reaching alarming rates, and security is a top priority. How to handle cybersecurity in Kubernetes?
7) Will containers and Kubernetes replace server virtualization technology?
8) What will Kubernetes look like in the future?
===================================
1) How is Kubernetes associated with Digital Transformation?
Digital transformation is a challenge that demands changes in companies, such as the use of cloud-native technologies, greater agility in processes, intensive use of automation, and the development of a collaborative culture within the organization.
Cloud-native applications are hosted in containers, allowing the isolation of the application and all the components necessary/related for its execution. In other words, with containers, we can be sure that the application will work properly, whether implemented in a public or private cloud environment – it is decoupled from the infrastructure. This feature is critical for companies to implement a multi-cloud strategy.
Kubernetes has quickly become the industry standard for centrally managing large numbers of containers. It is an open-source project initiated by Google and currently governed by the Cloud Native Computing Foundation (CNCF).
Kubernetes aims to simplify the deployment and operation of container-based environments, allow companies to utilize their infrastructure resources better, and have integrated features that allow orchestration of the application lifecycle.
Additionally, recent research shows that at least 90% of business leaders agree that cloud-native technologies, including Kubernetes, are helping transform how companies operate and deliver value to their customers.
2) In which areas can Kubernetes contribute to the transformation of organizations?
Kubernetes is one of the main tools available that allows increased business agility as it allows IT teams to stop dedicating so much time to managing infrastructure.
As software development processes become automated, new applications’ launch and deployment cycle is significantly reduced, allowing companies to adapt more quickly to market changes and add more value to their offerings.
Additionally, Kubernetes’ native autoscaling capability helps optimize the use of infrastructure resources and reduces costs. This capacity is very much in line with the elasticity and on-demand consumption characteristics that public cloud services already provide. Both allow IT teams to avoid failures due to a lack of resources and avoid paying for idle resources.
Another benefit of Kubernetes related to digital transformation is that it helps implement hybrid and multi-cloud adoption strategies. Its application portability capacity provides freedom of choice and good interoperability between different providers, measured in PTO (portability time objective).
As applications are developed, deployed, and managed using the same core set of Kubernetes features, they can be deployed or migrated between private, public, and edge clouds in a more user-friendly way.
On the other hand, the topic of DevX, or developer experience, is also critical in digital transformation. How developers interact with the resources needed to get work done can affect business strategy execution, productivity, company competitiveness, and customer satisfaction. Kubernetes, without a doubt, contributes significantly to improving the experience of developers as actions on the infrastructure are now defined by developers through code.
3) How are organizations deploying Kubernetes?
A recent report shows that among organizations that have already deployed Kubernetes, 46% of them have adopted a hybrid cloud model, and 44% have implemented a fully hosted deployment in the public cloud. Additionally, 53% of respondents plan to add or increase the capacity of their Kubernetes environments using different public cloud providers.
The multi-cloud Kubernetes deployment strategy is primarily driven by the need to reduce technological dependence on a single provider. It also aims to seek greater flexibility in cost management, enable high availability for applications, and deliver capacity for disaster recovery.
Furthermore, this same report revealed that organizations are moving away from the “do it yourself” or “do it yourself” (DIY) implementation mod
We must remember that Kubernetes represents only part of the components necessary for the perfect delivery and implementation of applications. Even with all the benefits of Kubernetes, other essential elements are still needed for containers to go live in a production environment.
In addition to there being more than 100 Kubernetes distributions available on the market, there are also hundreds of projects hosted at CNCF related to all the stages necessary for the implementation and operation of container-based environments: security, telemetry, observability, image registration, service mesh, service proxy, network, and so on.
Integrating these components and delivering a validated platform ready for operation is exhaustive and expensive work. Furthermore, these tasks are not directly related to the business purpose of most companies.
Therefore, organizations are increasingly adopting turn-key Kubernetes platforms, deployed on-prem or in public cloud services, capable of adding all the necessary complementary components and providing specialized, high-level technical support.
4) Kubernetes is an open-source project. How can organizations benefit from this?
Open-source projects allow anyone to access, modify, and distribute the code. They are developed in a decentralized and collaborative way, involving companies and individuals around the world.
Therefore, in general, open-source projects can deliver new features and innovations more quickly than proprietary code. They can also allow the creation of more reliable software as their revisions and problem corrections are more frequent, as a large group of collaborators maintains them.
As an illustration, according to CNCF figures, the Kubernetes project alone received more than 2.7 million contributions and more than 430 thousand code updates/commits in the last year alone.
Large companies also actively collaborate on new features and updates, as many use Kubernetes as an “upstream” project for their solutions and market distributions. And this ends up creating a standard in the IT industry.
5) What is the relationship between Kubernetes, DevOps and DevSecOps?
DevOps and security are related to cultural changes within the organization, as they require great collaboration between team members
Traditionally, security was not an element considered in software development. In the practice of DevSecOps, security concerns must be applied from the beginning of the software development cycle, that is, from the moment the application requirements are specified.
Ensuring consistency in DevOps and DevSecOps collaboration activities is a challenge that can directly impact process agility. Therefore, automation is widely used in application development, testing, and provisioning stages.
There are many ways to implement automation, including solutions that allow the definition and deployment of infrastructure through code (IaC). However, they can add complexity to the software development cycle, especially in container-based environments.
Kubernetes has enormous synergy with DevOps and DevSecOps as it has native mechanisms that enable complete automation of containers and related elements, making the development cycle simpler, faster, more frequent and better managed.
In addition to automation, Kubernetes adds the ability to abstract infrastructure. Developers can focus on functionality and specify infrastructure-related dependencies, actions, and policies as a part of the developed code, using native Kubernetes APIs.
6) Cybercrimes are reaching alarming rates, and security is a top priority. How to handle cybersecurity in Kubernetes?
The treatment of security in Kubernetes is no different from that which should be applied to the IT environment as a whole. Kubernetes security is effectively integrated into organizations’ cybersecurity policy.
Furthermore, it is necessary to provide security teams visibility into applications hosted in containers, seeking to integrate Kubernetes with other cybersecurity solutions that the company may use or is considering purchasing.
An essential action is to identify and contain vulnerabilities in the Kubernetes environment. Containment must begin by using images from trusted sources, checking the integrity of these images, making unauthorized access to cluster information difficult, and preventing privilege escalation.
Other security actions are also necessary, such as using secure hardware, defining access policies, and network micro-segmentation to prevent lateral movement and integrating with anti-virus and IDS/IPS systems. Adopting “sandbox” techniques to analyze and respond to incidents is also highly recommended.
Furthermore, the organization must be ready to recover the Kubernetes environment quickly during security incidents, relying on solutions that allow secure backup, replication, and disaster recovery policies.
7) Will containers and Kubernetes replace server virtualization technology?
Everything indicates that no, the hybrid model should prevail. In other words, server virtualization-based environments will continue to coexist with Kubernetes environments.
As not all monolithic applications are suitable or eligible for transformation to an architecture based on microservices, either due to high costs or due to intrinsic implementation characteristics, applications hosted on virtual servers will likely continue to exist for some time.
Furthermore, server virtualization technologies are widely used, have decades of market presence, and can deliver a robust and well-known set of tools for management and security.
For example, one of the fastest-growing projects at CNCF is the KubeVirt. This project allows Kubernetes to manage and control virtualized server environments based on a KVM hypervisor.
Some market suppliers also offer solutions that simultaneously allow the implementation and management of Kubernetes and virtualized environments.
We have had access to this feature just through public cloud services, where we can implement computing and Kubernetes services in the same private cloud (virtual private cloud) and manage them through the same console.
8) What will Kubernetes look like in the future?
The Kubernetes project still has a lot to evolve. Perhaps, soon, Kubernetes will become just another logical abstraction layer within the tools available to software developers.
Furthermore, with the advent of Artificial Intelligence, which is already widely incorporated into software development processes, many of the barriers and difficulties still existing in Kubernetes tend to be overcome and abstracted.
Therefore, it is up to us to monitor and be attentive to these developments.
Oi! Preparei um pequeno conjunto de perguntas e respostas (FAQ) que poderão ajudar a entender a relação entre o Kubernetes e a Transformação Digital nas organizações. Espero que seja útil, especialmente para aqueles que estão iniciando na jornada com o Kubernetes!
1) De que forma o Kubernetes está associado com a Transformação Digital?
2) Em quais áreas o Kubernetes contribui com a transformação das organizações?
3) Como as organizações estão implantando o Kubernetes?
4) O Kubernetes é um projeto de código aberto. Como as empresas podem se beneficiar disso?
5) Qual a relação entre Kubernetes, DevOps e DevSecOps?
6) Com os crimes cibernéticos alcançando índices alarmantes, a segurança é uma prioridade para as empresas. Como tratar a segurança cibernética no Kubernetes?
7) Os containers e o Kubernetes vão substituir a tecnologia de virtualização de servidores?
8) Como será o Kubernetes no futuro? Para onde ele caminha?
===================================
1) De que forma o Kubernetes está associado com a Transformação Digital?
A transformação digital é um desafio que demanda mudanças nas empresas como o uso de tecnologias nativas da nuvem, ou “cloud native”, maior agilidade nos processos, uso intensivo de automação e o desenvolvimento de uma cultura colaborativa dentro da organização.
As aplicações do tipo cloud native são hospedadas em containers pois eles permitem isolar a aplicação, e todos os componentes necessários para a sua execução, da infraestrutura. Ou seja, com os containers, passamos a ter certeza que a aplicação funcionará adequadamente, independentemente se ela for implementada num ambiente de nuvem pública ou privada. Esse recurso é absolutamente crítico para que as empresas possam implementar uma estratégia multi-cloud.
O Kubernetes tornou-se rapidamente o padrão de mercado para gerenciar uma grande quantidade de containers de forma centralizada. Ele é um projeto de código aberto (ou “open source”) iniciado pelo Google e que atualmente é governado pela Cloud Native Computing Foundation (CNCF).
Basicamente, o Kubernetes simplifica a implantação e a operação de ambientes baseados em containers, permite que as empresas utilizem melhor seus recursos de infraestrutura e possui recursos integrados que permitem a orquestração do ciclo de vida das aplicações.
Além disso, pesquisas recentes mostram que pelo menos 90% dos líderes de negócio concordam que as tecnologias do tipo cloud native, incluindo o Kubernetes, estão ajudando a transformar a maneira como as empresas operam e entregam valor aos seus clientes.
2) Em quais áreas o Kubernetes contribui com a transformação das organizações?
O Kubernetes é uma das principais ferramentas disponíveis que permite aumentar a agilidade dos negócios pois ele possibilita que as equipes de TI deixem de dedicar tanto tempo no gerenciamento da infraestrutura.
Como os processos de desenvolvimento de software passam a ser automatizados, o ciclo de lançamento e implantação de novas aplicações é bastante reduzido, permitindo que as empresas se adaptem mais rapidamente a mudanças de mercado e agreguem mais valor às suas ofertas.
Além disso, a capacidade nativa de escalonamento automático do Kubernetes ajuda a otimizar o uso dos recursos de infraestrutura e também a reduzir custos. Esta capacidade está muito alinhada com as características de elasticidade e de consumo sob demanda que os serviços em nuvem pública já proporcionam. Ambas permitem que as equipes de TI não apenas sejam capazes de evitar falhas devido à falta de recursos, mas também evitem pagar por recursos ociosos.
Outro benefício do Kubernetes relacionado com a transformação digital é que ele auxilia na implementação de estratégias de adoção de nuvem híbrida e multi-cloud. A sua capacidade de portabilidade de aplicações proporciona liberdade de escolha e um bom nível de interoperabilidade entre diferentes provedores, medido em PTO (portability time objective).
Como as aplicações passam a ser desenvolvidas, implantadas e gerenciadas utilizando basicamente um mesmo conjunto central de características do Kubernetes, elas podem ser implementadas ou migradas entre nuvens privadas, públicas e nuvens de borda (edge cloud) de uma forma mais amigável.
Por outro lado, o tema DevX, ou developer experience, também é muito importante dentro do contexto da transformação digital. A maneira como os desenvolvedores interagem com os recursos necessários para realizar o trabalho pode afetar a execução da estratégia de negócios, a produtividade, a competitividade da empresa e a satisfação dos clientes. E o Kubernetes, sem dúvida, contribui muito para melhorar a experiência dos desenvolvedores pois as ações sobre a infraestrutura passam a ser definidas pelos desenvolvedores através de código.
3) Como as organizações estão implantando o Kubernetes?
Um relatório recente mostra que, dentre organizações que já implantaram o Kubernetes, 46% delas adotaram um modelo de nuvem híbrida e 44% realizaram uma implantação totalmente hospedada na nuvem pública. Além disso, 53% dos entrevistados planejam adicionar ou aumentar a capacidade dos seus ambientes Kubernetes utilizando diferentes provedores de nuvem pública.
A estratégia de implementação do Kubernetes em múltiplas nuvens é impulsionada principalmente pela necessidade de reduzir a dependência tecnológica em relação a um único provedor. Ela também tem como objetivo buscar uma maior flexibilidade no gerenciamento dos custos, permitir alta disponibilidade para as aplicações e entregar capacidade para recuperação de desastres.
Além disso, este mesmo relatório revelou que as organizações estão se afastando do modelo de implementação “faça você mesmo” ou “do it yourself” (DIY).
Temos que lembrar que o Kubernetes representa apenas parte dos componentes necessários para uma perfeita entrega e implementação das aplicações. Mesmo com todos os benefícios do Kubernetes, ainda são necessários outros componentes importantes para que os contêineres entrem em operação num ambiente de produção.
Além de existirem mais de 100 distribuições Kubernetes disponíveis no mercado, também há centenas de projetos hospedados no CNCF relacionados com todos os estágios necessários para a implementação e a operação de ambientes baseados em containers: segurança, telemetria, observabilidade, registro de imagens, service mesh, service proxy, rede, e assim por diante.
Integrar estes componentes e entregar uma plataforma validada e pronta para operação é um trabalho exaustivo e caro. Além disso, estas tarefas não estão diretamente relacionadas com o propósito de negócio da maioria das empresas.
Por isso, as organizações estão cada vez mais adotando plataformas Kubernetes prontas, dedicadas ou baseadas em serviços de nuvem pública, que sejam capazes de agregar todos os componentes complementares que sejam necessários e que prestem um suporte técnico especializado e de alto nível.
4) O Kubernetes é um projeto de código aberto. Como as empresas podem se beneficiar disso?
Projetos de código aberto permitem que qualquer pessoa possa acessar, modificar e distribuir o código disponibilizado. Eles são desenvolvidos de uma forma descentralizada e colaborativa, envolvendo empresas e indivíduos ao redor do mundo.
Por isso, em geral, projetos de código aberto podem entregar novas funcionalidades e inovações com maior velocidade, quando comparado a um código proprietário. Eles também podem permitir a criação de softwares mais confiáveis pois suas revisões e correção de problemas são mais frequentes, já que mantidas por um grande grupo de colaboradores.
Como ilustração, segundo números do CNCF, apenas o projeto Kubernetes recebeu mais de 2 milhões e 700 mil contribuições e mais de 430 mil atualizações/commits de código apenas no último ano.
Grandes empresas também colaboram ativamente com as novas funcionalidades e atualizações pois muitas utilizam o Kubernetes como um projeto de “upstream” para as suas próprias soluções e distribuições de mercado. E isso acaba criando um padrão na indústria.
5) Qual a relação entre Kubernetes, DevOps e DevSecOps?
O DevOps e a segurança estão relacionados com mudanças culturais dentro da organização, pois exigem que uma grande colaboração entre os membros das equipes.
Tradicionalmente, a segurança não era um elemento considerado no desenvolvimento dos softwares. Na prática do DevSecOps, as preocupações com segurança devem ser aplicadas desde o início do ciclo de desenvolvimento do software, ou seja, desde o momento da especificação dos requerimentos da aplicação.
Garantir consistência nas atividades de colaboração do DevOps e do DevSecOps é um desafio que pode impactar diretamente na agilidade dos processos. Por isso, a automação é amplamente empregada nas etapas de desenvolvimento, testes e provisionamento das aplicações.
Existem muitas formas de implementar automação, incluindo soluções que permitem a definição e a implantação de infraestrutura através de código (IaC). No entanto, elas podem acrescentar complexidades adicionais no ciclo de desenvolvimento de software, especialmente em ambientes baseados em containers.
O Kubernetes apresenta uma enorme sinergia com o DevOps e DevSecOps pois ele possui mecanismos nativos que possibilitam a automação completa dos containers e dos elementos relacionados, tornando o ciclo de desenvolvimento mais simples, rápido, frequente e melhor gerenciado.
Além da automação, o Kubernetes acrescenta a capacidade de abstração da infraestrutura. Os desenvolvedores podem se concentrar nas funcionalidades e especificar as dependências, ações e políticas relativas à infraestrutura como uma parte do código desenvolvido, utilizando as APIs nativas do Kubernetes.
6) Com os crimes cibernéticos alcançando índices alarmantes, a segurança é uma prioridade para as empresas. Como tratar a segurança cibernética no Kubernetes?
O tratamento da segurança no Kubernetes não é diferente daquele que deve ser aplicado ao ambiente de TI como um todo. A segurança do Kubernetes esteja efetivamente integrada à política de cyber segurança das organizações.
Além disso, é preciso prover visibilidade para as equipes de segurança sobre as aplicações hospedadas em containers, procurando integrar o Kubernetes a outras soluções de cyber segurança que a empresa possa utilizar ou que cogita adquirir.
Uma ação muito importante é identificar e conter as vulnerabilidades no ambiente Kubernetes. A contenção deve começar pelo uso de imagens de fontes confiáveis, por verificações na integridade destas imagens, dificultando o acesso não autorizado a informações dos clusters e evitando o escalonamento de privilégios.
Outras ações de segurança também são importantes, como o uso hardware seguro, definição de políticas de acesso, microsegmentação de rede para impedir movimentação lateral, integração com anti-virus e sistemas IDS/IPS. A adoção de técnicas do tipo “sandbox, visando análise e resposta a incidentes também é muito recomendada.
Além disso, é importante que a empresa esteja preparada para recuperar o ambiente Kubernetes em caso de incidentes de segurança, contando com soluções que permitam a realização de backup seguro, replicação e políticas de recuperação de desastres.
7) Os containers e o Kubernetes vão substituir a tecnologia de virtualização de servidores?
Tudo indica que não, o modelo híbrido deve prevalecer. Ou seja, os ambientes baseados em virtualização de servidores continuarão coexistindo com os ambientes Kubernetes.
Como nem todas as aplicações monolíticas são adequadas ou elegíveis a transformação para uma arquitetura baseada em micro serviços, seja por custos elevados ou devido a características intrínsecas de implementação, aplicações hospedadas em servidores virtuais deverão continuar existindo por algum tempo.
Além disso, tecnologias de virtualização de servidores são amplamente utilizadas, possuem décadas de presença no mercado e são capazes de entregar um conjunto robusto e conhecido de ferramentas utilizadas para gerenciamento e segurança.
Por exemplo, um dos projetos que mais crescem no CNCF é o KubeVirt. Este projeto permite que o Kubernetes também possa gerenciar e controlar ambientes de servidores virtualizados baseados em um hypervisor KVM.
Alguns fornecedores de mercado também já disponibilizam soluções próprias que permitem a implementação e o gerenciamento de ambientes Kubernetes e virtualizados de forma simultânea.
Algo que já temos acesso há algum tempo através de serviços na nuvem pública, onde podemos realizar a implementação de serviços de computação e de Kubernetes numa mesma nuvem privada (virtual private cloud) e gerenciá-los pelo mesmo console.
8) Como será o Kubernetes no futuro? Para onde ele caminha?
O projeto Kubernetes ainda tem muito a evoluir. Talvez, em breve, o Kubernetes se torne apenas mais uma camada de abstração lógica dentro do conjunto de ferramentas disponíveis para os desenvolvedores de software.
Além disso, com o advento da Inteligência Artificial, que já está sendo amplamente incorporada aos processos de desenvolvimento de software, muitas das barreiras e dificuldades que ainda existem no Kubernetes tendem a ser superadas e abstraídas.
Assim, cabe a nós acompanharmos e estarmos atentos a estes desdobramentos.
Para evitar a perda de arquivos de backup devido a Ransomware, malware ou até mesmo ações não planejadas, é recomendado usar repositórios de backup imutáveis e a regra arquitetônica de proteção de dados 3-2-1-1-0.
Uma das opções disponíveis desde a versão 11 do Veeam Backup & Replication é utilizar um servidor Linux, aproveitando os recursos nativos de proteção de arquivos deste sistema operacional, como repositório de backup.
O Veeam Hardened Linux Repository oferece suporte aos seguintes recursos:
Imutabilidade dos arquivos: podemos especificar o período e os arquivos de backup permanecerão imutáveis. Durante esse período, os arquivos de backup não poderão ser modificados ou excluídos.
Credenciais de uso único: este é um dos pontos de segurança mais críticos. As credenciais de usuário do Linux são usadas apenas durante a implantação inicial do Veeam Data Mover. Esta operação só acontece ao adicionar o servidor Linux à infraestrutura de backup. Estas credenciais não são armazenadas na infraestrutura de backup. Mesmo que o servidor Veeam Backup & Replication esteja comprometido, o invasor não poderá obter as credenciais e conectar-se ao repositório protegido.
Instalação do Linux Ubuntu Server
A primeira etapa da instalação é selecionar o kernel “HWE”, que é o kernel “Hardware Enablement”. Se você não vir a opção de kernel HWE, então você está inicializando no modo BIOS legado. UEFI com UEFI Secure Boot ativado é recomendado:
A instalação será iniciada:
Finalizada esta etapa, selecionar o idioma desejado:
Selecione continuar sem realizar o update:
Selecione a configuração desejada para o teclado:
Selecione a opção de instalação Ubuntu server:
Selecione as opções de rede:
Se for necessário, configure o proxy de rede:
Aguarde a verificação, mantenha os valores default e clique em “Done”:
Selecionar a opção Custom Storage Layout:
Vamos ter que montar manualmente as partições, conforme as melhores práticas do CIS Benchmarks for Ubuntu Linux 20.04 LTS STIG:
Selecione freespace e adicione uma partição GPT:
Se esse hardened repository tornar parte de um repositório Scale-out Backup Repository, haverá dados temporários em /home/<username>/.
Portanto, criamos esta partição com 25 GB de tamanho. O ponto de montagem pode ser selecionado diretamente no menu suspenso. O sistema de arquivos permanece inalterado em ext4:
Para a partição /tmp, o caminho deve ser especificado manualmente:
O mesmo para /var:
O mesmo para /var/log:
O mesmo para /var/log/audit:
O mesmo para /var/tmp:
Por fim, adicione o sistema de arquivos raiz (“/”) sem especificar o tamanho. Ele ocupará todo o espaço livre disponível:
No final, devemos ter a seguinte configuração de partição:
A lista de “devicesdisponíveis” está agora reduzida ao volume de dados de backup. Este deve ser montado em /mnt/backup e usar o sistema de arquivos XFS:
Selecionar XFS e /mnt/backup:
Clicar em Done:
Aparecerá o aviso abaixo. Selecionar Continue:
Preencher os campos. Criar um usuário. Neste exemplo, criamos o usuário “veeamadmin”:
Your name: XXXXX
Your server´s name: vm05-ubuntu-vhr
Pick a username: veeamadmin
Choose a password: XXXXX
Pule o upgrade por enquanto, selecionando Continuar:
O usuário root não possui uma senha padrão no Ubuntu (outras distribuições podem exigir uma senha root). Isso significa que o root não consegue fazer login em uma máquina Ubuntu. O servidor OpenSSH é necessário para adicionar o servidor ao Veeam Backup & Replication como um repositório protegido. Habilite essa opção e continue:
Como queremos um Ubuntu Linux mínimo, mantemos tudo desmarcado na seleção de software (padrão):
A instalação será retomada. O processo demora alguns minutos:
Temos que aguardar que apareça a opção Reboot Now:
Logar com o usuário criado (veeamadmin):
Verifique que a conectividade está ok. Não devem ocorrer mensagens com “DUP. Você pode parar o “ping” pressionando CTRL+C.
ping 8.8.8.8
Obter e anotar o endereço IP do servidor
ip a
10.80.50.109
Finalizada a instalação do Ubuntu neste momento
Garantindo acesso de leitura e escrita ao usuário
Vamos agora dar permissão de escrita para o veeadmin no diretório de backup, para que possamos realizar a instalação dos serviços Veeam.
sudo -s
groupadd backupadmins
usermod -aG backupadmins veeamadmin
chown veeamadmin:backupadmins /mnt/backup
chmod 2775 /mnt/backup
ls -al
Configuração do Veeam Backup & Replication
Vamos agora ir até o console do VBR server para associar o servidor Ubuntu ao inventário.
Ir até Backup Infrastructure, selecionar Managed Servers e clicar em Add Server.
Selecionar Linux.
Digitar o endereço IP do novo servidor Linux:
Adicione as credenciais.
Importante: selecionar a opção “single-use credentials for hardened repository”:
Insira o usuário e a senha criada no momento da instalação do servidor Ubuntu:
Clicar em Next:
Clicar em Yes:
Selecionar Apply:
O VBR relizará a instalação dos serviços de transporte e de controle de imutabilidade:
Clicar em Next. Verificar o sumário e clicar em Finish:
O servidor Ubuntu deverá aparecer na relação dos “Managed Servers”:
Vamos agora adicionar um novo Backup Repository. Selecionar a opção Backup Repositories e clicar em Add Repository:
Neste exemplo, estamos utilizando uma VM (não recomendado para ambientes de produção). Por isso, vamos escolher a opção Direct Attached Repository:
Selecionar a opção Linux (Hardened Repository):
Atribuir um nome para este repositório. Por exemplo: Ubuntu-VHR:
Selecionar o servidor e clicar em Populate. Selecionar o caminho /mnt/backup/:
A opção Path to Folder será preenchida com o caminho /mnt/backup/
Clicar em Populate e conferir a volumetria.
Selecionar a opção Fast Cloning on XFS Volumes.
Selecionar o período de imutabilidade. Por exemplo 07 dias. Selecionar a quantidade de tarefas concorrentes que este repositório tratará. Por exemplo, selecionas 04 tarefas concorrentes
Selecionar o Mount Server desejado. Vamos manter o padrão:
Rever as configurações e clicar em Apply:
O repositório de backup será criado:
O repositório deve aparecer na relação dos disponíveis para uso:
Criando um job de backup para teste
Vamos criar um job de backup para teste:
Selecionar o Hardened Repository criado:
Clicar em Next. Criar um Schedule:
Selecionar “Run the job when I click Finish”. Clicar em Finish. Acompanhar o job finalizar:
O tentarmos apagar os arquivos de backup (full ou incremental) ocorre um erro pois o repositório é imutável:
Se analisarmos os arquivos e diretórios de backup:
cd /mnt/backup/Ubuntu-VHR-Test_1
ls
Temos os arquivos de backup full (.vbk), incrementais (.vib) e os metadados (vbm):
Se tentarmos remover um arquivo, mesmo com permissão elevada, a operação não é permitida:
Fortalecendo a segurança
Até este momento, temos o seguinte cenário:
Uma instalação mínima do Ubuntu com inicialização UEFI Secure;
Apenas uma conta de usuário com permissões sudo completas e a conta root está bloqueada (sem senha)
A conta de usuário “veeamadmin”, que foi criada durante o processo de instalação, tem permissões root completas (administrativas) porque é membro do grupo “sudo”.
“sudo” é o comando que permite executar um comando como root (administrador no Linux). Cada membro do grupo “sudo” pode executar todos os comandos com “sudo” no Ubuntu.
Ao instalar o hardened repositório, são necessárias permissões “sudo” ou “su”. Após a instalação, “sudo” ou “su” não são mais necessários a partir da V12. “su” (usuário substituto) neste contexto significa que um usuário pode inserir a senha root para se tornar root. Conforme mencionado anteriormente, o root atualmente não possui senha. Isso significa que não se pode usar “su” para mudar para o usuário root.
No entanto, ao remover o usuário “veeamadmim” posteriormente do grupo “sudo”, não há mais usuário administrativo/root utilizável disponível.
Nem mesmo um simples comando de “shutdown” ou “reboot” seria possível.
A recomendação da Veeam é atribuir para o usuário “veeamadmin” apenas comando “su” deshutdown e reboot.
Para isso, é preciso copiar e colar os comandos abaixo:
Mesmo que alguém descubra a senha do usuário “veeamadmin” e obtenha acesso ao console local (ou SSH, se habilitado), ainda assim não poderá causar nenhum dano. As permissões não poderão ser elevadas para root por meio de um comando “su” ou “sudo”.
O sistema está protegido e os backups passam a ser armazenados em um repositório imutável, criando uma camada adicional de proteção dentro da política de cybersegurança da organização.
This video presents a step-by-step guide to upgrading the Veeam Data Platform to version 12.1 and the Veeam Service Provider Console to version 8.0. I hope it can be helpful!
Over the last few years, the time to execute ransomware attacks dropped 94%; now, criminals take, on average, just 3.85 days to deploy a ransomware attack.
On the other side, according to the “Veeam Ransomware Trends – 2023 Global Report”, recovering the affected environment after a ransomware incident takes an average of 3.3 weeks of work, equivalent to 136 business hours of business downtime.
Along with exploiting application vulnerabilities, hackers heavily utilize client-side compromise techniques to deploy ransomware.
In each attack, criminals must take well-known steps to reach their targets. Based on this, models were created to identify and prevent cyber intrusion activity. One of the most famous is the Cyber Kill Chain, developed by Lockheed Martin.
For this purpose, we will focus on four stages of a client-side attack: delivery of exploitation, installation, command-and-control, propagation, and actions on the objective.
Client-side attacks through phishing, exploitation of public-facing applications, and use of valid accounts are the primary vectors for malware delivery.
After device exploitation, initial access, malware installation, and gaining command and control over the user’s endpoint, the cyber attacker must discover, recognize, and access sensitive data and another high-value asset.
To achieve this, the hacker needs higher-level permission to access these systems. This attack stage is called Privilege Escalation. The most common way to escalate the privileges is to exploit software vulnerabilities like application errors, operating systems characteristics, and kernel security weaknesses. Active Directory (AD) privilege escalation vulnerabilities allow standard domain users to impersonate administrators.
The subsequent action for the hacker is to discover valuable targets and propagate the attack using Lateral Movement, a set of techniques criminals use to enter and control systems connected to a network.
In many cases, the attacker uses existing and legitime tools installed in the environment to reduce the footprint and evade detection. This type of action is also called Living off the Land (LotL).
Some of the legitime tools used by criminals during the lateral movement are:
RDP – Remote Desktop.
Powershell.
SMB / psexec.
WinRM – Windows Remote Management.
WMIC – Windows Management Instrumentation.
After the attacker lands on the target, the first action is achieving access persistency across systems activities like restarts, credentials changes, or other interruptions.
Once persistence is guaranteed on the target, attackers apply actions to turn off security tools and other protection services, like backup services. Event logs are cleared, and the criminals perform data exfiltration using compression, encryption, and network protocols. The exfiltrated data is often used in the financial extortion phase or traded on the dark web.
Finally, sensitive data is encrypted, business operations are impacted, and the extortion phase of the ransomware attack begins.
Ransomware encryption speed According to a real test scenario conducted by Surge/Splunk, the time to encrypt 98.561 files placed in 100 directories of a Windows Server 2019 host is abot 5:50 minutes. LockBit is the fastest variant because it only encrypts 4KB of each file, rendering it unusable.
Extorsion Phase The extortion can be triple. If the ransom is not paid for recovering the encrypted and exfiltrated data, criminals can launch a distributed denial of service (DDoS) attack against the organization’s services.
As an additional measure to prevent the organization from recovering its environment and data, backup repositories are also targets for criminals. They encrypt the backup files to force the ransom payment.
According to the Veeam report, the backup repositories are fully or partially affected in 75% of attacks.
Once an attack is successful, the data cannot be recovered entirely, whether due to non-payment of ransom and inability to restore all data or by incomplete/failed restoration, even with the ransom payment and receiving a decryption key.
Due to the increase in the number and frequency of ransomware attacks over the past years, insurance has become more expensive, with increased premiums and coverage benefits reduced.
NIST Cybersecurity Framework
The good news is that we can deploy defense frameworks and techniques for each stage of this type of attack.
The NIST (National Institute of Standards and Technology) Ransomware Framework Profile identifies and maps security objectives from the NIST Cybersecurity Framework to security capabilities and measures that can be used to manage the risk of ransomware events.
A Public Draft of the NIST Cybersecurity Framework 2.0 for public comment is expected to be published in early 2024.
The NIST Cybersecurity Framework Core comprises cybersecurity activities, desired outcomes, and relevant references across critical sectors.
The six Framework Core functions are Govern, Identify, Protect, Detect, Respond, and Recover.
These functions are not meant to be serialized or intended to achieve a static end state. Instead, these functions must be applied concurrently and continuously to create an operational culture that can handle the dynamic nature of cyberattacks.
During a ransomware event, organizations have little time to mitigate or remediate the impact, restore their systems, recover their data, and communicate with their partners and customers. Therefore, organizations must be ready to deal with it.
Let’s verify and review the NIST Framework Core functions:
Govern
Establish and monitor the organization’s cybersecurity risk management strategy, expectations, and policy. It provides outcomes to inform how an organization will achieve and prioritize the outcomes of the other five Functions in the context of its mission and stakeholder expectations.
This function directs an understanding of organizational context, the establishment of cybersecurity strategy and supply chain risk management, roles, responsibilities, authorities, policies, processes, and procedures, and the oversight of cybersecurity strategy.
Some tools help to implement and complement this function, such as;
Governance, Risk, and Compliance tools
Disaster Recovery Planning
Identity Compliance and Identity Lifecycle Management
Data Governance and Modeling
Identify
Understanding the business context, the resources that support critical functions, and the related cybersecurity risks enables an organization to focus and prioritize its efforts. It is necessary to have hardware and software inventories to track information such as name and version, devices where it is currently installed, version and last patch date, and current known vulnerabilities.
It is also necessary to detect and prioritize the treatment of known and unknown vulnerabilities from the most severe and critical to the least urgent, based on a risk score/scale definition. Many solutions can detect, classify, and filter the environment’s vulnerabilities based on the degree of risk and associating it with CVEs (Common Vulnerabilities and Exposures) reports.
Some observability tools can map the relationship and communication between applications and systems, enabling the definition of network micro-segmentation policies within a zero-trust strategy.
At the same time, it is also necessary to deploy response and recovery plans.
It is fundamental to contain or limit the impact of a threat. Using identity management, authentication, and access control techniques is crucial to mitigate credential compromise. Multifactor Authentication (MFA) adds an extra layer of protection, especially for remote access. The constant review of granted access privileges and the least privileges approach is highly recommended.
Protect
It is fundamental to contain or limit the impact of a threat. Using identity management, authentication, and access control techniques is crucial to mitigate credential compromise. Multifactor Authentication (MFA) adds an extra layer of protection, especially for remote access. The constant review of granted access privileges and the least privileges approach is highly recommended.
Regularly auditing account logon and logon events like RDP, psexec, Windows Management Instrumentation, WinRM, and others are also important. It is necessary to create a baseline of configurations and best practices aligned with the organization’s security policy and perform audit and remediation actions over any deviation.
Keep relevant systems fully patched. Run scheduled checks to identify available patches and install these as soon as possible. Allow installation and execution of official/homologated apps only.
Conducting training and periodic awareness of the teams is essential since most attacks are made possible by users who carry out insecure practices.
Network micro-segmentation can limit the Lateral Movement, preventing ransomware from proliferating and reaching potential target systems. It is necessary to allow only strictly necessary communications between systems and applications.
Organizations must deploy Distributed Denial of Service (DDoS) protection systems and services in the network infrastructure.
Data security is crucial as it is necessary to guarantee its availability and reduce the ransomware’s impact. A good approach is to use the 3-2-1-1-0 rule for data security, which also includes maintaining an offsite backup, one backup copy offline, and ensuring verified backups that can be restored without errors and malware.
As backup repositories are also targets for ransomware, it is vital to use immutable backup repositories. The immutability feature protects backup files from overwriting, accidental deletion, ransomware attacks, and malicious insider actions.
Organizations can deploy replication between systems and sites to ensure high availability and lower Recovery Point Objective (RPO) and Recovery Time Objective (RTO) targets. Implementing asynchronous, near sync, and synchronous replication strategies is possible depending on the need of each type of application.
It is also essential to ensure the backup repository’s security/integrity and periodically test the disaster recovery capability by measuring the SLA performance through verification tests. The response and recovery plans must be updated and tested, including systems redundancy and disaster recovery sites.
Detect
It is necessary to develop and implement appropriate activities and tools to identify the occurrence of a cybersecurity event. To avoid phishing, it is essential to detect anomalous activity using Endpoint Detection and Response (EDR) systems, Next-generation Antivirus (NGAV), DNS protection, and email/web security solutions.
Activity monitoring, unauthorized connection alerts, and detection of unknown devices might detect insider threats, insecure staff practices, or compromised credentials and thwart potential ransomware events.
Network traffic analysis might detect intrusions and initiate protective actions automatically against data exfiltration or malicious connections. It is also necessary to detect communication deviations to the network baseline, like command-and-control traffic or a non-standard connection between a user endpoint and the Active Directory system.
Data Loss Prevention (DLP) systems can help to block data exfiltration.
Distributed Firewalls/IPS/IDS can detect and block malware installation. We can apply specific signatures to distributed IDS and IPS to prevent known vulnerabilities from being exploited during an attack. With this, the operation teams can protect their workloads and gain time to apply paths and corrections. It helps to protect the east-west and north-south network traffic.
Security Information and Event Management (SIEM) systems assist in the early detection of ransomware and aid in understanding how ransomware may propagate through the environment.
Security policies must be implemented and revised in all systems to improve the detection actions over time. Organizations must constantly reinforce the detection processes because the tactics used in ransomware attacks are continuously evolving.
Respond and Recovery
The response must be adequate if the threat becomes a security incident.
The first action is triggering a response plan.
Identifying the root cause is the first action. Isolating the infected device or application is required to stop the ransomware and minimize damage, preventing the infection from spreading to other systems and minimizing the impact on business continuity.
It is necessary to connect to the affected asset and execute commands, such as viewing/terminating a process, checking a file, collecting artifacts for analysis of unauthorized access, and other actions. Some techniques allow you to quickly delete files on a device or across your entire environment.
According to the severity of the incident, recovery procedures are performed to restore affected systems and assets. These procedures can be applied only to a specific system, or initiating more extensive recovery actions involving multiple systems and other sites may be necessary.
In any case, the recovery plan must be up to date and contain at least the following information:
People and teams involved in the recovery tasks.
The communication process – internal and external.
Critical applications and the applications recovery order.
Target SLA, RPO, and RTO per application.
The locations/infra/services where applications and data will be recovered. • Details about all infrastructure, applications, software, networking, cloud services, information about technical support contracts, etc.
It is essential to determine whether the backup or replica versions are also affected or might reintroduce malware in the environment. IT and security teams should perform validation in an “air-gapped” recovery environment, such as a sandbox.
In this isolated environment, starting applications from the backup or replicas must be possible. Usually, the validation is performed through a next-generation antivirus integration and custom scripts. After the analysis, if the application is operational and malware-free, it should be deployed back to the production environment.
While these measures are critical to mitigating ransomware attacks, especially those launched from users’ endpoints, nothing guarantees 100% protection against ransomware.
Paying the ransom is not recommended because it does not guarantee a solution to the problem. If the ransom is paid, it proves to the cybercriminals that ransomware is a reward crime, and they will continue their activity, looking for new ways to exploit systems.
The best alternative is:
Deploy a cybersecurity framework in the organization;
Keep up-to-date response and recovery plans;
Implement, as the last barrier to ensure business continuity and data loss, an effective backup and disaster recovery architecture/solution.
How can Veeam help?
The Veeam platform can support and maintain the five functions of the NIST Cybersecurity Framework 2.0. Each platform’s capabilities are mapped with these functions in the figure below.
In other words, if you already have or intend to acquire the Veeam platform, you will have already taken a first step towards adopting the NIST Cybersecurity Framework 2.0
I hope you got some helpful information from this post!
Veeam made the Service Provider Console version 7 available in FY23H1. It is essential to upgrade asap as many benefits and improvements have been added.
Here I share the step-by-step for upgrading VSPC v6 to v7.
Important: If you run Veeam Service Provider Console version 5.0, you must first perform an upgrade of all Veeam Service Provider Console components to version 6.0. For details on upgrading Veeam Service Provider Console to version 6.0, see Upgrading Veeam Service Provider Console. For details on upgrading management agents to version 6.0, see Upgrading Management Agents.
3. Mount ISO and start Wizard
Mount the installation image using disk image emulation software or burn the downloaded image to a CD/DVD. If you are installing Veeam Service Provider Console on a VM, use built-in tools of the virtualization management software to mount the installation image to the VM.
Run the Setup.exe file from the image to launch the setup splash screen.
On the splash screen, click the Upgrade tile to launch the Veeam Service Provider Console Setup wizard.
4. At the License Agreements step of the wizard, read and accept the Veeam license agreement, Veeam licensing policy, 3rd party components license agreement, and required software license agreement.
You cannot continue the installation if you do not accept the license agreement terms.
5. Review the components to upgrade at the Upgrade step of the wizard.
6. Wait for the System Configuration Check to validate. If any components required for installation are missing, follow the instructions before proceeding.
7. At the wizard’s Service Account step, specify the password for the account under which Veeam Service Provider Console services run.
8. Configure the settings in the Usage Report step of the wizard. If you want the latest Veeam Service Provider Console to automatically check for managed Veeam product updates, select the Allow Veeam Service Provider Console to check the versions of Veeam products check box. Select the Update license automatically check box to install new licenses automatically when you renew or expand your contract. If you enable the automatic license update and therefore enable usage reporting, you will double the number of workloads by which you can exceed your installed license
9. At the Ready to Install step of the wizard, click Install to begin Veeam Service Provider Console upgrade.
10. Check version post-update
11. Next Steps:
Veeam Service Provider Console and its management agents must run the same software version. Otherwise, they cannot properly communicate with each other. When you upgrade or migrate to a new version of Veeam Service Provider Console, or install an update, you also need to upgrade management agents running on client computers
Make sure all management agents are up-to-date. For details on management agents upgrade, see section Upgrading Management Agents of the Veeam Service Provider Console Guide for Service Providers.
If necessary, upgrade managed Veeam backup agents. For details, see section Upgrading Veeam Backup Agents of the Veeam Service Provider Console Guide for Service Providers.
Collect data from Veeam Cloud Connect and Veeam Backup & Replication servers. By default, Veeam Service Provider Console management agents send data to Veeam Service Provider Console every hour, or when specific events, such as backup job failure, occur. If required, you can initiate unscheduled data collection from machines that run management agents. These can be machines hosting Veeam backup agents, Veeam ONE, Veeam
I hope this procedure can be useful for Veeam Cloud Service Provider Partners.
Hey! Microsoft SQL Server backends some of the organizations’ most critical applications. Any loss of data or even the inability to fully recover this environment can cause catastrophic damage to the business.
Veeam offers several options to simultaneously protect the most business-critical applications and Microsoft SQL Server environments.
Starting with version 12 of Veeam Backup & Replication, the Veeam Plug-in for Microsoft SQL Server was made available.
This plug-in natively integrates with Microsoft SQL Server Management Studio, the Microsoft SQL Server management tool used by organizations’ DBAs (database administrators).
With this, DBAs now have complete control over the database backup and recovery processes, with zero friction in relation to their daily activities and an integrated manner with the organization’s data protection policy.
Therefore, the same Veeam platform protects virtual servers, Kubernetes clusters, physical servers, notebooks, desktops, and public cloud services.
Some differentiators of the Veeam Plug-in for Microsoft SQL Server:
• Simple and intuitive: only three buttons are added to the Microsoft SQL Server Management Studio menu;
• Scalability and performance: through the use of the SQL Virtual Device Interface (VDI), the plug-in supports up to 2,000 databases per SQL server and up to 10,000 databases per backup server;
• Scheduling full backups, differential backups, and transaction log backups using the tool’s native SQL Agent Job;
• With just a few clicks, it allows complete recovery or just specific database transactions;
• Integration with SQL Always-ON, protecting clusters or groups of servers;
• Backup of SQL backups, aiming for Disaster Recovery.
This video exemplifies a granular recovery operation the Veeam Plug-in for SQL provides to Microsoft SQL Server DBAs.
Container runtimes are fundamental components of Kubernetes. It is responsible for managing the execution and lifecycle of containers, and it is necessary to choose and install a container runtime into each worker node in the Kubernetes cluster to run PODs.
Container runtimes can be categorized into:
• High-level container runtimes: CRI-O, containerd and Docker.
• Low-level container runtimes: runc and crun.
• Sandboxed and virtual container runtimes: runsc (from gVisor) and kata-runtime/the-runtime (from Kata Containers).
The Container Runtime Interface (CRI) is the specification in charge of the communication between the kubelet and the high-level runtimes. The CRI defines gRPC APIs that allow the kubelet to interact as a client with different runtimes. CRI performs an abstraction layer for high-level runtimes.
The high-level runtimes use a lower-level container runtime to run and manage the components required to deploy and operate containers. Open Container Initiative (OCI) specifications allow the integration of different high- and low-level runtimes.
The OCI Runtime Specification is one of the three specifications defined by OCI. It describes the requirements for the runtime environment, the interfaces for containers, and the minimum set of functionalities that high and low-level runtimes must provide to be considered OCI compliant.