Netskope est nommé leader dans le Magic Quadrant™ du Gartner 2022 dédié au Security Service Edge Recevoir le rapport

  • Produits

    Les produits Netskope sont conçus sur Netskope Security Cloud.

  • Plateforme

    Une visibilité inégalée et une protection des données et des menaces en temps réel sur le plus grand cloud privé de sécurité au monde.

Netskope reconnu comme un des leaders dans le rapport du Magic Quadrant™ 2022 du Gartner dédié au SSE

Recevoir le rapport Présentation des produits
Netskope gartner mq 2022 leader sse

Netskope offre une solution moderne de sécurité du cloud, dotée de fonctions unifiées en matière de protection des données et de détection des menaces, et d'un accès privé sécurisé.

Découvrir notre plateforme
Vue aérienne d'une métropole

Optez pour les meilleurs services de sécurité cloud du marché, avec un temps de latence minimum et une fiabilité élevée.

Plus d'informations
Lighted highway through mountainside switchbacks

Neutralisez les menaces qui échappent souvent à d'autres solutions de sécurité à l'aide d'un framework SSE unifié.

Plus d'informations
Lighting storm over metropolitan area

Solutions Zero Trust pour les déploiements du SSE et du SASE

Plus d'informations
Boat driving through open sea

Netskope permet à toutes les entreprises d'adopter des services et des applications cloud ainsi que des infrastructures cloud publiques rapidement et en toute sécurité.

Plus d'informations
Wind turbines along cliffside
  • Suivi de nos clients

    Sécurisez votre transformation digitale et profitez pleinement de vos applications privées, cloud et Web.

  • Support client

    Un accompagnement proactif et la volonté d'optimiser votre environnement Netskope et de booster votre réussite.

  • Formation et certification

    Avec Netskope, devenez un expert de la sécurité du cloud.

Choisissez Netskope pour vous aider à faire face aux menaces toujours grandissantes, mais aussi aux risques émergents, aux évolutions technologiques, aux changements organisationnels et réseau, ainsi qu'aux nouvelles exigences réglementaires.

Plus d'informations
Woman smiling with glasses looking out window

Notre équipe mondiale d'ingénieurs qualifiés met à profit son expérience plurielle dans les domaines de la sécurité du cloud, la mise en réseau, la virtualisation, la diffusion de contenu et le développement logiciel pour fournir une réponse rapide et efficace à vos questions techniques.

Plus d'informations Support Portal
Bearded man wearing headset working on computer

Sécurisez votre parcours de transformation numérique et tirez le meilleur parti de vos applications cloud, Web et privées grâce à la formation Netskope.

Plus d'informations
Group of young professionals working
  • Ressources

    Découvrez comment Netskope peut vous aider à sécuriser votre migration vers le Cloud.

  • Blog

    Découvrez comment Netskope permet de transformer la sécurité et les réseaux à l'aide du Security Service Edge (SSE).

  • Événements et ateliers

    Restez à l'affût des dernières tendances en matière de sécurité et créez des liens avec vos pairs.

  • Security Defined

    Tout ce que vous devez savoir dans notre encyclopédie de la cybersécurité.

Podcast Security Visionaries

Episode 11: Empowering People for a Secure Future

Écouter le podcast
Black man sitting in conference meeting

Découvrez comment Netskope permet de passer au Zero Trust et au modèle SASE grâce aux fonctions du Security Service Edge (SSE).

Lire le blog
Sunrise and cloudy sky

SASE Week

Netskope is positioned to help you begin your journey and discover where Security, Networking, and Zero Trust fit in the SASE world.

Plus d'informations
SASE Week

Qu'est-ce que le Security Service Edge ?

Découvrez le côté sécurité de SASE, l'avenir du réseau et de la protection dans le cloud.

Plus d'informations
Four-way roundabout
  • Entreprise

    Nous vous aidons à conserver une longueur d'avance sur les défis posés par le cloud, les données et les réseaux en matière de sécurité.

  • Pourquoi Netskope

    La transformation du cloud et le travail à distance ont révolutionné le fonctionnement de la sécurité.

  • Équipe de direction

    Nos dirigeants sont déterminés à faciliter la réussite de nos clients.

  • Partenaires

    Nous collaborons avec des leaders de la sécurité pour vous aider à sécuriser votre transition vers le cloud.

Netskope permet l'avenir du travail.

En savoir plus
Curvy road through wooded area

Netskope redéfinit la sécurité du cloud, des données et des réseaux afin d'aider les entreprises à appliquer les principes Zero Trust pour protéger leurs données.

