FYI - in some organisations, one can file for a formal exception to the process. Theoretically, as long as the process for gaining exceptions is documented, and the formal exception itself is in writing (even if that is an email, if allowed by the process), you can get the exception and still claim full ISO9000 compliance. Back to reality, and we find that politics can easily despoil this utopia of ISO9000 compliance. (Well, as utopic as ISO9000 can be ;->)
Short version: I'd look for a formal exception if possible. Of course, you may have already pursued this course, in which case I point it out solely for posterity in case someone else happens upon this thread in the same situation.
(PS - The last time I saw "security" and "IIS" in the same sentence was in a MS advertisement, so I already guessed the OP was incorrect in their guess ;-})
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
