Skip to main content

AWS Security Anti Patterns

The below are a few security anti patterns for AWS cloud which should be avoided when implementing comprehensive cloud security strategy:

Security Anti-patterns Categories:
- Account Structure
- N/w design
- Auditing
- S/W delivery

AntiPattern (Account Structure): Personally owned AWS account
- Make sure the Root account (login, MFA) is not tied to a person's email id. Root email id should be tied to team DL
- Root MFA must be tied with some sort of official hardware device
- Contact info etc must be of office address
- No one logs into the account root. Use IAM only.

Anti-pattern (Account Structure): AWS account overcrowding
- Not all and every services/ teams should be placed under one single account. It becomes very hard to manage policy wise and governance wise
- If admin creds for the account is compromise, the blast radius will be more, all the services get compromised
- If some of the services are in scope for compliance, and since they are not separated, it'll be a concern from Compliance perspective.
- Multi- account pattern is recommended. Where the accounts are grouped logically.

Anti-pattern (N/W design): Trusted IP access w/p client auth

- Routing should not be treated as security
- Segregate and use a lot of relevant edge devices and services to achieve defense in depth- AWS Shield, API Gateway, IAM auth, cert etc

Anti-pattern (N/W design):N/W egress back hauling
- Don't directly talk to internet. Restrict egress via Exit VPC
- Use VPC endpoint to talk to publicly hosted services such as S3.

Anti-pattern (Auditing): Questionnaires
- Create attestations instead of entertaining long list of client's questionnaires about the organization's security postures and implementations.
- Get certifications/ assurances and maintain standards sich as ISO 2Ks, SOc2, PCI -DSS etc

Anti-pattern (Auditing): Manual technical auditing
- Inconsistent
- Time consuming, not frequent
- USe automated continuous auditing tools and processes such as Cloud Watch, Inspector, Trusted adviser, Evident.io
- Practice DevSecOps- securit as a code, proactive controls enforced by code

Anti-pattern (S/W delivery): Over-the-wall s/w delivery
- Dev, QA, and ops kept separte- no concept of DevOps basically
- A lot of manual process
- Infrequent release cycles
- Implement DevSecOps

Comments

Post a Comment

Popular posts from this blog

Breaking Excel password protection

If you came across an excel sheet asking for password for allowing to make any changes into it, you may want to unprotect it. All we need to do is to edit the xml file which comes intrinsically packaged with Excel 2007 or 2010. But what about Excel 2003? For that, open the Excel 2003 file within Excel 2007, save it as xlsx file. So, keep in mind all the Excel files below 2007 version, you need to convert them as Excel 2007 with extension .xlsx. Now here are the steps for doing that: 1. Open the Excel 2003 file (e.g. Secret.xlsx) and save it as .xlsx (Excel 2007) format. If you already have Excel 2007 file, then no need for any conversion. 2. Now change the extension of the above file to .zip and extract the zipped file. Browse through the file in the extracted folder and go to: <LocalPath>\Secret\xl\worksheets.   3. Now open the sheet/ sheets you want to remove protection in any xml editor. Look for keywords such as 'sheetProtection' or 'workbo...
10 comments
Read more

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

Data leakage in JSON

A web application is sending data in this format: {"t":1,"p":1,"r":1,"rows":[{"i":0,"c":["n","H, C","A","5","T","n"]}]} this is a valid JSON, before moving on lets understand an important concept: 1. Javscript expression 2. javascript statement javscript expressions are not executed by javascript parser, but statements are: for ex: <script> {"t":1,"p":1,"r":1,"rows":[{"i":0,"c":["n","H, C","A","5","T","n"]}]} </script> this will not be executed, that is, objects won't be created. The above example is for a javascript expression. But now when it is converted into a statement as given below: <script> [{"t":1,"p":1,"r":1,"rows":[{"i":0,"c":[...
6 comments
Read more