Where this offering fits
RidgeOne is a portfolio-level Ridge Security enquiry. Confirm its current role, included capabilities and relationship to RidgeBot in the manufacturer’s offer. The project should specify whether the requirement is assessment coordination, exposure review or another documented workflow rather than infer functions from a family name.
Architecture and rollout decisions
Map the intended users, environments and validation outcomes. Request a supported architecture and module schedule. Pilot a bounded workflow using authorised assets and known findings. Verify evidence traceability, ownership and the way results enter remediation. Existing deployments should include licence and configuration migration questions in the proposal.
An evaluation scenario for this offering
Once the manufacturer confirms RidgeOne’s current role and components, prepare a bounded evaluation around two known fictional findings with different owners. Ask the supplier to demonstrate the documented workflow for reviewing evidence, assigning treatment and recording closure. Add a finding whose asset identity is uncertain, requiring clarification instead of automatic assignment. Keep the configuration and component mapping with the results so the exercise assesses the actual offer rather than expectations inferred from a portfolio name. Retain the reviewer’s decisions and any unsupported requirement. Where active assessment is involved, use a separately approved laboratory scope and explicit stop conditions.
Evidence to request for this scope
- Obtain the current RidgeOne capability statement.
- Match included modules to approved objectives.
- Test evidence review and owner assignment.