{"id":1520,"date":"2021-07-19T08:00:03","date_gmt":"2021-07-19T01:00:03","guid":{"rendered":"https:\/\/vticloud.io\/?p=1520"},"modified":"2021-09-20T10:02:45","modified_gmt":"2021-09-20T03:02:45","slug":"checklist-bao-mat-dam-may-tren-amazon-web-services","status":"publish","type":"post","link":"https:\/\/vticloud.io\/en\/checklist-bao-mat-dam-may-tren-amazon-web-services\/","title":{"rendered":"Security Checklist for systems on Amazon Web Services"},"content":{"rendered":"

<\/p>\n

Security has always been a business concern when moving to the cloud, especially for businesses that store user data such as banking, finance, real estate, and insurance. Therefore, VTI Cloud will share our cloud security checklist for systems on Amazon Web Services (AWS) in the article below.<\/strong><\/p>\n

AWS Shared Responsibility Model<\/strong><\/h2>\n

Security and compliance are a shared responsibility between AWS and its customers. This shared model can help reduce the operational burden on customers as AWS operates, manages, and controls components from the server operating system and virtualization layer to the physical security of the facilities. The department is operating the service.<\/p>\n

The customers will be in charge of and manage the client operating system (including security updates and patches), other associated application software, and the configuration of the Security Groups and firewall provided by AWS.<\/p>\n

\"shared<\/p>\n

The customer should carefully consider the services he\/she chooses as the customer’s responsibility will vary with the service in use, the integration of those services into the customer’s IT environment as well as the law. and current regulations.<\/p>\n

This nature of shared responsibility also provides flexibility and provides the ability to control customers to enable deployment.<\/p>\n

Security in the Shared Responsibility Model<\/h3>\n

AWS’s Shared Responsibility Model makes it clear that certain aspects of AWS security are in the hands of the business, and businesses must be fully responsible for the security incidents that occur in the management of the business.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Security in the Shared Responsibility Model<\/p>\n<\/th>\n

\n
\n

Customer’s Responsibilities<\/strong><\/p>\n<\/div>\n<\/th>\n

\n
\n

AWS’s Responsibilities<\/strong><\/p>\n<\/div>\n<\/th>\n<\/tr>\n

\n

Preventing or detecting when an AWS account has been compromised<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Preventing or detecting a privileged or regular AWS user behaving in an insecure manner<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Preventing sensitive data from being uploaded to or shared from applications in an inappropriate manner<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Configuring AWS services (except AWS Managed Services) in a secure manner<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Restricting access to AWS services or custom applications to only those users who require it<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Updating guest operating systems and applying security patches<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Ensuring AWS and custom applications are being used in a manner compliant with internal and
\nexternal policies<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Ensuring network security (DoS, man-in-the-middle (MITM), port scanning)<\/p>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Configuring AWS Managed Services in a secure manner<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Providing physical access control to hardware\/software<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Providing environmental security assurance against things like mass power outages, earthquakes, floods, and other natural disasters<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Database patching<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Protecting against AWS zero-day exploits and other vulnerabilities<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n

\n

Business continuity management (availability, incident response)<\/p>\n<\/td>\n

\n
\n

 <\/p>\n<\/div>\n<\/td>\n

\n
\n

o<\/p>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

To understand more on this model, please read more on the following link: https:\/\/aws.amazon.com\/compliance\/shared-responsibility-model\/<\/a><\/span><\/p>\n

AWS Security Checklist<\/strong><\/h2>\n

VTI Cloud has developed a checklist of best practices and highest priority, which businesses must follow to proactively stop threats. This checklist provides customer recommendations for Security Pillar matching in the AWS Well-Architected Framework.<\/p>\n

\"aws<\/p>\n

\n

VTI Cloud wrote about AWS Well-Architected Framework in the latest blog post, here: AWS Well-Architected Framework l\u00e0 g\u00ec? | VTI CLOUD<\/a><\/span><\/p>\n<\/blockquote>\n

Security checklist of AWS Identity & Access Management (IAM)<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Avoid using the Access Keys of the root account in AWS as these allow full access to all resources<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Multi-Factor Authentication must be enabled for the root account to provide two-factor authentication<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Centralize identity with AWS Single Sign-On or 3rd party solution to avoid creating multiple IAM accounts arising frequently or using long-term (long-term) Access Keys<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure the user account also has MFA authentication<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • The IAM Access Keys must be renewed periodically<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure a strong password policy for users and set up a 90-day lifecycle for passwords<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Assign permissions to users based on User Groups, rather than on individual users<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Granting minimal access while creating IAM Policies, these policies are required to take certain actions.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Attach IAM Policies to Groups or Roles when creating<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Appropriate conditions should be used to limit refusal or authorization of action against resources<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Eliminate unnecessary IAM users who are inactive or inactive<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use IAM Roles to grant access to applications on EC2 Instance<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use multiple AWS accounts to separate data and resources on AWS, and enable the use of Service Control Policies to integrate guardrails in AWS Control Tower. AWS Control Tower makes it easy to set up and manage AWS multi-account environments<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist<\/strong> of <\/strong>Amazon S3<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Ensure S3 buckets are not publicly accessible (publicly read or write) – users can enable ‘Amazon S3 block public access to prevent access from Public<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use object-level or bucket-level permissions next to IAM Policies to grant access to resources.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Enable MFA Delete to prevent accidental deletion of buckets<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Consider encryption of stored data, which can be done in two ways – server-side and client-side encryption<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Allows encryption of incoming and outgoing traffic through SSL endpoints<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Configure S3 lifecycle management (S3 lifecycle) through rule-based actions and use Bucket Versioning, to deal with random deletion<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure S3 access logging is enabled<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Continuously inspect and monitor S3 buckets using Amazon CloudWatch metrics<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist<\/strong> of <\/strong>Amazon EC2, Amazon VPC, and Amazon EBS<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • \n

    Ensure data and disk (disk volume) in EBS is encrypted with AES-256<\/p>\n<\/li>\n<\/ul>\n<\/td>\n

\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Restrict access to instances from restricted IP ranges using Security Groups<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Limits the scope of ports opened on EC2 Security Groups, to prevent attacks through vulnerabilities<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use IAM policies with restrictions for IAM users, roles that are allowed to change or modify the original AMI (Amazon Machine Images)<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure Elastic Load Balancers have a valid Security Group associated with it and enable access logging<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Monitor and optimize default Security Groups, as they allow unlimited access for inbound and outbound traffic<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use AWS Firewall Manager to automatically apply the rules of Security Groups and AWS WAF<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure limited access to SSH, FTP, SMTP, MySQL, PostgreSQL, MongoDB, MSSQL, CIFS\u2026, limit access to fixed IPs if possible.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use IAM Roles to grant access to EC2, instead of Access Keys for temporary requests<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • If you are using the IAM user Access Keys for permanent permissions, make sure not to embed these keys directly in the code.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Create different keys for different applications, rotate Access Keys, use MFA validation, and deactivate unused Key pairs<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Enable and enable VPC flow logs to record incoming and outgoing traffic in VPC for better tracking and early diagnosis of potential problems<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Delete unused Virtual Private Gateway and VPC Internet Gateway<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure that no VPC endpoints are exposed to the public, by checking the key value in the policy.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure there are no Network ACLs that allow unrestricted access or exit<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist <\/strong>of <\/strong>AWS CloudTrail<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Make sure CloudTrail has Multi-region feature enabled<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • You should log into a centralized S3 bucket and use access logging and restrict access to the CloudTrail S3 bucket.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure both CloudTrail and CloudTrail logging have Multi-Region logging enabled<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure CloudTrail log file integrity authentication is enabled<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure CloudTrail logs are encrypted<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use in conjunction with Amazon CloudWatch for binding metrics, with Amazon GuardDuty for continuous monitoring and AWS Security Hub for a holistic view of security on AWS<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist<\/strong> of <\/strong>Amazon CloudFront, AWS WAF, and AWS Shield<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Uses Amazon CloudFront, AWS WAF, and AWS Shield to provide DDoS attack protection at Layer 3 (Network), Layer 4 (Transport), and Layer 7 (Application)<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use secure CloudFront SSL versions<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist<\/strong> of <\/strong>Amazon RDS<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Make sure the RDS Security Groups do not allow unrestricted access<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure encryption of RDS instances and snapshots, using AES-256 level encryption<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Protects data when transmitting to RDS over SSL endpoints<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Monitoring RDS control with AWS Key Management Service (KMS) and Customer Managed Keys<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Configure AWS Secrets Manager to automatically rotate secrets (a set of information, usernames, and passwords, and connection details used to access a secured service) to Amazon RDS<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure RDS database instances and snapshots are not publicly accessible<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Enable automatic minor upgrade for RDS<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist <\/strong>of <\/strong>Amazon Redshift<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Enable require_ssl parameter in all Redshift clusters to minimize the risk of data encryption in transit for the Redshift and connect SQL Client to the enterprise cluster<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Enables Redshift Cluster encryption<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Enable the require_ssl parameter for the RedShift Cluster<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure Redshift user activity logging is enabled<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Ensure Redshift encryption with KMS Customer-Managed Keys<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • We recommend that enterprises launch Redshift clusters in the VPC for better control<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Make sure that the Redshift clusters are not publicly accessible<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist<\/strong> of <\/strong>AWS Systems Manager<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Use AWS Systems Manager Patch Manager to automate the process of patching systems and code, including OS, application, and code dependencies<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Use the AWS Systems Manager Automation runbook or use Command to access the database or system indirectly<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Security checklist <\/strong>of <\/strong>Monitoring and Alerts<\/strong><\/h3>\n

 <\/p>\n\n\n\n\n\n
Work Checklist<\/strong><\/td>\nCheck<\/strong><\/td>\n<\/tr>\n
\n
    \n
  • Enable AWS Config to monitor historical data of resources, and use the Config Managed Rules to automatically alert or immediately alert unwanted changes<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n
\n
    \n
  • Alerts on the creation of both logs and events from AWS CloudTrail, to Amazon GuardDuty and application logs, help identify high-priority alerted events to investigate security incidents.<\/li>\n<\/ul>\n<\/td>\n
\u00a0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Conclusion<\/strong><\/h2>\n

The most important requirement when ensuring a secure infrastructure is complete visibility. Simply put, how can an enterprise take preventive action if it doesn’t even know what’s wrong?<\/p>\n

With the use of AWS security checklists recommended for some typical VTI Cloud services above, businesses will ensure the most essential elements to keep their infrastructure at risk. In addition, businesses can contact us, VTI Cloud, for advice and implementation on security checklists with AWS Well-Architected Review and Managed Services for businesses.<\/p>\n

We will ensure your system runs the most smoothly, but always ensure information security, system security, and especially the optimal cost of use of the current system.<\/p>\n

Read more on our AWS Well-Architected Review at the following link: https:\/\/vticloud.io\/services\/well-architected<\/a><\/span><\/p>\n

About VTI Cloud<\/h2>\n

VTI Cloud<\/strong>\u00a0is an\u00a0Advanced Consulting Partner<\/a><\/span>\u00a0of AWS Vietnam with a team of over 50+ AWS certified solution engineers. With the desire to support customers in the journey of digital transformation and migration to the AWS cloud, VTI Cloud is proud to be a pioneer in consulting solutions, developing software, and deploying AWS infrastructure to customers\u00a0in Vietnam<\/strong>\u00a0and Japan.<\/strong><\/p>\n

Building safe, high-performance, flexible, and cost-effective architectures for customers is\u00a0VTI Cloud\u2019s<\/strong>\u00a0leading mission in enterprise technology mission.<\/p>\n

<\/p>","protected":false},"excerpt":{"rendered":"

Security has always been a business concern when moving to the cloud, especially for businesses that store user data such as banking, finance, real estate, and insurance. Therefore, VTI Cloud will share our cloud security checklist for systems on Amazon Web Services (AWS) in the article below. AWS Shared Responsibility Model Security and compliance are […]<\/p>\n","protected":false},"author":5,"featured_media":1678,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[13],"tags":[78,70,42,51,77,67,50,34],"_links":{"self":[{"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/posts\/1520"}],"collection":[{"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/comments?post=1520"}],"version-history":[{"count":1,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/posts\/1520\/revisions"}],"predecessor-version":[{"id":3177,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/posts\/1520\/revisions\/3177"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/media\/1678"}],"wp:attachment":[{"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/media?parent=1520"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/categories?post=1520"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vticloud.io\/en\/wp-json\/wp\/v2\/tags?post=1520"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}