Conceptos generales de seguridad
Por qué Ciberseguridad para Desarrollo Web
No estamos seguros
Autorización Autenticación y Accountability : AAA
Funciona en mi local
Empecemos por la lógica
SQL Injection
De local a producción
Introducción a DevSecOps
DevSecOps como cultura
Creando pipelines
Corriendo nuestras pruebas
Listas de control de privilegios
Seguridad en la arquitectura
Diseñando la arquitectura
Infraestructura como código
Creando la infraestructura
Creando roles y policies
Desplegando funciones lambda
El mundo de la Base de Datos
Conectando lambdas a una VPC
Single point of failure
Evitando vulnerabilidades en el código
Configurando Auth0
Creando un lambda Authorizer
Secretos y API Keys
Creando Endpoints
Evitando Cross Site Scripting o XSS
Validando la integridad de los datos con tokens
Controles de seguridad sobre datos
Conociendo la naturaleza de los datos
Protege tus datos con Key Management Services
Monitoring y alertas
Sistema de logs
Observabilidad
Alertas y Postmortems
CORS y cierre
Errores de CORS
You don't have access to this class
Keep learning! Join and start boosting your career
In system and application management, it is crucial to be proactive about security. The use of logs, metrics and alerts can be your best ally. Alerts, for example, are sent when unexpected system behavior occurs and can be received in a variety of ways: text messages, emails, applications such as Ops Genie and even in corporate Slack channels. These tools allow you to detect potential problems before they become critical, but more importantly, these alerts must be actionable.
A postmortem is a ceremony within organizations that is performed to analyze a critical event that occurred in the system. The essential thing is to identify the root cause of the problem in order to avoid a recurrence. The aim is not to point the finger of blame, but to learn from the situation and improve processes and codes.
In postmortems, a thorough review is conducted to understand what caused the security breach and what measures can be taken to prevent future occurrences. Solutions may include process changes, code reviews or even infrastructure modifications.
CloudWatch is the tool in AWS for managing metrics and creating alerts. The following describes how to set up an alert to monitor requests to an API Gateway.
Access CloudWatch and Alarms:
Create a new alert:
Configure the alert:
Set actions for the alert:
Assign a name and description to the alert:
Confirm SNS subscription:
To confirm that our alert is working correctly, we can simulate its activation using the CloudWatch API.
aws cloudwatch set-alarm-state --alarm-name "maxAPIGateWaitHits" --state-value ALARM --state-reason "Testing"
This way, in addition to receiving the confirmation in your email, you can be sure that the configuration and notification of your alert is operational and ready to act in case of deviations in the monitoring of your system.
The creation and validation of alerts in AWS CloudWatch is essential not only for the operability of the systems, but also to continuously improve the reaction to incidents. Continue to explore other applications and services to enhance the monitoring and management of your systems.
Contributions 2
Questions 0
Want to see more contributions, questions and answers from the community?