Skip to main content
GullySystem
Technology

Roles and Permissions for Cybersecurity companies

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

Trace a shared system record used for “VAPT for web, mobile and API applications”. Include who creates it, which branch or team uses it, and how corrections are controlled.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Cybersecurity companies

How the business operates.

Security work is sold as a scope: a set of applications, networks or cloud accounts, tested by named people for a fixed period. The record that matters is what was in scope, what was found and what has been fixed.

Engagement register

Record each engagement with client, scope, targets, test window, assigned testers and stage, from proposal through report delivery and retest.

Scope and authorisation record

Store the signed scope, the permitted dates and the contacts at the client, so testers work against a written record and the rules of engagement are one click away.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Prospects and scoping. Record each enquiry with the kind of test asked for, the targets, the constraints and the questionnaire answers. Build the proposal from the firm’s own day rates and keep every revision.
  • Engagement register. Hold each engagement with client, test type, window, assigned testers and stage, from proposal through report issue and retest, so the whole bench can be read in one list.
  • Scope and rules of engagement. Store the signed scope, the in-scope and excluded hosts, the allowed hours and the client’s emergency contact. A tester opens the rules before touching a single target.
  • Tester allocation. Show which testers are free, which certifications and specialities each holds, and which weeks are already booked, before a start date is promised to a client.

Operational bottlenecks to check

Scope lives in an email thread

Which hosts were in scope, and which were excluded, is argued after the report is sent. The thread has the answer somewhere.

Findings sit in tester notes

Each tester keeps findings in a personal file and the report is stitched together at the end. Duplicates and gaps get through.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and scoping

    A prospect asks for a web application test, a cloud review or a monitoring plan. A scoping questionnaire is sent, targets and constraints are recorded, and the proposal is built from the firm’s own day rates.

  2. 2. Signed scope and authorisation

    The accepted proposal becomes an engagement. The signed scope, permitted dates, source addresses and client contacts are stored, so every tester works against the same written rules.

  3. 3. Allocation and testing

    The delivery lead picks testers from the bench by skill and free days. Testers log findings as they go, each with an affected asset, a severity, evidence and a suggested fix.

  4. 4. Review and report

    A reviewer checks every finding, adjusts severity on the firm’s scale and approves it. The report is assembled from approved findings, and each issued version is kept with its date and approver.

  5. 5. Retest and closure

    The client reports fixes. Each finding is retested and marked fixed, accepted as a risk or still open, and the retest letter is produced from those results.

  6. 6. Retainer and renewals

    Monitoring hours are logged against the plan, and resold licences are listed by client with their vendor dates. The renewal quote is prepared before the date, not after it.

Industry reports to connect with

  • Engagements by stage, test type and assigned tester
  • Findings by severity, affected asset and status
  • Reports awaiting review, with the reviewer and days waiting
  • Retests requested, done and still open, by client

Questions before implementation.

When should cybersecurity companies consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements