Home page logo
/

pen-test logo Penetration Testing mailing list archives

Re: auditing web/mail proxies
From: Anders Thulin <anders.thulin () sentor se>
Date: Tue, 06 Dec 2011 08:36:42 +0100

On 2011-12-05 10:21, cribbar wrote:

Has anyone ever audited a proxy during a pen test/IT audit or as an audit on
itself? If so do you have a scope of what kind of checks you reviewed, or a
checklist? 

  An audit is intended to answer the question: does the examined system work
according to the rules and regulations it should follow? The next question is,
obviously, are there any such rules?

  That should be answered by the organization owning or otherwise managing
the proxy: what rules should be followed? These will typically relate to the
management of the proxy: how is access controlled, how are changes implemented,
how are logs and backups handled, and so on. (Tests of proper function -- quality
testing -- is usually not regarded as part of an audit. That's more akin to
penetration testing.)  The rules need not be expressed for the proxy specifically,
they could be part of an IS or IT policy, applying to all IS or IT systems in
the organization. And in some special cases, they might even take the form of
local or national law.

  For an audit, you job includes defining the system you are auditing (the word
'system' is used an a fairly general sense here -- it needn't be just a network 'box',
but an entire proxy support and management -- don't forget helpdesk!), identify
the rules that are relevant that system, and then verify that they are indeed being
followed.

  If there are no relevant rules, an audit cannot be done.  If the system cannot
be strictly defined (in the sense of if some entity is part of the system or not),
there will be difficulties later. Additionally, if there are rules, but they cannot be
audited (quite often because they are imprecise), the only thing is to identify the
problem, and suggest a remedy for the next audit.

  There *are* usually best practice suggestions, which, in the absence of other
requirements, could (barely) be used. But again, the system definition decides:
are you looking at a proxy box only, or a component in a network, at a system
that must be managed over it's lifetime, alone or in relation to other information systems
of which it is considered a part?


  'Muscular audits' ... deciding on your own what the rules are (or should be) is a
possible way, technically, but it's so far from the accepted definition of an audit that
I don't consider it practical.

-- 
Anders Thulin      anders.thulin () sentor se      070-757 36 10 / Intl. +46 70 757 36 10

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]