Networked AV and Security: Liability, Specifying Requirements

Download the essential workbook for mitigating IT security risk and specifying requirements for Networked AV


When security requirements and configurations are overlooked when specifying an AV system, it can lead to a conflict later in the integration process. When expectations for the security features system of the system are not set, the proper requirements are not designed into the system. This crucial workbook explains which areas of IT security, user access control, and network security pertain to AV integration, and then suggests language to accurately convey the security requirements in a Request for Proposal (RFP) or proposal to set expectations for the security attributes of a system.

You will learn:

  • How to identify liability considerations in AV installations
  • Ways to address user access control needs, including AAA best practices for AV
  • Methods for using network security to secure network services
  • Sample language to use in a proposal or RFP for an integrated AV installation

Download the white paper today!


Sneak Peek

"Consultants and integrators often assert that, if they specify security requirements or configurations, they will be liable if there is a security breach. While that may be true, not specifying secure configurations for a system that is breached could leave them open to liability for negligence. Negligence is the failure to act reasonably which unfairly causes someone else to suffer loss or harm resulting in legal liability. The concept of due care is used as a test of liability for negligence. Due Care is the degree of care that an ordinary, reasonable and prudent person would normally exercise, over his or her own property or under circumstances like those at issue. Due care is also called ordinary care or reasonable care. With the rising profile of security related issues in the media, it is expected that a 'reasonable and prudent person' would secure their network in a business."