AWS Sagemaker Security Patterns- Part 2

We are going to look into some best security architecture of AWS Sagemaker. By default AWS Sagemker is a managed service and everything is managed by the AWS, and not the customer.

We'll talk about Authentication & Authorization and Encryption patterns, in this part.

Image courtesy- AWS

Authentication & Authorization patterns:
1. Access via IAM authentication & authorization
2. No multi- tenancy of Saagemaker Notebooks. Each Data Scientist (DS) should be provided their own Notebook
3. Each DS should only be allowed to opens/ start/ stop the Notebook

4. Notebook creation should require additional permissions. Additional roles should be created for more privileged actions.

5. Root access to the Notebooks should be disabled.

Recommended IAM conditions for Sagemaker, which contains best practices for resource launch and running:

Encryption patterns:

1. Data at rest- S3, Notebook- must be encypted with AWS KMS CMKs.

2. Data in transit - multi node training intercommunication- must be encrypted.

Comments

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...

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...

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...

Nilesh Kumar

Search This Blog