Add Oracle Aggregator and CCIP Integration
- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control. - Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities. - Created .gitmodules to include OpenZeppelin contracts as a submodule. - Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment. - Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks. - Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring. - Created scripts for resource import and usage validation across non-US regions. - Added tests for CCIP error handling and integration to ensure robust functionality. - Included various new files and directories for the orchestration portal and deployment scripts.
This commit is contained in:
80
monitoring/security/security-monitoring.yaml
Normal file
80
monitoring/security/security-monitoring.yaml
Normal file
@@ -0,0 +1,80 @@
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: security-monitoring-config
|
||||
namespace: monitoring
|
||||
data:
|
||||
# Security monitoring configuration
|
||||
ENABLE_SECURITY_MONITORING: "true"
|
||||
ALERT_ON_VULNERABILITIES: "true"
|
||||
ALERT_ON_UNAUTHORIZED_ACCESS: "true"
|
||||
ALERT_ON_ANOMALOUS_ACTIVITY: "true"
|
||||
SECURITY_LOG_RETENTION_DAYS: "90"
|
||||
---
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: security-monitor
|
||||
namespace: monitoring
|
||||
spec:
|
||||
replicas: 1
|
||||
selector:
|
||||
matchLabels:
|
||||
app: security-monitor
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
app: security-monitor
|
||||
spec:
|
||||
containers:
|
||||
- name: security-monitor
|
||||
image: security-monitor:1.0.0
|
||||
env:
|
||||
- name: ENABLE_SECURITY_MONITORING
|
||||
valueFrom:
|
||||
configMapKeyRef:
|
||||
name: security-monitoring-config
|
||||
key: ENABLE_SECURITY_MONITORING
|
||||
resources:
|
||||
requests:
|
||||
cpu: "100m"
|
||||
memory: "256Mi"
|
||||
limits:
|
||||
cpu: "500m"
|
||||
memory: "512Mi"
|
||||
---
|
||||
# Security monitoring Prometheus alerts
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: security-alerts
|
||||
namespace: monitoring
|
||||
data:
|
||||
security-alerts.yml: |
|
||||
groups:
|
||||
- name: security
|
||||
rules:
|
||||
- alert: UnauthorizedAccessAttempt
|
||||
expr: rate(security_unauthorized_access_total[5m]) > 0
|
||||
for: 5m
|
||||
labels:
|
||||
severity: critical
|
||||
annotations:
|
||||
summary: "Unauthorized access attempt detected"
|
||||
|
||||
- alert: VulnerabilityDetected
|
||||
expr: security_vulnerabilities_total > 0
|
||||
for: 1m
|
||||
labels:
|
||||
severity: high
|
||||
annotations:
|
||||
summary: "Security vulnerability detected"
|
||||
|
||||
- alert: AnomalousActivity
|
||||
expr: rate(security_anomalous_activity_total[5m]) > 10
|
||||
for: 5m
|
||||
labels:
|
||||
severity: medium
|
||||
annotations:
|
||||
summary: "Anomalous activity detected"
|
||||
|
||||
Reference in New Issue
Block a user