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

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...
1 comment
Read more

'Information Leakage-Improper Error Handling' dropped

From Owasp Top 10 2010 List, the issue 'Information Leakage-Improper Error Handling' has been dropped. But it's not the final list,its child release actually. Bu I feel it shouldn't be set aside because its still the one of the prevalent issues these days. That's why I mailed to Dave Wicher: Hi Dave, Excellent work, Congrats! Just one little query- Don't you think that Information Leakage & Improper Error Handling still deserves to be in Top 10? Dave replied: This topic is clearly a very prevalent issue that deserves attention by most organizations. However, the typical impact of such a flaw is usually very low. Therefore, the overall risk of this type of flaw is lower than the other items in the top 10, which is why it was replaced in this update with one of the 2 new items. Regarding dropping Info Leak/Error handling - It is incredibly prevalent, no question. But their impact is typically very low, so the overall risk is low, which is why it fell out of t...
3 comments
Read more

jtool - an alternative to otool

jtool comes with a capability of running on Linux environment. Some ipa scanning tools are created to run on Linux environment where mac environment is not available. In such cases tools such as otool and class-dump-z will not work. So jtool can be an alternative to otool. For more information on jtool please refer to http://www.newosxbook.com/tools/jtool.html . It lists down various commands which have same output as otool or a equivalent. There are several commands mentioned in link. But for our customized requirements and basis checks I have listed down the below ones after running on many binaries. The outputs are similar or equivalent to otool and class-dump-z: Commands for checking PIE flag (ASLR) in jTool jtool -d -v -arch | grep stack ·           Automatic Reference Counting (ARC) protection: jtool -d -v -arch | grep _objc_release ·           To check if the devic...
1 comment
Read more