I'm Cameron Stihel, a CISSP cybersecurity and DevSecOps engineer. The work spans DoD RMF authorization activities, eMASS documentation, NIST SP 800-53 implementation reviews, vulnerability management, Terraform, Kubernetes, CI/CD security, and Python/Bash automation.
I take scoped problems where documentation and engineering overlap: an SSP review, ACAS findings, a deployment pipeline, or repetitive compliance work that should be automated.
Offerings
Scoped cybersecurity work. I do the engineering and write what has to go with it. None of this is included with the free app.
RMF and ATO packages
I build the authorization package: boundary, diagrams, control write-ups, evidence, POA&Ms, and eMASS artifacts when you authorize access.
Vulnerability remediation
I take authorized scan and STIG results, put the fixes in order, and make the approved configuration, patch, and hardening changes.
CI/CD, containers, and infrastructure
I secure GitLab pipelines, containers, Terraform, and Kubernetes, and leave the configuration and a runbook.
Security automation
I write the Python and Bash that replaces repeated inventory, scan reports, and evidence assembly.
Policies, plans, and technical documents
I draft the security plan, procedures, and architecture descriptions so they match how the system runs.
Ongoing engineering
I stay on as a security engineer for a defined scope when you do not need a full-time hire.
I do not grant an authorization, run unapproved scans, or replace your security staff. eMASS work only happens when you authorize access.
Discuss a projectHow an engagement works
- 1. Define the problem. We talk through the system, the outcome, the constraints, and what can be shared safely.
- 2. Agree on scope. If it is a fit, you get deliverables, assumptions, responsibilities, access requirements, a schedule, and pricing. Work starts after the agreement.
- 3. Review and implement. The work follows that scope: documentation review, technical assessment, approved remediation, automation, or a combination.
- 4. Hand over usable work. You get the artifacts, implementation notes, and the actions still open so your team can keep going.
Why this practice is different
The work crosses compliance and engineering. That includes RMF, eMASS artifacts, SSPs, and control review, and also Linux, Windows, vulnerability scanning, Terraform, Kubernetes, GitLab pipelines, and automation.
The software is a tool I use, not the product I am selling you first. CompliNIST is a real local application. It reduces repetitive document work. It is not a substitute for engineering judgment or evidence.
Deliverables stay specific. The point is a corrected artifact, a remediated configuration, working automation, or a prioritized technical plan.
Who this is for
- Engineering teams that need help with a security plan, scan findings, or the fixes, and do not have enough security engineering capacity of their own.
- Technical teams preparing an SSP or related artifacts and needing a reviewer who has done the work.
- Organizations with ACAS, Nessus, or STIG findings they need to understand and remediate.
- DevSecOps teams that need security checks and documentation inside an existing delivery process.
Some requests need an established prime, a clearance, or an agency role I cannot provide on my own. If the project needs that, I will say so during scoping.
Software and consulting are separate
CompliNIST Software is the free local NIST SP 800-53 documentation workbench. You can download it without hiring me.
CompliNIST Consulting is professional work scoped to your environment. It may use the software. It can also be done entirely in the tools you already approve.
Download the free toolFrequently asked questions
- Can you guarantee we will receive an ATO?
- No. The authorizing official makes that decision. The work focuses on accurate documentation, readiness, evidence, remediation, and technical implementation.
- Can you work directly in our eMASS system?
- Only when an authorized customer sponsors the access and assigns the responsibilities. I can review and help prepare documents without claiming independent system access.
- Are you a government-designated assessor?
- My background includes security control assessment review and RMF work. This practice is not a designated government assessor, a C3PAO, a FedRAMP 3PAO, or another approved assessment organization.
- Do we have to use CompliNIST software?
- No. The workbench is optional. I can work inside your approved tools, subject to access and the contract.
- Do you publish hourly rates?
- No. After I see the requirements, the proposal is either a fixed deliverable price or defined time-and-materials terms. Nothing starts before that proposal.
- Can you work with our existing team?
- Yes. Useful engagements include the people who own the system, the control implementations, the evidence, and the change process.
- Can you handle sensitive defense information?
- Data handling follows your policies, contracts, access decisions, and approved systems. Do not send CUI, classified material, credentials, or sensitive artifacts through the public form.
- Do you provide penetration testing or official certifications?
- Those are not offerings here. Any scanning or assessment has to be explicitly authorized, scoped, and matched to the qualifications the work requires.
Let's talk about the actual problem.
Tell me what you are trying to finish, what is blocking it, and whether you need documentation support, implementation help, or both.
All services are subject to availability, conflict checks, authorized access, and a separate written agreement. No guarantee of authorization, certification, security effectiveness, or assessment outcome.
Professional services are scoped and contracted separately from the free CompliNIST application. eMASS access, government coordination, security testing, and system changes require client authorization and applicable approvals. No authorization, certification, security outcome, or assessment decision is guaranteed.