Netskope nombrado Líder en el Cuadrante Mágico de Gartner® 2024™ para Security Service Edge. Obtenga el informe

cerrar
cerrar
  • Por qué Netskope chevron

    Cambiar la forma en que las redes y la seguridad trabajan juntas.

  • Nuestros clientes chevron

    Netskope atiende a más de 3.000 clientes en todo el mundo, entre ellos más de 25 de las 100 empresas de Fortune

  • Nuestros Partners chevron

    Nos asociamos con líderes en seguridad para ayudarlo a asegurar su viaje a la nube.

Aún más alto en ejecución.
Aún más lejos en visión.

Sepa por qué 2024 Gartner® Cuadrante Mágico™ nombró a Netskope Líder para Security Service Edge por tercer año consecutivo.

Obtenga el informe
Netskope Nombrado líder en el gráfico 2024 Gartner® Magic Quadrant™ for Security Service Edge para Menu
Ayudamos a nuestros clientes a estar preparados para cualquier situación

Ver nuestros clientes
Woman smiling with glasses looking out window
La estrategia de venta centrada en el partner de Netskope permite a nuestros canales maximizar su expansión y rentabilidad y, al mismo tiempo, transformar la seguridad de su empresa.

Más información sobre los socios de Netskope
Group of diverse young professionals smiling
Tu red del mañana

Planifique su camino hacia una red más rápida, más segura y más resistente diseñada para las aplicaciones y los usuarios a los que da soporte.

Obtenga el whitepaper
Tu red del mañana
Presentamos la Netskope One Plataforma

Netskope One es una Plataforma nativa en la nube que ofrece servicios convergentes de seguridad y redes para hacer posible su transformación SASE y de confianza cero.

Learn about Netskope One
Abstracto con iluminación azul
Adopte una arquitectura de borde de servicio de acceso seguro (SASE)

Netskope NewEdge es la nube privada de seguridad más grande y de mayor rendimiento del mundo y ofrece a los clientes una cobertura de servicio, un rendimiento y una resiliencia incomparables.

Más información sobre NewEdge
NewEdge
Netskope Cloud Exchange

Cloud Exchange (CE) de Netskope ofrece a sus clientes herramientas de integración eficaces para que saquen partido a su inversión en estrategias de seguridad.

Más información sobre Cloud Exchange
Vídeo de Netskope
  • Servicio de seguridad Productos Edge chevron

    Protéjase contra las amenazas avanzadas y en la nube y salvaguarde los datos en todos los vectores.

  • Borderless SD-WAN chevron

    Proporcione con confianza un acceso seguro y de alto rendimiento a cada usuario remoto, dispositivo, sitio y nube.

  • Secure Access Service Edge chevron

    Netskope One SASE proporciona una solución SASE nativa en la nube, totalmente convergente y de un único proveedor.

La plataforma del futuro es Netskope

Intelligent Security Service Edge (SSE), Cloud Access Security Broker (CASB), Cloud Firewall, Next Generation Secure Web Gateway (SWG) y Private Access for ZTNA integrados de forma nativa en una única solución para ayudar a todas las empresas en su camino hacia el Servicio de acceso seguro Arquitectura perimetral (SASE).

Todos los productos
Vídeo de Netskope
Next Gen SASE Branch es híbrida: conectada, segura y automatizada

Netskope Next Gen SASE Branch converge Context-Aware SASE Fabric, Zero-Trust Hybrid Security y SkopeAI-Powered Cloud Orchestrator en una oferta de nube unificada, marcando el comienzo de una experiencia de sucursal completamente modernizada para la empresa sin fronteras.

Obtenga más información sobre Next Gen SASE Branch
Personas en la oficina de espacios abiertos.
Diseño de una arquitectura SASE para Dummies

Obtenga un ejemplar gratuito del único manual que necesitará sobre diseño de una arquitectura SASE.

Obtenga el eBook
Cambie a los servicios de seguridad en la nube líderes del mercado con una latencia mínima y una alta fiabilidad.

