✏️ EDIT MODE ACTIVE — Click any cell or text to edit. Use + buttons to add rows. Use × to delete.
C2M2 Audit Report · ACCESS Domain
Access Control Matrix
Muskingum Valley Electric Cooperative (MVEC) — Identity & Access Management Assessment
Organization
Muskingum Valley Electric Cooperative
Report ID
MVEC-ACM-2025-001
Assessment Date
March 28, 2025
Prepared By
IT Department / C2M2 Assessor
Classification
SENSITIVE — Internal Use Only
C2M2 Domain
ACCESS (Identity & Access Management)
🎯 1. Scope & Purpose
Purpose: This Access Control Matrix documents all user accounts, system access rights, privileged accounts, shared/generic accounts, and third-party access arrangements for MVEC. It supports evaluation of the C2M2 ACCESS domain (Identity & Access Management) at MIL 1–3 and maps known gaps against NERC CIP-007-6 and NIST SP 800-53 AC controls.
Scope: All MVEC information systems including corporate IT (Active Directory-equivalent local accounts), operational technology (SCADA/HMI, AMI head-end, RTUs), and third-party remote access pathways. Contractor and vendor accounts are included. Physical access controls are out of scope for this report.
📊 2. IAM Summary
22
Total Accounts
12
Named User Accounts
5
Privileged Accounts
3
Shared/Generic Accts
2
Service Accounts
3
Third-Party Accounts
0%
MFA Coverage
Critical Finding: MVEC has zero MFA deployment across all systems. No centralized identity provider (Active Directory, LDAP, SSO) exists. Accounts are managed locally on each system with no unified provisioning or de-provisioning workflow.
👤 3. User Account Inventory
Note: All accounts are local OS/application accounts. No enterprise directory (AD/LDAP) is in use. Password policies are applied per-system with no central enforcement. Account provisioning/de-provisioning is manual and undocumented.
Account IDFull NameRole / TitleDepartment Account TypeMFALast PW ChangeStatusNotes
harmon.dDale HarmonGeneral ManagerExecutivePrivilegedNone2024-01-15ActiveFull admin on Corp LAN; local admin on SCADA workstation
fulton.rRandy FultonOperations ManagerOperationsPrivilegedNone2024-03-10ActiveRead/Write SCADA; approves switching orders
albright.cCarol AlbrightOffice Manager / BillingFinanceStandardNone2024-02-28ActiveCIS billing full access; QuickBooks admin
bynum.tTerry BynumLead LinemanField OpsStandardNone2023-11-05ActiveSCADA read-only; GIS read; tablet field access
westfall.mMark WestfallLineman / Crew LeadField OpsStandardNone2023-09-18ActiveGIS read; tablet field access; no SCADA
dobrowski.kKurt DobrowskiIT / OT AdminITPrivilegedNone2024-06-01ActiveLocal admin on all servers; SCADA full admin; primary IT contact
zumpf.bBarbara ZumpfCustomer Service RepCustomer SvcStandardNone2024-01-22ActiveCIS read/write; M365 standard; no OT access
pryor.jJim PryorStaking Tech / EngineerEngineeringStandardNone2023-12-10ActiveGIS full access; AutoCAD; no OT access
techpath.adminTechPath MSP (shared)Managed IT AdminVendorPrivilegedNoneUnknownActiveAlways-on VPN; local admin on all IT servers; shared credential
techpath.helpTechPath MSP (helpdesk)Managed IT HelpdeskVendorStandardNoneUnknownActiveM365 support access; shared credential among TechPath staff
ge.scadaGE Grid Solutions (VPN)SCADA Vendor SupportVendorPrivilegedNoneUnknownActiveDedicated site-to-site VPN; SCADA maintenance access; no MFA; always-on
nisc.portalNISC (billing SaaS)Billing System VendorVendorServiceNone2022-05-10ActiveAPI service account for CIS ↔ NISC portal sync
🔐 4. System Access Rights Matrix
Legend: ADMIN full administrative access  |  R/W read & write  |  R/O read only  |  no access
Account Corp LAN / File Server M365 / Email CIS (Billing) GIS / AutoCAD SCADA / HMI AMI Head-End QuickBooks NISC Portal Buckeye EMS
harmon.dADMINR/WR/WR/OR/WR/OR/WR/WR/O
fulton.rR/WR/WR/OR/WR/WR/WR/W
albright.cR/WR/WADMINADMINR/W
bynum.tR/WR/WR/OR/O
westfall.mR/WR/WR/O
dobrowski.kADMINR/WADMINADMINADMINADMINR/WR/WR/W
zumpf.bR/WR/WR/WR/O
pryor.jR/WR/WADMIN
techpath.adminADMINADMINADMINADMIN
techpath.helpR/OADMIN
ge.scadaADMIN
nisc.portalR/WADMIN
🛡️ 5. Privileged Accounts Register
Finding: No Privileged Access Management (PAM) tool is deployed. Privileged accounts share the same login pathway as standard users with no additional authentication step. Session recording of privileged activity does not exist.
AccountName / EntitySystems with Admin MFADedicated Admin AcctSession RecordedReview FrequencyRisk
harmon.dDale HarmonCorp LAN, M365, CIS, SCADANoneNoNoAnnualHIGH
fulton.rRandy FultonSCADA/HMI, AMI, Buckeye EMSNoneNoNoAnnualHIGH
dobrowski.kKurt DobrowskiAll IT servers, SCADA, AMI, GIS, CISNoneNoNoAnnualCRITICAL
techpath.adminTechPath MSP (shared)All IT servers, M365, CIS, GISNoneYes (vendor)NoNone / UnknownCRITICAL
ge.scadaGE Grid SolutionsSCADA/HMI (full admin)NoneYes (vendor)NoNone / UnknownCRITICAL
⚠️ 6. Shared & Generic Accounts
Critical Finding: Multiple shared accounts exist with no individual accountability. The SCADA_ADMIN account is the most critical — it is the primary operational account used for SCADA/HMI control actions and is shared among multiple operators. This account cannot be attributed to any individual user action in logs.
Account IDSystem(s)PurposeUsers with Access Password ChangedJustification on FileRiskRecommended Action
SCADA_ADMIN GE e-terra SCADA/HMI, SRV-002 Primary SCADA operational account; used for all HMI control actions harmon.d, fulton.r, dobrowski.k, ge.scada vendor Never (factory) No CRITICAL Immediate: create individual named accounts; disable shared account
techpath.admin All IT servers, CIS, GIS, M365 MSP managed IT administration — shared by all TechPath technicians Multiple TechPath staff (count unknown) Unknown — never confirmed changed No formal MOU CRITICAL Require named accounts per technician; implement MOU; enable logging
techpath.help M365, Corp LAN (read) Helpdesk support — shared by TechPath helpdesk staff Multiple TechPath helpdesk staff Unknown No formal MOU HIGH Require named accounts; scope access per ticket/session
⚙️ 7. Service Accounts
Account IDSystemPurpose Credential MgmtLeast PrivilegeReview StatusNotes
nisc.portal CIS ↔ NISC SaaS Portal API sync: billing data between on-prem CIS and NISC hosted portal Hardcoded in config Partial Not reviewed since deployment (2022) Credential stored in plaintext config file on SRV-003; password last changed 2022-05-10
ami.svc AMI Head-End (SRV-004) ↔ SCADA Automated data exchange between AMI head-end and SCADA historian Hardcoded in app No — excess rights Never reviewed Account has SCADA R/W access despite only needing read for meter data push; excess privilege
🌐 8. Third-Party & Vendor Remote Access
Finding: Both vendor remote access connections are always-on (no just-in-time access). Neither connection requires MFA. Access is not monitored in real time and no session recording is in place for either vendor.
VendorConnection MethodAlways-On? MFASystems AccessedAccess Level Documented MOU/MSASession LoggingRisk
TechPath Solutions (MSP) IPSec VPN (site-to-site) to Corp LAN (192.168.1.0/24) YES — 24/7 None All IT servers, M365, CIS, GIS ADMIN No formal MSA None CRITICAL
GE Grid Solutions (SCADA OEM) Dedicated site-to-site VPN directly to OT LAN (10.0.10.0/24) YES — 24/7 None SCADA/HMI (SRV-002, OT-001) ADMIN Basic SLA only None CRITICAL
Buckeye Rural Electric (RTO tie) Dedicated fiber + SCADA EMS link Operational only None Buckeye EMS portal (read-only telemetry export) R/O ICA on file EMS logs only MEDIUM
🔧 9. OT Device Credential Status
Critical Finding: Multiple OT/ICS devices retain factory default credentials. The SEL-351 relay at substation SS-02 (Oak Hill) has confirmed default username/password. The GE e-terra SCADA platform uses a shared SCADA_ADMIN account with a factory-set password. DNP3 SAv5 authentication is not implemented on any RTU or relay.
Asset IDDeviceLocation Default Creds ChangedMFA AvailableProtocol Auth Local Admin AccountRisk
OT-001GE e-terra SCADA ServerCoshocton HQPartial (SCADA_ADMIN shared)NoProprietary (no SAv5)SCADA_ADMIN (shared)CRITICAL
OT-002GE D20MX RTUSS-01 (Coshocton)YesNoDNP3 (no SAv5)rtu.admin (local)HIGH
OT-003GE D20MX RTUSS-02 (Oak Hill)UnknownNoDNP3 (no SAv5)rtu.admin (local)HIGH
OT-004SEL-2414 Substation ControllerSS-01 (Coshocton)YesNoDNP3 (no SAv5)SEL local accountHIGH
OT-005SEL-351 Protective RelaySS-01 (Coshocton)YesNoNone (serial)SEL local accountMEDIUM
OT-006SEL-351 Protective RelaySS-02 (Oak Hill)NO — DEFAULT PASSWORDNoNone (serial)SEL default "OTTER"CRITICAL
OT-008Landis+Gyr AMI Head-End v8.2Coshocton HQYesNoRF mesh (proprietary)ami.admin (local)HIGH
🚨 10. Access Control Gaps & Findings
#FindingSeverityC2M2 Domain / Practice Affected SystemsGap DescriptionRecommended RemediationTarget MIL
ACM-01 No MFA on any system CRITICAL ACCESS: ACM-1c, ACM-2a All systems Zero multi-factor authentication deployed across all 12 accounts and 9 systems. Remote access (VPN) has no second factor. Deploy MFA starting with privileged accounts and remote access; use Microsoft Authenticator or TOTP tokens; enforce at VPN gateway MIL 2 → MIL 3
ACM-02 Shared SCADA_ADMIN account — no individual accountability CRITICAL ACCESS: ACM-1a, ACM-1b; SITUATE: SA-2b SCADA/HMI (OT-001, SRV-002) Primary SCADA operational account is shared by 3 MVEC staff and GE vendor. No individual attribution in audit logs. Factory password never changed. Create individual named SCADA accounts; disable SCADA_ADMIN; implement role-based SCADA access; change all factory passwords immediately MIL 0 → MIL 2
ACM-03 No centralized identity management (no AD/LDAP/SSO) CRITICAL ACCESS: ACM-1a, ACM-2c, ACM-3a All systems Each system manages accounts locally. No central provisioning, de-provisioning, or policy enforcement. Terminated employee access cannot be reliably revoked across all systems simultaneously. Deploy Microsoft Entra ID (Azure AD) or on-prem AD with group policy; integrate all systems; automate provisioning/de-provisioning via HR triggers MIL 1 → MIL 3
ACM-04 Always-on third-party VPN with admin access — no JIT CRITICAL ACCESS: ACM-1e, ACM-2d; THIRD-PARTIES: TM-1a TechPath VPN, GE Grid VPN Both vendor VPNs are permanently active with admin-level credentials. No just-in-time (JIT) access, no session approval workflow, and no session recording. Implement JIT VPN access with ticket-based approval; require MFA for all vendor sessions; deploy privileged access workstation (PAW) for vendor use; record all sessions MIL 0 → MIL 3
ACM-05 Default factory credentials on SEL-351 relay (OT-006) at SS-02 CRITICAL ACCESS: ACM-1a; ARCH: AM-1b OT-006 (SEL-351, Oak Hill) SEL-351 at Oak Hill substation retains factory default password "OTTER". Device is accessible via the OT network segment. Immediately change to a strong unique password per MVEC password policy; document in credential vault; verify SS-01 relay (OT-005) password as well MIL 0 → MIL 1
ACM-06 No PAM tool — no privileged session management HIGH ACCESS: ACM-2a, ACM-2b, ACM-3b All systems with privileged accounts No Privileged Access Management (PAM) tool deployed. Privileged sessions are not recorded, no time-based check-out of credentials, no automatic credential rotation. Deploy PAM solution (CyberArk, BeyondTrust, or Delinea); vault all privileged credentials; enable session recording for all admin sessions MIL 1 → MIL 3
ACM-07 No formal access review process HIGH ACCESS: ACM-2c, ACM-3c All systems No documented periodic access review (recertification). Access accumulates over time. No evidence that terminated/transferred employee accounts are reviewed and revoked consistently. Implement quarterly access recertification; document and track account lifecycle; assign account owner for each system; create off-boarding checklist MIL 1 → MIL 2
ACM-08 DNP3 SAv5 not implemented on any RTU or relay HIGH ACCESS: ACM-1d; ARCH: AM-1b OT-002, OT-003 (RTUs), OT-004, OT-005, OT-006 (relays) DNP3 Secure Authentication version 5 (SAv5) is not configured on any field device. SCADA polling traffic is unauthenticated and susceptible to spoofing or replay attacks. Upgrade GE D20MX firmware to support SAv5; configure SAv5 on all DNP3 devices; test with GE Grid Solutions; include in next maintenance window MIL 1 → MIL 2
ACM-09 Service account credentials hardcoded / plaintext in config files MEDIUM ACCESS: ACM-1b, ACM-2a SRV-003, SRV-004 (service accounts) The nisc.portal and ami.svc service account credentials are stored in plaintext configuration files. The nisc.portal password was last changed in 2022 and has never been rotated. Migrate credentials to a secrets manager or encrypted vault; enable automatic credential rotation; audit all config files for hardcoded passwords MIL 1 → MIL 2
ACM-10 ami.svc service account has excess SCADA privileges MEDIUM ACCESS: ACM-1c (Least Privilege) SRV-004 (AMI), SCADA The AMI-to-SCADA service account has read/write SCADA access despite only requiring read access for meter data forwarding. Violates least-privilege principle. Create a dedicated read-only SCADA API account for AMI data push; revoke write permissions from ami.svc; document access justification MIL 1 → MIL 2
📋 11. C2M2 ACCESS Domain — Current MIL Assessment
C2M2 ACCESS Domain (Identity & Access Management): Evaluates practices for managing identities and access to technology assets, information, and operational environments. MIL 1 = performed, MIL 2 = managed (policy-driven), MIL 3 = optimized (continuously improved).
Practice IDPractice Description Current MILEvidence / NotesTarget MIL
ACM-1aIdentify and authenticate users, devices, and other assets prior to granting accessMIL 1 (Partial)Local accounts exist but shared accounts and default creds undermine authentication integrityMIL 2
ACM-1bManage identities and credentials for authorized users, devices, and servicesMIL 0No central identity provider; no credential management policy; hardcoded service account passwordsMIL 2
ACM-1cAuthorize access based on least privilege and separation of dutiesMIL 0No formal RBAC; users accumulate access; dobrowski.k is de-facto superuser for all systemsMIL 2
ACM-1dProtect access control informationMIL 1 (Partial)System-level access lists exist but are not centrally documented or protectedMIL 2
ACM-1eManage remote accessMIL 0Always-on vendor VPNs with no MFA, JIT, or session monitoringMIL 3
ACM-2aManage access control policies and proceduresMIL 0No formal access control policy document exists at MVECMIL 2
ACM-2bManage privileged access and accountsMIL 0No PAM; privileged accounts use same login as standard; no session recordingMIL 2
ACM-2cReview and update access rights periodicallyMIL 0No access review process; no documented recertification cadenceMIL 2
ACM-2dManage access for third-party entitiesMIL 0No formal MOU for TechPath; no JIT access; no vendor session loggingMIL 3
ACM-3aAutomate and enforce access control mechanismsMIL 0All access management is manual; no automated enforcement or provisioningMIL 3
ACM-3bContinuously monitor access activityMIL 0No SIEM; no centralized log collection; no behavioral monitoring of access patternsMIL 3
ACM-3cImprove access management using lessons learnedMIL 0No process to capture lessons learned from access incidents or near-missesMIL 3
Overall ACCESS Domain MIL Rating: MIL 0 / MIL 1 (Performed — Partial)
MVEC demonstrates MIL 0 on 8 of 12 ACCESS practices. The two MIL 1 (partial) ratings reflect that basic authentication mechanisms exist in some form, but are not consistently applied, documented, or managed. No MIL 2 practices are fully satisfied. This represents the highest-risk domain finding in the MVEC C2M2 assessment.
🗺️ 12. Remediation Roadmap
PriorityActionFindings Addressed Estimated EffortCost EstimateTarget CompletionOwner
Immediate Change SEL-351 (OT-006) default password at SS-02 ACM-05 2 hours (on-site field work) $0 (staff time) Within 48 hours K. Dobrowski / R. Fulton
Immediate Create individual SCADA accounts; disable SCADA_ADMIN shared account ACM-02 1 day $0 Within 1 week K. Dobrowski + GE Grid Solutions
Short-Term (30 days) Enable MFA on all privileged accounts and remote VPN access ACM-01, ACM-04 3–5 days $500–$2,000/yr (TOTP tokens or Authenticator app) 30 days TechPath MSP + K. Dobrowski
Short-Term (30 days) Implement JIT/ticketed access for vendor VPNs; disable always-on connections ACM-04 2–3 days $0 (policy + firewall config) 30 days K. Dobrowski + TechPath
Medium-Term (90 days) Deploy Microsoft Entra ID (Azure AD) for centralized identity management ACM-03, ACM-06, ACM-07 2–4 weeks $2,400–$6,000/yr (M365 licensing) 90 days TechPath MSP
Medium-Term (90 days) Implement formal access review (quarterly recertification) process ACM-07 3–5 days (policy + tooling) $0 (process; leverage AD if deployed) 90 days D. Harmon + K. Dobrowski
Medium-Term (90 days) Migrate service account credentials to encrypted vault; rotate passwords ACM-09, ACM-10 2 days $0–$500 (open-source vault or AD Managed Service Accounts) 90 days K. Dobrowski + TechPath
Long-Term (180 days) Implement DNP3 SAv5 on all RTUs and protective relays ACM-08 2–4 weeks (firmware + commissioning) $5,000–$15,000 (GE firmware upgrade + commissioning) 180 days GE Grid Solutions + R. Fulton
Long-Term (180+ days) Deploy PAM solution for privileged account management and session recording ACM-06 4–8 weeks $8,000–$20,000/yr (e.g., BeyondTrust or CyberArk Workforce Identity) 180 days TechPath MSP + D. Harmon (approval)