Executing and monitoring tests

Tests refresh on their own schedule, but you can force one at any time, which is what you normally do before an audit or straight after fixing a configuration. This article covers refreshing them, reading a result, and getting integration tests running in the first place.

Manually refreshing tests

Tests in Tidal Control can be manually refreshed to get the most current compliance status, especially useful after configuration changes or for audit preparation.

Individual test refresh

Refresh a single test after a related change, or whenever you suspect its result is stale.

When to use individual refresh:

• After changes in related controls or assets
• For important tests before management reporting
• When suspecting outdated test results
• For validation after remediation actions

Individual refresh process:

1. Click on test name in Tests overview to open details
2. Find Refresh button top right in test detail page
3. Click "Refresh" to re-execute test
4. Wait for completion - Test status update may take several seconds
5. Check new results in Last results section

Bulk test refresh

Refresh in bulk after a broad configuration change, or when preparing your whole compliance status for an audit.

When to use bulk refresh:

• After major configuration changes in your ISMS
• For complete compliance status update before audits
• During systematic remediation of multiple failed tests
• For periodic system assessments

Bulk refresh process:

1. Go to Tests overview page
2. Select desired tests via checkboxes in first column
3. Bulk action bar appears at top
4. Click "Refresh" button in bulk action bar
5. Tests are executed in parallel for fast results

Viewing and interpreting test details

A test's detail page explains why the check matters, how to fix a failure, and which controls it counts towards.

Navigating test detail page

Each test has an extensive detail page with context information and remediation guidance.

Access to test details:

1. Click on test name in Tests overview table
2. Test detail page opens with complete information
3. Tabs available: Details, Previous results
4. Refresh button top right
5. Download test results button available in side panel

Understanding "Why is it important?" section

This section explains the regulatory and business reason the test exists, not just what it checks.

Compliance context explanation:

• Regulatory background - Which standards require this control
• Business impact - Why compliance is important for organisation
• Risk implications - Consequences of non-compliance
• Best practice guidance - Why this test is industry standard

Following "How to fix it?" instructions

This section gives the concrete steps to resolve a failure, not just a description of the problem.

Practical steps to fix tests:

• Specific steps to resolve test failure
• Links to relevant controls or assets
• Timeline guidance for implementation
• Verification steps to confirm success

Linking controls

A test is "In scope" when it is linked to at least one control. Tests without any linked controls are "Out of scope" and don't affect your compliance status.

1. Find the Controls section in the test detail page
2. Use the "Link control(s)" selector to add controls
3. Test automatically becomes "In scope" and affects your compliance status
4. Remove a control by clicking the X on a control chip

Downloading test results

Export a test's results when you need the detail outside Tidal, typically for an audit.

Using download functionality

The download button in test details allows you to export detailed test results for reporting and audit purposes.

Download process:

1. Open test detail page of desired test
2. Click Download button (⬇️) in side panel next to "Last result"
3. Test result file is downloaded to your computer
4. Open downloaded file for detailed analysis

Test monitoring strategies

How often you need to refresh depends on the kind of test: Tidal tests keep themselves current, integration tests run on a schedule.

Tidal tests

Tidal tests refresh automatically as soon as something changes in the situation they relate to. You typically don't need to refresh these manually.

For example:

• Policy tests refresh when a Policy changes status (in the Policies page)
• Risk tests refresh when Risk details are adjusted and when Risk assessments are performed or adjusted
• Control tests refresh when Control details are adjusted or Control status changes etc.

Integrations

When to refresh?

• System being tested is modified - after a major software release or configuration update
• Specific remediation actions performed in system - 2FA is enabled causing the Failed test to now Pass
• As part of PDCA cycle - when there's a task open under the Control 'Compliance monitored' and you need new results
• Periodically - even when no changes are known, it's still wise to run Tests periodically to confirm the situation hasn't changed

Configuring integrations for external tests

An integration test cannot run until its integration is connected, which is done once in Settings.

Prerequisites for external test activation

An external test can't run until its integration is fully configured and connected.

Understanding integration requirements:

• Settings → Integrations configuration must be complete first
• API credentials and permissions correctly set
• Network connectivity to external systems verified
• Verify scope - Which external data is relevant

Settings → Integrations configuration process

Every integration is set up from the same place: Settings, then Integrations, then the configuration wizard for that tool.

Integration activation steps:

1. Go to Settings in left navigation menu
2. Select Integrations section
3. Choose desired integration from available options
4. Follow configuration wizard for specific tool
5. Test connectivity to verify working status

Next steps

Now that you can execute and monitor tests:

• Develop periodic monitoring routine for critical tests
• Implement monthly or quarterly review process for trend analysis
• Configure relevant integrations for complete compliance coverage
• Optimise test scope based on priority and requirements