Más información sobre NewEdge
Lighted highway through mountainside switchbacks
Habilite de forma segura el uso de aplicaciones de IA generativa con control de acceso a aplicaciones, capacitación de usuarios en tiempo real y la mejor protección de datos de su clase.

Descubra cómo aseguramos el uso generativo de IA
Habilite de forma segura ChatGPT y IA generativa
Soluciones de confianza cero para implementaciones de SSE y SASE

Más información sobre Confianza Cero
Boat driving through open sea
Netskope logra la alta autorización FedRAMP

Elija Netskope GovCloud para acelerar la transformación de su agencia.

Más información sobre Netskope GovCloud
Netskope GovCloud
  • Recursos chevron

    Obtenga más información sobre cómo Netskope puede ayudarle a proteger su viaje hacia la nube.

  • Blog chevron

    Descubra cómo Netskope permite la transformación de la seguridad y las redes a través del borde de servicio de seguridad (SSE)

  • Eventos y Talleres chevron

    Manténgase a la vanguardia de las últimas tendencias de seguridad y conéctese con sus pares.

  • Seguridad definida chevron

    Todo lo que necesitas saber en nuestra enciclopedia de ciberseguridad.

Podcast Security Visionaries

On Patents, Trolls, and Innovation
In this episode host Emily Wearmouth chats with Suzanne Oliver, an intellectual property expert, and Krishna Narayanaswamy, co-founder and CTO of Netskope, about the world of patents.

Reproducir el pódcast
On Patents, Trolls, and Innovation
Últimos blogs

Lea cómo Netskope puede hacer posible el viaje hacia la Confianza Cero y SASE a través de las capacidades del borde de servicio de seguridad (SSE).

Lea el blog
Sunrise and cloudy sky
SASE Week 2023: ¡Su viaje SASE comienza ahora!

Sesiones de repetición de la cuarta SASE Week.

Explorar sesiones
SASE Week 2023
¿Qué es Security Service Edge (SSE)?

Explore el lado de la seguridad de SASE, el futuro de la red y la protección en la nube.

Más información sobre el servicio de seguridad perimetral
Four-way roundabout
  • Empresa chevron

    Le ayudamos a mantenerse a la vanguardia de los desafíos de seguridad de la nube, los datos y la red.

  • Liderazgo chevron

    Nuestro equipo de liderazgo está firmemente comprometido a hacer todo lo necesario para que nuestros clientes tengan éxito.

  • Soluciones para clientes chevron

    Le apoyamos en cada paso del camino, garantizando su éxito con Netskope.

  • Formación y certificación chevron

    La formación de Netskope le ayudará a convertirse en un experto en seguridad en la nube.

Apoyar la sostenibilidad a través de la seguridad de los datos

Netskope se enorgullece de participar en Vision 2045: una iniciativa destinada a crear conciencia sobre el papel de la industria privada en la sostenibilidad.

Descubra más
Apoyando la sustentabilidad a través de la seguridad de los datos
Pensadores, constructores, soñadores, innovadores. Juntos, ofrecemos soluciones de seguridad en la nube de vanguardia para ayudar a nuestros clientes a proteger sus datos y usuarios.

Conozca a nuestro equipo
Group of hikers scaling a snowy mountain
El talentoso y experimentado equipo de servicios profesionales de Netskope proporciona un enfoque prescriptivo para su exitosa implementación.

Más información sobre servicios profesionales
Servicios profesionales de Netskope
Asegure su viaje de transformación digital y aproveche al máximo sus aplicaciones en la nube, web y privadas con la capacitación de Netskope.

Infórmese sobre Capacitaciones y Certificaciones
Group of young professionals working

Una mirada a las buenas prácticas en el mundo real de AWS: registros

Sep 23 2021

Introducción

Best practices for securing an AWS environment have been well-documented and generally accepted, such as AWS’s guidance. However, organizations may still find it challenging on how to begin applying this guidance to their specific environments.

  • Which controls should be applied out-of-the-box vs. customized?
  • What pitfalls exist in implementing the various controls or checks?
  • How do you prioritize remediation of the “sea of red” violations?

