​​AWS Security Reference Architecture (AWS SRA) — документ по комплексной настройке сервисов безопасности в мульти-аккаунтной среде:

https://docs.aws.amazon.com/prenoscriptive-guidance/latest/security-reference-architecture/welcome.html

Although we rely on a one-page diagram as our foundation, an architecture goes deeper than a single block diagram and must be built on a well-structured foundation of fundamentals and security principles. You can use this document in two ways: as a narrative or as a reference.

#security

🔸How we prevented subdomain takeovers and saved $000s

Blog post describing new open source tool for protecting cloud infrastructure from subdomain takeover, using AWS Lambda functions integrated with Amazon Route53.

https://tech.ovoenergy.com/how-we-prevented-subdomain-takeovers-and-saved-000s/

#aws

🔶 Why AWS SSO is vulnerable by design to device code authentication phishing?

"In this post, we demonstrate that AWS SSO is vulnerable by design to device code authentication phishing – just like any identity provider implementing OpenID Connect device code authentication. This technique was first demonstrated by Dr. Nestori Syynimaa for Azure AD. The feature provides a powerful phishing vector for attackers, rendering ineffective controls such as MFA (including Yubikeys) or IP allow-listing at the IdP level."

https://blog.christophetd.fr/phishing-for-aws-credentials-via-aws-sso-device-code-authentication/

#aws

🔸Building an end-to-end Kubernetes-based DevSecOps software factory on AWS

"DevSecOps software factory implementation can significantly vary depending on the application, infrastructure, architecture, and the services and tools used. In a previous post, I provided an end-to-end DevSecOps pipeline for a three-tier web application deployed with AWS Elastic Beanstalk. The pipeline used cloud-native services along with a few open-source security tools. This solution is similar, but instead uses a containers-based approach with additional security analysis stages. It defines a software factory using Kubernetes along with necessary AWS Cloud-native services and open-source third-party tools. Code is provided in the GitHub repo to build this DevSecOps software factory, including the integration code for third-party scanning tools."

https://aws.amazon.com/ru/blogs/devops/building-an-end-to-end-kubernetes-based-devsecops-software-factory-on-aws/

#aws

🔸Automated Github Backups with ECS and S3

Architecture and implications of an automated process aiming to backup a Github account, relying on ECS Fargate and S3 Glacier. The author, Marco Lancini, explains in his blog the architecture and implications of the final setup he decided to go with.

https://www.marcolancini.it/2021/blog-github-backups-with-ecs/

#aws

🔶 Best practices for securing Identity and Access Management on Amazon Web Services

Post looking at different approaches to help keep IAM configuration tidy, auditable and right-sized.

https://bridgecrew.io/blog/best-practices-for-securing-identity-and-access-management-on-amazon-web-services/

#aws

🔶 The Gamer Guide to Playing Amazon Web Services (AWS)

In this article, the author shares a getting started guide for AWS, in a similar style to the getting started guides that many experienced MMORPG players write for new players. It is a lot easier to get into a game, understand what to do, where to go, and how to play optimally when you have tips from other players who have gone before you.

https://nathanpeck.com/gamers-guide-to-playing-aws/

#aws

🔶 Uncomplicate Security for developers using Reference Architectures
In this blog, Anunay Bhatt,
Cloud Security Architect, will walk through some of the salient features of a meaningful security reference architecture and the process required to develop one. The author will also look at the challenges that one might expect to face while launching a successful security reference architecture program.
https://ab-lumos.medium.com/embedding-security-into-sdlc-using-reference-architectures-for-developers-29403c00fb3d
#aws

🔶 AWS Service Control Policy (SCP) Repository

A repository of AWS Service Control Policy templates and examples that can be deployed using CloudFormation custom resource or AWS CLI noscripts.

Some great examples like: preventing users from disabling or altering the configuration of CloudTrail, AWS Config, and CloudWatch, preventing any VPC that doesn’t already have Internet access from getting it, and more.

https://asecure.cloud/l/scp/
#aws

🔶Hardening AWS EKS security with RBAC, secure IMDS, and audit logging

