Linux Biometric Authentication Server

Linux Biometric Authentication

15 Reasons Why you should implement Biometric Authentication on a Linux Server

  1. Fast Web Server Application Speeds
  2. Fast Database Speeds for CRUD SQL operations
  3. Database Security
  4. Web Server Security
  5. Software Application Security
  6. Files Security
  7. Network Security
  8. Firewall
  9. No Viruses
  10. No Malware
  11. Remove GUI and boot only to Terminal
  12. Reduced Crashes and NO Reboots Required
  13. Stability
  14. Reduced Frequent Updates and System Maintenance Operations
  15. Boost Confidence of your Client and End Users
PHP Biometric Authentication Linux Server Software pack
  1. Fast Web Server

Ever run the WAMPP stack on Windows and the LAMPP stack on Linux?

Which is Faster, a LAMPP or a WAMPP stack?

There is a reason why organizations like Facebook, Google, Quora and other leading online services companies run their back-end on Linux.

Speed is one important factor when you have a Web Application that is servicing millions of Web Requests online. To leverage on this, stability, scalability, Load balancing and speed is paramount. These 4 items can only be provided all together by a Linux platform.

To get the best out of your Web Server like Apache or Nginx or Apache Tomcat for your Web Biometric Server, it is recommended to have your Web Server on Linux.

But before then, you can do a little test on your own to determine whether to deploy your Web Server on either Windows or Linux. First, Get around 100, 000 Fingerprint Templates in a Windows Server as well as in a Linux Server then perform Biometric Authentication for one person in both Servers. It will be evident that the Speeds on the Linux LAMPP Server are much higher than in a Windows WAMPP server.

2. Fast Database for CRUD SQL Operations

The Database in a Linux Server is much faster than in Windows.

Big companies and organizations are already cognizant of the overheads in Windows File Systems ( like NTFS) which makes retrieving and writing to it to be much slower than Linux File Systems (Reisers, Ext4, Ext3, Journal). This ultimately affects the speed with which a simple CRUD SQL query operation will take to complete a single Atomic transaction in a Database in a Linux or Windows Server.

A Linux Server with the same hardware resources as a Windows Server will perform much faster than a Windows Server for SQL operations. Did you know that Microsoft’s SQL 2016 Server also runs on Linux these days? As from MSSQL 2016 Microsoft let’s their clients choose if they want to run their MSSQL on Linux. This is so as to take advantage of the stability, scalability, Load balancing and speed offered by Linux servers.

Similarly, your Biometrics Server would perform optimally and with higher speeds if deployed on a Linux Biometric Server. Think about it! In fact, should you have an ASP.NET Web Biometric Application, you should take advantage of MSSQL 2016 and above which run on Linux to implement a Linux Biometric Authentication Server for your ASP.NET Web Application and enjoy the Blitz speeds.

3. Files Security

Linux gives you an added feature to granulize the level of Files Security properties.

Everything on a Linux Operating System is considered as a File including the Devices connected to the Linux Server. This also implies that if you choose to save Biometric Fingerprint Data images from Biometric Enrolled person they will also be saved as Files.

Since in Linux you can grant File permissions to a group or individual user accounts, you can decide the level to which a group or individual user account can Read, Write, and Execute a file.

Even if the Biometric Authentication Software application that runs on your Linux Biometric Server is executable, you can remove the execute permission from a group of users or to particular user accounts. This gives you control to establish who can run Biometric Authentication on your Linux Biometric Server.

To further make good use of Files Security properties of Linux, you can also encrypt the File System with all Biometric Data Files such that should thieves or an espionage operation target your Biometric Data Hard Disk containers, they would not be able to decrypt back the contents of a stolen Hard Disk’s Biometric Data.

The Encrypted Data would be meaningless to the bad guys. They would not be able to get back the encrypted Biometric Data in a format they can use it against you. It would be useless to them. This is an added security feature that should be the more reason why you choose to implement a Linux Biometric Server for your Biometric Authentication back-end.

4. Database Security

To ensure your Biometrics Database is water tight secure, it is best to install and Deploy it on a Linux Biometric Server.

There are no Viruses, Malware or Trojan Horses on Linux. Even if they found their way into your Linux Biometric Server, they would have to have permission from you to run and even thus, they would not even run because there would be nothing to activate them. The chances of getting your Biometric Database getting messed up by external malevolent applications is close to nil. It would have to be a collaborated internal affair that you would get wind off sooner than later.

