Skip to content
Stepwork logoStepwork logo
Marketplace
Deterministic AgentsSecurity

The Stepwork Platform

Deterministic work across the tools you already run

  • Extraction
  • Rule
  • Webhook

In product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • File processingExtract fields, split scans, and fill PDF forms
  • Ask BobBuild a flow by chatting

Solutions

How Stepwork shows up for your team and industry

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
⌘K
Log inBook a Demo

Product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • File processingExtract fields, split scans, and fill PDF forms
  • Ask BobBuild a flow by chatting
Marketplace

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
Deterministic AgentsSecurity
Log inBook a Demo

FedRAMP Automation

Automate the manual work behind FedRAMP

FedRAMP Rev 5 and FedRAMP 20x break down into hundreds of recurring browser, portal, and workbook chores across your authorization boundary. Stepwork records each step once as a deterministic Flow and chains them into auditable Procedures—even in internal tools and government portals with no API.

Book a FedRAMP walkthroughExplore the 6 Procedures
  • Initial ATO & SSPNIST 800-53 screenshots, IIW sync, FIPS verification
  • Monthly ConMon & POA&MScanner exports, 30/90/180-day SLAs, Deviation Requests
  • Access & Change ControlPrivileged reviews, 24h offboarding, SCR triage
  • 3PAO & FedRAMP 20xERL fulfillment and continuous KSI evidence

Every manual step, mapped

Where FedRAMP teams lose hundreds of hours—and how Stepwork runs it

