|
| FEATURES |
|
|
| Platform and Database |
| AKIVA is built on Java, JDBC and Struts to be deployed on UNIX / Windows platforms and ORACLE database.
|
|
|
| Back to top |
|
| Masking Algorithms |
Inbuilt masking algorithms provide the logic for de-identifying data and allow clients to mask data in numerous ways according to different requirements. Following are the algorithms built into AKIVA.
- Scramble
Arithmetically generates new values in required field format based on user input
- Shuffle
Mutates and/or riffles data within the database in several ways. Logical realignment of data is done in the database
- Blankout
Nullifies the data
- Replacement
Substitutes the field values with a static value provided by the user
- Lookup
Replaces employee names and addresses choosing from an inbuilt repository of over 200,000 names
- SSN Generator
Generate valid US Social Security Numbers for all employees
- Luhn Generator
Generate new numbers satisfying Luhn Checksum condition. Typically used for Credit Card Number generation
- Sequence and Random Number Generators
Generate numbers in order or in random
- Pattern Generator
Generate a set of numbers adhering to patterns. User has the flexibility to define infinite number of patterns
- Rule based masking
Consistently masks the database based on rules/custom masking algorithms defined by the user
- Compensation Skewing
Masks compensation related fields consistently across the database
|
|
|
| Back to top |
|
| Application Focus |
AKIVA understands the complete Application Architecture.
Hence, there is no impact on Business Processes. |
|
|
| Back to top |
|
| Multi-threading |
| AKIVA supports parallel execution to reduce runtime. |
|
|
| Back to top |
|
| Key field masking |
| Supports masking of all key fields without any impact. After masking, AKIVA will retain the indexes in the database in order to maintain the uniqueness in the data |
|
|
| Back to top |
|
| Reusability and Batch Processing |
Masking configurations can be reused for different runs.
AKIVA can be invoked from the command line which allows the customer to run it as a batch process. |
|
|
| Back to top |
|
| Flexibility |
| Enables data security officers to choose any of the sensitive data elements across enterprise using Akiva's online interface. This includes customized components too. |
|
|
| Back to top |
|
| Flat File Masking |
| Masks inbound and outbound files |
|
|
| Back to top |
|
| Report Generation |
| Generates audit report which is useful during audits. |
|
|
| Back to top |
|
| Database Driven |
| AKIVA retrieves and manipulates data directly from database and masks data consistently across the enterprise, so that the same entity relationship is maintained post masking |
|
|
| Back to top |
|
| Realistic Data |
| AKIVA uses different masking techniques to create realistic and fully functional data. Once the data is masked, it maintains its correct behavior needed for use in a variety of non-production environments. |
|
|
| Back to top |
|
| Preview masking |
Provides the user the opportunity to see a sample of the data post-masking.
It aids the user in selecting the appropriate algorithm for each field. |
|
|
| Back to top |
|
| Mask it your way |
Incase the user doesn't want to use any of the inbuilt algorithms, AKIVA allows the user to define any custom masking algorithm/rule to mask the database.
This offers the user infinite options to perform masking. |
|
|
| Back to top |
|
| Database Level Security |
| Database access is defined by the security inherent in the database, not in the AKIVA application. The username and security permissions for AKIVA are the same as those privileged by the database. This security feature ensures that only those individuals with high level database access have access to AKIVA. |
|
|
| Back to top |
|
| Limit masking |
| AKIVA allows the user to mask only a selected subset of tables. Other database tables are not impacted. |
|
|
| Back to top |
|
| User Interface |
| AKIVA is feature-packed and comes in a simple, intuitive and user-friendly web interface |
|
|
| Back to top |
|
| Data Subsetting |
| Allow the user to remove confidential data by sub setting the data according to the user requirements. This would help in Infrastructural cost reduction |
|
|
| Back to top |
