Table of Contents

Getting Started

Welcome

Platform Onboarding

Testing Process

Using the Platform

Findings Management

Testing Activities

Reporting

Security Metrics & Analysis

Attack Surface

Account Management

Integrations

FAQs & Support

FAQs

Best Practices

Guidance for running a successful security program with Sprocket.

Prioritize Remediation

Not all findings require the same urgency. Use severity levels and SLA configurations to guide your team's remediation efforts.

• Address Critical and High findings first. These represent the greatest risk to your organization and are most likely to be exploited.
• Use the Findings Distribution on the Dashboard to get a quick view of your open findings by severity and state.
• Assign findings to the appropriate team members to establish clear ownership. See Assigning Findings.
• Configure SLA notifications to keep your team informed when findings are approaching their remediation deadline. See Account Management.

Working with Sprocket Testers

Your Sprocket testing team works most effectively when your organization is prepared and engaged throughout the testing process.

• Come prepared to onboarding calls. The information you provide during onboarding directly determines the scope and quality of testing. Gaps in information slow the entire engagement. See Preparing for your Kickoff Call for what to prepare.
• Use comments on findings to ask questions, share context, or flag anything your Sprocket team should know about a specific vulnerability. This is the quickest way to resolve any questions you might have.
• Respond to findings promptly. The sooner your team begins remediation, the sooner Sprocket can validate fixes and close out findings.

Preparing for Retesting

When your team has addressed a vulnerability and is ready for your Sprocket tester to validate the fix, mark the finding as Retest Ready. This notifies your Sprocket team automatically and initiates retesting within the next few business days.

• Update the finding State to Retest Ready when you believe the vulnerability has been resolved. See Managing Remediation.
• If you have specific context about the fix — such as what changed or where — add a comment to the finding before marking it Retest Ready.

<aside> <img src="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" alt="notion://custom_emoji/ede23b80-db43-4102-883e-d404c44f363c/32f14309-3808-804c-a39b-007a3a539ba4" width="40px" />

Note: There is no in-platform indicator that a retest is underway. Your Sprocket team will follow up with results directly.

</aside>

Maintaining Ongoing Coverage

Sprocket continuously discovers and monitors assets across your attack surface. Keeping your asset inventory accurate ensures your testing coverage reflects your actual environment.

• Review the Changes page regularly to stay aware of newly discovered or modified assets. Unexpected changes may indicate misconfigurations or unauthorized activity.
• Exclude assets from CPT scope if a newly discovered asset is out of bounds for testing. This prevents unnecessary testing on assets that are not relevant to your program. See Asset Management for how to do this.
• Dispute ownership of any asset Sprocket has discovered that does not belong to your organization. This keeps your attack surface accurate and focused on assets you own. See Asset Management for how to do this.
• Review the Summary page periodically to track trends in your asset count and identify areas of unexpected growth in your attack surface.