First in a series of blog posts looking into the default settings used in AWS Elastic Kubernetes Service (EKS) deployments, and demonstrating how small misconfigurations or unwanted side-effects may put our clusters at risk.

https://snyk.io/blog/hardening-aws-eks-security-rbac-secure-imds-audit-logging/

#aws

🔶 Build an end-to-end attribute-based access control strategy with AWS SSO and Okta

"This blog post discusses the benefits of using an attribute-based access control (ABAC) strategy and how to use ABAC with AWS SSO when you’re using Okta as an identity provider. With ABAC, you can simplify your access control strategy by granting access to groups of resources, which are specified by tags, instead of managing long lists of individual resources."

https://aws.amazon.com/blogs/security/build-an-end-to-end-attribute-based-access-control-strategy-with-aws-sso-and-okta/
#aws

🔶 How to defend against DNS exfiltration in AWS?

Key facts from the post:
1️⃣ VPCs by default use the Amazon-provided DNS which can be used to bypass some network-level protection mechanisms (e.g. NACLs or SGs) or monitoring (e.g. VPC Flow Logs).
2️⃣ Recently a new service has been released: the Route 53 Resolver DNS Firewall which allows for blocking and monitoring DNS queries to Amazon DNS.
3️⃣ GuardDuty can also detect malicious DNS traffic, but only in a limited manner.

https://towardsaws.com/how-to-defend-against-dns-exfiltration-in-aws-a65b9214d4e1
#aws

🔹 MITRE ATT&CK mappings released for built-in Azure security controls

The Security Stack Mappings for Azure research project was recently published, introducing a library of mappings that link built-in Azure security controls to the MITRE ATT&CK techniques they mitigate against.

https://www.microsoft.com/security/blog/2021/06/29/mitre-attck-mappings-released-for-built-in-azure-security-controls/

#azure

🔶 AWS Incident Response Playbook Samples

A collection of playbooks covering several common scenarios faced by AWS customers. They outline steps based on the NIST Computer Security Incident Handling Guide, that can be used to gather evidence, contain and then eradicate the incident, recover from the incident, and conduct post-incident activities.

https://github.com/aws-samples/aws-incident-response-playbooks

#aws

🔹 What author have learned from doing a year of Cloud Forensics in Azure AD?

Post sharing experience, challenges, and a methodology on doing Cloud forensics in Azure AD.

https://m365internals.com/2021/07/13/what-ive-learned-from-doing-a-year-of-cloud-forensics-in-azure-ad/

#azure

🔶 S3 Bucket Namesquatting - Abusing predictable S3 bucket names

Abuse of permissions in S3 buckets is one of the more common security issues companies face but this post addresses a different issue, S3 Bucket Namesquatting.

https://onecloudplease.com/blog/s3-bucket-namesquatting

#aws

🔹 Azure Flow Log Analysis

Azure flow logs don't have the same instance ID that AWS flow logs do. So how we can figure out which VM the logs came from?

https://catscrdl.io/blog/azureflowloganalysis/

#azure

🔶🔷🔴 Mapping of On-Premises Security Controls Versus Services Offered by Major Cloud Providers

By the link below you can find the fifth version of a diagram that started in March 2017, with just AWS and Azure versus On-Premises. The diagram began as an effort to make a translation between the typical on-premises security controls that everybody, more or less, knows what they do and the various services advertised by major public cloud providers. As the cloud providers tend to assign catchy names to products that quite often transcend the initial functionality of the on-prem control, it becomes harder and harder to stay up-to-date on what service does what.

https://www.managedsentinel.com/mapping-of-on-premises-security-controls-versus-services-offered-by-major-cloud-providers/

#aws #azure #gcp

🔶 Bye bye bastion hosts...Hello AWS IAM!

How Segment got rid of SSH bastion hosts, reducing cost, complexity, and maintenance of their infrastructure, as well as eliminating the need to distribute SSH Keys. Last but not least, they reduced their attack surface by not having any SSH port open to the world.

https://segment.com/blog/infrastructure-access/

#aws