Levels of Access Control to a Linux Server are more monitored and precisely captured in the audit trails and same case would apply to any operations carried out on your Linux Biometric Server Database.

Your Biometric Data would be more secure on a Linux Server where you have control over what transpires in your Linux Box.

5. Web Server Security

Running your Web Server like (Apache, Nginx or Apache Tomcat) on Linux is very secure. The Web Server will run on its own path where other user accounts without permission to access its files cannot access it.

For instance, if your Web Biometric Authentication PHP project files run on a path like e.g. /var/www/webbiometricapp you could remove permissions from other users in the Linux Biometric Server from Reading, Writing or Executing any files in this path. This would provide more security in your Web Biometric Authentication Web Server Folders and Files.

6. Software Application Security

In the same way that your Linux Biometric Server is able to securely run its Web Server, the Biometric Software Application (e.g. PHP Web Biometric Software Application) that is served by the Linux Web Server will also inherit the Parent folder Permission properties and will be protected from Access and Execution by User groups and User accounts with no Permissions to Execute and Run it.

7. Network Security

You can configure your Network configurations further on Linux than you would on Windows.

In a Linux Biometric Authentication Server even without a Network Router, you can implement Secure Networking Configurations that can make your Linux Box behave like a Network Router on the Network. You can even partition your Network so that only a particular subnet is able to access Biometric Data for purposes of Biometric Authentication or Biometric Data archiving. This would help prevent unwanted access to your Biometric Data in your Linux Biometric Server.

You can do IP Natting and Port Forwarding in your Linux Biometric Server so that e.g. if your MySQL Database service runs on port 3306 you can assign it to another port like e.g. 99999950. No one would be able to listen to your MySQL service on port 3306 (default port) because you are already port forwarding all traffic on 3306 to 99999950 which is only known to you. The Linux Server would report back to the attacker / application targeting default port that there is no service running on that port. An added security measure.

You can also configure IP masquerading on you Linux Server so that it acts as a gateway for another inside Linux Biometric Server which is not visible to the outside network. An added security measure to protect and secure your Biometric Data and Biometric processes.

8. Firewall

The Firewall and SeLinux in Linux gives you a variety of options to configure your Biometrics Server Box for security.

Different versions of Linux will come with different varieties of Firewalls but they are all better equipped to secure and prevent external attacks to your Biometrics Server.

It is even possible to determine which IP addresses that can be allowed to connect to your Web Biometric Server so that traffic that is not required is prevented from gaining access into your Linux Biometric Server.

This way, your Biometric Authentication server will be very Secure and Safe from External Attacks and theft of Biometric Data.

9. No Viruses

On Linux you will hardly find yourself in a scenario where you have to quickly install the latest Antivirus update because a Virus has been detected on your Linux Biometric Server.

Viruses are mostly designed for Microsoft Windows desktops.

Your Biometric Authentication Server is more Secure, Safe and FREE from Viruses if implemented on a Linux Server.

10. No Malware

Malware is covertly sneaked into a computer system by software utilities purporting to be a safe applications that do not do engage in harmful activities.

This prank can be easily pulled on you on a Windows Computer and the Malware remains resident on your Windows platform doing whatever it wants.

On Linux, if a Malware were to work on a Linux Box it would require you to assign it execute rights. On Linux, nothing runs without your consent. You grant rights to anything you want to run on Linux. You do not have to be afraid that the Malware registered itself on the Registry as a Safe application because on Linux it is Safe and Secure to run whatever application and besides, you will even know what resources an application intends to access before you run it.

Your Biometric Authentication is Safe and Secured from Malware if you choose to run your Biometrics Authentication from a Linux Biometric Server.

11. Remove GUI and Boot only to Terminal

By the way, did you know that you could make your Linux Box to boot only to terminal ( init level 2 ) and display no GUI? This is not possible on Windows.

The beauty of this is that you make it hard for messy and nosy individuals to maneuver around your Linux Box because your average person may struggle to some extend to get their way around a Black and White screen to make any significantly harmful changes or your Linux Biometric Server.

Running your Linux Biometric Authentication Server in Terminal mode ( Bash Shell prompt ) only, deters aggression from petty individuals who may find their way inside your Linux Biometric Server.

Though this does not prevent a determined hacker, it is one of those lines of defense you could consider using in your Linux server. Make your Server only boot into CMD ( Command Prompt only).

This could serve you well in a scenario like where a random support guy or techie with a gun pointed on their head by an attacker would not be able to extract the data in the Linux Biometric Server quickly like they would in a Windows Server as there is no GUI to make the attack run Quickly. They would struggle to get the right tools to get to extract data required by an attacker and by this time, you will have called the Police or security details will have been alerted and help will be on its way to your rescue before not so long.

12. Reduced Crashes and No Reboots Required

Did you know that your Linux box could run for many days, weeks, months and years without requiring a reboot?

Imagine how many times you have had to reboot a Windows Computer Server to give it a manual reset so that it stops hanging?

Have you noticed those instances where your Windows Server becomes slow over sometime and you find that you have to reboot it to prevent it from crashing on you and destabilizing Business operations?

On Linux, your Biometrics Authentication Server can run for a long long time without requiring a reboot or a restart. You could go for two (2) or even more annual leaves without your Linux Biometric Server ever requiring a reboot or encountering a crash.

By the way, disabling the GUI of your Linux box will even make your Linux box more stable to run for years as there will never be an instance of a crashed desktop utility acting up because the Linux GUI froze or needs refreshing.

13. Stability

No production Server should be unstable, unreliable or prone to frequent break downs.

Choosing to install a Linux Server for your Biometric Authentication Server is choosing Stability and Business continuity for the long term.

There are several variants of Linux that do not require you to fix frequent updates on them for them to be stable.

Linux Operating Systems distributions like CentOS, RedHat, Debian and SLES (SUSE Linux) can run on a Server for years as stable Operating Systems.

Not unless you want to add an update by yourself on your own volition, Linux operating systems will be stable to run your Biometric Authentication Server for years without requiring your intervention whatsoever.

Compare the stability of Linux with a random Windows server which will need Engineers to work over the weekend to install updates, Antivirus updates and carry out maintenance on it to make it usable and ready for the new week.

If you want to make the experience of your Software Developers and DevOps Engineers to be interesting and enjoyable, consider migrating your Server computing platform to Linux. You will ultimately free yourself and team from the many petty and non-trivial things that engage your manpower resources and use that resource elsewhere to increase productivity of your team and turn around time of your deliverables.

Your Biometric Authentication Server will be stable and run without hitches on a Linux Server. You can then concentrate your efforts on improving or providing more value to your users on the Client Side of things like developing more intuitive GUIs for Biometrics  Enrollment,

14. Reduced Frequent Updates and System Maintenance Operations

Since most Linux Operating Systems are designed and developed to run for a long without need for updates, you will not find yourself requiring to do a quick update e.g. to your Linux Kernel or File System or to your Firewall or any other components of your Linux System.

In Windows, every now and then you have to check for the latest patches from Microsoft and install them lest your Windows Server Computer becomes another sitting duck at the mercy of the many Hackers and Attackers of your Biometric Data on the internet.

Not unless your Linux Server requires e.g. a Memory upgrade or maybe you need to add a needed PCI card to it, you will not find yourself required to do frequent weekly maintenance operations on your Linux Server Computer.

Running Biometric Authentication on a Linux Server will free you from the need to constantly keep checking whether your Linux Biometric Server is running optimally and if a Software update is slowing down Biometric Authentication speeds.

15. Boost Confidence of Users and Clients

What is a better way to improve the confidence of a prospective CEO of a Company you are targeting to bring onboard as a new client when the CEO of that Company asks, “…and what does your Background run on? Windows or Linux?” Then you confidently tell them, “ We are on Linux and our Servers are all running CentOS 7.5” or “We recently upgraded to RedHat and we are having an easy time managing aspects of Security and Data Integrity on Linux now with RedHat Linux”.

Sometimes it is just how you have packaged your wares on the Shelves that draws the attention of your client hopefuls and in this case, mentioning that your back-end runs on Linux makes your prospective clients know that you take matters security, stability, speeds and Client data integrity seriously.

No one wants their Data to be haphazardly managed on an unstable operating system.  Hiring DevOps Engineers who are good on issues Linux is going to be a big win for you and that of your clients as you will be able to implement Linux Back-ends that give safety assurance to prospective clients before they entrust you with handling their Biometric Data in your Linux Biometric Authentication Server.

PHP Biometric Authentication Linux Server Software pack

Why Jomutech Systems?

Why choose Jomutech as your Biometrics Integration partner

Want to consult Joseph about Biometrics?

Web Biometric Enrollment (Fingerprint Registration)

Web Biometric Enrollment

What is Web Biometric Enrollment?

