Continuum helps small and midsize defense contractors connect cybersecurity requirements, actual implementation, and evidence to a manageable plan of work.
FEDERAL ASSESSMENT DISCIPLINE. PRACTICAL COMPLIANCE SUPPORT.
Ivan is a cybersecurity risk and security control assessment professional with more than 10 years of experience supporting federal information systems. His work spans the NIST Risk Management Framework, control testing, evidence validation, security documentation, and continuous monitoring.
Across security control assessment, ISSO, and risk assessment roles, Ivan has evaluated NIST SP 800-53 control implementation and developed or reviewed System Security Plans, Security Assessment Plans and Reports, risk assessments, and Plans of Action and Milestones. His work connects documentation, personnel explanations, and supporting artifacts to specific findings, corrective actions, and risk decisions.
Ivan leads Continuum's client relationships, engagement scoping, coordination, and deliverable review. His approach is to confirm the applicable requirements, understand the environment, validate evidence, and give the organization a prioritized plan with clear responsibilities. Federal authorization experience and CMMC readiness are distinct contexts; each engagement uses its applicable requirements and assessment procedures.
NIST RMF and security control assessment
SSP, SAP, SAR, risk assessment, and POA&M documentation
Evidence review and control implementation validation
Corrective-action tracking and continuous monitoring
Master of Science in Cybersecurity, University of Maryland Global Campus, 2020
Identify the contractual and assessment context before evaluating implementation. Federal RMF and NIST SP 800-53 experience provide assessment discipline; NIST SP 800-171 and CMMC readiness require their own applicable requirements and procedures.
Connect claims to evidence.
Review what documentation describes, what personnel can explain, and what the environment demonstrates. Record uncertainties and missing support so your organization can act on specific findings.
Keep ownership clear.
Define deliverables and responsibilities with your organization. Any technical changes or specialist testing are separately scoped with the client and a qualified provider before that work begins. Official certification assessments are performed by appropriately authorized or accredited organizations.
See how that approach becomes useful work.
Explore illustrative deliverables or discuss a defined diagnostic engagement for your organization.
Ivan provides a named point of accountability for scoping, client coordination, risk communication, and deliverable review. Each engagement starts with an agreed scope and the responsibilities needed to complete it.
A written scope.
Agree the systems and requirements to review, working assumptions, deliverables, exclusions, and information your organization will provide before work begins.
Named responsibilities.
Identify the client decision-maker, system and evidence owners, and Continuum's responsibilities. Any additional practitioner or technical provider is identified and scoped before their work begins.
Agreed communications.
Set points of contact, an update cadence, and a way to track findings, dependencies, and decisions. Raise scope changes for agreement before adding work.
Reviewed deliverables and next steps.
Review findings and supporting evidence with designated stakeholders, record unresolved questions, and hand over prioritized actions with ownership and evidence expectations.
See how the functions of a readiness engagement are assigned through our delivery model.