VIRTUAL CAIM   SAMPLE REPORT - fictional engagement, sanitized
All downloadsDownload PDF
VIRTUAL CAIM
Managed security and SOC

Monthly Security Operations
Report: October 2026

Prepared for Example Finserv Ltd. (fictional client). Round-the-clock monitoring, detection and response summary for 1 to 31 October 2026.
SAMPLE REPORT - fictional engagement, sanitized
Report ID
VC-SAMPLE-SOC-2026-10
Client
Example Finserv Ltd. (fictional NBFC)
Reporting period
1 October 2026 to 31 October 2026
Issued
5 November 2026
Service
24x7 SOC monitoring, detection engineering, incident response support
Classification
Confidential (sample). Fictional data throughout.

Document control and scope of service

Prepared by
Virtual Caim SOC (sample)
Reviewed by
SOC Manager and Service Delivery Lead (sample)
Distribution
CISO, Head of IT, Head of Risk, Compliance Officer (named list held in the service agreement)
Monitored estate
58 log sources, 1,240 endpoints with EDR, 2 data centres and 1 cloud region (all India), 3 business-critical applications
Use cases in production
142 detection rules mapped to MITRE ATT&CK, 9 SOAR playbooks
Operating hours
24x7x365, three shifts, Tier 1 and Tier 2 analysts with an on-call incident lead

Contents

  1. 1. Executive dashboard3
  2. 2. Alert volume and triage funnel4
  3. 3. Incident summaries5
  4. 4. Detection coverage against MITRE ATT&CK7
  5. 5. Log source health and retention9
  6. 6. SLA performance10
  7. 7. Threat intelligence and exposure11
  8. 8. Tuning actions12
  9. 9. Recommendations and next month12
  10. Annex. Definitions and conventions13
How to read this reportSection 1 is written for management and takes five minutes. Sections 2 to 8 are for the security and IT teams. Section 9 lists what we ask you to decide or do. Every metric is defined in the annex so that month-on-month comparison is fair.

1. Executive dashboard

412.6 M
Events ingested
up 6.1% on September
27
Incidents
1 P1, 4 P2, 13 P3, 9 P4
9 min
Median time to detect
September: 12 min
22 min
P1 time to contain
target 60 min
97.8%
Alert acknowledgement SLA
target 95%
96.3%
Resolution SLA
target 95%
1
Reported to CERT-In
within 6 hours
0
Confirmed data loss
month total
Overall posture: STABLE, WITH ONE WATCH ITEMNo incident this month led to confirmed loss of customer data or service. One P1 (phishing leading to a mailbox compromise, INC-2610-004) was contained in 22 minutes from acknowledgement and reported to CERT-In within the 6 hour window. The watch item is credential-based attacks: phishing and password spraying both increased, which supports the multi-factor and conditional access actions in section 9.

Alerts per week

1 to 7 Oct4310
8 to 14 Oct4702
15 to 21 Oct4988
22 to 31 Oct4640

Incidents by severity

P1 Critical1
P2 High4
P3 Medium13
P4 Low9

Median time to detect, last six months (minutes)

May 202617
June 202615
July 202614
August 202613
September 202612
October 20269

Top detection categories

CategoryAlerts reviewedShareTrue positive rate
Authentication anomalies (spray, impossible travel)1,10434.4%23%
Endpoint malware and suspicious execution68821.4%41%
Web application attacks (WAF, application logs)60218.7%19%
Network scanning and reconnaissance41012.8%12%
Data movement and DLP2387.4%37%
Other1705.3%30%

2. Alert volume and triage funnel

Raw correlation matches are enriched and de-duplicated by SOAR playbooks before an analyst sees them. The funnel below shows how volume reduces to the incidents that needed human response.

StageCountNotes
Events ingested412,600,00058 log sources, EDR telemetry, cloud audit logs
Correlation matches (raw alerts)18,640142 rules
Auto-closed by SOAR (enrichment, allow-list, known benign)15,42882.8% of raw alerts; each closure auditable
Analyst-reviewed alerts3,212Tier 1 and Tier 2
True positive alerts91828.6% of reviewed
False positive alerts2,29471.4% of reviewed (September: 76.0%)
Incidents opened27Grouped from related true positives

Funnel view

Raw alerts18640
Reviewed3212
True positive918
Incidents27

Alerts by log source family

Source familyRaw alertsReviewedIncidents
Identity and email5,2301,1049
Endpoint (EDR)4,1106888
Network and perimeter3,8704103
Web application and WAF3,4206025
Cloud and data2,0104082

Observations

3. Incident summaries

Six of the 27 incidents are summarised here: the P1, the P2 incidents and one P3 that carried a lesson. Technical detail for all 27 is in the case management system, available to named client users.

INC-2610-004 Credential-harvesting phishing and mailbox compromise (finance user)  Critical

Category
Phishing, unauthorised access (identity theft and phishing; unauthorised access of IT systems and data)
ATT&CK techniques
T1566.002 Spearphishing Link; T1078 Valid Accounts; T1114.003 Email Forwarding Rule
Timeline (IST)
8 Oct 14:12 detection (new inbox rule plus sign-in from an unusual location). 14:19 acknowledged. 14:41 account disabled, sessions revoked, rule removed. 15:30 scope check: 3 other recipients identified, no other sign-ins. 17:25 reported to CERT-In by the client Point of Contact (3 h 13 min after noticing).
Response
Account disabled and password reset. Phishing message removed from 3 mailboxes. Sender domain and link blocked. Affected user retrained. Mail logs reviewed for 30 days: no data transfer beyond the forwarding rule, which had forwarded 6 messages.
Root cause
User entered credentials on a lookalike sign-in page. Legacy authentication was still permitted for one protocol.
Reportability
Reported. Directions of 28 April 2022 require reporting within 6 hours of noticing. Client PoC filed the report with SOC support. The 6 forwarded messages held no customer personal data, and the client's internal personal-data breach assessment recorded that no notification duty arose.

INC-2610-009 Password spraying against the VPN gateway  High

Category
Unauthorised access attempt
ATT&CK techniques
T1110.003 Password Spraying
Timeline (IST)
12 Oct 02:40 detection (low-and-slow attempts across 212 accounts from rotating addresses). 02:47 acknowledged. 03:05 source ranges blocked. 03:20 two accounts with weak passwords reset.
Response
No successful sign-in (MFA enforced on all accounts). Attempt volume dropped to zero within the hour. Conditional access rule added for the gateway.
Root cause
Predictable passwords on two service-desk accounts.
Reportability
Assessed as an attempt with no compromise. Logged, not individually reportable.

INC-2610-012 Suspicious script execution on a branch workstation  High

Category
Malicious code
ATT&CK techniques
T1204.002 Malicious File; T1059.001 PowerShell; T1105 Ingress Tool Transfer
Timeline (IST)
14 Oct 11:03 detection by EDR behaviour rule. 11:08 acknowledged. 11:15 host isolated. 12:30 forensic triage complete. 15:10 host rebuilt.
Response
Host isolated and rebuilt. Hash and domain blocked tenant-wide. Mail gateway rule updated for the macro-enabled attachment type.
Root cause
User opened an attachment from a spoofed supplier email.
Reportability
Contained at the endpoint with no spread. Logged. No CERT-In report required.

INC-2610-017 Large upload to personal cloud storage by a contractor account  High

Category
Data leak (policy violation, internal)
ATT&CK techniques
T1567.002 Exfiltration to Cloud Storage
Timeline (IST)
19 Oct 16:44 DLP alert (1.2 GB in 9 minutes). 16:51 acknowledged. 17:10 session terminated and account suspended. 18:00 manager contacted.
Response
Contractor access suspended. Uploaded content reviewed with the client: internal project documents, no personal data. Contract reminder issued. DLP rule extended to cover two more storage services.
Root cause
Contractor used personal storage to work from home.
Reportability
Assessed as an internal policy violation with no personal data. Decision rationale recorded by the client Compliance Officer. Not reported.

INC-2610-021 Scanning followed by exploit attempts on a public web server  High

Category
Attack on application, targeted scanning
ATT&CK techniques
T1595.002 Vulnerability Scanning; T1190 Exploit Public-Facing Application
Timeline (IST)
22 Oct 20:15 detection (WAF plus web log correlation). 20:22 acknowledged. 20:35 offending ranges blocked. 21:10 patch status of the targeted component verified.
Response
All attempts blocked by WAF. The targeted component was already patched. Rule coverage for the vulnerability family confirmed.
Root cause
Opportunistic internet scanning of a known component.
Reportability
Mass internet scanning is not reported individually. Directions list targeted scanning of critical systems as reportable; this activity was assessed as untargeted. Logged with rationale.

INC-2610-023 Privileged account used outside the change window  Medium

Category
Policy deviation
ATT&CK techniques
T1078.002 Domain Accounts
Timeline (IST)
26 Oct 23:20 detection. 23:50 acknowledged. 27 Oct 11:00 confirmed as an emergency change with late approval.
Response
No malicious activity. Change record updated. Resolution SLA missed by 3 hours, waiting on the application owner.
Root cause
Emergency change raised after the work started.
Reportability
No report required. Process improvement noted.

