The Professional Practice is the final hands-on stage of my Information Security studies at Teclab. I did it at Jiro Health, on the AppSec side of a HIPAA-regulated backend on Google Cloud Platform, and closed it with a recorded presentation in Spanish.
Mapping the cloud environment: how services connect, how data flows between them, and which users need which resources.
A licence-based authorization model with roles and privilege levels, designed together with the other engineers.
A CI/CD remediation pipeline on GitHub for Node.js projects: dependencies, secrets, and supply-chain vulnerabilities.
Reviewing Google Cloud Armor security policies and analysing AppSec incidents.
The hardest part was the remediation pipeline. The projects used different package managers, and no existing tool covered every requirement, so it took a long round of research and testing before it ran reliably everywhere.
The company evaluation rated every general and discipline skill as excellent, with time organisation and planning marked as good.
Speech script
This is the script I prepared for the recording, in Spanish, followed by an English translation. The spoken version follows it closely but not word for word.
Original script in Spanish
Slide 1, cover. Buenos días. Mi nombre es Artem Krivoshchekov y les presento los resultados de mi Práctica Profesionalizante. A lo largo de esta presentación voy a contarles quién soy y cuál fue mi rol en la organización, las dificultades que enfrenté durante la experiencia, y los aprendizajes que me llevo de ella.
Slide 2, who I am, role, contributions. Me desempeño como desarrollador backend con especialización en seguridad de aplicaciones, lo que se conoce como AppSec. Durante la práctica me integré al equipo de ingeniería de Jiro Health Inc., trabajando sobre un entorno en la nube, en Google Cloud Platform, con datos sensibles protegidos por la normativa HIPAA.
Mi primer paso fue comprender ese entorno: cómo se conectan los servicios, cómo fluyen los datos entre ellos y qué usuarios deben acceder a cada recurso. A partir de ahí realicé varios aportes concretos.
En primer lugar, junto a otros ingenieros, diseñé un sistema de autorización basado en licencias, con distintos roles y niveles de privilegio, administrador, moderador, archivador y lector, dentro de una misma organización. El resultado fue un módulo de autorización mejorado, con nuevas tablas en la base de datos, nuevos middlewares y funciones de verificación de permisos.
En segundo lugar, desarrollé un pipeline de remediación en CI/CD, sobre GitHub, para proyectos en Node.js, que audita y corrige automáticamente las dependencias. Esto ayudó al equipo a mitigar riesgos de cadena de suministro, filtración de secretos y vulnerabilidades en los paquetes.
Y por último, participé en la revisión de políticas de seguridad en Google Cloud Armor y en el análisis de incidentes de seguridad, evaluando la criticidad de cada vulnerabilidad, los módulos afectados y su forma de corrección.
Slide 3, difficulties. En cuanto a las dificultades, la principal la encontré al implementar el pipeline automático de remediación de vulnerabilidades. Los distintos proyectos de software trabajaban con diferentes gestores de dependencias, y tuve que adaptar la solución a cada uno de ellos.
El desafío fue que no existía una herramienta totalmente automática que cumpliera con todos los requerimientos del entorno. Por eso realicé una gran cantidad de pruebas e investigación, hasta llegar a una solución que funcionara de manera confiable en los distintos proyectos. Esta dificultad me exigió profundizar en el funcionamiento interno de cada ecosistema y fortalecer mi capacidad de análisis.
Slide 4, what I learned. Para cerrar, quiero compartir lo que aprendí. Esta práctica me permitió aplicar en un caso real conceptos de control de acceso y mínimo privilegio, en un contexto regulado por la normativa HIPAA. También aprendí a integrar la seguridad dentro del ciclo de desarrollo, mediante la automatización en CI/CD, y a trabajar sobre políticas de seguridad en la nube y análisis de riesgos de fuga de información.
Entre mis fortalezas destaco el trabajo en equipo con otros ingenieros, la autonomía técnica para investigar y resolver problemas que no tenían una solución preexistente, y la capacidad de traducir requerimientos de seguridad en soluciones concretas.
Agradezco a Jiro Health y a Teclab por esta experiencia, que integró lo aprendido en la carrera con un ámbito profesional real. Muchas gracias.
English translation
Slide 1, cover. Good morning. My name is Artem Krivoshchekov and I am presenting the results of my Professional Practice. Over this presentation I will tell you who I am and what my role in the organisation was, the difficulties I faced during the experience, and what I take away from it.
Slide 2, who I am, role, contributions. I work as a backend developer specialised in application security, known as AppSec. During the practice I joined the engineering team at Jiro Health Inc., working on a cloud environment on Google Cloud Platform, with sensitive data protected under HIPAA.
My first step was to understand that environment: how the services connect, how data flows between them, and which users should access each resource. From there I made several concrete contributions.
First, together with other engineers, I designed a licence-based authorization system with different roles and privilege levels, administrator, moderator, archiver and reader, within a single organisation. The result was an improved authorization module with new database tables, new middlewares and permission-check functions.
Second, I built a CI/CD remediation pipeline on GitHub for Node.js projects that audits and fixes dependencies automatically. This helped the team mitigate supply-chain risks, secret leaks and package vulnerabilities.
Finally, I took part in reviewing the Google Cloud Armor security policies and in security incident analysis, assessing the criticality of each vulnerability, the affected modules and how to fix them.
Slide 3, difficulties. The main difficulty came up while implementing the automatic vulnerability remediation pipeline. The different software projects used different package managers, and I had to adapt the solution to each of them.
The challenge was that no fully automatic tool met every requirement of the environment. So I did a great deal of testing and research until I reached a solution that worked reliably across the projects. This forced me to dig into the internals of each ecosystem and sharpen my analytical skills.
Slide 4, what I learned. To close, I want to share what I learned. This practice let me apply access control and least privilege concepts in a real case, in a HIPAA-regulated context. I also learned to integrate security into the development cycle through CI/CD automation, and to work on cloud security policies and data leak risk analysis.
Among my strengths I would highlight teamwork with other engineers, the technical autonomy to research and solve problems with no existing solution, and the ability to turn security requirements into concrete solutions.
I thank Jiro Health and Teclab for this experience, which brought together what I learned in the programme with a real professional setting. Thank you very much.
The recording is in Spanish. If you do not speak it, the translated script above is the quickest way to follow along.
Before: US medical practitioners had to piece together income, referrals and cash flows from systems that were slow to integrate.
After: as a principal/founding engineer I own API development end to end for my pods, building enterprise-grade interfaces on Node.js with Python background data processing.
How an in-house pipeline at Jiro Health finds vulnerable dependencies across repositories, patches them safely, and delivers one reviewable fix PR with a Jira ticket and Slack summary.
With the Teclab professional practice presented, I transferred to Universidad Siglo 21 to continue towards the Licenciatura en Seguridad Informática, a distance programme.
Open for contract collaboration
I am available for contract-based collaboration. If you have an interesting project idea, schedule a call via Calendly.