In this blog series, we’ll analyze anonymized data from Netskope customers that include security settings of 650,000 entities from 1,143 AWS accounts across several hundred organizations. We’ll look at the configuration from the perspective of the best practices, see what’s commonly occurring in the real world and:

  • Discuss specific risk areas that should be prioritized
  • Identify underlying root causes and potential pitfalls
  • Focus on practical guidance for applying the Benchmark to your specific environment

This blog post focuses on IAM security controls related to logging. Based on the Netskope dataset analyzed, we will highlight four opportunities to improve security:

  1. Enable VPC flow logs: 81% of VPCs do not have VPC flow logging enabled, which will hinder incident response and investigations.
  1. Encrypt CloudTrail logs at rest: 91% of CloudTrail logs are not encrypted at rest. Encryption at rest supports data compliance controls and is easy to do.
  1. Ensure S3 bucket access logging is enabled for CloudTrail buckets: 41% of CloudTrail buckets do not have server access logging enabled. Logging should be enabled for all CloudTrail S3 buckets.
  1. Ensure CloudTrail logs are integrated with CloudWatch or a SIEM: 54% of CloudTrails are not integrated with CloudWatch. These should be reviewed to ensure they are integrated with a production log search service or SIEM.

Logging

These nine technical best practices involve logging configuration, including AWS CloudTrail, bucket access logging, and VPC flow logs. They were analyzed against 1,485 CloudTrails, 11,101 VPCs, and 16,281 keys across 1,143 accounts in the Netskope customer dataset.

#Best Practice# Violations%
1Ensure CloudTrail is enabled in all regions393.4
2Ensure CloudTrail log file validation is enabled27118.2
3Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible20.13
4Ensure CloudTrail trails are integrated with CloudWatch Logs79953.8
5Ensure AWS Config is enabled in all regions1049.1
6Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket61041.1
7Ensure CloudTrail logs are encrypted at rest using AWS KMS CMKs1,35891.4
8Ensure rotation for customer created CMKs is enabled3,33820.5
9Ensure VPC flow logging is enabled in all VPCs9,01581.2

1. CloudTrail enabled in all regions

Background: CloudTrail should be enabled for all regions to ensure complete activity logging is available, including activity in unused regions is detected.

Data: In this dataset, 39 accounts (3.4%) do not have a CloudTrail enabled for all regions.

Analysis: This control is crucial as it is a prerequisite for visibility into having logging enabled in the first place in all regions. Any violations should be immediately remediated.

Controls: 

  • Detection/Audit
    • CloudTrail should be enabled for all regions and regular, automated checks on CloudTrail configurations should be done to enforce this setting.
    • The CloudTrail configuration setting, IsMultiReegionTrail, can be checked via CLI:

      aws cloudtrail describe-trails

    • AWS Config has a rule that will also detect if CloudTrail is not enabled for all regions.
  • Prevention/Mitigation
    • The CloudTrail setting, IsMultiRegionTrail, can be configured via CLI:

      aws cloudtrail update-trail

2. CloudTrail log file validation

Background: A digitally-signed hash of each CloudTrail log can be created on the same S3 bucket where the CloudTrail logs are stored. This is invaluable in ensuring the integrity of the logs and determining if a log was changed or deleted after CloudTrail wrote the log. Enable file validation on all logs to provide additional integrity checking of CloudTrail logs.

Data: 271 out of 1,485 CloudTrail logs (18%) do not have file validation enabled.

Analysis: Log file validation is easy to turn on and should be enabled for all CloudTrail logs.

Controls: 

  • Detection/Audit
    • The CloudTrail log file validation setting, LogFileValidationEnabled, can be checked via CLI:

      aws cloudtrail describe-trails

    • AWS Config has a rule that will also detect if log file validation is not enabled.
  • Prevention/Mitigation
    • To set the CloudTrail setting, LogFileValidationEnabled, use the CLI:

      aws cloudtrail update-trail

    • One can also validate log files for a specified period of time, on demand with this CLI command:

      aws cloudtrail validate-logs

3. CloudTrail private bucket

