Do I need OSCAL for FedRAMP?
Increasingly, yes. FedRAMP 20x is built on continuous, machine-readable validation, and OSCAL packages are the exchange format. Even under the current program, agencies and 3PAOs increasingly expect OSCAL. Treating your SSP as living OSCAL - rather than a Word file you convert once under deadline - is now a practical prerequisite.
How do I convert a FedRAMP SSP to OSCAL?
Upload your FedRAMP Word or Excel SSP, including the Appendix A control-implementation format, to OscalIQ. It extracts the control implementations, parameters, and responsible roles, maps them to the OSCAL SSP model, and validates the result - producing a machine-readable OSCAL package you can export and maintain.
What is FedRAMP 20x and how does OSCAL fit?
FedRAMP 20x is FedRAMP's modernized path built around continuous, machine-readable validation using Key Security Indicators (KSIs) instead of a static once-a-year package. It assumes your security data is in OSCAL. OscalIQ converts your SSP to OSCAL, tracks each KSI, shows live 20x readiness, and emits the machine-readable package.
Does it handle FedRAMP Appendix A?
Yes. OscalIQ is built to read the FedRAMP control-implementation format (Appendix A) as well as narrative SSPs, extract the control data, and map it to OSCAL.
Which frameworks does OscalIQ support beyond FedRAMP?
FedRAMP (including 20x KSIs), NIST SP 800-53 Rev5, DISA STIGs, and CMMC 2.0 / NIST SP 800-171 Level 1 and Level 2 with DoD SPRS scoring - plus POA&M management and deviations.