Journal Update/support/internships
- Get link
- X
- Other Apps
Part Two: Capstone Ideas
For my first Capstone, I’d build a GovCloud-ready DevSecOps pipeline that automates secure software delivery: GitHub Actions would run tests, static analysis, and dependency scans; Terraform would provision a Kubernetes cluster with OPA/Gatekeeper policies; and Clair (or Anchore) plus Falco would handle image and runtime threat detection. I’d document alignment with DoD standards (e.g., FISMA) and demonstrate a one-click, compliant microservice deployment.
For my second Capstone, I’d create a secure over-the-air firmware update system for field devices: a Go-based agent would periodically check a signature-verified server, while a FastAPI backend hosts signed firmware and logs updates to a tamper-evident ledger. I’d simulate man-in-the-middle attacks to prove the client rejects tampered binaries and set up a CI/CD pipeline with an HSM emulator to build, sign, and publish firmware.
For my third Capstone, I’d implement an ML-powered network anomaly detection dashboard: Kafka would stream simulated NetFlow logs, Python scripts would extract features and train an Isolation Forest model, and a FastAPI backend would score flows and push alerts to a React front end. Containerizing everything with Docker/Kubernetes and automating weekly model retraining via CI/CD would showcase full-stack DevSecOps with practical machine learning.
Part Three: Learning Journal Update
This week’s readings on conflict showed me that disputes often escalate when I prioritize metrics or deadlines over relationships—forcing a fix can solve the problem quickly but erodes trust, while avoiding merely postpones critical issues. I learned that collaboration requires active listening (e.g., asking, “What security concerns keep you up at night?”) and negotiating trade-offs to find solutions everyone owns. For instance, instead of insisting on a strict CI/CD rollout schedule, I might pause to understand my teammate’s deployment worries and work together to build in additional security checks. Going forward, I’ll gauge both how much I care about the technical outcome and how much I value my coworker’s perspective before choosing among avoiding, accommodating, compromising, forcing, or collaborating.
Internships & Graduate Schools
Since I want to become a DevSecOps engineer in the defense sector, I’m targeting summer internships that blend cybersecurity, cloud infrastructure, and compliance with government standards (e.g., a DevSecOps role at a cleared defense contractor or a security-focused team at AWS GovCloud). I’ve updated my résumé to highlight container-hardening labs and a small FastAPI service instrumented with automated security tests so recruiters see I can integrate security into every phase of development.
For graduate school, I’m applying to master’s programs strong in information security and cloud-native architectures—UC San Diego’s Master of Advanced Studies in Networked Systems and UC Berkeley’s M.S. in Cybersecurity Engineering stand out because they offer coursework and research aligned with DevSecOps best practices (including FIPS-compliant deployments and continuous monitoring). I’m reaching out to faculty working on secure software pipelines in defense contexts to discuss potential research projects. Combining these conflict-management insights with targeted internships and a security-oriented graduate program will prepare me to design and maintain scalable, secure infrastructures within cleared defense environments.
- Get link
- X
- Other Apps


Comments
Post a Comment