Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. Vulnerability reporting

Technology · Security

Vulnerability reporting

A vulnerability report should quickly reach people able to reproduce it, assess the risk and prepare a fix — without exposing user data.

  • responsible disclosure
  • triage
  • no production data
  • from working documentation — to be approved

Context

Responsible disclosure of security issues

The security of an IGA platform depends on the correctness of the authorisation logic, the integration with the IdP, the protection of entitlement data and control over the changes made. Reports concerning a possible bypass of approvals, privilege escalation, access to other people's data or misuse of an integration account require a different mode of handling than an ordinary functional problem.

The description below is the proposed responsible disclosure process for sara.next. We accept reports by e-mail at sales@sara-next.com — use “Security report” as the subject. The same address is listed in the security.txt file published at /.well-known/security.txt.

NoteThis description is not a separate VDP policy or bug bounty programme and does not set response times.

How to report

Reporting step by step

Step 1

Send an e-mail

Address: sales@sara-next.com, subject: “Security report”.

Step 2

Describe the problem

Include the information from the list below: component, reproduction steps, initial impact assessment.

Step 3

No sensitive data

Reports travel by ordinary e-mail. Do not paste tokens, passwords or personal data — if needed, suggest a preferred secure channel for further contact.

Request

What to include in the report

The easier it is to reproduce the problem, the faster the risk can be assessed. Do not include tokens, passwords or personal data.

Contents of the report

  • A description of the observed behaviour and the expected security mechanism.
  • The affected component, version or deployment identifier (without disclosing unnecessary production data).
  • Minimal, repeatable reproduction steps and preconditions.
  • An initial impact assessment: a breach of confidentiality, integrity, availability or of the permission granting process.
  • Sanitised logs, a request identifier and a sample API response — without tokens, passwords or personal data.
  • The reporter's preferred secure contact channel.

Handling

Suggested handling process

When classifying a report, the team should distinguish a genuine product vulnerability from an incorrect environment configuration, an overly broad technical account scope or an error in a client's custom adapter. Separating these cases does not remove the need to manage risk in the specific deployment.

  1. 01Registration
  2. 02Triage
  3. 03Reproduction
  4. 04Risk classification
  5. 05Remediation plan
  6. 06Regression test
  7. 07Fix or workaroundPublication of a fix or a recommended workaround.
  8. 08Closing the report

Escalation

Examples of situations requiring fast escalation

Examples of situations requiring fast escalation
ExampleWhat should be assessed
A user sees someone else's requestWhether data or permissions outside the role's scope were disclosed
Approval can possibly be skippedWhether access can be granted without proper authorisation
A token exposed in a logWhether the token can be used, its scope and lifetime
A script performs a broader operation than the one approvedParameter control, connection permissions, effects in the target system
Access cannot be revokedThe scale and duration of unwanted permissions being kept

Principles

How to test safely

NoteDo not carry out unauthorised tests on other clients' data, do not perform DoS or mass data reads and do not modify real users' permissions.

If reproduction requires an operation that affects access, agree on a test environment and scope with the team responsible for maintenance.

An implementation expert's view

A business authorisation flaw can be more dangerous than a technical one

In an IGA system a business authorisation flaw can be more dangerous than a classic technical vulnerability. That is why during triage I would analyse separately:

  1. who could initiate the request,
  2. who approved it,
  3. which validation conditions were skipped,
  4. whether the actual access in the target system changed without an appropriate decision.

Report a potential vulnerability: sales@sara-next.com

Use “Security report” as the subject and include a description, reproduction steps and an initial impact assessment — without tokens, passwords or personal data.