IuriiO Notebook
  • Broken Code Notebook
  • Architecture and Design
    • Architectural Decision Records
    • Trade-off Analysis
    • Data Decomposition Drivers
    • Selecting a Database Type
    • Service Granularity
    • Consumer-driven Contracts
  • Cloud
    • AWS
      • Resources
      • Compute
        • EC2
        • Batch
        • ECS & ECR
        • Elastic Beanstalk
      • Storage & Data Management
        • S3
        • Storage Gateway
        • RDS
        • DynamoDB
        • ElastiCache
        • Redshift
        • EBS
        • EFS
        • FSx
        • Snowball
        • Athena
        • Encryption and Downtime
        • Untitled
      • Security & Compliance
        • IAM
        • Web Identity Federation
        • Organizations
        • Service Catalog
        • Tags and Resource Groups
        • STS
        • KMS
        • GuardDuty
        • Compliance
        • Marketplace Security Products
        • DDOS
        • Compliance Frameworks
      • High Availability
        • Global Infrastructure
        • Disaster recovery
        • Elastic Load Balancers
        • Untitled
      • Monitoring & Reporting
        • Cost Explorer
        • CloudWatch
        • Systems Manager
        • Config
        • CloudTrail
        • Cost control
        • Untitled
      • Networking
        • Networking 101
        • Route53
        • CloudFront
        • VPC
        • DirectConnect
        • WAF
        • Shield
        • Global Accelerator
      • Deployment & Provisioning
        • Untitled
        • Untitled
      • Automation & Optimization
        • CloudFormation
          • Links
          • Github resources
          • YAML 101
          • Videos
        • OpsWorks
        • Untitled
      • Application Services
        • SQS
        • SWF
        • SNS
        • Untitled
      • Serverless
        • Lambda
        • API Gateway
        • DynamoDB
        • SAM
        • Untitled
      • Well-Architected Framework
    • Azure
      • Tools
      • Organization & Management
      • Authentication & Authorization
      • Compute
      • Networking
      • Storage
      • Databases
      • Security
      • Privacy, Compliance & Trust
      • Cost Management
  • Containers & Services
    • Docker
      • Useful Links
      • Containers
      • Images
      • Dockerfile
      • System
      • Compose
      • Swarm
      • Docker & NodeJS
    • Kubernetes
      • Useful Links
      • Introduction
      • Getting started
      • Exposing containers
      • Kubernetes Management Techniques
        • Declarative YAML
      • Labels and Annotations
      • Storage in Kubernetes
      • Ingress Controller
      • CRD's and The Operator Pattern
      • Kubernetes Dashboard
      • Kubectl Namespaces and Context
  • Frontend
    • Resources
    • Design
      • Search experience
Powered by GitBook
On this page

Was this helpful?

  1. Cloud
  2. AWS
  3. Security & Compliance

Compliance Frameworks

  • ISO/IEC 27001:2005 - specifies the requirements for establishing, implementing, operating, monitoring, reviewing, maintaining and improving a documented Information Security Management System within the context of the organization's overall business risks.

  • FedRAMP - The Federal Risk and Authorization Management Program, is a government-wide program that provides a standardized approach to security assessment, authorization and continuous monitoring for cloud products and services.

  • HIPAA - Federal Health Insurance Portability and Accountability Act of 1996. The primary goal of the law is to make it easier for people to keep health insurance, protect the confidentiality and security of healthcare information and help the healthcare industry control administrative costs.

  • NIST - National Institute of Standards and Technology - framework for improving critical infrastructure cybersecurity. A set of industry standards and best practices to help organizations manage cybersecurity risks.

  • PCI DSS v3.2 - The Payment Card Industry Data Security Standard is a widely accepted set of policies and procedures intended to optimize the security of credit, debit, and cash card transactions and protect cardholders against misuse of their personal information.

    Requirements:

    • 1: Install and maintain a firewall configuration to protect cardholder data.

    • 2: Do not use vendor supplied defaults for system passwords and other security parameters.

    • 3: Protect cardholder data at rest.

    • 4: Encrypt transmission of cardholder data across open, public networks.

    • 5: Protect all systems against malware and regularly update antivirus software or programs.

    • 6: Develop and maintain secure systems and applications.

    • 7: Restrict access to cardholder data by business need to know.

    • 8: Identify and authenticate access to system components.

    • 9: Restrict physical access to cardholder data.

    • 10: Track and monitor all access to network resources and cardholder data.

    • 11: Regularly test security systems and processes.

    • 12: Maintain a policy that addresses information security for all personnel.

  • Other frameworks:

    • SAS70 - Statement on Auditing Standards No.70.

    • SOC1 - Service Organization Controls - accounting standards.

    • FISMA - Federal Information Security Modernization Act.

    • FIPS 140-2 - US Government computer security standard used to approve cryptographic modules. Rated from level 1 to Level 4, with 4 being the highest security. CloudHSM meets the Level 3 standard.

PreviousDDOSNextHigh Availability

Last updated 5 years ago

Was this helpful?