Chapter 34 — Information security: integration
Lesson map
Lesson 34 published. Map, example, EX100.
flowchart TD
N0["Learning outcomes"]
N1["34.1 Partner integrations"]
N2["34.2 Credentials for interfaces"]
N3["34.3 Data minimisation"]
N4["34.4 Monitoring exchanges"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX100"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["34.1 Partner integrations"]
N2["34.2 Credentials for interfaces"]
N3["34.3 Data minimisation"]
N4["34.4 Monitoring exchanges"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX100"]
[Learning outcomes]
|
v
[34.1 Partner integrations]
|
v
[34.2 Credentials for interfaces]
|
v
[34.3 Data minimisation]
|
v
[34.4 Monitoring exchanges]
|
v
[Worked example] --> [Exercise EX100]
Learning outcomes
You will (1) secure integrations between systems and partners; (2) manage application programming interface credentials; (3) monitor data exchanged with third parties.
34.1 Partner integrations
Saltmarsh exchanges data with retailers, carriers and a payroll bureau through automated interfaces. Lindiwe lists each integration with its data, direction, authentication method and owner. She finds that one carrier connection uses a fixed password sent in each request over an encrypted channel, while another uses certificates. Prof. Hale notes that integrations are easily forgotten after setup and often hold broad access, making them attractive to attackers. She completes the list for eleven integrations and confirms an owner for each with the relevant business manager.
34.2 Credentials for interfaces
Interface credentials need the same care as staff passwords. Lindiwe recommends that each integration have its own credential, limited to the operations it needs, stored in a managed secret store and rotated on a schedule. She discovers that two carriers share one credential, so revoking access for one would break the other. Separating them takes a week of coordination but means each partner can be managed independently in future. She moves both credentials into the managed secret store and sets rotation every ninety days.
34.3 Data minimisation
The payroll bureau receives full employee records, including emergency contacts it does not need. Lindiwe reviews the fields with the human resources team and removes six unnecessary ones from the export. She explains that every field shared is a field that can leak from the partner's systems, and that minimising data shared reduces Saltmarsh's exposure without any technical control. The bureau confirms the reduced export meets its needs. The human resources team updates the export specification and records the reasons for each removed field.
34.4 Monitoring exchanges
Lindiwe sets up monitoring for interfaces: volumes per partner per day, error rates and unusual request patterns. A sudden rise in requests for customer addresses from one retailer's credential would suggest misuse. She sets thresholds from three months of synthetic history. Prof. Hale asks who responds to an alert at weekends; she adds the integration owner to the on-call rota so alerts have a clear recipient. The first month produces two alerts, both explained by planned promotions at one retailer, and she adjusts the thresholds accordingly.
Worked example
Lindiwe inventories partner integrations, separates a shared carrier credential, removes six unneeded payroll fields and monitors interface volumes with a named responder.
Synthetic case. Integrations are synthetic.
Errors and limits
A credential shared between partners cannot be revoked for one without affecting the other.
Exercises
- EX100 — Shared credential. What problem did two carriers create? Rubric: 3 = they shared one credential;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX101 — Removed fields. How many unnecessary fields were removed? Rubric: 3 = six;; 2 = partly correct;; 1 = wrong;; 0 = none.
- EX102 — Misuse signal. What would suggest misuse of a retailer credential? Rubric: 3 = sudden rise in address requests;; 2 = partly correct;; 1 = vague;; 0 = none.
Continue studying — lesson 34 (chapter 34 of 50)
← Chapter 33 · Course chapter index · Chapter 35 →
Continue to the next authored lesson.