Skip to main content
Workforce LibreTexts

6.6: Security vs. Availability

  • Page ID
    22756
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    Much of the business networks will still be up and running. Security staff recognizes that network stability must be maintained for the company to achieve its goals.

    Any company or industry has a small tolerance for downtime on networks. Usually, this tolerance is based on calculating downtime costs with the cost of insuring against downtime.

    For example, using a router as a single point of failure could be tolerable in a small retail business with only one location. However, if a large portion of that company's sales is from online shoppers, the owner may want to have a redundancy degree to ensure there is always a connection.

    Desired uptime is also expressed in the number of down-minutes in a year. For example, an uptime of "five nines" means the network is up by 99.999 percent of the time or down by no more than 5.256 minutes a year. "Four nines" would be a 52.56-minute downtime per capita.  

    However, security cannot be so powerful that it interferes with employee needs or business functions. This is often a tradeoff between good security and allowing companies to work efficiently.

    Availability %

    Downtime

    99.8%

    17.52 hours

    99.9% (“three nines”)

    8.76 hours

    99.99% (“four nines”)

    52.56 minutes

    99.999% (“five nines”)

    5.256 minutes

    99.9999% (“six nines”)

    31.5 seconds

    99.99999% (“seven nines”)

    3.15 seconds

     

    Fun Fact - Three nines \(\PageIndex{1}\)

    Why 99.9% uptime is called 'three nines'? And downtime is 5.256 minutes?  

    Answer

    99.9% uptime = "three nines".   This means the network is available 99.9% of the time.

    To calculate the total allowable downtime:

    1 year = 365 days x 24 hours x 60 minutes = 525,600 minutes

    0.1% downtime = 525,600 minutes x 0.001 = 525.6 minutes

    So "three nines" allows a downtime of 525.6 minutes per year.

     

     

     


    This page titled 6.6: Security vs. Availability is shared under a CC BY 3.0 license and was authored, remixed, and/or curated by Ly-Huong T. Pham and Tejal Desai-Naik (Evergreen Valley College) .