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

* 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

* SSo
* Least privileged accounts
* Segregation of accounts


Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at:

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T