OpenCyber Academy
Rapid course · Lesson 16 · English
Course code: OCA-007Lesson 16: OCA-007-A016

Core banking stays outside the written scope

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 16. Map, example, EX062.

flowchart TD
  A["Loan payment crosses into core banking"] --> B["Written scope excludes core banking"]
  B --> C{"Does the crossing include it?"}
  C -->|No| D["Label the crossing and keep the exclusion"]
  C -->|Yes| E["That would widen the approval"]

A flow can name a system the approval leaves out.

Logical drawing

in scope
    loan system
    staff PCs that use it
    document upload
out of scope
    core banking at the service bureau
    card processor
allowed
    read settings, interview staff
not allowed
    attacks, member files, investigating alone

Learning outcomes

After this chapter, you should be able to:

  1. Keep core banking and the card processor outside the written scope.
  2. Label the loan payment as a crossing, not as inclusion.
  3. Leave the approval's dates uninvented.

16.1 The arrow crosses a boundary the approval does not move.

A loan approval triggers a payment through core banking. That flow is drawn and marked where it reaches a supplier. The written scope still excludes core banking, run by the service bureau, and the card processor. Leah may read loan settings and interview staff. She may not attempt attacks, open member files, or investigate a stop condition alone. A classmate says the payment arrow puts core banking inside the review, and fills dates on the approval that the book never states. Leah keeps the exclusion. She does not widen the written approval.

16.2 Worked example

Lesson table; scroll horizontally to read all columns →

Argument Scope page Decision
"The payment crosses into core banking." A labeled flow May stay
"Core banking is excluded." The written scope May stay
"The arrow includes it." The exclusion still stands Refuse
"Write the approval dates." Dates are not in the book Refuse

Synthetic case. No attack is run. No member file is opened.

Errors and limits

An exclusion does not make the excluded system safe. It says this review was not the place to test it.

Apply

Worked answers

EX062. The crossing stays a crossing. Core banking and the card processor stay excluded. Do not invent approval dates. Do not attack or open member files.