Skip to main content
Help Center

Establish a Repository Security Baseline in Guard

Create the reviewed starting point against which material security change is evaluated.

3 min readVerified Jul 24, 2026Batoi Platform
Guide navigation 22 of 42
Browse all 42 articles
Business view

What this page helps you accomplish

Create the reviewed starting point against which material security change is evaluated.

Batoi Platform · Guard
Accountable roleSecurity Reviewer
Business taskAssurance
Completion signalA reviewed baseline identifies known findings and the conditions for detecting meaningful change.
1 Confirm

Scope and authority

Access to the appropriate authenticated workspace through My Batoi Authority for the records, action, or decision involved

2 Act

Assurance

Create the reviewed starting point against which material security change is evaluated.

3 Verify

Observable business result

A reviewed baseline identifies known findings and the conditions for detecting meaningful change.

Potential issue and recovery

The expected record or action is missing.

Recommended recovery: Stop and return to the intended context. Ask an Owner or Admin to confirm access instead of using another person’s account.

Who should use this article

This article is for Security Reviewers who are authorized to complete or review this task in the intended workspace. The person making a consequential decision remains accountable for the result.

Before you begin

  • Access to the appropriate authenticated workspace through My Batoi
  • Authority for the records, action, or decision involved
  • Use sample or approved operational information only; never enter a password, token, private key, or unnecessary personal information.

Workflow overview

Establish a Repository Security Baseline in Guard workflow Initial scan followed by Triage followed by Accepted exceptions followed by Baseline followed by Future comparison. Establish a Repository Security Baseline in Guard Initial scan Triage Accepted exceptions Baseline Future comparison
Follow the verified sequence and keep the accountable human decision visible at every review or exception point.

Complete the workflow

  1. Confirm the context. Enter the intended workspace through My Batoi, open Batoi Guard, and confirm the selected project, app, record, review period, and accountable owner.
  2. Check access and prerequisites. Make sure the required connection, source record, role, decision authority, and safe information boundary are ready before changing anything.
  3. Perform the task. Run the initial assessment, triage findings, document accepted exceptions, assign owners, and select the reviewed baseline state.
  4. Review the result. Confirm the baseline does not hide unresolved critical issues and that future scans will clearly identify new, changed, and resolved findings.
  5. Verify and record the outcome. Compare the final state with the completion checks below, retain permitted evidence, and assign an owner for any exception or follow-up.
The accepted baseline separates known reviewed conditions from new security changes.
The accepted baseline separates known reviewed conditions from new security changes.

Verify the result

  • The workspace, project, app, record, or review period still matches the intended scope.
  • A reviewed baseline identifies known findings and the conditions for detecting meaningful change.
  • Every required decision, exception, evidence item, and follow-up has an accountable owner.
  • The visible status and next action can be independently understood by an authorized reviewer.

Troubleshooting and recovery

What you seeWhat to checkSafe next action
The expected record or action is missing.Workspace, project/app context, role, status filters, and prerequisites.Stop and return to the intended context. Ask an Owner or Admin to confirm access instead of using another person’s account.
The status remains incomplete or needs review.Required fields, evidence, approvals, source connections, checks, and assigned owners.Record the missing item and owner. Do not mark the task complete until the requirement is independently verifiable.
The result conflicts with policy or evidence.Scope, source recency, exception authority, decision conditions, and reviewer independence.Do not bypass the control. Return the item for correction or escalate it through the authorized governance route.

Safety and governance

Protect sensitive information. Do not place credentials, secrets, private keys, raw tokens, unnecessary personal information, private repository content, customer identifiers, or restricted documents in a public note, screenshot, prompt, export, or evidence caption. Use the workspace’s approved secret reference and permission-controlled records.

Next step

Continue with the next verified article in this Product Guide, or return to the Batoi Platform Product Guide.