Le directeur principal de la cybersécurité de Hikvision discute du pharming, une attaque de piratage malveillante, et des conseils pour les éviter, Partie 2

juillet 29, 2020

Hikvision HikWire blog article Chuck Davis pharming cybersecurity part 2

Dans le blogue d’hier, le directeur principal de la cybersécurité de Hikvision, Chuck Davis, a présenté le pharming, une attaque de piratage malveillant.

Tel qu’expliqué hier, le pharming est un type de cyberattaque qui redirige le trafic d'un site Web vers un site malveillant qui semble être le vrai site. Le pharming est fréquemment utilisé dans les attaques d’hameçonnage pour inciter une victime à partager ses identifiants de connexion, ses informations bancaires ou d'autres données sensibles avec l'attaquant.

Ci-dessous, nous fournissons des exemples d'attaques de pharming pour vous aider à identifier à l'avance les pirates malveillants.

Exemples de pharming

Il est difficile de rechercher des exemples visuels de pharming car, côte à côte, de nombreux sites Web réels et sites Web malveillants se ressembleront exactement. Cependant, Norton a partagé une courte liste d'exemples d'attaques de pharming que j'ai ajoutés ci-dessous.

· Exemple 1 : Un exemple concret de pharming a été rapporté par Symantec en 2008 avec le premier cas d'attaque de pharming ‘‘au service à l’auto’’ contre une banque mexicaine. Dans ce cas, les pirates ont modifié les paramètres DNS du routeur haut débit non sécurisé d'un client via un courriel qui semblait provenir d'une société de cartes de vœux légitime en langue espagnole. Le code malveillant contenu dans le courriel a modifié le routeur de l'utilisateur pour rediriger son navigateur Web vers le faux site bancaire frauduleux de l'attaquant.

· Exemple 2 : Un autre exemple d'attaque de pharming plus sophistiquée s'est produit en 2017, lorsque plus de 50 institutions financières se sont retrouvées victimes d'une attaque de pharming exploitant une vulnérabilité de Microsoft, créant des sites Web frauduleux imitant les sites bancaires ciblés. Les victimes - des clients en ligne aux États-Unis, en Europe et en Asie-Pacifique - ont été dirigés vers un site Web contenant un code malveillant qui a ensuite téléchargé un cheval de Troie avec cinq fichiers à partir d'un serveur russe.

L'apprentissage du pharming peut vous aider à identifier et potentiellement vous protéger contre cette cyberattaque. Voir ci-dessous pour des conseils pour booster votre cybersécurité.

Conseils pour éviter de devenir une victime du pharming et moyens pour renforcir la sécurité

Vous trouverez ci-dessous plusieurs conseils qui vous aideront à renforcer la cybersécurité :

• Activez l'authentification multifacteur (AMF) partout où elle est disponible. De cette façon, si vous êtes amené à partager vos informations d'identification, l'attaquant ne pourra pas se connecter à votre compte réel.

• Recherchez le HTTPS sur le site Web de destination. Bien que ce ne soit pas une méthode infaillible, un site utilisant le HTTP seulement est un drapeau rouge définitif de nos jours.

• Gardez votre routeur à jour. Si votre routeur ne dispose pas de mises à jour automatiques, envisagez de le remplacer par un nouveau routeur qui se met à jour automatiquement

• Remplacez les paramètres DNS de votre routeur et de vos périphériques par un autre DNS crypté tel que Cloudflare's 1.1.1.1, IBM's 9.9.9.9et Google DNS.

• Suivez les recommandations anti-hameçonnage standard.

Pour plus de conseils Hikvision, visitez la section cybersécurité de nos blogues

Cybersécurité

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).