Two Factor – user’s regular password and IDentiWall’s One-Time-Password (OTP)
One Time Password (OTP)
- Event driven password issuing
- Time driven password issuing
- Pre-issued password
- Seed driven (RFC #: 2289) password issuing
EAP support
LDAP support
MD5 support
Voice ID voice biometrics based authentication
Radius support.
Token device – support for physical token devices
Location - based authentication – integration with Made4Biz’s Dynamic! Security. These location-
based authentication methods will be applied both for the user’s location as well as for the location of the laptop.
- Secure transactions
- Block My Account
response over cellular network.
- Encrypted OTP
which gets decrypted exclusively by Pin Code based Mobile Agent.
- Transaction Verification
over IP and cellular networks.
- Split Transaction
over two networks.
- Session recording
server
- Behavioral engine
- SMS transmission
- SMPP protocol
supported by selective high end SMS Brokers.
- Web Service (SOAP)
Published by various SMS Brokers.
- API
provided by various SMS Brokers.
- Billing methods
- Pre-paid User License – discounted SMS. The organization pays for SMS credit.
- Pay-As-You-Go – free User License but undiscounted SMS.
- Reverse Billing – the end user pays for SMS credit.
- SMS paying through Billing server – the customer or the user buys SMS credit from Made4Biz’s Billing server.
- SMS paying through external SMS broker – the customer buys SMS credit from his SMS broker
- SMS paying through Skype – the customer or the user buys SMS credit from Skype.
This technology sits between the user and Web site and monitors the HTTP content that flows between these two.
Typically the gateway reads the URLs that pass through and when it detects one that was pre-defined it looks into the
HTML body as well. This technology helps in interpreting the HTML content and it can zoom into the content of a specific
field and check it against the organizational policy.
For example: the HTTP gateway can go into a money transfer HTML form, check the content of the ‘sum to be
transferred’ and the ‘target account’ fields, consult the organizational behavioral engine as to the compliance of the
transaction and thereafter act upon its recommendations.
IDentiWall utilizes its own full blown Radius server.
IDentiWall is an SMPP client and the SMS routing server, which is described below, is both SMPP client and
server.
Support for SSL encryption as well as two-way SSL.
This is a technology that helps users perform secured registration in IDentiWall.
Authentication against LDAP servers such as MS-Active Directory.
- SOAP client
- Mobile pre-installed agent
A pre-installed IDentiWall agent on the user’s mobile handset and performs various security tasks such as:
- Open up only after the user supplies a Pin Code.
- Decrypt those SMSs which were sent by IDentiWall
- Encrypt messages sent from the user’s handset to IDentiWall
- Additional functions that are confidential at present…
This WAP page that is actually an IDentiWall Mobile Agent gets pushed to the user’s mobile handset together
with the content that IDentiWall wishes to send to the user. This agent performs tasks such as:
- Open up only after the user supplies a Pin Code.
- Decrypt those SMSs which were sent by IDentiWall
- Encrypt messages sent from the user’s handset to IDentiWall
- More functions that couldn’t be discussed yet …
IDentiWall or other products send their SMSs to the gateway and it redistributes them to the various SMS brokers
depending on their coverage and associated cost structure. Communication to the server from the SMS originators can be
accomplished via SMPP (in such case the gateway acts as SMPP server), SOAP or its published API. At the other end, the
gateway communicates with SMS brokers via SMPP (SMPP client), SOAP, and published APIs of the SMS brokers.
The gateway is designed to support over a billion SMSs per month.
The gateway works in conjunction with the Billing server that is described below. For this communication it supports
a proprietary protocol that is in use only between the gateway and the Billing server.
This is an engine that records and follows up the user’s behavior during their session. The engine is designed to
record full patterns of behavior accumulated over time and determine whenever the user is going out of a known pattern.
IDentiWall is designed to use such behavioral engine whether its his own or when it interfaces with an external one
that is already in use by the customer.
This server has the capability of recording and playing back HTTP user’s sessions. When working in conjunction with
the Behavioral engine, the Recording server can get instructions to start recording even in the midst of an ongoing
session.
A recorded session gets saved for various periods of time depending on the organizational policy and in conjunction
with the Behavioral engine’s instructions.
This is a web server with these functions:
- Manage the customer’s profile
- Manage the user’s profile
- Facilitate the SMS credit purchase both for customers and users
- Notify the customers and the users that their credits reached the minimum balance that they defined.
- Supports PayPal and other payment options
- Multiple pricelists
The syndication server is designed to facilitate cooperation between parties who wish to do so. For example:
- Insurance companies who wish to deploy IDentiWall for insurance brokers. In this situation the
relationship is a many-to-many relationship (insurance company has many brokers and each of the brokers is connected to
many companies).
- Emergency notification of terror event. This could be used in real time by universities to notify their students of a
security event as it unfolds.