Background: CloudTrail logs are stored in an S3 bucket, which should not be publicly accessible.

Data: In this dataset, two out of 1,485 CloudTrail buckets are public (0.13%).

Analysis: There is only a very small percentage of CloudTrail buckets that are public. However, remediating the two public buckets is critical as the CloudTrail logs are at risk of being readable or possibly writable publicly, which leaks sensitive information and puts log integrity at risk.

Controls: 

  • Prevention/Mitigation
    • To mitigate a public CloudTrail bucket, apply the Public Access Block, which will ensure that the bucket is not only private but will prevent it from accidentally being changed to public by blocking modification of the bucket policies or ACLs.
    • The Console and CLI provide easy ways to set the Public Access Block setting:

      aws s3api put-public-access-block

4. CloudTrail integrated with CloudWatch

Background: To provide better searching, metrics, and monitoring alerts, CloudTrail should be integrated with CloudWatch or a product such as a SIEM.

Data: 799 out 1,485 CloudTrails (53.8%) are not integrated with CloudWatch. 

Analysis: About half of the CloudTrails are not integrated with CloudWatch. If CloudWatch is the standard service used for metrics and alarms, then these CloudTrails should be remediated immediately. If an alternative product, such a SIEM, is the standard, then there are mitigating controls, and this control can be deprioritized.

Controls: 

  • Detection/Audit
    • CloudWatch configuration for CloudTrails can be checked via CLI:

      aws cloudtrail describe-trails

    • AWS Config has a rule to check for CloudTrail configuration with CloudWatch.
  • Prevention/Mitigation
    • To configure CloudTrail to integrate with CloudWatch log groups, use the CLI:

      aws cloudtrail update-trail

5. AWS Config enabled in all regions

Background: AWS Config can detect common misconfigurations and also is the basis of AWS compliance findings in AWS SecurityHub. It should be enabled in all regions.

Data: 104 out of 1,143 accounts (9.1%) do not have AWS Config enabled for all regions.

Analysis: AWS Config should be enabled for all regions in every account.

Controls: 

  • Detection/Audit
    • Ensuring that AWS Config is enabled involved 3 checks which can be done via CLI:

      aws configservice describe-delivery-channels

      aws configservice describe-configuration-recorders

      aws configservice \ describe-configuration-recorder-status
  • Prevention/Mitigation
    • To turn on AWS Config with the CLI:

      aws configservice put-configuration-recorder

      aws configservice put-delivery-channel

6. CloudTrail bucket has access logging enabled

Background: S3 access logging should be enabled on the CloudTrail bucket to ensure an audit trail exists for all accesses to this sensitive bucket.

Data: 610 out of 1,485 CloudTrail buckets (41.1%) do not have S3 server access logging enabled. 

Analysis: Without server access logging, unexpected access to or modification of the CloudTrail logging bucket may not be detected. This should be remediated immediately.

Controls: 

  • Detection/Audit
    • The logging status of a bucket can be checked via CLI:

      aws s3api get-bucket-logging

    • AWS Config will also check whether S3 bucket logging is enabled.
  • Prevention/Mitigation
    • To enable bucket logging, use the CLI:

      aws s3api put-bucket-logging

7. CloudTrail logs encrypted at rest

Background: It is recommended to encrypt CloudTrail logs at rest by utilizing the AWS KMS service and customer-managed keys (CMKs). This supports data privacy compliance. Several encryption options are available and are free, often with little work required.

Data: 1,358 out of 1,485 CloudTrails do not have encrypted logs (91.4%).

Analysis: Encryption at rest is not popular, and at a minimum should be used to support data privacy compliance efforts.

Controls: 

  • Detection/Audit
    • A bucket’s encryption policy can be checked via CLI:

      aws s3api get-bucket-encryption

    • AWS Config can also specifically check that the CloudTrail bucket has server-side encryption using an AWS KMS CMK.
  • Prevention/Mitigation
    • To set bucket encryption, use the CLI:

      aws s3api put-bucket-encryption

8. Customer CMKs are rotated

