Ni ruhusa kuchapisha makala hii kwenye gazeti lolote la Tanzania au website inayosomwa na Watanzania bira kubadilisha content au nia ya mwandishi na hakikishaga unatowa credit kwa JamiiForums pamoja mwandishi wa makala Saidhorizons.
What happened to the tax payers' billions of shillings and who was asleep at the switch when this fraud and money laundering were taking place? It's one thing to be robbed at gun point but completely another when the "alleged" financial fraud or scam appears to be an insider job perpetrated by trusted employees that are paid to protect government resources. Presumably, whoever is responsible for this scam is someone who has been thoroughly vetted to perform this critical and sensitive function. How can that be possible? I think some of the managers and directors in the respective institutions must know precisely what happened than they are letting on.
In spite of the banal accusations and counter-accusations that are trumpeted in the local press, there are some basic and fundamental questions that no one is bothering to address in the emotion and heat of the verbal war, and for this, I can't help but single out for special mention the BOT, the custodian and operator of the newly introduced Tanzania Interbank Settlement System, and the TRA, the owner and operator of the TRA Electronic Payment System. I am singling out these two institutions not because I think they are directly responsible for the fraud, (no one knows that for sure), but because they are, or at least they should be better equipped to identify the weaknesses in the Interbank payment settlement system and the TRA Electronic Payment System that can be exploited by cyber criminals. This would allow the investigators to derive some useful insights into the inner workings of these complex systems so that action can be taken to fix the problem, now that we are finding out, to our utter dismay, that these systems have huge security holes through which you can virtually drive a train or pilot an aircraft carrier much to our complete shock and horror!.
Government investigators need to approach this problem with reckless abandon otherwise it might get worse if the guilty parties are not quickly identified and punished. Our initial reaction is to start asking the BOT and TRA some tough but fair questions: What kind of vetting was performed on both systems before they were declared ready for prime time? There was, of course, one way to find out: test the systems. I am assuming, therefore, that pilot trials were performed on both cases and one of the key objectives of the pilot trial was clearly to determine conclusively how the system would stand up against fraud by trusted insiders or by international cyber criminals.
Were the system interfaces and domains of responsibility clearly defined and assigned, including the hand-over or handshake protocol between one management domain and another? Usually cyber attackers take advantage of the security weaknesses at these handover interface points between systems where often domain responsibility may be poorly defined or not at all. This would be the case if this type of technology and expertise is over the heads of the people involved in the system definition and specification. I am not particularly referring to Tanzanians, even in the US I have come across IT amateurs (commonly known as vilaza) masquerading as IT consultants and getting paid ridiculously high wages for their incompetency!. These are the type of issues and reasons that have made a pilot trial an essential and integral part of any newly introduced technology based financial system. Pilot trials provide the opportunity to make appropriate changes to the system or introduce new business processes if necessary prior to deployment in order to plug in any identified security holes before an irreparable and expensive $77 million damage is inflicted as we are sadly finding out now.
Be that as it may, it is abundantly evident, even to the hoi-polloi (yaani sisi akina pangu pakavu), that the person or persons responsible for the operations management and security systems for TISS and the TRA Electronic Payment System (EPS) must have been asleep at the switch, literally, if they found out months after the fact that a whole $77 million of the people's tax revenues cannot be accounted for! Either that or some of them were part and parcel of the cyber-crime syndicate that successfully conducted the fraud. Let's examine some of the evidence:
At the risk of losing some of the readers, I would like to let you (the reader) in on a little IT secret that anyone that is vaguely familiar with these modern electronic payment settlement systems would know. Without boring you (by getting too technical), a Payment Settlement system like TISS or TRA's EPS is comprised of several subsystems: a Terminal Access Device (TAD), The Core Transactions Database System, the Payment Gateway, Operations Control System or Terminal (OCT), and the Extranet, which is a kind of secure private network that can only be accessed by authorized participants. For the purpose of this discussion and in the interest of time I will focus only on the Terminal Access Device and the Operations Control Terminal or Management System.
The Terminal Access Device (TAD) is a workstation (Windows or Linux PC based) that is supplied to each participant or clients (eg, TANESCO and TTCL) by the entity that operates the system. Presumably, in this case the TAD is was recommended, tested, supplied and managed by the BOT if the BOT is responsible for operating TISS. Clients such as TANESCO and TTCL use the TAD to post transactions (eg, make fund transfer requests) as well as perform regular housekeeping tasks such as generating daily reports, usually at the click of a mouse. Needless to say, access to the terminal is highly secure and severely restricted for obvious reasons. Only a handful of thoroughly screened and trusted employs are provided with carefully monitored access to the system.
One of the industry's preferred secure access technology implemented in many of these systems is known as Secure ID (or SecurID) which is a computer authentication mechanism developed and marketed by a company known as RSA. It is widely used in the ICT industry because it is a highly secure and hacker-resistant. The standard user-name and password access security that most computer users are familiar with is just not secure enough for the financial and banking sectors.
Passwords can easily broken even by high school computer hackers let alone sophisticated and international mafia-like cyber crime syndicates with deep pockets. A system that is entrusted with the safety of millions of tax-payers dollars deserves to have the best security that money can buy in order to prevent unauthorized and ill-intended users from causing massive damage. This much we know with a reasonable degree of certainty. What I am personally not sure is what security system has been implemented on either TISS or TRA EPS but I hope it is not the standard user-name, and password or PIN number because that would not be secure enough for such a sensitive and vital financial system.
The other subsystem I would like to spend a bit of time explaining is the Operations Control Terminal (OCT) or Management System (It goes by different names). It is also a workstation (windows or Linux PC based) that is equipped with sophisticated system management software that is primarily used to monitor the TISS and EPS systems. Only the operators (BOT in the case of TISS and TRA in the case of EPS) of the systems would have access to the OCT; clients such as TANESCO or TTCL do not and should not have access to the OCT and this is done deliberately to ensure the utmost security of the system. Transactions posted by clients (TTCL and TANESCO) can be and are monitored but the clients are not necessarily aware that such monitoring is taking place or if they do they may not know what is being monitored. Which is just as well because they need to be kept in the dark for the security of the system.
A powerful application package associated with the OCT that I would like to bring to your attention is the Audit Trail software. Its job is to maintain a chronological log or history of all the key events or transactions that have been performed on the system by each person that has been granted access. That would be considered the minimum must-have capability or function included in such a system, assuming of course that the system procurement team was reasonably conversant with the importance of having such technology and that there was no pressure from management to cut corners in order to save a dime here and a nickel there. We need to find out.
Some of the benefits of audit trail logging include: Fraud detection through the active monitoring and reporting of unauthorized or unapproved information manipulation in the system. Another important benefit of the trail logging feature is what is known as "Data-change Non-repudiation". Simply put, this means if a client changes a designated critical record in the system, for example, transfer tax funds to a CRDB account instead of a TRA account, and then denies having made that transfer. The validity of that claim can be confirmed by inspecting the audit trail log. Imagine how powerful that can be!
Examples of the type of information that can be logged in support of auditing includes: the date and time of the event (eg transfer of funds), the unique ID of the person that invoked the transfer, the nature of the transfer (eg TTCL tax remittance to TRA), whether or not the attempted transfer was a success or failure, and who else (name of person and title) may have authorized the transfer in case more than one person is required to electronically or digitally sign-off the transfer. I would imagine if the transfer involve a large remittance over, say, $1 million, a Director would have to authorize by "digitally" signing-off the transfer. I am sure you have notice my emphasis on a "digital signature" because such signatures are electronically encrypted for authenticity which means it is almost impossible to forge the signature even if you try hard.
All in all it is a rather comprehensive and powerful set of features and one would rightly think fraud is all but impossible under such a tightly monitored system. Apparently not so in our beloved Bongo, which is really a sad indictment of our society!
My questions to the institutions that are charged with the responsibility of operating TISS and EPS are: Have a similar or equivalent audit trail capability been implemented as part of the operations support system and can these logs be used to identify the person or persons that are responsible for making the $5M (or $77M whatever the case may be) transactions that are currently the subject of investigation? If not, why not? What information is missing from both management systems. or more correctly, who dropped the ball on this? Such reports should be available in the operations support systems and should be accessible in a matter of seconds or minutes, not days or months.
When did management first find out that a financial fraud has been perpetrated? Why was it not known sooner? Or more correctly, why did it take so long to detect these financial irregularities given that the operations control system is capable of detecting and reporting on such abnormalities in a matter of seconds? So many questions, so few answers. While it appears (on the surface at least) that the TRA should probably bear the bulk of responsibility instead of trying to wash their hands of their obligations. the matter can be resolved much faster if both the BOT and TRA jointly work together since their systems do interface at some point, which technically could create a security domain black-hole, or what I would like to call the "demilitarized zone" or "a no man's land" that can be exploited by astute cyber criminals.
TANESCO and TTCL should not be allowed to get off scot-free either. I certainly did not want to give the impression that they have zero responsibility in this sad saga and that they are only coming along for the ride! Not so! They should produce a digitally signed document that demonstrates that the purported funds transfer was successfully posted on the EPS system, but the question that I can't answer is that did the TRA include digital signature confirmation in their system that would confirm the transfer had been attempted and succeeded? As I have said before prima facie evidence suggests TANESCO and TTCL also have a few questions of their own to answer and who knows, they may also eventually share culpability. But first things first: at this early stage of the investigation the buck must stop with the BOT and TRA who should have done a much better job of monitoring the operations control systems for TISS and EPS respectively. Overall system security belongs in the hands of the BOT and TRA and not TANESCO or TTCL who after all are only users and have limited visibility to the rest of the system.
One last parting shot to all concerned parties in this saga: Please spare us from this melodramatic finger-pointing public relations exercise through the press. Don't send us on a wild goose chase, let's deal with the real issues and potential solutions and put the finger-pointing and confabulation aside for now. We "the people" - the rank and file - need and deserve to get real and honest answers, not some manufactured smoke screen laid-down by managers who are busy protecting their patushkas instead of seeking a solution to the problem at hand.