Upload Tests require you to manually upload files or links on a recurring interval you configure (Monthly, Quarterly, Annual, and so on).

Integration Tests pull automated evidence from connected tools (AWS, GitHub, Okta, and similar). They pass or fail based on synced configuration and activity, not manual uploads.

Platform Tests run inside Secureframe for workflows such as policy acknowledgments, Security Awareness Training, and personnel onboarding tasks. They use built-in product cadences rather than user-defined upload intervals.

Expected behavior. Last Uploaded applies to manual file uploads on Upload Tests. Integration and Platform tests collect evidence automatically through syncs or in-product activity, so there is no uploaded file date to display.

For Integration tests, check Last Synced on the integration or open the test Evidence tab to see the automated proof Secureframe collected. For Platform tests, review completion data on the test detail page (for example training completions or policy acknowledgments).

The Tests table in the product may show Last Uploaded for Upload Tests, but the standard CSV export currently includes Last Updated instead. These are different timestamps.

To review upload dates in bulk today, filter Upload Tests in the Tests UI or export evidence from individual test detail pages. If you need Last Uploaded in a spreadsheet export, contact [email protected] with your use case.

Go to Monitoring → Integrations, open the connection, and click Sync. Then open the test and use Refresh or re-run evaluation from the test detail page if available.

Allow a few minutes for results to update. If the test still shows stale data, confirm the integration connection is healthy and that in-scope assets are not filtered out by framework scope rules.

Test intervals apply to Upload Tests where you manually upload evidence on a schedule. Platform tests (training completions, published policy acknowledgments) run on automated cadences built into Secureframe. Security Awareness Training is treated as annual by design. Policy tests pass when the policy is published, linked to the policy test, and assigned personnel complete acknowledgments.

Not today. Due dates and test intervals are configured per Upload Test from the test detail page. For large programs, prioritize tests approaching due dates using Tests filters and owner assignments. Bulk due date editing is a common product request.

Yes. The tolerance window is grace time after the due date. If you upload valid evidence before the due date with the correct Completed on date, the test should pass for that interval. If the due date passes without acceptable evidence, the test may move to At Risk and then Failing after the tolerance window expires.

Uploading evidence before the due date does not automatically prevent failure if the evidence does not satisfy the test requirements, falls outside the required date range, or ages out when the next interval begins.

Cadence depends on test type and interval. Upload Tests follow the interval you set (Annual, Quarterly, Monthly). Integration tests re-evaluate on sync. Platform tests use product-defined schedules. During an audit, auditors expect evidence within the audit window for each in-scope test, which may require fresh uploads even if a test passed earlier in the year.

Completed on (sometimes shown as activity completion date) is when the control activity occurred, not when you uploaded the file in Secureframe. Set it to the date the evidence actually reflects (for example the report coverage end date, communication send date, or review completion date). Auditors use this date to confirm evidence falls inside the test interval and audit window.

Pass with Upload submits evidence that is intended to satisfy the test requirement and change pass/fail status for the current interval.

Additional Evidence attaches supporting files or notes without replacing the primary evidence record. Use it for auditor context, supplemental screenshots, or documentation that does not change how the test is evaluated.

If a test is still failing after upload, confirm you used the correct action, set the right Completed on date, and uploaded the evidence type described in the test guidance.

Common formats include PDF, PNG, JPG, CSV, XLSX, DOCX, and TXT. Individual files must be under 500 MB. You can attach multiple files to a test. If a format is rejected, try exporting to PDF or contact support with the test name and file type.

Screenshots can work for readiness when they clearly show the required configuration or activity and your auditor accepts them. Many auditors still request source exports, logs, or signed documents during the audit. Follow the test guidance and confirm expectations with your auditor before relying on screenshots alone.

Assigning a control or test owner does not pass the test. Owners are accountable for remediation, but the test still needs passing evidence (automated sync results, platform completions, or uploaded proof). Open the test Evidence tab to see failing line items or missing requirements.

For cloud asset ownership tests, confirm the owner is an individual user with access to remediate, not only a team name, when the test guidance requires it.

Open the test from Tests and go to the Evidence tab (or Remediation view). Failing integration results, missing uploads, and out-of-interval evidence are listed there with details on what did not pass.

Filter the Tests page by framework and status to narrow failing items. For policy acceptance gaps, see FAQs: Personnel management for exporting acknowledgment data.

Yes. From the Tests page, use Export to download test metadata. Control mappings are available from the Frameworks or Controls views depending on your workflow. Exports reflect the columns supported in each table; see the Last Uploaded FAQ above if you need upload-specific dates in export.

Yes. Use the Tests export or open the specific policy acknowledgment test and export results. You can also add the Accepted Policies column on the Personnel page or export policy acceptance data from the Data Room when configured.

Not automatically. Test evidence lives on the test record for pass/fail evaluation. The Data Room is a separate repository often used for audit-period document storage. You may upload the same file to both places if your auditor expects it in the Data Room, but linking is not automatic.

There is no global filter for attachment file type across all tests. Review Upload Tests individually or export test evidence from tests you manage. Saved views on the Tests page can help group tests you routinely audit for screenshot-based proof.

See FAQs: SOC 2 compliance documentation and evidence in Secureframe for privacy policy communication and notice requirements. Uploading the document alone may not satisfy the test if stakeholders were not notified per the test guidance.

Open your audit from Audits, go to the Testing tab, and filter or group by response status. Submitted means evidence or responses were provided for auditor review. Not Ready means the test still needs customer action or updated evidence before it is ready for the auditor.

Integration and Platform tests may show as Submitted when automated evidence is in place even if Last Uploaded is blank on the Tests page. Upload Tests generally require you to submit or confirm evidence within the audit workflow.

Audit completion reflects how many in-scope tests or assertions in the audit have ready evidence or accepted responses versus those still open. Passing a test in the general Tests module does not always mean the audit Testing tab shows 100% until responses are submitted and marked ready for the auditor in that audit context.

If completion looks lower than expected, filter the Testing tab for Not Ready items, confirm framework scope for the audit, and refresh integration tests that may need a recent sync.

Upload Tests typically require you to upload or confirm files and set activity dates. Integration and Platform tests are updated by fixing the underlying configuration or completing in-product requirements, then syncing or refreshing so automated evidence flows into the audit Testing tab. You cannot replace automated results with a manual upload unless the test is an Upload Test.

Confirm the uploaded reports cover the exact date range required by the test interval and audit window. Reports for the wrong quarter or missing accounts will not pass. Complete reviews in Access → Reviews when using Secureframe UAR. See User Access Reviews (UAR) for workflow and evidence guidance.

See FAQs: Background checks for Vetty, Checkr, group exceptions, and evidence date range troubleshooting.