Defending Your IT Infrastructure Through Effective Patch Management

    Date28 Sep 2004
    3262
    Posted ByAnthony Pell
    Imagine that you are the IT Director of a large retail bank with an active and highly visible Internet banking service. While driving into the office, half-listening to the radio news, you hear your bank's name being announced, immediately followed by the words "hacker", "massive system failure" and "identity theft". . . . Imagine that you are the IT Director of a large retail bank with an active and highly visible Internet banking service. While driving into the office, half-listening to the radio news, you hear your bank's name being announced, immediately followed by the words "hacker", "massive system failure" and "identity theft". As you take the news in, you recall an earlier email concerning a patch that needed to be applied to your web servers. Two thoughts pass through your mind: "Surely those patches were deployed properly" and "Should I bother driving to the office?"

    According to Gartner, patches are defined as "a software fix made or distributed in a quick and expedient way - typically, via a separate piece of software that users can download and run to modify an application already installed on their computers."

    You are not authorised to post comments.

    LinuxSecurity Poll

    Which Linux distribution(s) do you use?

    Message!

    Poll results are hidden from public viewing.

    You are not authorized to vote on this poll.

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 5 answer(s).
    /component/communitypolls/?task=poll.vote
    7
    radio
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.