GRC platforms track what you owe, but your ISSOs and security engineers still spend weeks clicking through consoles, exporting CSVs, taking screenshots, and reconciling workbooks. Filter by lifecycle phase to see how each step maps to a repeatable Flow and Procedure.

    • AWSAWS
    • OktaOkta
    • Internal toolInternal tool
    • VantaVanta
    Monthly / Pre-3PAO
    Readiness & SSPCA-2CM-6AC-7

    Capture NIST 800-53 control screenshots across boundary apps

    Manual today

    Logging into 15–30 cloud, identity, SIEM, and internal admin consoles to take full-page screenshots with visible timestamps and rename every file by control ID.

    With Stepwork

    A scheduled Procedure loops through the control register, runs a recorded Flow per console, extracts the live setting value, and saves a timestamped screenshot to the control folder.

    FlowExtractionRule
    Timestamped control screenshots filed by NIST 800-53 ID
    See Procedure canvas→
    • AWSAWS
    • CrowdStrikeCrowdStrike
    • ExcelExcel
    Monthly
    Readiness & SSPCM-8SA-9

    Reconcile the Integrated Inventory Workbook (IIW)

    Manual today

    Cross-checking EC2 instances, containers, databases, SaaS tools, and network devices across consoles against the FedRAMP IIW spreadsheet to catch unrecorded assets before ConMon submission.

    With Stepwork

    Extractions pull asset tables from cloud consoles, EDR, and internal inventories, diff them against the live IIW rows, and update or flag deltas for ISSO review.

    ExtractionRuleFlow
    Reconciled IIW sheet with net-new & decommissioned asset diff
    See Procedure canvas→
    • AWSAWS
    • CloudflareCloudflare
    • Internal toolInternal tool
    • SlackSlack
    Quarterly / Pre-3PAO
    Readiness & SSPSC-8SC-13

    Verify FIPS 140-2/140-3 crypto & TLS settings across endpoints

    Manual today

    Checking load balancers, KMS policies, database encryption flags, and internal web portals one by one to prove FIPS-validated modules and TLS 1.2+ remain enforced.

    With Stepwork

    A deterministic Extraction reads cipher suites, KMS key rotation, and encryption flags across consoles, alerting owners immediately if any setting drifts from baseline.

    ExtractionRule
    Crypto baseline verification table + configuration screenshots
    See Procedure canvas→
    • OktaOkta
    • AWSAWS
    • ExcelExcel
    • VantaVanta
    Quarterly
    Readiness & SSPPL-2SA-4

    Refresh SSP implementation parameters & subprocessor tables

    Manual today

    Hunting down session timeout values, password lengths, backup retention windows, and third-party FedRAMP/SOC 2 dates across owners to keep the SSP accurate.

    With Stepwork

    Scheduled Extractions read live parameter values directly from system settings and populate the SSP parameter tracking sheet, flagging mismatches against documented policy.

    ExtractionRuleFlow
    Updated SSP parameter register with drift exceptions
    See Procedure canvas→
    • TenableTenable
    • WizWiz
    • AWSAWS
    • SharePointSharePoint
    Monthly (ConMon)
    Monthly ConMonRA-5SI-2

    Export OS, container, database & web-app vulnerability scans

    Manual today

    Triggering and downloading raw scan CSV/XML reports from Tenable, Qualys, Wiz, or AWS Inspector, verifying 100% boundary asset coverage, and archiving raw scan proof.

    With Stepwork

    On the first business day of the month, a Procedure exports every required scan report, checks asset coverage against the IIW, and saves immutable raw outputs.

    FlowExtractionAPI
    Monthly OS, container, DB, and web scan archives + coverage check
    See Procedure canvas→
    • TenableTenable
    • QualysQualys
    • ExcelExcel
    • JiraJira
    Monthly (ConMon)
    Monthly ConMonRA-5CA-7

    Deduplicate scanner findings & map CVE severity to assets

    Manual today

    Normalizing duplicate CVEs across OS and container scanners in Excel, mapping each finding to the responsible engineering team, and separating new findings from recurring items.

    With Stepwork

    Extractions join scanner tables with asset owners in the IIW, apply deterministic deduplication rules, and classify every open finding by FedRAMP severity tier.

    ExtractionRule
    Normalized monthly vulnerability ledger mapped to system owners
    See Procedure canvas→
    • SharePointSharePoint
    • BoxBox
    • Vendor portalVendor portal
    • SlackSlack
    Monthly (ConMon)
    Monthly ConMonCA-7CA-5

    Assemble & upload the monthly ConMon deliverables package

    Manual today

    Zipping raw scans, the updated POA&M, IIW, deviation requests, and executive summary into the exact folder naming convention and uploading to agency or government portals.

    With Stepwork

    After ISSO Approval, a recorded Flow verifies every required deliverable is present, uploads the bundle to the repository or portal, and logs the submission confirmation.

    RuleApprovalFlow
    Complete ConMon submission archive + upload confirmation screenshot
    See Procedure canvas→
    • DatadogDatadog
    • CrowdStrikeCrowdStrike
    • SlackSlack
    • VantaVanta
    Weekly
    Monthly ConMonAU-6IR-4

    Collect weekly SIEM alert & audit log review evidence

    Manual today

    Exporting weekly SIEM anomaly summaries, verifying log ingestion health across boundary services, and capturing proof that security alerts were triaged by an analyst.

    With Stepwork

    A weekly Procedure extracts SIEM ingestion status and high-priority alert resolution states, routing unreviewed alerts to Slack and filing signed evidence.

    ExtractionRuleFlow
    Weekly AU-6 log review record & ingestion health proof
    See Procedure canvas→
    • TenableTenable
    • JiraJira
    • ExcelExcel
    • SlackSlack
    Weekly / Monthly
    POA&M & DRsCA-5SI-2

    Sync High (30d), Moderate (90d) & Low (180d) POA&M SLAs

    Manual today

    Manually calculating FedRAMP remediation deadlines in the POA&M workbook, chasing engineers in Jira and Slack before 30/90/180-day clocks expire, and updating status comments.

    With Stepwork

    A Procedure syncs open findings with Jira/ServiceNow tickets, calculates remaining SLA days, escalates at 14/7/3 days remaining, and writes ticket progress back to the POA&M.

    ExtractionRuleFlowAPI
    Live FedRAMP POA&M workbook synced with engineering tickets
    See Procedure canvas→
    • JiraJira
    • WizWiz
    • TenableTenable
    • SharePointSharePoint
    Continuous
    POA&M & DRsCA-5RA-5

    Verify vulnerability remediation & capture closure evidence

    Manual today

    When an engineer closes a Jira ticket, an ISSO must re-check the scanner console to prove the CVE is actually gone, screenshot the clean scan, and mark the POA&M closed.

    With Stepwork

    Ticket closure triggers a Procedure that checks the scanner for the specific asset + CVE, captures clean-scan proof if resolved, or reopens the ticket if the finding persists.

    ExtractionRuleFlow
    Clean re-scan screenshot linked to closed POA&M row
    See Procedure canvas→
    • JiraJira
    • TenableTenable
    • Internal toolInternal tool
    • SharePointSharePoint
    As needed / Monthly
    POA&M & DRsCA-5RA-5

    Compile False Positive, Risk Adjustment & Vendor Dependency DRs

    Manual today

    Gathering vendor advisories, upstream patch timelines, compensating control screenshots, and scanner raw outputs into a formatted Deviation Request package for AO/3PAO sign-off.

    With Stepwork

    A Procedure extracts scanner details, pulls compensating-control proofs, checks completeness against FedRAMP DR requirements, pauses for ISSO Approval, and builds the DR folder.

    ExtractionRuleApprovalFlow
    Complete Deviation Request workbook + supporting evidence folder
    See Procedure canvas→
    • ExcelExcel
    • Vendor portalVendor portal
    • SlackSlack
    • JiraJira
    Monthly
    POA&M & DRsCA-5CA-7

    Track Vendor Dependency & Deviation Request renewal windows

    Manual today

    Realizing a vendor dependency or risk adjustment expired last week during ConMon review, forcing a last-minute scramble to re-verify upstream patch availability.

    With Stepwork

    Scheduled Rules scan active DR expiry dates 30 days ahead, re-check vendor advisories automatically, and route renewals to the ISSO before deadlines lapse.

    ExtractionRuleApproval
    Updated DR renewal status + re-verified vendor advisory capture
    See Procedure canvas→
    • OktaOkta
    • AWSAWS
    • GitHubGitHub
    • Internal toolInternal tool
    Monthly / Quarterly
    Access & SoDAC-2AC-6

    Run monthly/quarterly privileged user access reviews

    Manual today

    Exporting admin lists from Okta/Entra ID, AWS IAM, GitHub, jump hosts, databases, and legacy admin tools without SCIM, reconciling them in spreadsheets, and chasing manager sign-offs.

    With Stepwork

    Scheduled Extractions pull privileged rosters from every boundary app, compare against approved entitlements, pause for System Owner Approval, and archive signed review evidence.

    ExtractionRuleApprovalFlow
    Signed privileged access review sheet + before/after admin screenshots
    See Procedure canvas→
    • WorkdayWorkday
    • OktaOkta
    • AWSAWS
    • ServiceNowServiceNow
    Event-driven (24h SLA)
    Access & SoDPS-4AC-2

    Execute & prove 24-hour terminated-user access revocation

    Manual today

    Manually revoking sessions and admin accounts across boundary consoles within FedRAMP's tight offboarding window and proving every account was disabled on time.

    With Stepwork

    HRIS termination triggers a deterministic Procedure that revokes access across IdP, cloud, and non-SCIM consoles, captures timestamped deactivation proof, and logs closure.

    FlowExtractionRule
    Timestamped revocation screenshots proving <24h deprovisioning
    See Procedure canvas→
    • OktaOkta
    • Microsoft Entra IDMicrosoft Entra ID
    • AWSAWS
    • VantaVanta
    Monthly
    Access & SoDIA-2AC-2(3)

    Verify phishing-resistant MFA & inactive account lockouts

    Manual today

    Auditing factor types across identity providers and bastion consoles to prove FIPS-validated/phishing-resistant MFA is enforced and accounts inactive >35/90 days are disabled.

    With Stepwork

    An Extraction reads MFA factor policies and last-login timestamps across IdP and boundary tools, flags exceptions to SecOps, and archives compliant snapshots.

    ExtractionRuleFlow
    MFA enforcement & inactive-account audit log + screenshots
    See Procedure canvas→
    • GitHubGitHub
    • AWSAWS
    • JiraJira
    • VantaVanta
    Quarterly
    Access & SoDAC-5CM-5

    Check Separation of Duties (SoD) across prod & CI/CD

    Manual today

    Proving the same engineer cannot author code, self-approve a pull request, and deploy directly into the FedRAMP production boundary without independent review.

    With Stepwork

    Extractions pull GitHub branch protection rules, CI/CD deploy roles, and IAM admin groups, cross-checking for conflicting memberships and flagging violations.

    ExtractionRule
    SoD conflict matrix + branch protection evidence captures
    See Procedure canvas→
    • JiraJira
    • GitHubGitHub
    • AWSAWS
    • SlackSlack
    Per release / Weekly
    Change & SCRsCM-3CM-4

    Screen releases for Significant Change Request (SCR) triggers

    Manual today

    Reviewing Jira epics, Terraform diffs, and architecture tickets by hand to spot new external interconnections, encryption changes, or boundary shifts that require formal SCR notice.

    With Stepwork

    Change tickets trigger a Procedure that extracts PR scope and cloud asset changes, applies SCR trigger rules, and escalates significant changes for ISSO/CISO Approval.

    ExtractionRuleApproval
    SCR impact determination log + ISSO sign-off record
    See Procedure canvas→
    • JiraJira
    • GitHubGitHub
    • ServiceNowServiceNow
    • SharePointSharePoint
    Per release
    Change & SCRsCM-3SA-11

    Collect CAB approvals, test results & rollback plans

    Manual today

    Chasing down missing peer reviews, QA test pass screenshots, and Change Advisory Board approvals across Jira, GitHub, and Slack right before a 3PAO sample audit.

    With Stepwork

    A Procedure validates required PR reviews, CI test runs, and CAB sign-offs before release, pausing for Approval when fields are missing and archiving the complete change packet.

    ExtractionRuleApprovalFlow
    Auditable CM-3 change ticket packet with linked PR & test proof
    See Procedure canvas→
    • WizWiz
    • AWSAWS
    • Microsoft IntuneMicrosoft Intune
    • JiraJira
    Weekly / Monthly
    Change & SCRsCM-6CM-7

    Monitor CIS / STIG hardening & baseline configuration drift

    Manual today

    Exporting hardening benchmark scores from cloud posture and MDM consoles, investigating drifted security groups or open ports, and documenting remediation tickets.

    With Stepwork

    Scheduled Extractions pull posture benchmark findings, filter out approved baselines, open remediation tickets for drifted resources, and record baseline compliance.

    ExtractionRuleFlow
    Baseline hardening report + drift remediation ticket trail
    See Procedure canvas→
    • AWSAWS
    • Internal toolInternal tool
    • SharePointSharePoint
    • VantaVanta
    Monthly / Annual
    Change & SCRsCP-4CP-9

    Document backup verification & annual CP-4 tabletop evidence

    Manual today

    Logging into backup consoles to verify encrypted snapshots completed, checking restore test logs, and compiling annual Contingency Plan test evidence.

    With Stepwork

    Monthly Flows capture backup job health, encryption status, and restore test timestamps across databases and storage, filing signed proof into the CP evidence folder.

    FlowExtractionRule
    Encrypted backup & restore verification log with screenshots
    See Procedure canvas→
    • ExcelExcel
    • AWSAWS
    • OktaOkta
    Initial ATO & Annual
    3PAO & 20x KSICA-2All families

    Fulfill 3PAO Evidence Request Lists (ERLs) at scale

    Manual today

    Scrambling to gather 150–400 requested screenshots, population lists, and sample artifacts from 10 different teams while auditors bill hours waiting on incomplete folders.

    With Stepwork

    A Procedure reads the 3PAO ERL spreadsheet row by row, dispatches recorded Flows across boundary apps, verifies freshness and naming, and flags missing items before upload.

    ExtractionFlowRule
    Structured 3PAO evidence bundle indexed by ERL row & control ID
    See Procedure canvas→
    • AWSAWS
    • WizWiz
    • OktaOkta
    • Internal toolInternal tool
    Continuous / Automated
    3PAO & 20x KSIFedRAMP 20xKSIOSCAL

    Continuously validate FedRAMP 20x Key Security Indicators (KSIs)

    Manual today

    FedRAMP 20x shifts authorization toward continuous, machine-verifiable KSI evidence—yet many legacy, internal, and vendor tools still lack clean APIs to report their state.

    With Stepwork

    Stepwork bridges the API gap: deterministic Extractions read live configuration state off any screen or API, normalize structured KSI outputs, and keep continuous proof fresh.

    ExtractionAPIRule
    Structured KSI status payload + verifiable step screenshots
    See Procedure canvas→
    • WorkdayWorkday
    • VantaVanta
    • SlackSlack
    • SharePointSharePoint
    Quarterly / Pre-3PAO
    3PAO & 20x KSIAT-2AT-3PS-3

    Audit security awareness training & background check rosters

    Manual today

    Exporting active boundary personnel from HRIS, cross-checking LMS completion dates and role-based security training certificates, and nudging overdue staff.

    With Stepwork

    A scheduled Procedure reconciles the boundary roster against HRIS and training portals, messages overdue personnel in Slack/Teams, and compiles the AT-2/PS-3 audit table.

    ExtractionRuleFlow
    Reconciled AT-2/PS-3 completion roster + training proof
    See Procedure canvas→
    • JiraJira
    • GitHubGitHub
    • TenableTenable
    • SharePointSharePoint
    Annual
    3PAO & 20x KSICA-2CA-5

    Package annual assessment sampling & SAR re-test evidence

    Manual today

    Re-pulling sampled tickets, offboarded users, and patch records from the past 12 months—and quickly capturing re-test screenshots to clear findings before SAR lock.

    With Stepwork

    Given the 3PAO sample IDs, a Procedure pulls every matching ticket, PR, user record, and scan result automatically, packaging clean re-test proof in minutes.

    ExtractionFlowRule
    Annual 3PAO sample binder & SAR remediation re-test proof
    See Procedure canvas→

