Sponsored Content
Full Discussion: Fake MicroSoft calls
Special Forums Cybersecurity Fake MicroSoft calls Post 303011432 by Neo on Thursday 18th of January 2018 08:17:32 AM
Old 01-18-2018
I recall VoIP vulnerabilities over the years and for many years.

On another note, it is always important to keep in mind that (IT) RISK is the intersection of VULNERABILITY, THREAT & CRITICALITY.

So, even if there is a VULNERABILITY, if there is no real THREAT or CRITICALITY, then RISK is LOW.

For example, for someone who uses VoIP and is not a high profile person or spy or criminal etc who has THREATS and if a VULNERABILITY is exploited, it does not do critical harm (in the case of VoIP threats for most people who use VoIP daily), then the RISK is low.

I've been aware of possible VoIP exploits for many years, but it does not stop me from using the myriad technologies that use VoIP. This especially applies to VoIP technologies which are encrypted. LINE, What's App and I believe Skype are all encrypted and so exploiting these VoIP vulnerabilities are non trivial, as I recall, and so most users who use encrypted VoIP are not at high RISK.

There is also the RISK MITIGATION model, which combines TECHNICAL (LOGICAL) CONTROLS, PHYSICAL CONTROLS AND ADMINISTRATIVE CONTROLS, should be considered as well

Encrypting a VoIP channel is a TECHNICAL CONTROL and having a policy whereas HIGHLY SENSITIVE USERS do not use these apps unless approved is an ADMINISTRATIVE CONTROL.

It is important to keep in mind that RISK MANAGEMENT and RISK MITIGATION is a multidimensional and multifaceted approach, so VULNERABILITIES must be viewed in context to the THREAT and CRITICALITY; and RISK MITIGATION must be viewed in terms of RISK and the "best" combination of controls (ADMIN, TECH, PHYSICAL) based on RISK (and this implies budget as well).

Cheers.
This User Gave Thanks to Neo For This Post:
 

2 More Discussions You Might Find Interesting

1. IP Networking

Identification of data calls & voice calls

Is there any facility to filter/identify the data calls and voice calls coming throug modem? OR Can we get the data or voice calls information through a script(preferably C Kermit)? (0 Replies)
Discussion started by: pcsaji
0 Replies

2. Windows & DOS: Issues & Discussions

Microsoft Powerpoint 2003 stops working after 12 April 2011 Microsoft Updates

For the benefit of the community this is a widespread worldwide problem affecting multiple versions of Microsoft Windows. Powerpoint erroneously reports Powerpoint presentation damaged and then often hangs. Until Microsoft sort this out, try removing Powerpoint security update KB 2464588... (0 Replies)
Discussion started by: methyl
0 Replies
TIMETRANS(1p)						User Contributed Perl Documentation					     TIMETRANS(1p)

NAME
timetrans - Converts time into time SYNOPSIS
timetrans [units-options] [-count] DESCRIPTION
timetrans converts time from one type of unit to another. If any of the units options are specified, then timetrans will convert those time units into the number of seconds to which they add up. If given the count option, timetrans will convert that number of seconds into the appropriate number of weeks, days, hours, minutes, and seconds. The converted result is printed out. Units options cannot be specified in the same execution as the count option, and vice versa. timetrans is intended for use with DNSSEC-Tools, for calculating a zone's expiration time. OPTIONS
Units Options The converted value of each unit is totaled and a single result printed. -seconds seconds Count of seconds to convert to seconds. -minutes minutes Count of minutes to convert to seconds. -hours hours Count of hours to convert to seconds. -days days Count of days to convert to seconds. -weeks weeks Count of weeks to convert to seconds. Count Option The specified seconds count is converted to the appropriate number of weeks, days, hours, minutes, and seconds. -count seconds Count of seconds to convert to the appropriate set of units. Other Options timetrans has the following miscellaneous options. -Version Displays the version information for timetrans and the DNSSEC-Tools package. EXAMPLES
Example 1: Converting 5 days into seconds $(42)> timetrans -days 5 432000 Example 2: Converting 2 weeks into seconds $(43)> timetrans -w 2 1209600 Example 3: Converting 8 days and 8 hours into seconds $(44)> timetrans -d 8 -hours 8 720000 Example 4: Converting 1 week, 1 day, and 8 hours into seconds $(46)> timetrans -w 1 -days 1 -h 8 720000 Example 5: Converting 14 weeks, 4 days, 21 hours, 8 minutes, and 8 seconds into seconds $(47)> timetrans -w 14 -d 4 -h 21 -m 8 -s 8 8888888 Example 6: Converting 720000 seconds into time units $(48)> timetrans -c 720000 1 week, 1 day, 8 hours Example 7: Converting 1814421 seconds into time units $(49)> timetrans -c 1814421 3 weeks, 21 seconds Example 8: Converting 8888888 seconds into time units $(50)> timetrans -c 8888888 14 weeks, 4 days, 21 hours, 8 minutes, 8 seconds COPYRIGHT
Copyright 2004-2012 SPARTA, Inc. All rights reserved. See the COPYING file included with the DNSSEC-Tools package for details. AUTHOR
Wayne Morrison, tewok@tislabs.com SEE ALSO
zonesigner(8) Net::DNS::SEC::Tools::timetrans.pm(3) perl v5.14.2 2012-06-21 TIMETRANS(1p)
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy