Security
Subscriber data is a programme, not a policy PDF
Most operator security documents describe a perimeter. The customer does not live on a perimeter. A prepaid profile is written by digital, read by campaign, updated by care, and billed by revenue and billing management. If those four systems disagree about who may see the record, you do not have a control. You have a hope, neatly formatted.
Innova Core Technologies sits in Riyadh with operators and integrators whose estates already contain Microsoft, Oracle, IBM, MongoDB, Sugar CRM, and a campaign stack. The tools are rarely the gap. The gap is that each programme designed access for its own go-live, then left. The next programme inherited four answers to one question: who is this subscriber, and who is allowed to export them?
Follow the identifier
Start with the keys. MSISDN, account id, party id — whatever the estate actually uses, not what the architecture slide named three years ago. Map every store that holds a copy. MongoDB collections, Sugar CRM, campaign audiences, loyalty membership, and billing products often drift by a field or two. That drift is where access reviews fail. It is also where a subject-access request becomes a project.
Write the data classes in language BSS and care will recognise. Identifiers, credentials, marketing attributes, financial events. A campaign segment that includes a financial flag it should never have held is not a “data quality issue.” It is a control failure that marketing will not see until someone else does.
Copies count. Lower environments refreshed from live, partner files, and backups that restore more than you intended are still the customer. A policy that only names production is unfinished. Restore is a security event. If you have not tested who comes back from backup — including privileges you thought you had removed — you have not tested the control.
Put logging where operations sit
A SIEM nobody queries is decoration. Ask who will look at the log on a Thursday, in which console, and what they will do next. Then design the audit trail to that job, using the Microsoft, Oracle, or IBM tools already in the room where they fit. Inventing a second console that only the project team loved is how logging dies at handover.
Privilege change should be visible. So should a campaign extract, a CRM export, and a failed login that matters. If the log cannot answer “who took this segment, when, and under which role,” you will not survive a serious question. Data security as a service is this work: access design, queryable logging, and an operating practice for joiners, movers, and leavers that does not depend on the people who implemented it still answering chat.
Test the ugly cases
A go-live pack that only proves the happy path will not survive a regulator question or a steering committee that has been burned before. Privilege change, backup restore, and a campaign extract of a suppressed or restricted segment belong in the test plan from week one. They belong beside the functional journeys — a prepaid offer, a loyalty earn, a CRM case, a bill — because those journeys are how the data actually moves.
Defects should name the system, the data class, the expected control, and the observed gap. “Security to review” is not a defect. It is a delay. Testing as a practice exists so a vendor or an internal squad can act before traffic, not after the war room forms.
Leave a programme, not a PDF
Handover is the operating note: who approves access, which log is truth, what to do when a partner file arrives, how a restore is requested. Certified, repeatable delivery means the next CX or automation programme does not redesign identity from scratch. Teams we have already sat with — Systems Arabia, STC, Zain KSA, Mobily, Airtel, Maalim Al Khabra, Smart Solutions — know the cost of a policy that never made it into the systems that hold the customer.
If your security work is still a document and the customer already lives in four platforms, that is a programme. Request a callback from Riyadh, or write to Info@innovacore-tech.com. The Data Security service is the delivery thread; this note is the argument for starting it on week one.