Procedures in action

6 end-to-end Procedures that automate the FedRAMP lifecycle

Switch tools below to match your security stack, inspect how variables flow from step to step, or start the guided walkthrough on any Procedure. Every blue pipe connects recorded Flows, Extractions, Rules, and Approvals into one repeatable run.

Monthly ConMon scan export → POA&M workbook & Jira SLA sync

Every month Stepwork exports raw boundary scans from Tenable, reconciles each CVE against your IIW and POA&M clocks, updates remediation tickets in Jira, escalates findings approaching FedRAMP's 30/90/180-day deadlines in Slack, and files the complete ConMon package into SharePoint.
  • Tenable
  • Excel
  • Jira
  • Slack
  • SharePoint
Swap in your systemsThe steps stay the same. Only the screens change.
Vulnerability scanner
Remediation tracker
Security alerts
ConMon archive
Monthly ConMon scan export → POA&M workbook & Jira SLA sync
Extraction
Tenable

Export monthly boundary scans from Tenable

Scheduled · 1st business day at 06:00

Extracted variables

  • cve_id
  • asset_host
  • severity
  • raw_scan_csv
Extraction
Excel

Match assets & SLA clocks against IIW and POA&M

Input variables

  • asset_host
  • cve_id
  • severity

Extracted variables

  • system_owner
  • days_remaining
  • poam_id
