Security

Practical controls around the information that matters.

Operating records deserve careful handling. RBA begins by defining what the work requires, preferring narrow and read-only access where practical, and keeping the analytical and AI boundaries clear.

Working principles

Start narrow. Keep the reasoning reviewable.

Security requirements vary with the records, systems, people, and scope involved. RBA discusses the applicable handling and access arrangement before client work begins rather than relying on broad claims that may not fit the engagement.

01

Start with what is required

Access should match the agreed question and scope, not expand by default.

02

Read-only first where practical

Analytics needs to understand operating systems; it does not need to operate them. Prefer access patterns that limit unintended change.

03

Keep client information separate

Client information stays within its engagement boundary. Public examples remain clearly labeled synthetic data.

04

Control the AI boundary

Not every record needs to pass through a language model. The analytical system and conversational AI interface are distinct layers.

05

Keep important numbers traceable

A material result should remain connected to its source records, business definition, reporting period and calculation.

06

Match the engagement

Specific contractual, regulatory, handling, retention and access commitments belong to the actual systems and scope involved.

Public website boundary

The public site contains no client operating data.

The analytical example on this website is synthetic and is labeled that way. Authorized clients use the separate, invite-only Client Portal for the client relationship and delivery experience.

Discuss the scope

Have a security question?

Tell us what the engagement may involve. We will discuss the relevant requirements directly.

Tell us what you're trying to figure out Already a client? Open Client Portal ↗