You could also reframe this Question to ask, What is Web Biometric Registration?

Web Biometric Enrollment is the Capture of a Person’s Biometric Data for the first time into a Biometric System’s Database together with their other particulars that uniquely identify them like Name, Date of Birth, Gender and Nationality.

Web Biometric Registration is the first step of getting data into a Biometric System’s Database.

Emphasis must be made during Web Biometric Enrollment that, quality Biometric Data is captured at this step because Web Biometric Authentication’s success is dependent on best practices being adhered to during Web Biometric Registration.

To further understand the Web Biometric Enrollment process, it is vital to look at the factors that influence the success of Web Biometric Registration.

Web Biometric Enrollment

5 Factors that influence success of Web Biometric Enrollment

1. Mixing of Biometric Scanners from different vendors during Web Biometric Enrollment.

Fingerprint images from different manufacturers will produce Fingerprint Images with different Dimensions (length & width), Image Details, Pixel Resolution, and Quality. 

Fingerprint images from Fingerprint Scanners which have met FBI and NIST standards are the fingerprints that are recommended for use in Web Biometric Enrollment.

Usually, it is the leading Biometric Scanner manufacturers which will avail their devices for assessment of adherence and meeting of quality standards pressed upon by institutions like the FBI and NIST.

Take note that not every company which alleges to be a leading Biometric influencer in the Biometrics industry is one!  The Biometrics companies in this league have certifications to show for every one of those qualifications they have earned for excelling in the Biometrics industry. Imposters in the industry will add the tag ‘leading biometric company’ to their trademark. 

IMPORTANT: Always look for genuine certifications that are also acknowledged by other sectors in the Biometric industry to determine authenticity of a Biometric Scanner from any vendors.

Also, a leading Biometric Scanner manufacturer will have been in the industry at least for over a decade with a line of Fingerprint Scanners over the years with information on when every one of them was made available to the market.

This post will also recommend to you some of the Biometric Scanners which have met FBI and NIST standards for use in the Biometric industry.

Do not forget, during Web Biometric Enrollment, always use Fingerprint Scanners of the same type so that in your Biometric Database you have Fingerprints of the same Dimensions, Pixel Resolution, Image Details and Quality. This way, it will be easier to make any calibrations to the Fingerprint Images with the same parameter to meet any required adjustments in future like converting existing Biometric Data to a new industry Biometric Data type or industry requirement. This would not be possible if in your Biometric Database you have Fingerprint images of different configurations from various diverse Biometric Scanner vendors.

PHP Web Biometrics Lite pack

2. Dry Fingers

Quality of Fingerprint Images captured during a Web Biometric Enrollment exercise can be affected by how dry the Fingerprint images are.

Dry Fingerprint s will be coarse and when presented on the Biometric Scanner for capturing of Fingerprint images will produce low quality Fingerprint images that will also make Web Biometric Authentication problematic later on.

To prevent Dry Fingerprint images from negatively affecting your Web Biometric Enrollment exercise, it is important to figure out how to handle this before Fingerprint images are captured.

A person with dry Fingerprints could be asked to rub their dry Fingers on their face. This can help moisten up a bit because the human face is usually oily before they present their Fingerprints again for enrollment.

The person with dry Fingerprints could oil their hands to make them smooth before presenting them again on a Biometric Scanner.

3. Wet Sweaty Fingers

Wet Fingerprints on the other hand can be a hindrance to a Web Biometric Enrollment exercise. First, they could mess up any paper work because if ink on paper is stained, it will discolor the registration documents or if on the Fingerprint Scanner, affect the Quality of the captured Fingerprint images.

Some people have Fingerprints which naturally sweat and are always wet. This however should not make them worry at all when they are required to present their Fingerprints for a Web Biometric Enrollment exercise.

To make it easy for Wet Sweaty Fingers to be enrolled on a Biometric System, you could recommend to the person to rub their Fingers on their trousers, skirt to dry them up before presenting their Fingerprints on a Biometric Scanner.

4. Cuts and injuries on Fingers

Temporary cuts and injuries can affect the quality of Fingerprint images during Web Biometric Enrollment.

This is so because, the cuts and injuries will heal after some time and future Biometric images captured during Web Biometric Authentication will be different from those captured during Web Biometric Enrollment.

The differences between Fingerprint images captured during Web Biometric Enrollment and during Web Biometric Authentication could influence the Comparison match scores to an extend that if the match scores fall below the desired threshold, the comparison result returns a NO MATCH value.