Rule logic

Within 7 days of 30 / 90 / 180-day SLA?

Input variables

  • severity
  • days_remaining

Paths

  1. If High ≤30d, Moderate ≤90d, or Low ≤180d deadline is within 7 daysThen: Escalate nearing SLA breach to owner in Slack
  2. OtherwiseThen: Create or update remediation ticket in Jira
Execution
If SLA at risk
Slack

Escalate nearing SLA breach to owner in Slack

Input variables

  • poam_id
  • cve_id
  • system_owner
  • days_remaining

Output

  • escalation_note
Execution
Within normal SLA window
Jira

Create or update remediation ticket in Jira

Input variables

  • poam_id
  • cve_id
  • asset_host
  • system_owner

Output

  • ticket_key
Summary

Compile monthly ConMon summary & updated POA&M

Input variables

  • ticket_key
  • escalation_note
  • raw_scan_csv

Output

  • conmon_bundle
Execution
SharePoint

Upload ConMon package & raw scans to SharePoint

Input variables

  • conmon_bundle
  • raw_scan_csv

Drag to explore · pinch to zoom

Step by step

  1. 1
    Monthly scans are exported automatically
    On the first business day, Stepwork signs in to Tenable, pulls OS, container, database, and web scan outputs, and keeps the raw scan files for audit proof.
  2. 2
    Each finding is matched to your IIW & POA&M
    Stepwork checks every host against your Integrated Inventory Workbook to assign the system owner and calculates remaining days against FedRAMP's 30-day High, 90-day Moderate, and 180-day Low clocks.
    Repeats: For each open vulnerability in monthly scan · 140 findings
  3. 3
    SLA rule flags overdue or at-risk items
    Findings approaching their FedRAMP remediation window branch upward for immediate owner escalation; findings inside normal SLA go straight to ticket sync.
    • If SLA at riskEscalate nearing SLA breach to owner in Slack
    • Within normal SLA windowCreate or update remediation ticket in Jira
    Repeats: For each open vulnerability in monthly scan · 140 findings
  4. 4
    At-risk SLAs alert the owner in Slack
    Before a finding breaches ConMon SLA—or needs a Deviation Request—Stepwork alerts the system owner and ISSO in Slack with the POA&M ID and days remaining.
    Only on this path: If SLA at riskRepeats: For each open vulnerability in monthly scan · 140 findings
  5. 5
    Engineering tickets stay synced in Jira
    Stepwork opens new tickets or updates existing ones in Jira with CVE details, affected boundary hosts, and the exact FedRAMP due date.
    Only on this path: Within normal SLA windowRepeats: For each open vulnerability in monthly scan · 140 findings
  6. 6
    Monthly ConMon deliverables are assembled
    After the final finding, the Summary card generates the updated POA&M log, asset coverage check, and executive delta summary.
  7. 7
    Raw scans and POA&M are filed in SharePoint
    The recorded Flow uploads the raw scan files, updated POA&M, and ConMon summary to SharePoint using your agency or 3PAO folder structure.