4. Detection coverage against MITRE ATT&CK

Coverage is measured against techniques that the joint threat model has marked as relevant for Example Finserv (a lending business with retail and agent channels). A technique is Covered when at least one tested rule produces a usable alert, Partial when coverage depends on a single data source or is untested, and a Gap when nothing detects it.

ReconnaissanceTA0043
4 covered, 1 partial, 3 gap
56%
Resource DevelopmentTA0042
2 covered, 1 partial, 3 gap
42%
Initial AccessTA0001
9 covered, 1 partial, 1 gap
86%
ExecutionTA0002
10 covered, 1 partial, 1 gap
88%
PersistenceTA0003
11 covered, 3 partial, 2 gap
78%
Privilege EscalationTA0004
8 covered, 2 partial, 2 gap
75%
StealthTA0005
11 covered, 4 partial, 3 gap
72%
Defense ImpairmentTA0112
5 covered, 1 partial, 2 gap
69%
Credential AccessTA0006
10 covered, 2 partial, 2 gap
79%
DiscoveryTA0007
7 covered, 3 partial, 2 gap
71%
Lateral MovementTA0008
6 covered, 1 partial, 1 gap
81%
CollectionTA0009
5 covered, 2 partial, 2 gap
67%
Command and ControlTA0011
7 covered, 2 partial, 1 gap
80%
ExfiltrationTA0010
5 covered, 1 partial, 1 gap
79%
ImpactTA0040
7 covered, 1 partial, 1 gap
83%

Weighted coverage counts Partial as one half. Tactics follow the current ATT&CK Enterprise matrix as retrieved in November 2026. Overall: 160 prioritised techniques, 107 covered, 26 partial, 27 gaps, 75% weighted.

75%
Weighted coverage
September: 66%
107
Covered techniques
of 160 prioritised
27
Gaps
down from 33
11
New or improved rules
this month

Detail by tactic

TacticIDPrioritisedCoveredPartialGapWeighted %
ReconnaissanceTA0043841356%
Resource DevelopmentTA0042621342%
Initial AccessTA00011191186%
ExecutionTA000212101188%
PersistenceTA000316113278%
Privilege EscalationTA00041282275%
StealthTA000518114372%
Defense ImpairmentTA0112851269%
Credential AccessTA000614102279%
DiscoveryTA00071273271%
Lateral MovementTA0008861181%
CollectionTA0009952267%
Command and ControlTA00111072180%
ExfiltrationTA0010751179%
ImpactTA0040971183%

Largest remaining gaps and plan

AreaWhy it mattersPlan
Reconnaissance and resource developmentMostly outside your network. Visibility depends on threat intelligence.Brand-abuse and lookalike-domain monitoring added in November
Stealth (log tampering, masquerading)Attackers hide after initial accessAdd audit-policy change and log-clearing rules for 12 server groups
Discovery on endpointsEarly signal of intrusion, but noisyBehavioural baselines for admin tooling, tested in December
Collection (staging of data)Precursor to exfiltrationExtend DLP and file-access analytics to the lending database share

5. Log source health and retention

SourceTypeAvg events per secondHealth (month)Retention (days)LocationStatus
Perimeter firewalls (2)Network2,14099.98%365IndiaOK
Core and branch switchesNetwork61099.90%180IndiaOK
Identity provider and directoryIdentity48099.99%365IndiaOK
EDR (1,240 endpoints)Endpoint3,02099.70%180IndiaOK
Web application firewallWeb1,33099.95%365IndiaOK
Cloud audit logsCloud54099.95%180India regionOK
Email security gatewayEmail26099.90%180IndiaOK
Core lending applicationApplication19099.60%180IndiaOK
Legacy ERP applicationApplication3598.20%90IndiaAction
Branch router syslog (14 sites)Network7597.40%180IndiaWatch
CERT-In log retention checkThe CERT-In Directions of 28 April 2022 require logs of all ICT systems to be enabled and maintained securely for a rolling 180 days within Indian jurisdiction. All monitored sources meet the period except the legacy ERP application, which is set to 90 days. A change request has been raised with the application owner. Time synchronisation was also checked: 56 of 58 sources are within one second of the reference source; two branch routers drifted by 4 to 6 seconds and have been re-pointed to the corporate NTP server, which is itself synchronised to NIC or NPL servers.

Health issues this month

6. SLA performance

Clocks start when the alert is raised. Acknowledgement means an analyst has taken ownership. Response means containment has begun or a documented decision has been made.

