Le directeur principal de la cybersécurité Hikvision donne des exemples de vishing et six conseils pour vous protéger du vishing, Partie 2

août 4, 2020

Hikvision HikWire blog article Chuck Davis Vishing Part 2

Dans le blogue d’hier, le directeur principal de la cybersécurité de Hikvision, Chuck Davis, a couvert les problèmes de sécurité liés aux escroqueries. Le blogue d'aujourd'hui présente des exemples de vishing pour vous aider à éviter de devenir une victime.

Le vishing est une combinaison du mot ‘‘voix’’ et du mot ‘‘phishing’’. C'est une forme d’hameçonnage qui utilise des appels vocaux plutôt que des courriels pour inciter une victime à divulguer des informations personnelles, sensibles ou confidentielles à un attaquant. C'est un nouveau terme pour désigner une escroquerie téléphonique. Ci-dessous, nous fournissons des exemples de vishing afin que vous puissiez apprendre à les identifier.

Exemples de vishing

Épisode 69 de Darknet Diaries partage un exemple de vishing. L'épisode entier est perspicace, mais l'histoire qui comprend le vishing commence à 50h29.

En 2018, KrebsOnSecurity nous explique comment certains experts en technologie ont même été arnaqués ou presque arnaqués par des attaques vishing intelligentes.

Tous les appels vishing ne sont pas faits à la victime. Dans la vidéo ci-dessous, vous verrez comment un ingénieur social participant à la conférence de piratage DefCon a pu prendre le contrôle du compte de téléphone portable d'un journaliste (avec autorisation) simplement en passant un appel téléphonique :

· Vidéo YouTube “Real Future: What Happens When You Dare Expert Hackers To Hack You, Episode 8

Six conseils pour vous protéger du vishing

Vous trouverez ci-dessous six façons de vous protéger contre une attaque vishing :

1. Ne donnez pas d'informations personnelles et sensibles à quiconque qui vous appelle directement, sauf si vous pouvez absolument vérifier leur authenticité.

2. Si vous recevez un appel qui pourrait être une attaque de vishing, recherchez le numéro de téléphone de l'entreprise et rappelez-la. Cependant, soyez prudent car certains vishers mettent en place des sites malveillants pour donner de faux numéros de téléphone, alors soyez très prudent lorsque vous recherchez le numéro de téléphone.

3. Comprenez que les attaquants peuvent avoir des informations sur vous lorsqu'ils appellent.

4. Ne répondez pas aux appels provenant de numéros inconnus.

5. Ne payez pas les appelants avec des cartes-cadeaux ou des virements électroniques. Les fraudeurs les veulent comme paiement car ils sont presque impossibles à suivre et vous n'avez aucun moyen d'annuler les frais. Au lieu de cela, effectuez des paiements avec une carte de crédit.

6. Signalez toute attaque vishing :

· Si vous avez perdu de l'argent à cause d'une escroquerie téléphonique ou si vous avez des informations sur l'entreprise ou le fraudeur qui vous a appelé, signalez-le à l'adresse ftc.gov/complaint.

· Si vous n’avez pas perdu d’argent et souhaitez simplement signaler un appel, vous pouvez utiliser le formulaire de rapport simplifié de la FTC à l’adresse donotcall.gov.

Pour plus de conseils afin d’accroître la sensibilisation aux cyberattaques et autres problèmes de sécurité, consultez nos cyberblogues.

IMPORTANT! Ce modèle nécessite un logiciel non standard. N'installez pas de logiciel standard (par exemple, v.4.1.xx) sur ce modèle. Cela endommagerait définitivement votre système. Vous devez utiliser le logiciel personnalisé v.4.1.25 à partir de la page du produit iDS-9632NXI-I8/16S

View the most updated version of this document here:

https://techsupportca.freshdesk.com/en/support/solutions/articles/17000113531-i-series-nvr-firmware-upgrade-instructions

 

The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.

 

Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.

 

After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.

 

Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.

 

Upgrading from v3.4.92 build 170518 or Older

  1. All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
  2. If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
  3. After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
  4. After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
  5. To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
  6. If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.

 

Upgrading from Any v4.X Build to v4.50.00.

  1. Any v4.X build can be upgraded directly to v4.50.00.
  2. Export configuration is highly recommended before performing the upgrade.
  3. If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.

 

Downgrading

Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience. 
 


Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.
 


Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.

 

Action after firmware upgraded 

1. Upgrade the DVR according to the chart above. 

2. Reconfirming Channel's Recording Schedule 

    - Confirm channel's recording schedule is enable. 

    - Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

    - Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode. 

4. Perform Database Rebuild locally. 

    • Some version above support Database Rebuild via web access - K51 and K72

    • Perform Database Rebuild regardless if system is having any database issue symptom. 

    • Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

    • After Database Rebuild - Check log to confirm Database Rebuild has went thru properly. 

    • If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

    • To check log > System > Log > Information > Database Rebuild Started and Stopped.

    • If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process. 

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.

 

 

 

 

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the DS-76xxNI-Q1(2)/P NVRs, also known as “Q series.”

 

These changes do not have any effect on the performance, specifications, or the user interface of the NVRs. For the ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

 

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

 

  • The C-Version NVRs must use firmware version v4.31.102 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v4.30.085 or older.

 

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the Value Express Series NVRs

These changes do not have any effect on the performance and specification of the recorders. For ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

  • The C-Version NVRs must use firmware version v4.30.216 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v3.4.104 or older.

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

En téléchargeant et en utilisant des logiciels et autres matériels disponibles sur ce site, vous acceptez d'être lié par les Conditions Générales d'Utilisation de HIKVISION. Si vous n'acceptez pas ces conditions, vous ne pouvez télécharger aucun de ces documents. Si vous êtes d'accord sur votre entreprise, vous déclarez et garantissez que vous avez le pouvoir de lier votre entreprise aux Conditions Générales d'Utilisation . Vous déclarez et garantissez également que vous avez l'âge légal de la majorité dans la juridiction dans laquelle vous résidez (au moins 18 ans dans de nombreux pays).