Topicos Calidad en DevOps

Arquitectura software

Katalon Recorder (Selenium tests generator)

§  Automatización de pruebas de usario

§  Herramienta para emular interacción de usuario con un aplicativo Web

§  Exportación de pruebas de Casos de Uso

Librería Polly:

§  Resilencia del software (Wait and Retry + Circuit Breaker)

Proyecto Simmy:

§  Simmy es una herramienta de ingeniería de caos e inyección de fallas basada en la idea

SonarCloud

§  Amalisis de Código

STRIDE (buenas prácticas| Seguridad):

• Suplantación de identidad de usuario
• Inyección SQL
• Tampering
• Repudio
• Divulgación de información (brecha de privacidad o filtración de información)
• Denegación de servicio (D.o.S)
• Elevación de privilegios

Arquitectura empresarial

Cucumber:

§  Herramienta de software que admite el desarrollo basado en el comportamiento.

§  BDD (Behavior-Driven Development)

§  Analizador de Lenguaje Gherkin

SpecFlow:

§  Especificación de requerimientos, se generan escenarios en palabras de negocio

§  Ejecución de pruebas de aceptación de los escenarios finitos

Actividades

Entrenamiento Katalon Recorder

Entrenamiento Gherkin y SpecFlow

Discusión Seguimiento de métricas SonarCloud

Discusion STRIDE

Prueba de Concepto MSCA

Azure DevOps Dashboards with PowerBI

--

Polly 7.2.1 

Polly is a library that allows developers to express resilience and transient fault handling policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner.

https://www.nuget.org/packages/Polly/

Simmy

Simmy is a chaos-engineering and fault-injection tool, integrating with the Polly resilience project for .NET. It is releasing April 2019 and works with Polly v7.0.0 onwards.

Simmy allows you to introduce a chaos-injection policy or policies at any location where you execute code through Polly.

http://www.thepollyproject.org/2019/06/27/simmy-the-monkey-for-making-chaos/

https://github.com/Polly-Contrib/Simmy

---

https://www.katalon.com/resources-center/blog/katalon-automation-recorder/

https://chrome.google.com/webstore/detail/katalon-recorder-selenium/ljdobmomdgdljniojadhoplhkpialdid

Katalon Automation Recorder Quickstart

Thank you for using Katalon Recorder – the champion project of Katalon Hackathon. This is the Selenium IDE-compatible replacement on latest Chrome and Firefox that helps record, play, debug, manage automated tests, and export to C#, Java, Ruby, Python, Groovy, or Robot Framework.

To make the best use of the tool, we encourage you to go through this quickstart.

https://cucumber.io/

https://cucumber.io/docs/gherkin/reference/

Lenguaje→gherkin

Tools & techniques that elevate teams to greatness

It’s simple. Whether open source or commercial, our collaboration tools will boost your engineering team's performance by employing Behavior-Driven Development (BDD). And with our world-class training, take it to places it’s never been. 

https://specflow.org/

https://specflow.org/getting-started/

Behavior Driven Development for .NET

SpecFlow helps teams bind automation to feature files and share the resulting examples as Living Documentation across the team and stakeholders.

https://bolt.whitesourcesoftware.com/ 

WhiteSource BoltFree developer tool for finding and fixing open source vulnerabilities
https://anchore.com/Seguridad, analizar images de Docker

DevSecOps at Full Speed

Enable High Velocity, Policy-Based Container Workflows Without Compromise

https://secdevtools.azurewebsites.net/

Run security analysis tools in Azure DevOps Pipelines

The Secure Development Lifecycle (SDL) Guidelines recommend that teams perform static analysis during the implementation phase of their development cycle.

The Microsoft Security Code Analysis extension empowers you to do so, easily integrating the running of static analysis tools in your Azure DevOps pipelines.

https://sonarcloud.io/

https://es.wikipedia.org/wiki/STRIDE_(seguridad)

STRIDE (seguridad)

Ir a la navegaciónIr a la búsqueda

STRIDE es un modelo de amenazas desarrollado por Praerit Garg y Loren Kohnfelder en Microsoft¹​ para la identificación de amenazas de seguridad informática.²​ Esta proporciona un mnemónico para las amenazas a la seguridad en seis categorías³​

Las amenazas son:

·         Suplantación de identidad de usuario

·         Tampering

·         Repudio

·         Divulgación de información (brecha de privacidad o filtración de información)

·         Denegación de servicio (D.o.S)

·         Elevación de privilegios

STRIDE fue creado inicialmente como parte del proceso de modelado de amenaza. STRIDE es un modelo de amenazas, utilizado para ayudar a razonar y encontrar amenazas a un sistema. Está utilizado conjuntamente con un modelo del sistema objetivo que puede ser construido en paralelo. Esto incluye un desglose lleno de procesos, bancos de datos, flujos de datos y fronteras de confianza.⁴​

Hoy es a menudo utilizado por expertos de seguridad para ayudar contestar la pregunta "¿Qué puede salir mal en el sistema en el que estamos trabajando?"

Cada amenaza es una violación de una propiedad deseable para un sistema:

Amenaza	Propiedad deseada
Spoofing	Autenticidad
Tampering	Integridad
Repudio	No repudio
Revelación de información	Confidencialidad
Denegación de Servicio	Disponibilidad
Elevación de Privilegio	Autorización

https://owasp.org/www-project-top-ten/

Top 10 Web Application Security Risks

1.   Injection. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.

2.   Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently.

3.   Sensitive Data Exposure. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser.

4.   XML External Entities (XXE). Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks.

5.   Broken Access Control. Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc.

6.   Security Misconfiguration. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion.

7.   Cross-Site Scripting XSS. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

8.   Insecure Deserialization. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.

9.   Using Components with Known Vulnerabilities. Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts.

10.     Insufficient Logging & Monitoring. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Top Web Applications Security Risk

Azure Web Application Firewall on Azure Application Gateway

Azure Web Application Firewall (WAF) on Azure Application Gateway provides centralized protection of your web applications from common exploits and vulnerabilities. Web applications are increasingly targeted by malicious attacks that exploit commonly known vulnerabilities. SQL injection and cross-site scripting are among the most common attacks.

WAF on Application Gateway is based on Core Rule Set (CRS) 3.1, 3.0, or 2.2.9 from the Open Web Application Security Project (OWASP). The WAF automatically updates to include protection against new vulnerabilities, with no additional configuration needed.

All of the WAF features listed below exist inside of a WAF Policy. You can create multiple policies, and they can be associated with an Application Gateway, to individual listeners, or to path-based routing rules on an Application Gateway. This way, you can have separate policies for each site behind your Application Gateway if needed. For more information on WAF Policies, see Create a WAF Policy.

 Note

Per-site and per-URI WAF Policies are in Public Preview. That means this feature is subject to Microsoft's Supplemental Terms of Use. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.

Application Gateway operates as an application delivery controller (ADC). It offers Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), termination, cookie-based session affinity, round-robin load distribution, content-based routing, ability to host multiple websites, and security enhancements.

Clean Code

Rockstar Status

Eliminate bugs and vulnerabilities.
Champion quality code in your projects.