Latest Posts »
Latest Comments »
Popular Posts »

Secured in Place

Written by WishBoNe on June 26, 2007 – 4:42 pm

A system was to be built to deter information leakage. All information should be highly secured. The developer should build it such that he/she won’t be able to access the actual data after the roll out but must be able to troubleshoot whenever the user calls.

So, when the user calls, the problem must solved. The irony is that the user assumes the developer is able to check on the actual data. Unfortunately, no. The developer is not supposed to.

The next issue is that the problem can’t be replicated in the test environment. So, the developer has to go the user’s desk to see what was the issue. All these can take place for 2 days. The rectification takes another day at least. Testing by the user takes another day depending on the availability.

In the end, it takes about 4 days to complete the rectification including the testing and confirmations. Security is important so even if it takes this much days to resolve, it has incurred the wrath of public users. Lose will be incurred.

If it’s for internal users, the wrath will still be faced. So, security has to be in place and even if it takes longer to resolve, it still has to be in place.


Posted in Design, Life, Software, Technology |

Leave a Comment


Top Technology blogs