[VoiceOps] SS7

Kidd Filby kiddfilby at gmail.com
Thu Apr 21 18:26:34 EDT 2016


Dan;

I totally agree with you on where the industry is headed and we will get
there.  Encryption has definitely become a MUST-HAVE with the technology
change to connectionless vs. timeslot-oriented network.  However, we are
not there yet.  Where there is a will, there is a way... on both sides of
the coin, unfortunately.

Although some individuals are just seeing the light, security is king, in
communications, and it has been for a long time.  I recall designing VSAT
systems for major corporations in the 80's, for both voice and data
applications.  Their #1 priority was encryption on both.  Along with this,
network isolation and ingress points MUST be key components to the design
of the deployment &/or service offering to protect both your customer and
YOUR network.

This has been a great discussion on a very important topic.

Kidd



On Thu, Apr 21, 2016 at 1:44 PM, Dan York <dyork at lodestar2.com> wrote:

> This is generally true if the calls are *unencrypted* on VoIP...
>
> On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>
>>
>> Also folks, don't forget, the same outcome of recording someone's call is
>> MUCH easier to accomplish once it is VoIP.  IMHO, of course.  ;-)
>>
>
> ... BUT... what's fascinating is the recent rise in end-to-end (e2e)
> encryption among IP-based communications platforms that include voice.
>
> WhatsApp, for instance, just completed the rollout of e2e encryption on
> April 5, and not just for messaging, but also for voice and video calls as
> well as file transfers (
> https://blog.whatsapp.com/10000618/end-to-end-encryption ).  Just
> yesterday the team behind Viber announced that they will soon have e2e
> encryption for all clients.  The app Wire ( http://wire.com ) also does
> e2e encryption for voice, video and group chats.
>
> In a US Congress hearing this week, a Congressman asked a Dept of Homeland
> Security representative if e2e encryption available in apps would have
> prevented this interception that happened via SS7. The DHS answer was that
> it would mitigate the interception of the content, although the location
> meta-data would still be available.  (You can view the exchange via the
> link in this tweet:
> https://twitter.com/csoghoian/status/722854012567969794 )
>
> The end result is that we're definitely moving to a space where the
> communication over IP-based solutions will wind up being far more secure
> than what we had before.
>
> Interesting times,
> Dan
>
> --
>
> Dan York
> dyork at lodestar2.com  +1-802-735-1624   Skype:danyork
> My writing -> http://www.danyork.me/
> http://www.danyork.com/
> http://twitter.com/danyork
>



-- 
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160421/fbc96c7f/attachment.html>


More information about the VoiceOps mailing list