Common Cybersecurity Breach Scenarios Disrupted by Zero Trust

June 29, 2021

Hikvision HikWire blog article Common Cybersecurity Breach Scenarios Disrupted by Zero Trust

Four Rules of Zero Trust to Boost Cybersecurity

 

As businesses face more dynamic cyber threat actors than ever before, Zero Trust is recognized as a leading cybersecurity framework for addressing the expanding threat landscape. With cybercrime expected to cost the world $10.5 trillion USD by 2025, let’s take a look at the types of breaches a Zero Trust security approach can prevent and mitigate.

First, a refresher on Zero Trust. The framework of Zero Trust is outlined in our recent white paper Securing a New Digital World with Zero Trust, and includes the premise that all traffic should be regarded as suspicious until verified: “never trust, always verify.” Four key tenets of the Zero Trust approach include:

  1. Protect the crown jewels: Deploy network segmentation to create perimeters and micro-segments, while limiting user privileges (such as unnecessary administrative rights).
     
  2. Automate your lookout: Use leading incident detection and response tools, with automated solutions where possible.
     
  3. Make your tools work together: Integrate cybersecurity offerings across multi-vendor networks to create a comprehensive, unified cyber approach.
     
  4. Keep an eye out: With full network visibility, watch for suspicious behavior and other patterns across data, devices, applications, networking tools and other channels.

With this approach, let’s take a look at common cybersecurity attacks Zero Trust can address:

Phishing Attacks

Phishing is a common type of cyberattack that uses social engineering to fool unsuspecting users. Often, a user will receive an email with an attachment or undercover download link, which tricks them into taking an action that downloads malware or takes them to a fake login page to give away credentials. Consider a scenario where employees receive a forged email that requests them to change their password in a short timeframe. By visiting the link and inputting their credentials into a counterfeit site, users can give threat actors access to a login portal, which allows hackers to move within a network and find additional weak points.

A Zero Trust approach accounts for this by assuming that any user can be compromised. Cybersecurity protocols that allow security administrators to maintain visibility into the network and watch for suspicious behavior can help quickly mitigate attacks as they occur.

A true Zero Trust approach should include informing employees and organizational stakeholders on cyber risk and how to prevent threats. Many Security Operations Centers (SOCs) will run regular exercises and tests including sending their own fake emails to employees to simulate what a phishing attack might look like. In some cases, employees may be asked to take a training course if they mistakenly engage with the fake malicious messages.

Business Email Compromise (BEC)

Business Email Compromise (BEC) often uses a combination of social engineering, malicious email campaigns and other impersonation methods to gain users’ trust with tactics like domain spoofing and lookalike domains. By targeting users with seemingly genuine messages and prompts, attackers can manipulate employees to make wire transfers, hand over credentials and allow threats to penetrate the network.

With Zero Trust, security administrators can use their visibility into a network to detect suspicious behavioral patterns, such as third-party users communicating with large numbers of staff via malicious email campaigns and unauthorized login activity from new devices, locations and users. Zero Trust should extend from the cloud to on-premise, and security personnel should have monitoring capabilities—ideally with automated detection and response—that prioritize mitigating BEC threats.

As with the whole of the Zero Trust approach, user education is key. Business users should understand common giveaways of email compromise, including email addresses and domains that don’t match the official versions, urgent requests for unusual or financially risky behavior including wire transfers and other account actions, and other signs of suspicious activity. Like phishing education, in some cases security personnel may test employees or networks with examples of BEC attacks to determine whether cybersecurity protocols are sufficient to address the threat.

Ransomware

In 2021, ransomware is one of the top challenges facing businesses, with the cost of ransomware rising globally to $1.85 million USD per incident. Ransomware usually comes in the form of employees or authorized users accidentally downloading malware, whether via email or a web portal or other application, that encrypts an organization’s files and data until a ransom is paid. In some cases, ransomware can be delivered via phishing or BEC attacks. In other cases, threat actors compromise credentials, move laterally within the network and deliver ransomware directly to the organization by posing as one of its employees.

A Zero Trust security posture assumes the threat of ransomware is ever-present. With automated detection tools, Zero Trust implementations watch for suspicious activity, malware and user behavior commonly associated with ransomware, such as unauthorized user activity or impersonation websites and other vehicles for malware delivery.

In some cases, ransomware attacks can be stopped at the infiltration stage with simple two-factor authentication. By requiring that all company portals use two-factor authentication for access, such as a text message or a unique code via a two-factor app like Google Authenticator, Zero Trust security practices can use layered security to prevent a malicious actor from gaining the initial login access they need to escalate privileges or infect an organization.

As businesses take steps to address their exposure to cybersecurity risk, Zero Trust represents one of the most important frameworks for building a cyber secure, robust enterprise. View our white paper to learn more.

 

IMPORTANT! This model requires non-standard firmware. Do Not Install standard firmware (e.g. v.4.1.xx) on this model. Doing so will permanently damage your system. You must use custom firmware v.4.1.25 from the iDS-9632NXI-I8/16S product page.

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.

By downloading and using software and other materials available via this website, you agree to be legally bound by HIKVISION General Terms of Use . If you don’t agree to these terms, you may not download or use any of those materials.

If you are agreeing on behalf of your company, you represent and warrant that you have legal authority to bind your company to the General Terms of Use above. Also you represent and warrant that you are of the legal age of majority in the jurisdiction in which you reside (at least 18 years of age in many countries).