Background: The encryption keys used to encrypt CloudTrail logs should be rotated regularly to mitigate key compromise. AWS provides a configuration setting that will automatically rotate KMS CMKs.

Data: Overall, 3,338 out of 16.281 keys (20.5%) are not rotated automatically.

Analysis: To provide better security for encryption best practices, encryption keys need to be rotated. With one-fifth of all keys not rotated, encryption practices are weakened with the use of old keys. Enabling automatic key rotation is easy to do and improves security.

Controls: 

  • Detection/Audit
    • The KMS rotation policy can be checked via CLI:

      aws kms get-key-rotation-status

    • AWS Config has a rule to check whether KMS automatic key rotation is enabled.
  • Prevention/Mitigation
    • To set automatic key rotation, use the CLI:

      aws kms enable-key-rotation

9. VPC flow logging is enabled for all VPCs

Background: VPC flow logging should be enabled for packet rejects for all VPCs. Should an incident occur, this supports investigations into associated suspicious traffic.

Data: 9,015 out of 11,101 VPCs (81.2%) do not have flow logging of any kind enabled.

Analysis: Most VPCs do not have VPC flow logging enabled. Flow logging is instrumental to network traffic investigations and this should be prioritized for remediation.

Controls: 

  • Detection/Audit
    • VPC flow logging can be checked can be done via CLI:

      aws ec2 describe-flow-logs

    • AWS Config has a rule to check if a VPC has flow logging enabled.
  • Prevention/Mitigation
    • VPC flow logging can be enabled with the CLI:

      aws ec2 create-flow-logs

Conclusión

Many best practices have been codified but many AWS environments lag behind in implementing these best practices. Remediating the issues is straightforward for many of the security settings, and there exists specific prescriptive guidance on auditing and remediating your configurations in these areas, which can result in a large reduction in risk.

Here are some basic measures that can be done to address some of the common risk areas due to logging in your AWS environment:

  1. Enable VPC flow logs: Flow logs can be easily enabled and support incident response and investigations. They should be treated with the same priority as API logging with CloudTrail.
  1. Encrypt CloudTrail logs at rest: Encrypt CloudTrail logs to protect log integrity. Encryption at rest supports data compliance controls and is easy to do.
  1. Ensure S3 bucket access logging is enabled for CloudTrail buckets: CloudTrail logging is crucial and to ensure integrity of the logs, S3 access logging should be enabled for all CloudTrail buckets.
  1. Ensure CloudTrail logs are integrated with CloudWatch or a SIEM: CloudTrail logs are best searched or processed in CloudWatch or a SIEM. Any CloudTrails that do not have an associated CloudWatch log group should be reviewed to ensure they are integrated with a production log search service or SIEM.

In upcoming blogs, we’ll explore other best practices and how individual organizations can apply these best practices specific to their environment.

Additionally, Netskope’s Public Cloud Security platform also can automate configuration checking of your AWS environment, implementing both compliance standards, as well as custom configuration checks.

Dataset and Methodology

Time Period: Data was sampled/analyzed from January 24, 2021. 

Source: The analysis presented in this blog post is based on anonymized usage data collected by the Netskope Security Cloud platform relating to a subset of Netskope customers with prior authorization.

Data Scope: The data included 1143 AWS accounts and several hundred organizations. 

The data was composed of configuration settings across tens of thousands of AWS entities including IAM users, IAM policies, password policy, buckets, databases, CloudTrail logs, compute instances, and security groups.

Logic: The analysis followed the logic of core root account security checks found in best practices regarding AWS configuration settings with a few adjustments for the dataset and methodology. Some best practices might define “recent usage” for the root account as a last logged-in time occurring within the past 24 hours to determine whether the root account has been used recently. Because this dataset comes from a point-in-time snapshot, this was changed to within the past 7 days prior to the audit date.

author image
Jenko Hwong
Jenko has 15+ years of experience in research, product management, and engineering in cloud security, AV/AS, routers/appliances, threat intel, Windows security, vulnerability scanning and compliance. At Netskope, he researches new cloud attacks.

Stay informed!

Subscribe for the latest from the Netskope Blog