Security & Responsible Engineering

Design security into the working system.

Security affects who can use the system, what they can do and how information is handled. Follow one staff action to see how these decisions fit together.

Follow one fictional staff action

One action can involve several security decisions.

A staff member reviews request R-204 and prepares an update for another system. See which permissions and checks that action needs.

Identity: Is this staff member allowed to review R-204? Permission to view a record is different from permission to record a decision. The system must enforce those permissions; a visible button is not enough.
Application: Is request R-204 complete, and does it still contain the reporting period that was reviewed? If the record changes, it must be reviewed again before coordination.
Integration: Update U-204 includes request R-204, its review status and the person responsible for the next step. Agree what the receiving service accepts and who handles a rejected update.
Data: Send the review status and required reference without copying every attachment. Agree what each recipient needs and which team manages the original record.
Infrastructure: Keep this sample staging request separate from production records and settings. Agree how an approved application change is released to production.
Operations: Can the support team trace a rejected update U-204 back to the review of R-204? Keep the records needed to investigate without exposing unnecessary inquiry content.

Identity · Reviewer permission

Identity

Application

Integration

Data

Infrastructure

Operations

The diagram shows related security responsibilities, not the actual protective layers of a deployed system.

Identity / Reviewer permission

Is this staff member allowed to review R-204? Permission to view a record is different from permission to record a decision. The system must enforce those permissions; a visible button is not enough.

Action: Staff review of R-204
Exchange: U-204 · review status and person responsible for the next step
Design question: Reviewer permission

Discuss your project →

Start with what the person needs to do.

Decide who can take the action, which information they need and what happens when something goes wrong. Plan the records and monitoring that help the support team investigate problems.

This page explains our design approach. It is not a claim about deployed security controls, certification or audit results.