← Back to projects

Case file / Project 004

Security Proposal Workspace

A fictional security assessment that brings requirements, controls, evidence, and follow-up actions together.

  • Python
  • Cybersecurity
  • NIST CSF 2.0

The purpose

Why I built this

Working in IT has shown me how many security threats organizations face in their day-to-day operations. As AI changes the technology landscape, I want to help build a stronger security posture that can withstand both familiar and emerging risks.

At a cybersecurity summit in Philadelphia, a speaker who led IT at a New York hospital described an incident where default credentials in network settings gave someone a way in. That example stayed with me. A small detail can expose a foundational weakness, even when an organization has invested in other security measures.

The questions

The Questions Behind the Work

This project is helping me connect security frameworks to practical questions:

  1. Who owns a control?
  2. What evidence supports it?
  3. What still needs attention?

The process

From requirements to safeguards

The Security Proposal Workspace grew from my experience working on the technical side of a security proposal. I wanted a way to bring requirements, safeguards, evidence, and follow-up actions together so that gaps are easier to identify and discuss.

The project uses a fictional marketing company to demonstrate that process. For example, it can flag an MFA control that is marked as implemented but has no evidence linked to it.

Explore the assessment →

Proposed architecture

A fictional marketing company

This conceptual design illustrates proposed boundaries and safeguards for the fictional assessment. It is not a deployed or tested system.

Proposed security architecture. Public visitors reach a website through edge protection. Staff sign in with MFA and access a private application and restricted data. Selected systems send logs to monitoring; data is backed up separately.
Solid lines show requests or data; dashed amber shows identity verification; dotted blue shows security logs; purple shows backup.

The diagram is a proposal, not evidence that controls are configured, tested, or compliant.

Reflection

Returning to the questions

Findings and lessons will be added as the hands-on work is completed.