To prevent cuts and injuries affecting quality of Biometric Fingerprint Data captured during Web Biometric Enrollment, people could be asked to reschedule the web Biometric Registration until a time when their Fingerprint will have been healed. Affected persons could be asked to seek attention or non-affected fingers used instead during Fingerprint Registration.

5. Worn out and under developed Fingerprints

There are some exceptional cases that could prevent capturing and enrollment of quality Biometric Fingerprint images during Web Biometric Enrollment like Worn out Fingers and Under Developed Fingerprints.

People who engage in lots of menial jobs could after some time observe that their Fingerprint patterns are not clearly visible. During capturing of Fingerprints, their Fingerprint image patterns will not be clear and this could make it hard for some type of Biometric Fingerprint scanners to draw Biometric data from them. Persons who experience such should be advised to use protective gloves when working.

Under developed Fingerprints on the hand is prevalent with young kids whose Fingerprints are still developing. A kid’s fingerprints will change with time as they grow until to around age 5-6 years when their fingerprints will have become fully developed. Enrolling Biometrics of a kid could be different from the same fingerprints again in a 2-3 years’ time when they present them again for Web Biometric Authentication.

It is best recommended for kids  below ages 5-6 years to have their parents or guardians use their fingerprints instead for any Biometrics required registration processes until the kids are all grown up to be able to use Biometrics on their own.

There are studies and research currently underway, working towards availing Biometrics Scanners that can help with Biometric Fingerprint Enrollment of young kids into a Biometrics System.

A correctly done Web Biometric Registration exercise is one which endeavors to capture all pertinent information about a Person together with their Biometric Data.

What data is captured during Web Biometric Enrollment?

During Web Biometric Enrollment a series of activities happen. These activities target to register and enroll the following data. They are;

  1. Registration of Person’s Identifying Particulars
  2. Capturing of Person’s Biometric Data

1. Registration of Person’s Identifying Particulars

The Person details that can captured during registration entail but are not limited to the following;

  • First Name
  • Surname
  • Middle Name,
  • Date of Birth
  • Gender
  • Nationality
  • Blood Group type
  • Religion
  • Employer
  • Marital status
  • National Identity Number / Social Security  Number

The information captured about a person at this step should only be the required information for the purpose at hand.

Depending on a case by case scenario, the person’s data captured can vary and in some instances there may be no much data required other than e.g the names and maybe the national identity number.

2. Capturing of Person’s Biometric Data

To capture Biometric Data of a Person, several things too need to be considered beforehand. The following are things that could be looked into to determine what Biometric Data is going to be captured during Web Biometric Enrollment.

  • Which Fingerprints are to be captured for Left Hand
  • Which Fingerprints are to be captured for Right Hand
  • Is one or more Fingerprints required for Fingerprint Registration
  • Are indexes of Enrolled Fingers required to be captured too e.g. is Fingerprint 1 a Left Index or a Middle Right |Finger or a Right Thumb
  • What is the format of the enrolled Biometric Fingerprint going to be? Is it going to be an image of type PNG, JPG, JPEG, BMP, GIF or another data format?

After required Biometric Data is captured, together with other captured pertinent data of the person, the entire data set is combined together and archived in a Web Biometric Database.

To secure Web Biometric Enrollment process, it is important to factor in security concerns and ensure that the enrolled Biometric Data is safely channeled thru a secure network connection to the Biometric Database especially if it is being done remotely outside a company / organization’s headquarters.

How should Biometric Registration and Enrollment be secured on Web?

To secure the entire Web Biometric Enrollment process, the following can be put into practice.

  • Run the Web Biometric Enrollment via a secure SSL connection. You should ensure that the Web Biometric Enrollment page is served to client computer via a secure HTTPS URL  link that would resemble something like https://CompanyWebAddress/WebBiometricEnrollmentPage Take not that it is NOT just http:// but https://
  • Update your preferred Web Browser to the latest version that has updated security features so that you only Web Biometric Enrollment on a Web Browser version you have confidence in.
  • Always download new Web Browsers or updates of your Web Browsers from the Web Browser vendors themselves to ensure that you do not install compromised Web Browsers on your Computers. For instance, you should never download Mozilla Firefox Web Browser from any other website other than from Mozilla website itself. Similarly, do not download Google Chrome Web Browser from any other website other than from Google itself. The same applies for other Web Browsers like Opera, Microsoft Edge and Internet Explorer.
  • Use Biometric Fingerprint Scanners from Trusted sources and Companies. Do not just buy or use in your network any Biometric Scanner you see or find in the market. As the twist of fate goes, these suspect Biometric Scanners are the ones that will fetch cheap market prices. Take care! These are devices that could be priced lowly in the market so as to be easily fordable but under the hood they are espionage electronic devices stealing Biometric Data and sending it to some country somewhere oversees for use by unscrupulous government agencies that have no respect for data rights and God knows for what other purpose they intend to use your Biometric data for.

