Skip to main content

AWS Landing Zones

AWS Landing zone: A framework for defining and creating foundations for accounts by automating, baking security baseline, controls, governance, organized, auditable, scalable and self serviceable.

A set of best practices ingested in an AWS account before migration. Reliable infrastructure. The tenet of LZ are:
- Automation driven versioned infrastructure, such as CI/ CD, Cloudformation templates
- Multi-account AWS environment based on AWS best practices, limiting blast radius
- Adaptable foundation with guardrails, safeguarding in case of any mis happening
- Set of architecture patterns, proxy accesses

Building/ Designing LZ components:
- Accounts: as discussed Multi account strategy
- Network:Domains, Direct Connect, Core Services
- Security: Centralized Logging, Configuration, Image (AMI)
- IAM: Access, Identity, Federation
- Cloud Users: Provide users to deploy the accounts, services by using Service Catalog, Automation (avoid manual steps) etc
- Now, Migrate, Iterate the above steps and Operate and Optimise.

Further break ups:
What we need to design/ think of when creating the components:
- Account Structure
* Centralized Logging
* Environment Isolation
* Billing Visibility
* Shared Services
* Limited Blast Radius

- Network Design
* VPC Design- how many VPC needed
* Subnet Design- Dividing them in private/ public depending on requirement and expose of services, Bastion hosts
* ACL and Security Groups- Properly defined Access control lists to check ingress/ egress traffic
* Logging and Motioning- Enabling Cloudwatch/ Cloudtrail, checks who did what, Intel

-Security
* Amazon GuardDuty enabled
* Amazon CloudWatch for metrics and alarms
* AWS CloudTrail logs for audit
* VPC Flow logs enabled
* AMI Factory for approved and tested images
* AWS Config rules to track changes

-IAM
* SSo
* Least privileged accounts
* Segregation of accounts

Comments

Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more