Continuous Monitoring vs Infrastructure Overhead
Focus monitoring on anomaly detection and critical-service degradation thresholds required by NIS2, discarding low-value telemetry to cut infrastructure overhead.
CyberTRIZ analysis · Banking contradiction OR011 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Continuous monitoring improves operational visibility but increases resource consumption across servers, networks, and cloud environments.
Banking TRIZ Resolution
Apply intelligent monitoring focused on abnormal behaviour, service degradation, and critical infrastructure rather than collecting every possible metric.
Recommended Principles
Principle 2 - Taking Out
Principle 21 - Skipping
Principle 23 - Feedback
Expected Outcome
Better operational visibility
Lower monitoring overhead
Faster incident detection
TRIZ principles applied
P2 Taking OutP21 SkippingP23 Feedback
Controls that address this (22)
EU_NIS2-CTRL-001 - Daily safeguarding reconciliationoperational · critical priority · Daily reconciliation between safeguarded customer balances, core ledger balances and safeguarded bank accounts. Variances above EUR 100 mustEU_NIS2-CTRL-002 - Critical ICT incident reportingoperational · critical priority · All major ICT incidents impacting payment services, customer data or availability must be classified within 4 hours and reported under DORA EU_NIS2-CTRL-003 - GDPR breach notification workflowoperational · critical priority · Personal data breaches must be assessed within 12 hours and reported to the Belgian DPA within 72 hours where risk to data subjects exists.