SeverityAcknowledge targetRespond targetIncidentsMedian acknowledgeMedian respondSLA met
Critical P115 min60 min17 min22 min1 of 1
High P230 min4 h47 min1 h 12 min4 of 4
Medium P34 h24 h1331 min5 h 20 min12 of 13
Low P41 business day3 business days92 h 10 min1 business day9 of 9

Service-level summary

MeasureTargetAchievedTrend
Alert acknowledgement within target95%97.8%Up 1.1 points
Incident response within target95%96.3%Up 0.4 points
Monthly report issued by working day 5YesYes (5 November)Stable
Critical alerts handled by Tier 2 within 15 minutes100%100%Stable
Platform availability (SIEM)99.5%99.93%Stable

SLA exception

INC-2610-023 (P3) exceeded its resolution target by 3 hours because the confirmation needed from the application owner arrived the next morning. No security impact. We have agreed a named delegate for out-of-hours confirmations.

Resolution time by severity, median (hours)

P1 Critical0.4
P2 High1.2
P3 Medium5.3
P4 Low24

7. Threat intelligence and exposure

Relevant advisories and campaigns

ThemeRelevance to the clientSOC action
Phishing kits targeting financial services sign-in pagesDirectly relevant (see INC-2610-004)Lookalike-domain watchlist, mail gateway rule, user alert issued
Password spraying on remote accessSeen this month (INC-2610-009)Conditional access review, weak-password audit
Exploitation of internet-facing web componentsScanning observed (INC-2610-021)Patch verification and WAF virtual patch review
CERT-In advisories received and reviewed17 advisories this month9 applicable, 9 actions closed, 0 pending

External exposure snapshot

MeasureSeptemberOctoberComment
Internet-facing hosts4647One new host, owner confirmed
Critical or High exposures open53Two patched; one in change window
Expired or expiring certificates (30 days)21Renewal booked
Leaked credentials found in monitored sources47All forced to reset; none linked to a successful login
Lookalike domains registered23Takedown requests filed

Phishing simulation and reporting

Users reported 214 suspicious emails this month, up from 168. Median time from user report to SOC verdict was 14 minutes.

8. Tuning actions

Tuning keeps analysts focused on real activity. Each change is tested in a staging mode against seven days of history before release, and rolled back if true positives are lost.

Rule or use caseIssueChangeFalse positives beforeAfter
Impossible travel (identity)VPN exit nodes caused false alertsExcluded corporate VPN ranges, added device trust check31064
Brute-force on VPNThreshold too low for password sprayingAdded per-source and per-account windows4012
PowerShell encoded commandAdmin scripts flaggedAllow-list signed scripts by hash18841
Large outbound transferBackup jobs flaggedExcluded backup service accounts with time window9618
WAF scanning noiseDuplicate alertsGrouped by source over 15 minutes42095
New admin accountProvisioning flow flaggedCorrelated with approved change tickets527
Rare process on serverPatch cycle noiseMaintenance window suppression12630
Email forwarding rule (new)No rule existedAdded after INC-2610-004; 0 false positives to date-0

New detections released

9. Recommendations and next month

#RecommendationWhyOwner (suggested)PriorityTarget
1Disable legacy authentication tenant-wide and enforce phishing-resistant MFA for finance and privileged usersINC-2610-004 root causeIT and securityHigh30 days
2Raise ERP log retention to 180 days, confirm India-resident storageCERT-In direction (iv)Application ownerHigh30 days
3Enforce a password blocklist and review service-desk accountsINC-2610-009ITMedium30 days
4Complete EDR coverage on 14 silent endpointsCoverageITMedium15 days
5Add payments gateway and HR audit logsCoverage of critical applicationsSOC and application ownersMedium45 days
6Run a tabletop exercise on data breach notification (CERT-In 6 hours, regulator and DPDP process)ReadinessCISO, Compliance, SOCMediumQ1
7Name an out-of-hours delegate for change confirmationsSLA exceptionHead of ITLow15 days

Planned for November

Decisions we need from you

Annex. Definitions and conventions

TermDefinition
EventA single log record
AlertA correlation match raised by a detection rule
IncidentOne or more related true-positive alerts that require response
MTTDMedian time from first malicious activity visible in logs to alert (measured on incidents with a known start)
P1 to P4Critical, High, Medium, Low by impact and urgency, agreed in the service schedule
False positiveAlert reviewed and judged not to be malicious or a policy violation
Covered, Partial, GapDetection coverage categories used in section 4
SOARSecurity orchestration, automation and response
EDREndpoint detection and response
DLPData loss prevention
NTPNetwork time protocol

All names, systems, incidents and figures are fictional. MITRE ATT&CK is a registered trademark of The MITRE Corporation.