1. Start with the business request
Capture the SaaS product, provider, requestor, business owner, technical owner, change ticket, purpose, request type, and urgency.
Customer help
Use this page as a customer-facing guide to the portal's review workflow, decision language, local storage model, installation notes, and common support questions.
Getting started
Workflow
Capture the SaaS product, provider, requestor, business owner, technical owner, change ticket, purpose, request type, and urgency.
Document data types, accidental CUI concern, repositories, Security Protection Data, AI behavior, permissions, controls, evidence, FedRAMP status, and CMMC scope impact.
Use the Reviewer view to save the decision, notes, scope, prohibited use, required controls, approvers, evidence documents, and reassessment date.
Use Approval Record for the selected review and SaaS Register for the review list. Treat exported PDFs, JSON, and questionnaires as sensitive records.
Decision meanings
The SaaS may be acceptable for the documented non-CUI use case, subject to the recorded scope, reviewed evidence, and prohibited-use language.
Restricted federal data is in scope and the review rules found the required authorization path, without a blocking expert-review trigger.
The request may be acceptable after listed controls, evidence, restrictions, or reviewer requirements are completed. It should not be treated as final until conditions are resolved.
The request includes triggers such as broad tenant permissions, repository integrations, Security Protection Data, AI indexing or retention risk, equivalency claims, or CMMC scope impact.
The request conflicts with a strict rule, such as restricted federal data without an acceptable authorization path or an AI/data-use condition that cannot be controlled.
Data storage
The portal saves review data, settings, audit entries, and questionnaire tracking locally. Evidence documents added to a review are copied as normal files into the selected portal data folder.
The app uses operating-system-backed protected storage when available. Organizations should still protect the Windows profile and data folder with normal workstation controls, backups, endpoint security, disk encryption, and access controls.
Do not store CUI, CDI, export-controlled data, credentials, secrets, or sensitive personal data unless your organization has approved this app and storage method for that use.
Install notes
For support, use the contact form on the home page or email support@requestpathsecurity.com.
FAQ
No. It creates an internal decision-support record. It does not certify a product, establish compliance, or replace cybersecurity, legal, privacy, contract, CMMC, NIST, FAR, DFARS, or FedRAMP review.
Yes. Admin Settings controls request types, data actions, data types, repositories, FedRAMP choices, service categories, scope categories, controls, permissions, evidence, AI flags, branding, approvers, and review timing.
Evidence may include security reports, privacy terms, subprocessor lists, data processing terms, retention and deletion details, AI/data-use statements, authorization information, and other records your organization requires for review.
No. The local audit log helps with accountability inside the app, but it is not a tamper-proof or centrally controlled audit system.
Yes. The desktop workflow is local. Normal workstation, storage, export, email, and backup behavior still depends on your environment and policies.
Yes. Version 1.0.0 is free to use as a local desktop decision-support tool.
Need help?