Plus d'informations
Switchback road atop a cliffside

Penseurs, concepteurs, rêveurs, innovateurs. Ensemble, nous fournissons le nec plus ultra des solutions de sécurité cloud afin d'aider nos clients à protéger leurs données et leurs collaborateurs.

Rencontrez notre équipe
Group of hikers scaling a snowy mountain

La stratégie de commercialisation de Netskope privilégie ses partenaires, ce qui leur permet de maximiser leur croissance et leur rentabilité, tout en transformant la sécurité des entreprises.

Plus d'informations
Group of diverse young professionals smiling
Blog Threat Labs A Real-World Look at AWS Best Practices: Password Policies
Jun 03 2021

A Real-World Look at AWS Best Practices: Password Policies

Introduction

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 account password policies. Based on the Netskope dataset analyzed, we will highlight two opportunities to improve security by making simple IAM changes:

  1. 73% of accounts have an account password policy with a password length less than 14, which is easier to brute-force and compromise. Half of these accounts are using the default AWS Password Policy.
  1. 80% of IAM User accounts have a password reuse/history setting that is less than 24, leading to password reuse and higher chances of compromise.

Password Policy: legacies and defaults

“Don’t live life by default.”

― Steven Redhead

These two technical best practices involve the IAM User Password Policy strength. In a high majority (70-80%) of the 1,143 accounts, the account Password Policy is weak:

#Best Practice# of Violations%
1Ensure IAM password policy requires a minimum length of 14 or greater83272.8%
2Ensure IAM password policy prevents password reuse91076.9%

1. Password Length

Background: Minimum suggested password lengths should be at least 14 in order to prevent easy brute-force compromise of passwords.

Data: 832 (72.8%) of accounts have an account password policy with a password length less than 14.

Analysis: If we analyze the breakdown of the 832 accounts by the length in the password policy, we find:

Password LengthViolations% (out of 1,143)
00%
6-7544.7%
853947%
9-1323921%

In 2020, AWS changed the default Password Policy, increasing the minimum length from 6 to 8 characters. As we can see, 539 accounts (47%) have a password length of 8. Interestingly, more than 80% of the 539 accounts or 440 are set to 8 because they use the default password policy i.e. a custom password policy is not created. 

Controls: 

  • Detection/Audit
    • Auditing the password length in a custom account password policy can be done via CLI:
      aws iam get-account-password-policy
    • The AWS Config Rule: iam-password-policy will also detect password policies that are too weak.
  • Prevention/Mitigation
    • Best practices call for modifying default settings to harden accounts. It is generally easier for users to increase password entropy by increasing length versus character variation.
    • Create a custom password policy that has a password length of at least 14. Using a password manager with random, long passwords is the best way to achieve this.

2. Password Reuse

Background: A similar story is told with the password reuse (history) setting. Best practices recommend preventing password reuse with a large setting of 24.

Data: 910 (80%) of IAM User accounts have a password reuse/history setting that is less than 24

Analysis: To provide more context, we breakdown the 910 accounts by their actual reuse setting:

Password ReuseViolations% (out of 1,143)
0 (default)44038%
1-4928%
513512%
6-1113612%
12-23272%

In 440 accounts (38%), password reuse is set to 0, inherited from the default Password Policy. When customizing a policy, the Console will supply a suggested value of 5 for the reuse setting. For those that set a custom policy, about 12% choose 5. In summary, default values (0 or 5) have been used for password reuse in 50% of the accounts in this dataset which introduces more risk than recommended.

Controls:

  • Detection/Audit
    • Auditing the password reuse in a custom account password policy can be done via CLI:
      aws iam get-account-password-policy
    • The AWS Config Rule: iam-password-policy will also detect password policies that are too weak.
  • Prevention/Mitigation
    • Setting password reuse is recommended to prevent and mitigate compromised credentials.

Additional Controls

  • Enabling MFA for regular IAM users will also help mitigate compromised credentials.
  • If you are using or can use cross-account access or federated/SSO authentication, it avoids the IAM User password policy issues since cross-account access will utilize temporary credentials. Authentication and password policies including length, reuse, and MFA can be handled centrally by the federated identity system instead of in each account.

Conclusion

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 IAM configuration in your AWS environment:

  1. Customize your AWS Password Policy, do not use the default.
  1. Increase the password length to at least 14, and set the password reuse to 24.
  1. Especially for larger environments, using a federated identity system or by isolating all IAM Users in one account and granting cross-role access, will allow centralized management of user accounts and password policies.

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
About the author
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.
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.