Field map

FromTo
TenablePlugin / CVE ID & SeverityExcelFedRAMP POA&M: Weakness ID & Risk
ExcelIIW: System Owner & SLA Due DateJiraAssignee & Due Date
TenableRaw CSV / XML scan bundleSharePointMonthly ConMon folder

Capture NIST 800-53 control screenshots & settings into Vanta

Instead of ISSOs spending a week screenshotting consoles before an assessment, Stepwork works through your NIST 800-53 control list, inspects each boundary app (with or without an API), catches drift before it becomes a finding, and files timestamped evidence into Vanta.
  • Excel
  • AWS
  • Internal tool
  • Vanta
  • Slack
Swap in your systemsThe steps stay the same. Only the screens change.
GRC platform
Drift alerts

Step by step

  1. 1
    Reads your NIST 800-53 evidence matrix
    Stepwork loads each control ID (e.g., AC-7, SC-13, CM-6), the boundary console to inspect, and the exact configuration baseline documented in your SSP.
  2. 2
    Inspects every console—API or no API
    Inside the loop, a recorded Flow opens each boundary console, reads live settings like FIPS mode, TLS ciphers, or session timeouts, and captures a timestamped screenshot.
    Repeats: For each NIST 800-53 control in boundary register · 28 boundary apps
  3. 3
    Checks the live state against your SSP
    If a setting drifted out of compliance, Stepwork routes it upward to the owner rather than uploading failing proof.
    • If control driftedAlert control owner of config drift in Slack
    • Meets SSP control baselineUpload control screenshot & metadata to Vanta
    Repeats: For each NIST 800-53 control in boundary register · 28 boundary apps
  4. 4
    Routes drift directly to the system owner
    Owners receive an alert in Slack naming the exact control ID, app, and observed value so remediation happens immediately.
    Only on this path: If control driftedRepeats: For each NIST 800-53 control in boundary register · 28 boundary apps
  5. 5
    Files verified screenshots in Vanta
    Compliant captures are uploaded directly to the matching control in Vanta with standardized control-ID naming and run date.
    Only on this path: Meets SSP control baselineRepeats: For each NIST 800-53 control in boundary register · 28 boundary apps
  6. 6
    Publishes SSP readiness status
    The final Summary card reports total controls verified, evidence links filed, and open drift items remaining.

Field map

FromTo
AWSKMS & TLS policy configuration screenVantaControl SC-13 / SC-8 evidence attachment
Internal toolSession timeout & lockout settingVantaControl AC-7 / AC-12 evidence attachment
ExcelSSP Control Matrix: expected baselineSlackDrift alert when observed value differs

Privileged access review & 24-hour revocation across Okta, AWS & portals

Proves AC-2, AC-6, IA-2, and PS-4 continuously: Stepwork extracts privileged accounts from Okta, AWS, GitHub, and non-SCIM consoles, pauses for named ISSO approval in Slack on every exception, executes revocations with screenshots, and files the signed evidence packet in SharePoint.
  • Okta
  • AWS
  • GitHub
  • Slack
  • ServiceNow
  • SharePoint
Swap in your systemsThe steps stay the same. Only the screens change.
Identity provider
ISSO approvals
Audit ticket
Evidence archive

Step by step

  1. 1
    Extracts every privileged account across the boundary
    Stepwork collects admin memberships, last-login dates, and MFA factor types across Okta, AWS IAM, GitHub, and internal admin tools that lack SCIM.
  2. 2
    Checks inactivity, offboarding & MFA compliance
    Compliant accounts pass straight to the signed roster. Orphaned, inactive, or unapproved privileged roles branch upward for action.
    • If exception foundPause for named ISSO approval in Slack
    • Approved & compliantCompile AC-2 / AC-6 privileged access review roster
    Repeats: For each privileged account inside the boundary · 42 privileged accounts
  3. 3
    Named ISSO approves revocation in Slack
    Before removing access, Stepwork pauses for an ISSO or System Owner decision in Slack and records who approved and when.
    Only on this path: If exception foundRepeats: For each privileged account inside the boundary · 42 privileged accounts
  4. 4
    Executes revocation and captures proof
    Once approved, a recorded Flow removes the role inside the target console and saves a timestamped screenshot proving the account was disabled within SLA.
    Only on this path: If exception foundRepeats: For each privileged account inside the boundary · 42 privileged accounts
  5. 5
    Logs an immutable audit ticket in ServiceNow
    Stepwork writes the approver identity, timestamp, and revocation screenshot into ServiceNow for 3PAO sampling.
    Only on this path: If exception foundRepeats: For each privileged account inside the boundary · 42 privileged accounts
  6. 6
    Builds the AC-2 / AC-6 review binder
    Summarizes every verified admin, every revoked account, and every approver sign-off in one structured table.
  7. 7
    Archives evidence directly into SharePoint
    Uploads the final review workbook and all before/after screenshots to SharePoint under the current review period.

