SECURING GENERATIVE AI IN THE CLOUD
-
ENTERPRISE SOC MONITORING WITH GCP & SPLUNK
SECURING GENERATIVE AI IN THE CLOUD
-
ENTERPRISE SOC MONITORING WITH GCP & SPLUNK
Secured Generative AI APIs with real-time GCP → Splunk pipeline processing 18.94GB+ logs
In choosing this project, I wanted to push beyond my comfort zone. My goal was to apply my foundational cybersecurity knowledge in a real-world simulation, bridging theory with practice. By leveraging AI assistance as a tool, I managed complex tasks, accelerated my learning, and delivered results that demonstrate adaptability and problem-solving under real constraints.
I created a complete security monitoring pipeline that protects generative AI APIs while giving security teams real-time visibility into threats. The system processes logs automatically and detects threats in under 60 seconds. It protects Vertex AI APIs while enabling SOC teams with real-time threat detection. Automated log processing eliminated 10+ hours/week manual work while reducing attack surface by 80%.
- 80% attack surface reduction through network isolation
- <60 second threat detection vs. previous hours
- 18.94GB+ security data processed automatically
- 10+ hours/week manual effort eliminated
2. ARCHITECTURE
User Requests → API Gateway (with keys) → AI API Service → Cloud Logging → Pub/Sub → Cloud Functions → Splunk
The security layers I added:
- API keys required for all access
- Firewall rules locked down to specific IPs
- Service accounts with minimal permissions
- Static IPs for reliable connections
- Automated threat detection pipeline
3. DASHBOARD SECTION
While dynamic IP constraints currently limit dashboard access, the entire data pipeline is production-ready:
- Real-time data flow from GCP → Splunk confirmed
- 18.94GB+ log processing capability proven
- <60 second pipeline latency achieved
- Dashboard infrastructure waiting for stable access
4. EVIDENCE GALLERY
#19: Successfully Configured Splunk
Established secure cloud foundation following industry best practices
#0: GCP Console with enabled APIs
Created production-ready generative AI API using Vertex AI
Vertex AI Studio — text chat (us-central1) with Temperature = 0.2. Prompt and generated SOC-hardening tip shown.
Vertex AI Studio (us-central1) — I tuned the model to Temperature 0.2 for predictable, low-variance outputs, which is important for SOC automation. Testing with a simple “SOC hardening tip” prompt establishes a baseline response I later reproduce from Cloud Run and API Gateway.
#1: Vertex AI Studio configuration
#2: Cloud Run deployment success (shows DevOps competency)
Implemented defense-in-depth security controls
#3: IAM least privilege configuration (shows security fundamentals)
#4: API Gateway security setup (shows API security expertise)
#5: VPC firewall rules (shows network security knowledge)
Conducted comprehensive security testing.
Successfully deployed and secured a generative AI API on Google Cloud. The API returns SOC hardening tips and enforces API key authentication through API Gateway. Demonstrated end-to-end functionality with 200 OK responses for authorized requests and 401/403 errors for unauthorized access attempts. Postman tests: 401/403 responses.
#6: Attack simulation results (shows offensive security understanding)
Demonstrated systematic problem diagnosis
#10: Logs Explorer with 0 results
#11: IAM configuration verification (shows thorough methodology)
Made strategic decision to migrate to new environment rather than incurring support costs or delays. Demonstrated cloud leadership by prioritizing project momentum while maintaining security standards.
#12: New project creation
#13: API enablement success
Delivered complete security monitoring pipeline.
#14: Rapid Cloud Run redeployment
#15: Logging breakthrough in new project (shows problem-resolution)
#16: Logs Router with data flow (shows pipeline success)
#17: Splunk data input configuration
#18: Splunk search results (shows operational visibility)
INFRASTUCTURE & SECURITY
#20: Static IP addresses reserved
#21: VM creation with static IP
#22: Firewall rules configuration
#23: Splunk installation completed
#25: Splunk Web accessible via curl
#27: Firewall secured to specific IP
#28: Cloud NAT configuration
#29: Splunk Dashboard
#30: Token creation review page
#31: Token value page
#32: Source code error + HEC token test
#33: Splunk data flow
Cloud Security
- Secure API design and protection
- Network isolation and firewall rules
- Identity and access management
-Static IP architecture
Monitoring & Operations
- Real-time log processing
- Threat detection pipelines
- Splunk integration
- Automated alerting
Infrastructure
- Google Cloud services
- Serverless functions
- Message queue systems
- Production deployments
Companies are rushing to use AI APIs but don't always secure them properly. I built a system that:
- Protects AI services from abuse and attacks
- Gives security teams real-time visibility
- Automates the boring monitoring work
- Scales to handle enterprise traffic
The technical challenges were real - changing IPs, service integrations, security configurations. But the system works and the data proves it.
This project was a real challenge, bridging the gap between cybersecurity theory and real-world practice. When I hit obstacles that stretched beyond my current knowledge, I used AI as a strategic tool—whether to verify configurations, generate code, or troubleshoot complex steps.
What made this experience truly valuable was taking complete ownership: I set the vision as if working for the world's most important client, then self-directed every step to make that vision real.