Activity
161 followers
-
Conor Moening reacted on thisConor Moening reacted on thisView my verified achievement from Amazon Web Services (AWS).
-
Conor Moening reacted on thisConor Moening reacted on thisI am humbled and honored to share that I placed 1st in the National Cyber League Individual game a few weeks ago, hosted by Cyber Skyline. We had a wonderful team game as well with SANS Technology Institute - teamwork makes the dream work! Major thanks to the NCL and Cyberskyline for the competition! #cyber #cyberskyline #ncl #sansinstitute #sansedu
-
Conor Moening reacted on thisConor Moening reacted on thisToday, Cyber Skyline has officially delivered 100,000 cybersecurity assessments and we're honored to have played a role in the careers of so many people. It's been a crazy 7 years filled with tons of challenges turning a dorm room project into a real business. Grateful to have Toby Lin and, more recently, Conor Moening along for the journey. Onwards to 1,000,000! There's a lot more in store.
-
Conor Moening liked thisConor Moening liked thisI’m super happy to announce that I will be starting work at Google as a software engineer in July. I can’t wait! Shout out to Chico State Computer Science Department for providing such a great learning environment and resources!
Experience
Education
Licenses & Certifications
Honors & Awards
-
1st Place National Cyber League Team Game
National Cyber League & Cyberskyline
Placed 1st of 368 teams in the NCL.
-
Eagle Scout
Boy Scouts of America
Other similar profiles
Explore more posts
-
Tobias Heldt
Context determines risk. Our GitHub client had critical risks, suddenly through an unmarked CVE. The OSS dependency simply started filing CVEs. The vulnerabilities were there, the whole time. But because they weren't CVEs nobody knew. Risk is in the runtime, not in the dashboard. #cybersecurity #oss #startup
-
Meek M.
BREAKING: Is this happening because the developers failed to give the AI agent enough context or is it the capabilities of AI not being able to discern what the consequences of the code that they write are? This is a really challenging problem. AI is currently not performing well in small contract audit benchmarks, I hope this would change soon.
-
Eric Beans
RSA-2048 just got a death sentence. A new paper - "The Pinnacle Architecture" - proves it can be broken with fewer than 100,000 physical qubits. A year ago that number was a million. The year before, ten million. The timeline isn't shrinking. It's collapsing. This isn't theoretical. The math works under standard hardware assumptions available today. Your encryption is running out of time. Your vendors are still running RSA. Your incident response plan wasn't written for this world. H33 was. FHE. ZK proofs. Dilithium-3 on every operation. NIST FIPS 204-compliant. Running in production. Not a roadmap - a live system hardened against the threat that just got a lot more real. The quantum era just got a whole lot more serious, a whole lot sooner than we hoped... Are you ready?
-
Nielet D'Mello
What a well written article that demonstrates what it takes to operate on multiple levels of engineering simultaneously. It validates the challenges security engineers navigate, speaks of the velocity and friction dynamics for product teams, highlights the blueprint for platform engineering work and strongly makes a case of better abstractions. As a practitioner, I enjoyed reading about the journey and the learnings towards such maturity that comes from actually building these systems. Larkins Carvalho 👏🏻
-
Onyedikachi Obidiegwu
"Containers are isolated. They're secure by design." I hear this from developers. Here's the reality: Containers share the same kernel. One escape and your "isolated" containers are sharing more than just resources. That means: → A vulnerability in one container can potentially affect the host. → Your privileged containers have root access to the entire node. → That image you pulled from Docker Hub? It has 47 vulnerabilities and a crypto miner. (Yes, this is common.) Containers give you process isolation, not security isolation. They're lighter than VMs because they share the underlying operating system. That sharing is also their attack surface. The container security that actually works: → Scan every image before deployment, not just at build time → Run containers with minimal privileges (nobody needs root for a web server) → Update base images regularly (that Alpine image from 2019 isn't "stable," it's vulnerable) → Use runtime security that monitors container behavior, not just image contents Containers revolutionized deployment speed. But speed without security just means you're deploying vulnerabilities faster. Your container orchestration platform can spin up 100 pods in seconds. Can your security team detect a compromised container just as fast? Containers aren't inherently secure. They're inherently fast. Security is what you build on top. #CloudSecurity #ContainerSecurity #DevSecOps #Kubernetes
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content