Field map

FromTo
OktaAdmin groups, MFA factor & last loginSharePointAC-2 / IA-2 quarterly review workbook
SlackNamed ISSO approval & timestampServiceNowAudit ticket approval note
AWSIAM role removal confirmation screenSharePointPS-4 24h revocation screenshot

Significant Change Request (SCR) triage & IIW boundary sync from Jira

Stops unapproved boundary changes before deploy. Every release ticket in Jira triggers an automated check of GitHub PRs and cloud resource diffs, flags FedRAMP Significant Change criteria for ISSO/CISO approval in Slack, keeps the IIW in sync, and files complete CM-3 proof.
  • Jira
  • GitHub
  • AWS
  • Excel
  • Slack
  • SharePoint
Swap in your systemsThe steps stay the same. Only the screens change.
Change management
CAB / ISSO approval
Change register

Step by step

  1. 1
    Starts from your existing release ticket
    Jira fires a webhook whenever a production deployment or infrastructure change request opens.
  2. 2
    Extracts PR approvals, test runs & resource diffs
    Stepwork reads GitHub PR sign-offs, CI test results, and cloud asset changes without engineers manually pasting screenshots.
  3. 3
    Screens against FedRAMP SCR rules
    Changes touching external interconnections, authentication, encryption, or boundary scope take the top SCR approval path.
    • If Significant ChangeRoute SCR impact analysis for ISSO / CISO approval in Slack
    • Standard CM-3 changeUpdate IIW asset rows & CM-3 change packet
  4. 4
    ISSO / CISO signs off on SCR impact in Slack
    Security leadership reviews the exact asset delta and approves whether 3PAO or Agency notification is required.
    Only on this path: If Significant Change
  5. 5
    Standard changes auto-update the IIW
    Routine releases update the Integrated Inventory Workbook rows and record CM-3 peer review and test evidence automatically.
    Only on this path: Standard CM-3 change
  6. 6
    Builds an auditor-ready CM-3/CM-4 packet
    Combines peer review status, CI test proof, IIW delta, and SCR determination into one clean record.
  7. 7
    Archives proof to SharePoint
    Files the packet into SharePoint and writes the audit link straight back onto the Jira record.

Field map

FromTo
GitHubPR approver, commit SHA & CI test statusSharePointCM-3 change control evidence binder
AWSNet-new / modified boundary resourcesExcelIntegrated Inventory Workbook (IIW) rows
SlackISSO / CISO SCR determinationJiraCM-4 security impact analysis note

Deviation Request & vendor-dependency evidence packager

Turns multi-hour Deviation Request assembly into a clean, repeatable Procedure: extracts raw Tenable outputs and compensating controls, verifies nothing is missing before ISSO review, captures named sign-off in Slack, and files the AO-ready folder in SharePoint.
  • Jira
  • Tenable
  • Internal tool
  • Slack
  • SharePoint
Swap in your systemsThe steps stay the same. Only the screens change.
POA&M / DR ticket
Vulnerability scanner
ISSO sign-off
DR package folder

Step by step

  1. 1
    Starts when an engineer flags a DR in Jira
    Tagging a POA&M finding as False Positive, Risk Adjustment, or Vendor Dependency sends the POA&M ID, CVE, and advisory link to Stepwork.
  2. 2
    Collects scanner proof & compensating controls
    Stepwork extracts the exact plugin output from Tenable, captures compensating-control screenshots (such as WAF or firewall rules), and reads vendor patch ETAs.
  3. 3
    Checks FedRAMP DR completeness before review
    Incomplete requests bounce back to the engineer instead of wasting ISSO or 3PAO review cycles.
    • If proof missingRequest missing justification from engineer in Slack
    • Ready for ISSO sign-offPause for ISSO approval & sign-off in Slack
  4. 4
    Prompts the engineer in Slack
    Only when required justification is missing: Stepwork pings the owner with the exact field still needed.
    Only on this path: If proof missing
  5. 5
    ISSO reviews and signs off in Slack
    Complete DR packages pause for named ISSO approval, with the approval timestamp saved permanently in the run record.
    Only on this path: Ready for ISSO sign-off
  6. 6
    Packages the Deviation Request in SharePoint
    Stepwork populates the DR template, bundles all raw proofs and screenshots, and files them in SharePoint while scheduling a 30-day renewal reminder.
    Only on this path: Ready for ISSO sign-off

Field map

FromTo
TenableRaw plugin output & affected host listSharePointDeviation Request: technical proof appendix
Internal toolWAF / network segmentation screenshotSharePointDeviation Request: compensating control proof
SlackISSO approval & renewal windowJiraDR status & 30-day renewal date

3PAO Evidence Request List (ERL) & FedRAMP 20x KSI continuous validation

Eliminates the pre-assessment evidence scramble—and prepares your team for FedRAMP 20x continuous validation. Stepwork pulls fresh metrics and screenshots across cloud, Okta, Wiz, and internal portals, verifies completeness before auditors look, and publishes the indexed bundle to SharePoint.
  • Excel
  • AWS
  • Okta
  • Wiz
  • Slack
  • SharePoint
Swap in your systemsThe steps stay the same. Only the screens change.
Identity provider
Vulnerability scanner
Readiness digest
3PAO data room

Step by step

  1. 1
    Reads your 3PAO ERL or KSI checklist
    Stepwork ingests every requested evidence item, its source system, and the maximum allowed evidence age.
  2. 2
    Collects structured metrics & screenshots
    Combines API calls and deterministic UI Extractions so even tools without APIs report continuous KSI status alongside visual proof.
    Repeats: For each 3PAO ERL row or FedRAMP 20x KSI · 185 evidence items
  3. 3
    Validates freshness & pass criteria
    Stale or failing checks branch upward to the control owner immediately—never silently into the auditor's folder.
    • If stale or failingFlag pre-audit gap to control owner in Slack
    • Auditor-readyUpload indexed ERL / KSI bundle to SharePoint
    Repeats: For each 3PAO ERL row or FedRAMP 20x KSI · 185 evidence items
  4. 4
    Alerts owners before the 3PAO asks twice
    Posts exact missing or failing ERL / KSI IDs to Slack so teams close gaps ahead of fieldwork.
    Only on this path: If stale or failingRepeats: For each 3PAO ERL row or FedRAMP 20x KSI · 185 evidence items
  5. 5
    Files indexed artifacts in SharePoint
    Uploads structured KSI payloads and timestamped screenshots into your 3PAO data room in SharePoint using exact ERL numbering.
    Only on this path: Auditor-readyRepeats: For each 3PAO ERL row or FedRAMP 20x KSI · 185 evidence items
  6. 6
    Gives the CISO a live readiness score
    Publishes percentage complete, verified KSI counts, and remaining pre-audit blockers after every run.

Field map

FromTo
Excel3PAO ERL row / FedRAMP 20x KSI IDSharePointIndexed folder & standardized filename
AWSLive posture & boundary configuration stateSharePointStructured KSI status JSON / CSV + screenshot
WizActive vulnerability & scan coverage metricsSlackWeekly CISO readiness digest

Flows vs. Procedures

Record a Flow once. Chain them into FedRAMP Procedures.

Most FedRAMP automation stalls because half the boundary has APIs and the other half lives in legacy consoles, admin portals, and Excel workbooks. Stepwork combines browser Flows, screen Extractions, API calls, Rules, and Approvals in one deterministic canvas.

  • Flow
    Single-app task

    Recorded Flows (UI & no-API portals)

    Do a task once—like exporting a Tenable scan, screenshotting an AWS IAM policy, or uploading a ConMon zip to a portal—while Stepwork records it. It replays the exact path every run using AI vision to stay resilient to layout updates.

    • Export monthly OS & container scan CSVs
    • Capture timestamped NIST 800-53 settings
    • Revoke access in non-SCIM internal admin tools
  • Extraction
    Structured data

    Extractions & File Processing

    Read tables, settings, and multi-page lists (up to 100 pages) directly off app screens—or parse PDFs, XML/CSV scans, and compliance workbooks up to 7 MB—into typed variables ready for rules and tickets.

    • Pull full privileged user tables across consoles
    • Parse scanner outputs & IIW asset sheets
    • Extract KSI status values for FedRAMP 20x
  • Rule & Approval
    Governance

    Deterministic Rules & ISSO Approvals

    Branch cleanly on exact criteria—30/90/180-day POA&M SLAs, config drift, or SCR triggers—without letting an LLM improvise. Pause any sensitive step for a named ISSO or CISO approval, logged permanently in the run record.

    • Escalate High CVEs approaching 30-day SLA
    • Pause for ISSO sign-off before access revocation
    • Route Significant Changes for CISO approval
  • Procedure
    End-to-end orchestration

    Procedures + API Calls on Schedule

    Wire Flows, Extractions, REST API calls, Rules, and Approvals into one Procedure that runs on a schedule (daily, weekly, monthly ConMon) or via webhook from Jira, ServiceNow, or your HRIS.

    • Monthly ConMon scan → POA&M → Jira sync
    • Quarterly privileged access review end to end
    • 3PAO ERL & annual sampling bundle builder
How Procedures work→Explore Extractions→Browse the Marketplace→

The ConMon math

What manual FedRAMP operations actually cost each month

Even after achieving ATO, maintaining FedRAMP Moderate or High drains senior security engineering and GRC hours every single month. Here is an illustrative look at recurring manual effort for a typical SaaS boundary (~20–30 boundary tools).

Illustrative estimate, not a quote. Hours reflect typical manual effort reported by security and GRC teams running FedRAMP Moderate/High ConMon. Your boundary size, baseline, and tooling will differ—we can size your exact workflows together.

  • Monthly OS, container, DB & web scan exports, dedup & IIW coverage checksMonthly
    ~18 hrs / month
    See Procedure →
  • POA&M workbook updates, Jira SLA chasing & closure re-scan verificationWeekly / Monthly
    ~24 hrs / month
    See Procedure →
  • SSP & NIST 800-53 configuration screenshots across boundary consolesMonthly
    ~20 hrs / month
    See Procedure →
  • Privileged access reviews, MFA checks & 24h offboarding proofMonthly / Quarterly
    ~14 hrs / month
    See Procedure →
  • Significant Change triage, CAB packets & CIS/STIG drift ticketsWeekly
    ~12 hrs / month
    See Procedure →
  • Deviation Request packaging, vendor dependency renewals & 3PAO ERL prep (amortized)Monthly / Annual
    ~22 hrs / month
    See Procedure →
Illustrative recurring manual effortAcross monthly ConMon, POA&M, SSP evidence, access reviews, SCRs, and 3PAO prep
~110 hrs / month~1,320 hrs / year

Built for security boundaries

Designed for CISOs who cannot let an agent improvise

Stepwork automates your team's FedRAMP workflows inside isolated environments you control—with deterministic execution, vault-referenced credentials, and a complete screenshot audit trail of every run.

  • Run inside your own cloud or network

    Enterprise teams can deploy Stepwork containers inside their own AWS, Azure, or Google Cloud account—or on a dedicated managed machine inside your network—so internal admin consoles and boundary tools stay unreachable from the public internet.

  • Deterministic paths, zero LLM guesswork

    Stepwork never lets an unconstrained LLM decide what to click inside your production security consoles. Every Flow follows the exact recorded path, and every branch follows explicit Rules you define in advance.

  • Credentials stay in your 1Password vault

    Passwords are never pasted into procedure variables or stored in plaintext. Stepwork stores a reference to your 1Password vault item and retrieves credentials only at runtime; API keys are encrypted at rest with AWS KMS.

  • Auditor-ready run records & named approvals

    Every run records its steps, extracted values, outcome, duration, triggering user, named approver decisions, and a screenshot of every step—turning automation execution itself into clean 3PAO evidence.

Stepwork is SOC 2 Type II certified and GDPR ready (NIST and ISO 27001 are on our roadmap as coming soon). Stepwork automates your organization's FedRAMP workflows; deployment architecture and boundary scoping are reviewed with your InfoSec team during onboarding.

Read our Security architecture→Explore Containers & deployment→Visit the Trust Center→

CISO FAQ

Questions security leaders ask about FedRAMP automation

  • GRC platforms track your controls, map frameworks, and generate SSP/POA&M documentation—and they work great where native API integrations exist. Stepwork handles the operational last mile they cannot reach: logging into internal tools, legacy consoles, government portals, and scanners with incomplete APIs to collect screenshots, reconcile workbooks, open and verify remediation tickets, and upload verified evidence directly into your GRC platform or repository.
  • Yes. For enterprise teams, Stepwork containers can run inside your own AWS, Azure, or Google Cloud account, or on a dedicated Windows or Mac machine inside your network. A container running inside your network reaches what that machine can reach—including internal tools and on-prem apps—while keeping automated sessions isolated from everyday user browsers.
  • No. Stepwork builds deterministic agents. You perform a task once while Stepwork records it, and it replays that fixed path every time. AI vision helps recognize updated UI labels or layout shifts so the run stays on track, and LLMs can assist with structured extraction or summaries—never improvising new actions in production consoles.
  • For FedRAMP Rev 5, Stepwork automates recurring ConMon scans, POA&M SLA tracking, SSP control screenshots, IIW reconciliation, privileged access reviews, Deviation Requests, and 3PAO ERL packages. For FedRAMP 20x, Stepwork's Extractions and API steps continuously pull structured Key Security Indicator (KSI) metrics and live configuration proof from both API-enabled cloud services and UI-only tools.
  • Every Stepwork run produces an auditable run record: the exact steps executed, extracted values, timestamps, duration, triggering user or schedule, named approver sign-offs, and a screenshot captured at every step. You can file those screenshots and structured outputs directly into SharePoint, Box, Google Drive, Jira, ServiceNow, or your GRC platform using your 3PAO's naming convention.
  • Credentials stay in your 1Password vault. Stepwork stores only a reference to the vault item—never the password itself—and retrieves it only when a flow runs. Passwords are never placed in procedure variables, and API keys are encrypted at rest with AWS Key Management Service (KMS) with no employee access.
  • Stepwork is SOC 2 Type II certified and GDPR ready, with NIST and ISO 27001 listed as coming soon on our Security page. Stepwork is built to automate your organization's FedRAMP compliance processes—and enterprise teams can run execution containers inside their own cloud environment or local network with customer-controlled diagnostics and logging.

Automate FedRAMP

Turn monthly ConMon and 3PAO prep into scheduled Procedures

Bring your ConMon checklist, POA&M workflow, or 3PAO Evidence Request List—we will map your first deterministic FedRAMP Procedures live with your security team.

Book a FedRAMP walkthroughReview our Security page
Stepwork

Deterministic agents for work that must run the same way every time.

Product

  • Procedure
  • Extractions
  • File processing
  • Marketplace

Solutions

By team
  • IT
  • Security & Compliance
  • Finance & Accounting
  • Sales & RevOps
  • Operations
  • HR & People
By industry
  • Healthcare
  • 3PL and warehousing
  • Freight and trucking
  • Fuel and convenience stores
  • Construction
  • Manufacturing and distribution
  • Accounting firms
  • Field services and trades
  • MSPs

Capabilities

  • Deterministic Agents
  • Stepwork MCP
  • Containers
  • Ask Bob

Company

  • ROI
  • Security
  • FAQ

Resources

  • Calm Case Study
  • Claude Co-Work Alternative
  • Free IT Ticket Analysis
  • Stack check
  • For AI tools (llms.txt)

Legal

  • Terms and Conditions
  • Privacy Policy
  • Data Processing Agreement
  • Subprocessors

Ask your AI about this page

  • ChatGPT
  • Claude
  • Perplexity

2261 Market Street #4481, San Francisco, CA 94114, USA

Loot Discount inc dba Stepwork

© 2026 Stepwork. All rights reserved.