Skip to main content

AWS Security

Technically, part about 16, but these are the first published notes. No pictures, not fun stuff, but proof that I'm doing something.

Well, here's something funny;
 Gives training to employees (Unlike most companies who want the perfect person right out of the gate).

AWS Training
Security Compliance

- Risk and Compliance

- Compliance Approach
    - Shared responsibility
    - Services on secure and controlled platform w/ a wide array of security features
The Customer configures their IT infrastructure.

- Compliance Responsibilities
Shares information about risk for customers to document their framework.

Security Sharing involves getting Certs, making white papers, giving documentaion under ND and works with outside auditors.

Assurance Programs
- Certs
- Laws, regs, privacies.

Functionality offered sometimes re: Laws, regulation, privacy for compliance, also alignments and frameworks.

Risk Management

- Implement control and mitigation.
- Re-evaluated at least bianually to ID risks
- Put in measures to solve the problem!
- Also other risk assessments.

Policies based upon these:

* Cobit

- Maintains policy
- Gives training to employees (Unlike most companies who want the perfect person right out of the gate).
- Perform application security reviews
    - AAA, you know this.
Scans internet facing interfaces for vulnerabilities.
Let’s people know about the problems.
Ext. vulnerability assessments performed regularly by third parties, who send the information to AWS leadership. But not a replacement for customer scans.

Customers can ask for cloud infrastructure scans.

Control Environment

- Policies, processes, control activities.
- Securely delivers AWS offerings.
- People
- Processes
- Tech
- All that supports AWS framework, and AWS gets input from leading cloud computing societies to make things work.
Once again, confidentiality, integrity, availability.

You should check the white papers.

Info Sec.

Customers have governance over IT enviroment, which sounds challenging and cool to me.

LEARN about the enviroment from different sources.
DESIGN what works.
IDENTIFY what other people can access.

AWS Security Resources 

Auto-Cloud Expert who helps fix your resources to follow best practices, which I’m guessing are the security compliances.

Oh, they are, And to help save money, improve performance and reliability.


First port of confact, AWS Help Desk people, “read this, maybe it can solve the problem.”


The hardcore Help Desk concierge people with fast support. Must take a lot to be one of those, god speed.


Helps you to develop policies and proceedures to fit compliance. There are hundreds of them, hundreds!


Help you navigate around current threats.



Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl