Diagnose This Gate Access Install, Unsecure Cabling?

How would you handle this?

You are looking at the unsecured side of the gate that protects the area behind it. Notice the flex-tite conduit installed on this unsecured side of the fence.

Is this the best approach?

In my opinion, the device cabling should be installed inside the fence in rigid pipe to inhibit tampering vulnerability of just cutting or yanking it away from the reader/intercom.

But then again, putting conduit inside the fence puts it inline with gate travel, making routine maintenance hard, and potentially even making UL325 Compliance (Safety Offsets/Travel Limits of Commercial Gates) impossible.

How would you install this?

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*** **** *** *** ***** ***** **** ***** ** *** fence *** ** *** **** **** *** ***** ***** ** on *** *** ** ** ********* ***** ***** ***** ********* the ****-****, *** *** **** *** **** ***** **** *** back.

******** ** ***** ***** ******* ** * ******** *** *** the ****** ****** ** *** ******** ** *** ******** *** reader.

***** **** ** **** *** **** ** **** ** **** a ******* ****** *** '******' *******. * *** *****, * have **** ********* ******* ** *** ****, *** ********* *** the **** *** *** **.

*** ******* *** **** * *** ****, ** * ******* the ***** ***** ** ***** *** ***** ****** ** **** the ****. ** **, **** ** * ***** ******** ****.

*** *******, *** *** ***, ******** *** *****, *** *** in * *** ** ******* * ****, *** ** ************* when **** ****** ** *** **** ***** ***** ** ******* entry, *** **** **** ****** ** ******* ********** ***** (****** to ****** ** ****** ********** ********** ******).

**** ** ** **********? ** **** ****** ***** ** ******* some ****** ** ****** ********, ** ** **** ** **** keep ****** *******-** ***?

******* ******* **** ** ***** *********/**** ** ** ****, ** is **** ** *** ** **** ****** **** *** ****** change. * ***** **** *** ******* ** *******, *** **** to *** ** ***** ****** ** ***** ** *********, *********, etc.

** ***** ** ** ** **** **** ** *******!!

******* ******** ********** ******* ** * ********* ******** ******* ** the ********* ****. ***** **** ****** ******* ** *** ******** face **** ******-***** ****** *** ***** **** ****** ***** ********. All ***** ***** ** ************, **'* ** **** **** ** breach, *** ***** **** ****.

***'* ****** *** ******** ************* ******* ** *** **** ********** key ******. * **** ** ******* ** **** ***** ** my *** ****:******** *************** ******* ** ******** *** ********.

********* *****-** ** **** ******** ************* *******!

** ********, *** *********** **** **** ***** **** ** ********* access ***** *** **** ****** ***** **** **** *****, **** the **** ** ***** ****** ***** *** ** ********* ** distance ***** * **** ***** *******, **** ** *** (****** Fox) ****** ** *****.

** *** **** ** *** **** **** **** ** ****. What ** ********** ** **** **** '**** *** *******-****' ***** keyboxes **** ** ***** **** **** ******** ***** ********** **** long ***** *****-********* **********. **** ******* ******* ** * *******'* Cage. **** *** *** **** ** *** ** ** ***.

*** ** ***** *********, (**** ******** ******** **** *** ***** were ****), ** **** ** **** ********** ** **** ***** data **********. ** **** **** **** **** *** ***** **** onto *********** *****. ***** ***-********** ***** ******** *** ******* & first ********** ******* *** ****** ******!

** ***, **** ** ** ******, ********, *** *********. **** interesting.

****'* * ******* ** *** ****** ***-***** ******. ****** ** uses * **** ***** (**: **** *****) ******.

** **** ** * *** *** ** ******* ***** ****. And ** ********** *** ****** ***** ** ***** ******* ******** key *****!

*******, ** **** **** ************ **** ******** "***** ***" ******* hackers **** *** **** ** ****** ***** **** *** ********* in ********** ***** ****** ** *****. ** *** *** ********** to *** *********** + *** ******!

****, ***???

** **** * ******** ** **: ** **** *** ********* with *** ******** (*** ******** ****** ** *****), *** * second ******* **** ** ****** *** (*** ******** **.***** ** Cards).

**** **** ****!

*** ** ****** **** *** ******?

****, **** **** ****** **** *** ***** **** ***. **'* the **** ********** ** *********.

*******, *** ****** **** * ****** ** * ********* **** repository ***** *** ********* ******* **/* ** ******** *** **** of *** ** ************, ********** ****. (** ****** *** ****** have ******* **** *******).

**** *** ******** ******* *** ** *** **** ** *** secured, *********** *****.

****, **** **** ****** **** *** ***** **** ***.

******. **** **********: *'* * ****** *** *** *****'* ********** you ***** ** ****! :)

****: *** **** ** '******' ******* ****:************* ********* *** ****** ******* *****

*** ******** *** **** ****** ****** *****... *** **'* *** a *********** ***** ** ** ** * ******** ************. ****** dark, ****** ** ****** * *** ***** ** ****** & cyber-criminals. *** ** **** *** ******** *,**** ******* **** **. (To *********: ****** *** *** ******* *******!)

** ******** ** * *** **** ** ****'* ** *******, with *** ******* ******** ***** *** *****. *****, ** ***** be **** ** **** **** ******** ******** ************* **** ***** be **** ********* ** ********** ** ******* ** *** ******** more *************.

* ** **** **** ** *** ********** **** ******! **'** learned ** **** ** **** *****. * **** **** ** be **** ** ********** ** *** *** **** **** (** whatever ** *** ******* **), ** *** *** ******* **** we ****** **** **** ********* ******.

#*****************

******** **** **** *** *** ***** *** ***** *** **** the ********, ***** **** *****, ****'* ****** *** ******* **** a ******** ******? ** ******* ****** **** *** ******* *** got ** *** ******* ***** ** ******* *****, **** ***** they ****** ** **** **?

***:******

** ****** ** *** ** * ****** ******** *' **** and ******* *** ** *** ** *** ***** ** ********. There ****** ** ** ****** **** *** **** *** **** within *' ** *** **** ****** ***** ** **** ** UL325 ********** (**** **** ** ** ********* **** **'* **** an **** ***)