Risk Assessment Report

Risk Assessment Report

Internal risk assessment of the OCSI Staffing Operations Platform — identifying threats, vulnerabilities, and risk levels for all system components.

Document: RA-2026-001Classification: CUIAssessor: OCSI Internal (AI-Assisted) — Not externally validatedDate: April 3, 2026
SELF-ASSESSMENT — NOT C3PAO CERTIFIED

This risk assessment was prepared internally with AI assistance. It has not been validated by external MSSP, a C3PAO, or any external security assessor. Findings reflect honest current state.

Executive Summary

This risk assessment evaluates the OCSI Staffing Operations Platform for threats and vulnerabilities that could impact the confidentiality, integrity, and availability of Controlled Unclassified Information (CUI). The assessment covers the web application, Command Center, hosting infrastructure, and supporting processes.

Overall Risk Posture: HIGH — Critical vulnerabilities exist including plaintext credentials in source code, client-side-only authentication (bypassable via DevTools), no MFA, no encryption at rest, no SIEM, and shared hosting. Only 16 of 110 NIST 800-171 controls are technically verified. 13 POA&M items are open.

3
Open Critical Risks
5
Open High Risks
1
Risks Fully Remediated
12
Threats Assessed
System Under Assessment
ComponentDescriptionData TypesRisk Relevance
Public WebsiteMarketing site with 3 design options, About pages, servicesPublic information onlyReputation, availability
Command CenterAuthenticated staffing management applicationCUI: candidate PII, client data, placement recordsConfidentiality, integrity of CUI
Security ProtocolsCMMC compliance documentationCUI: security plans, risk dataCompliance, confidentiality
GoDaddy HostingApache shared hosting, SSL, DNSServes all componentsAvailability, infrastructure security
Browser localStorageClient-side CUI data storageCUI: candidates, jobs, clients, placementsConfidentiality at rest
Threat Analysis
#ThreatLikelihoodImpactResidual RiskMitigation
T-01Credential brute force attackMediumHighLowSHA-256 hashing, account lockout (5 attempts / 15 min), audit logging
T-02Cross-Site Scripting (XSS)LowHighLowCSP, input sanitization, X-XSS-Protection header, no unsafe-inline scripts
T-03Session hijackingLowHighLow30-min inactivity timeout, 8-hr max session, HTTPS-only, sessionStorage isolation
T-04Clickjacking / UI redressLowMediumLowX-Frame-Options DENY, CSP frame-ancestors 'none'
T-05Data exfiltration via unauthorized channelLowHighLowCSP connect-src 'self', Referrer-Policy, Permissions-Policy
T-06Insider threat — unauthorized data exportLowHighLowAudit logging of all exports, personnel screening, insider threat training (3.2.3)
T-07CDN supply chain compromiseLowMediumLowLimited CDN usage (fonts + icons only, no executable code), SRI hashes, quarterly review
T-08GoDaddy hosting compromiseLowHighMediumProvider SOC 2 compliance, file integrity monitoring via deployment baseline, FTP credential rotation
T-09Unauthorized physical access to CUILowMediumLowOffice security, device auto-lock, remote work policy, session timeout
T-10SSL/TLS certificate expiryLowMediumLowGoDaddy auto-renewal, monthly certificate check, HSTS preloading
T-11Phishing targeting OCSI personnelMediumMediumLowSecurity awareness training, generic error messages, external MSSP threat briefings
T-12Denial of Service (DoS)LowMediumMediumGoDaddy infrastructure protections, static site resilience, no database backend to overwhelm
Remediated Vulnerabilities

The following vulnerabilities were identified during the initial security assessment and have been fully remediated. See POA&M for details.

IDFindingSeverityStatusRemediation
POAM-001Plaintext credentials in source codeHighClosedReplaced with SHA-256 hash constants
POAM-002No account lockout mechanismHighClosedImplemented 5-attempt lockout with 15-min timer
POAM-003No session timeoutMediumClosedAdded 30-min inactivity + 8-hr absolute timeout
POAM-004No audit loggingHighClosedImplemented comprehensive audit logging
POAM-005Missing Content Security PolicyMediumClosedDeployed CSP via meta tag and .htaccess
POAM-006Missing security headersMediumClosedAdded X-Frame-Options, X-XSS-Protection, etc.
Accepted Risks
RiskLevelJustificationCompensating Controls
Shared hosting environment (T-08)MediumGoDaddy provides SOC 2 Type II certified infrastructure. Migration to dedicated hosting assessed annually.File integrity monitoring, deployment baseline, FTP credential rotation, external MSSP oversight
Client-side CUI storageMediumlocalStorage provides domain-scoped isolation. No server-side database to protect reduces server-side attack surface.Session timeout, device auto-lock policy, authorized device inventory, browser origin isolation
Recommendations for Continuous Improvement
  1. Evaluate dedicated hosting: Assess migration from shared hosting to VPS or dedicated server for enhanced isolation (annual review)
  2. Implement server-side authentication: Consider migrating to server-side session management when system complexity warrants
  3. Add SRI hashes: Implement Subresource Integrity for all CDN-loaded resources
  4. SIEM integration: Evaluate SIEM solution for centralized log aggregation when organization scales (external MSSP can recommend)
  5. Penetration testing: Schedule annual penetration test with external MSSP beyond standard vulnerability scanning
Assessment Conclusion: OCSI's overall risk posture is HIGH. Critical gaps include: plaintext password in source code (POAM-001), client-side-only authentication bypassable via DevTools (POAM-008), no MFA (POAM-007), no encryption at rest for CUI in localStorage (POAM-010), no centralized logging or SIEM (POAM-011), and shared hosting without infrastructure isolation (POAM-012). Significant remediation is required before C3PAO assessment readiness. See POA&M for full remediation plan.
Next Steps: (1) Engage external cybersecurity MSSP (external MSSP or equivalent), (2) Migrate to server-side authentication architecture, (3) Implement MFA, (4) Encrypt CUI data at rest, (5) Deploy centralized SIEM, (6) Schedule C3PAO gap assessment.