Cloud Infrastructure Vulnerabilities

1. Data privacy violation;
2. Incorrect configuration and inadequate change control;
3. Lack of security strategies in the cloud and security architecture;
4. Lack of identification, separation of rights and access control procedures;
5. Hacking and theft of accounts;
6. Internal threats

Threat 1. Data privacy violation

• Target attack
• Human error
• Application vulnerabilities
• Lack of security measures

• Large attack surface due to shared and shared resources
• Cloud service providers often become an attractive target for hackers due to the popularity and huge amount of data stored.
• There is a distribution of responsibility when the client is responsible for data security, and the cloud provider is only responsible for the availability of infrastructure and tools.

• Protection in depth - creating protection in the client cloud;
• Principle of least privilege;
• Introduction of monitoring and journaling procedures in the cloud;
• A reliable and proven incident response plan;
• Encryption can help protect data, but adversely affects system performance.

Threat 2. Incorrect configuration and inadequate control

• Public cloud storage
• Unsecured Cloud Databases
• Inappropriately protected backups
• Open NAS connected to the Internet

• Full description of the infrastructure life cycle
• Flexible, proactive cloud management
• Confidential Data Encryption
• Logging Configuration Changes

Threat 3. Lack of cloud security strategy and security architecture

• Secure cloud architecture requires new features and new tools.
• Organizations have to learn new technologies when it comes to cloud adoption.

• New, and therefore sophisticated, technologies are used;
• A new hybrid cloud security model is needed;
• The right balance is needed between innovation and control;
• There is no reference architecture or documentation.

• Ensure that your security architecture is aligned with your business goals and objectives.
• Design and implement a security architecture framework.
• Ensure that the threat model is constantly updated.
• Ensure continuous visibility of the actual security status.

Threat 4. Inadequate identification, separation of rights and access control procedures

• Inadequate credential protection.
• Lack of regular automatic rotation of cryptographic keys, passwords and certificates.
• Lack of scalable identity access control systems.
• Refusal to use multi-factor authentication and strong passwords.

• Read, filter, modify and delete data
• Obtain management and control privileges
• Watch transmitted data
• Introduce malware by disguising it as acquired from legitimate sources

• Use temporary security credentials (AWS IAM roles) instead of long-term access keys
• Do not insert access keys directly into the code. Use different keys for different applications.
• Change keys periodically
• Remove unused access keys
• Set up multi-factor authentication for your most important tasks.

Threat 5. Hacking and account theft

• Inadequate Identity and Access Control (IAM) measures.
• Lack of logs, monitoring, and alerts at the account level.
• Lack of protection in the client cloud (deep protection)
• Lack of protection against phishing and exploitation of stolen credentials.

• It is likely to get cloud service accounts and services.
• Uncertainty stems from the cloud service delivery model.
• Data and applications reside in cloud services that are available through a cloud account or subscription.
• /
• ,

• ,
• IAM : , , , .
• IP-,

6.

• Limit the radius of possible impact using Identity and Access Policies (IAM) and least privileges.
• Prevent "unintentional insider behavior."
• Provide employees with a secure work environment by default
• Automated configuration management, initialization and protection.
• Introducing new monitoring and discovery capabilities for cloud environments (SaaS / PaaS / Iaas).
• Develop a business continuity plan.