Thanks Elly,
Please share back the pertinent lessons Kenic learnt from this episode
going forward, particularly:-
1. It’s impact assessment on the .KE space, especially economically/
Technical goodwill.
2. Elevation as a critical national security infrastructure
3. Mitigation measures and DR preparedness
4. Critical system upgrade/Change management process/Third party system
handling policy..
Let’s set up this Registry as a world class shining example..
Harry
On 20 Jan 2018 21:41, “Senior System Administrator” <[email protected]>
wrote:
> Hi Harry,
>
> 1) The upgrade was by the developer on his software and it was done in the
> last quarter of last year.
> 2) KeNIC technical team was working with the developer to get real cause
> and restore services before communication. As you acknowledge, .KE is a key
> resource and its restoration in case of a down time is key and needs to be
> followed by an authentic communique.
> 3) KeNIC has a recovery fall back in case of a disaster. This case was
> peculiar because we were protecting client’s transactions in the process of
> service restoration.
> 4) First and most important aspect is done – service restoration.
> Assessment comes after.
>
> Thank you.
>
>
> Kind Regards,
> ……………………………………………
>
> Elly Kadenyo
> Senior System Administrator
> [email protected]
> +254 0720062293
>
> ——————————
> *From: *”Harry Delano” <[email protected]>
> *To: *”KICTAnet ICT Policy Discussions” <