Which are the Best and most Recommended Biometric Scanners for use in Web Biometric Enrollment?

Below is a list of Biometric Scanners you can confidently buy and use for your Web Biometrics Project. Just make sure you buy then from authentic sources and be wary of counterfeits that mimic their brands. They are;

  • DigitalPersona 4500
  • DigitalPersona 5100
  • DigitalPersona 5160
  • DigitalPersona 5200
  • DigitalPersona 5300
  • Eikon Touch 510
  • Eikon Touch 710
Recommended Biometric Fingerprint Scanners

What Web Browsers should be used for Web Biometric Enrollment?

You can use any Web Browser you love or are comfortable using but make sure it is a secure Web Browser that has recent updates and one that has been around for long  and with a good reputation in the market.

Some Web Browsers you could use for your Web Biometrics system are;

  • Mozilla Firefox
  • Google Chrome
  • Opera
  • Microsoft Edge
  • Internet Explorer

Finally, if you want to have Web Biometric Enrollment running on a Computer without hitches of Operating Systems glitches, consider using the following Microsoft Windows Operating Systems. Do not use Microsoft XP and anything below it at all. You should only use Windows 7 and above. Here are some stable Microsoft Windows operating systems you could use. Make sure you have genuine, registered and activated copies. They are;

  • Microsoft Windows 7
  • Microsoft Windows 8
  • Microsoft Windows 8.1
  • Microsoft Windows 10
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

That’s all. Is there anything you deem should have been in this post but is missing and you would like it added to this post? Write to Jomutech Systems on the below e- mail for it to be looked into and reviewed for consideration for addition onto this post.

Send an e-mail to get Help with your Biometrics Project. Reach out to Joseph

Why Jomutech Systems?

Why choose Jomutech as your Biometrics Integration partner

Want to Consult with Joseph about Biometrics?

Web Biometric Server

What is a Web Biometrics Server?

Web Biometric Server

A Web Biometrics Server is the Computer where the main Web Biometric Application is Installed, Hosted and Served to Client Computers from. In some Web Biometrics Authentication setups, t is also where the Biometrics Database is installed.

A Web Biometrics Server is a special back-end Computer where a couple of Biometrics functions take place like Biometrics Authentication and Biometrics Data Storage.

To further understand a Web Biometrics Server in details, it is essential to be well versed with the particulars that entail Good qualities of a Web Biometric Server.

The following items come into focus when identifying what goes for a good Web Biometric Server;

  1. Operating System
  2. RAM
  3. Processor Type and Speeds
  4. Hard Disk
  5. Ethernet Ports
  6. Web Server
  7. Database
  8. Network Security

1. Operating System:

In order to get the best out of your Web Biometric Server, plan to install an Operating System that will help you achieve what you want to do with your Biometrics Server.

The Operating System you choose to use should be one that has ongoing support from its Software Company. For example, to install Microsoft XP operating system for your Web Biometric Server would be a dumb thing to do circa 2019.

There are no Security Patches released for Microsoft XP nowadays and Microsoft no longer supports this operating system. Not unless your mission is Suicide, to prefer Microsoft XP against e.g. Windows Server 2016 or Windows Server 2019 for your Web Biometrics Server would set you up on a path to Failure.

Similarly, installing Linux Servers with Linux versions that run old Kernels of Linux to your Web Biometrics Server is disastrous as these too like their Windows counter parts will not have been patched against recent security threats that are potentially able to dog them.

Even if you have the latest Operating System, you should always update it with the current Security Patches released by your Operating System vendor.

As you may have determined by now, you cannot be planning to implement a Web Biometric Security solution then slack on security updates of the Operating System where you will install your Biometric solution.

So what is an Ideal Operating System for a Web Biometrics Server?

