I’m Nikos Paschos, Senior DevOps Engineer at eSHARE. I’ve spent the last eight years deep in DevOps—shipping and scaling systems, building CI/CD, IaC, observability, and security controls that stick. Before eSHARE, I worked on platform reliability at Skroutz for 3+ years; earlier I co‑founded VisualEyes and built computer‑vision products at Loceye.
I studied Computer Software Engineering at AUTH.
In “SOC 2 to FedRAMP: A DevOps Survival Guide,” I’ll share a hands‑on playbook—policy‑as‑code, least‑privilege, reproducible pipelines, continuous evidence, and incident readiness—so teams can move from audit‑ready to cloud‑native compliant without slowing delivery.
I’m Nikos Paschos, Senior DevOps Engineer at eSHARE. I’ve spent the last eight years deep in DevOps—shipping and scaling systems, building CI/CD, IaC, observability, and security controls that stick. Before eSHARE, I worked on platform reliability at Skroutz for 3+ years; earlier I co‑founded VisualEyes and built computer‑vision products at Loceye.
I studied Computer Software Engineering at AUTH.
In “SOC 2 to FedRAMP: A DevOps Survival Guide,” I’ll share a hands‑on playbook—policy‑as‑code, least‑privilege, reproducible pipelines, continuous evidence, and incident readiness—so teams can move from audit‑ready to cloud‑native compliant without slowing delivery.
FedRAMP is the ticket to entry into the US public sector, unlocking access to $50B+ in annual federal IT spending. But it’s 325+ prescriptive controls can stall engineering velocity if treated like paperwork.
We took a different path. By embedding NIST 800-53 controls into infrastructure-as-code and automating continuous monitoring through CI/CD, we advanced from SOC 2 to FedRAMP efficiently. In this talk, we’ll share how DevOps practices turned compliance into code — accelerating delivery while meeting federal requirements.
