Previous Article

How to Shop for a Security System

Next Article

What is Security Clearance Status?

What is Security Architecture?

The security service that a system provides is often referred to as its architecture. Security architecture includes all that is needed by its users to implement and maintain the services, as well as what the performance levels are. There are agreed upon principles, that when adhered to, will provide additional information about your system.

Architectural security is a set of nine basic principles. Knowing these principles will aid in making more informed decisions when installing and configuring software. While exercising these principles will not guarantee ultimate protection, it will save you from a false sense of security.



  • Know what is on your system and set a security policy.
    It is necessary to know what needs to be secured.  Once that is documented, a policy for security is to be derived.

  • Actions must be verifiable.
    All actions must be able to be checked for completion

  • Give the least privilege practical.
    Only the required access should be given to any user, process or program. This helps deflect the damage done when someone cracks your system. They may gain some access, but not enough to fully control the system.

  • Practice defense.
    If a firewall is the only security on the system, once that is breached the entire system is exposed. There should be a variety of security levels employed to provide a better defense. Features such as authentication, permissions, whitelists and blacklists are key to more robust security.

  • Review and retain system logs.
    A log is a record of changes made to the system. Often the first sign of integrity loss is seen in the changes in logs.

  • Build to contain intrusions.
    A way to minimize the consequences when security is breached is to limit the access. This contains the damage and aids in protection of the system utilities and configuration files.

  • A system is as strong as its weakest link.
    Users are often the weakest link, not the system itself. Time is well-spent providing basic security practice education of users. Sporadic auditing to assure the practices are being followed is part of this.

  • It is ineffective to lock the barn after the horse is gone.
    Security that is done after a breach occurs does not address the issue of if the system is truly secure. Applying the previous principles will save you from having to reformat and restore your system using backups.

  • Practice full disclosure.
    Notify the users as soon as possible when the system has been successfully breached. This will allow them to implement their own precautionary plans.