Ideal Features of a Web Biometric Server’s Operating System.

  • Operating System should be a 64 bit Server. A 64 bit Server unlike a 32 bit Server will make it possible for your Operating System to use more than the 3.5Gb of RAM,. If you have for instance 8Gb RAM in your Server and your Operating System is 32 bit, it will only use 3.5Gb and the remaining 4.5 Gb will be wasted as the 32 bit Operating System will not allocate it System Resources of your Biometric Server.
  • Regular release of OS Security Patches by Software Vendor. The vendor of your Operating System should frequently release service packs to update security features that help secure your platform against adversarial attacks.
  • Reliable OS Support by Software Vendor. Establish if the support provided by the vendor is agreeable to your type of business model. You can subscribe for premium software support from your OS vendor to make it easy and quick to enlist for a helping hand when your platforms breaks down.
  • Easy to update online. There are various ways of updating operating system but the most convenient one is where you can connect a server to the internet, click update button and the OS is automatically updated.
  • Has a Good Reputation as a Stable OS for a Production Server. Scour tech forums and blog posts to see what the tech community has to say about the operating system you want to use. Is it troublesome? Is it stable? Does it crash often in production? Is it easy to maintain and install other software on it? How many big companies in the service line industry are using it? If you get positive responses to questions like these you will be able to assess its reliability.

2. RAM:

Web Biometric Authentication requires lots of memory to run at optimum speeds. It is even more resource intensive if the activity being carried out is Bioemetrics Identification (1:N) where a single fingerprint is being matched against several thousands of other fingerprints to narrow down to an individual.

This is the more reason why it is recommended by Jomutech Systems to prospective clients to have at least 16Gb of RAM or more in their Web Biometrics Server for optimum Biometrics Authentication speeds.

As a rule of thumb, if you are struggling to procure a Server with higher RAM because of cost implications then Biometrics is not for you. Find some other alternative security solution to implement but not Biometrics.

As mentioned earlier, stashing more memory RAM sticks on a Server with a 32 bit architecture or on a Server running a 32 bit Operating System is an exercise in futility. Ensure that you have a 64 bit Server / Operating System before embarking on upgrading the RAM to meet at least 16Gb of RAM.

3. Processor Type and Speed:

A Web Biometric Server needs super speeds to perform Biometric Authentication very fast otherwise you will have a lagging server that processes Biometric Authentication requests at snail speeds.

Those who get Web Biometric Servers with fast Several Core Processors realize Higher speeds for Biometric Authentication Speeds.

Most Servers will have 4 or more Core Processors. The more they are the more your Server can break down Biometric Authentication process into several thread processes and independently work on every one of them thus lowering the time taken to perform Biometric Authentication.

If you are cash strapped or the notion of having a procuring a Server with multiple core processors sounds like an extra cost for you, abandon the thought of implementing / integrating your Software Application with Biometrics. There is no need of waiting for 10 minutes for results of a Single Fingerprint Biometric Authentication process because you do not want to spend money on buying a Server with multiple core high speed processors then pretend to not know that Biometrics Applications require high speed processors to be responsive and fast.

A slow Web Biometric Application because of slow processor speeds and few core processors to help with multithreading will ultimately annoy those operating client computers running your Web Biometrics Application and their customers as well. The end loser will be you when they transition to a provider who offers an infrastructure with high speed processors with multiple core processing units onboard.

4. Hard Disk:

Biometric Data significantly occupies large data space in a Server and for this, you need to arrange to have enough space on your disk farm before implementing your Web Biometrics solution on any Server.

If you have several disk containers, configure RAID on them before installing Operating System. The Operating System will access the RAID configured disk containers as a single Hard Disk Resource.

The minimum size of Hard Disk space for an SME should be 1 Terabyte (Tb). The more space you have the better because a single Fingerprint Template or Blob field in the Database could occupy 312Kb or more depending on the preferred data type for archiving subjects’ Biometric data.

To get the best bargain for a Hard Disk (Disk containers), you can negotiate for better prices when buying a complete Server unlike buying single units of Hard Disks (Disk containers).

If you are just setting about to procure a Server for your Web Biometrics project, ask your hardware provider to give you a catalogue of Servers with 4, 8 or more core processors for you to choose from. The higher the number of core processor the better.

5. Ethernet (eth) Ports:

A Web Biometric Server will need to be connected to the network, internet, LAN, WAN for it to be accessible by Client Computers that will make remote calls to it for Biometric Authentication or for archiving of enrolled Biometrics Data.

To achieve a connection between Web Biometric Server and Client Computers, network ports popularly known as Ethernet ports will need to be present on the server.

You will need 4 or more Ethernet ports for your server.

If you are wondering why 4 Ethernet ports, first Ethernet cards do not cost an arm and a leg. They are among the cheapest peripherals that sub units that make up a Server. Now that we are past the cost hurdle, having at least 4 Ethernet ports will come in handy if you connect to several Routers and Switches to connect your Server to several Client computers.

Also, sometimes you need to block a particular network for maintenance and you do not want your Web Biometric Server to be offline for other partitions of your entire network so in this case having more Ethernet ports equips you to handle things amicably in a big network.

Lastly, if you have configured and connected your server to several failover Routers by procuring network connection services from multiple service providers, in the unfortunate event that one service provider experiences a down time, the availability of your Web Biometric Server to remote client computers is not affected. This is only possible if you have several Ethernet ports to juggle with.

6. Web Server:

To serve a Web Application over the network to client computers a Web Server is required.

What is a Web Server?

A Web server facilitates the provision, interpretation and processing of data requests from client computers. 

You will need to install software applications that provider Web Server instances on your Web Biometrics Server.

Web Server Software Applications you could install on your Web Biometrics Server include the following;

A PHP Web Biometrics Application would require an Apache, Nginx or IIS Web Server to process requests on the Web Bioemetric Server.

An ASPNET Web Biometric Application would require an IIS Web Server to process requests on the Web Biometric Server

A NodeJS Web Biometric Application could require ExpressJS Server to be installed at the Web Biometric Server for it to work.

Whichever Web Server you choose to use for your Web Biometric Server implementation,  make sure that you use the latest Web Serve and also make sure that the Web Server is a Stable release and not a beta release.

7. Database:

To archive Biometric Data in a Web Biometric Server you need a dedicated container for this. You could think of this as a special folder or a Software System for saving Biometric Data. This is what you call a Biometric Database.

There are several databases you could choose to use for archiving your Biometric Data.

Below is a list of Databases you can install in your Web Biometric Server for saving Biometric Data. They are;

If you are going to run an ASPNET Web Biometric application, you will be better off using MSSQL for your Biometric Database.

MSSQL is a Microsoft product and you will need to buy it before you could use it.

Nowadays there is MSSQL for Linux as well unlike in the past where MSSQL would only run on Windows hosts only.

PHP Web Biometric applications are popularly run on a MySQL or MariaDB backend. This is mostly because the LAMPP, WAMPP and XAMPP stacks ship both PHP, MySQL and MariaDB together.

For your Biometrics Database, try and get the stable and latest Database version of the Database currently available so that you can be assured that you are running your Biometrics Database on a secure Database and also get the benefit of using the latest Database management tools the current Database offers which are not available on previous Database versions.

8. Network Security:

One other thing you are going to have to make sure you get it right from the very beginning while setting up your Web Biometrics Server is Network Security.

Your Web Biometric Server should be secure and trusted by other nodes in the network.

The client computers should be assured that they are accessing a secure Web Server on your Web Biometric Server.

Modern Web Browsers like Mozilla Firefox and Google Chrome have been designed and developed with Security in mind. They will raise an alert and complain that the Network connection they are about to remit data thru is not safe after evaluating the authenticity of the Network connection.

To secure the connection between your Web Biometrics Server and client computers running the Web Biometrics application you will need to install an updated SSL Certificate on the Web Biometric Server.

Initially this was not a must but nowadays you have no option but to install one.

This is the only way you can secure your connection and give credibility to client web browsers that they are running a safe Web Application from your Web Biometrics Server.

Clients who are keen on matters security will call you and notify you when you are no longer serving secured web applications to their client computers.

An SSL secured web application will run on a client web browser with a preceding https:// at the address bar. Take note that for a SSL secured connection it will be https:// and not http://

Your SSL secured web link served by your Web Biometric Server should be something like the following

https://WebBiometericServer/WebBiometricAuthenticationPage/ for Biometric Authentication web page or

https://WebBiometricServer/WebBiometricEnrollmentPage/ for Web Biometric Enrollment web page.

There is https:// at the beginning of each of the URLs. and not a http://

Is there anything wish to be covered in this post that would best feature on a post like this? If so, notify us about it on the e-mail below and we will put it into consideration for reviewing and addition to this post.

Send an e-mail to get Help with your Biometrics Project. Reach out to Joseph

Why Jomutech Systems?

Why choose Jomutech as your Biometrics Integration partner

Want to consult with Joseph about Biometrics?