The Fortress

• Save your passwords, banking information, user names, notes ... each in its own Vault.
• Make connections between Vaults. Connections allow you to jump from one vault to another; use your own logic and associations to jump between vaults.
• The Fortress is Safe and secure, at both the front end where you the user signs in (using iPicPass), and at the backend where your data is stored (using CORA).
• Sign in (authenticate) with iPicPass; use your own pictures and markers (gestures) to sign in.
• Passwords are optional and don't have to be cryptic - you can choose any password that makes sense to you.
• The complexity of your authentication is found in the visual cues and combinations of gestures (and/or passwords) rather than being forced to use 7 upper case, 5 lower case, 2 numbers and 3 special characters.
• Backup your data locally or online using our Context Ordered Replacement Algorithm (CORA). More information is available in the iPicPass navigational placard in the upper left hand corner of this page.
  • You can save the data files and data key locally on your computer.
  • You can save the data files globally on 1 or more servers, and keep the data key local on your computer or usb.
  • You can save everything globally on multiple servers.
  • You can save one data file locally on your computer or usb, and the rest on 1 or more servers.
• Use Keywords to organize your Vaults.
• Connections and keywords make finding your information fast, intuitive and easy.
• Search by keyword and/or phrases.
• Filter results by your search criteria.

Vault markers are found at the left edge of each row. Vault markers provide visual feedback to the user as shown in the following diagram:

Vault markers can also be used to instantly edit a Vault by clicking on it with a mouse or tapping on it with your finger on a mobile device.

Secure Backup

iPicPass

Security

• Security that goes beyond a text based password.
• Don't be forced into using cryptic codes, numbers and letters that are impossible to remember.
• Increase the complexity of your authentication while simplifying your usage!

• Currently passwords are text based.
• This paradigm erroneously expects the user to provide greater security by using numbers, uppercase, lowercase and other characters.
• Visual authentication is far more complex while being user specific and friendly.

• Create multiple profiles.
• Set your own permissions; one login doesn’t have to fit all situations.

• Have you ever wondered why you only get one user name and password to your online activities?

• A picture is worth a thousand words.
• Upload your pictures.
• Create your own unique pattern for a given picture; this produces a profile.
• Choose a sensitivity and permission for a given profile.
• Add a password if you so desire.

• Your passwords can be as simple or detailed as "you" choose.
• The complexity isn’t found in the text, it is found in the pattern, the sensitivity and the picture.
• Only you know your pictures; you will know why you drag Aunt Sis’ mouth to her foot!

• Swipe through to your dog's photo.
• Click on his head.
• Type a password, say "beauty".
• Drag his heart to the sky.
• Click once again on his right paw.
• Give this profile top permissions - access to all of your accounts.

• Swipe through to your first car.
• Drag the hood to the trunk.
• Click on the driver's door.
• Give this profile lower permissions - access to your petty cash account only.

CORA (Context Ordered Replacement Algorithm)

• Keep your data safe.
• Manage your online data independent of unknown trust relationships.
• Protect your data even if the server is compromised! Even the most secure servers have at times been comprimised.
• Don't rely on a single trust relationship.

• Once it is online, it is somewhere, forever.
• If someone hacks a server, and grabs your data, even if it is encrypted, they have forever to break the encryption.
• Even the most protected servers have occasionally been compromised!

• CORA uses a replacement algorithm to separate your data into multiple files. Each file may be saved locally or remotely on a single, or multiple servers. All files are needed to re-assemble your data. Your data is safe!

• Use two separate servers; as difficult as it is to break into one server, it is nearly impossible to compromise two specific servers belonging to different locals and networks.
• Keep fragments locally on your computer or on your usb.
• Your data is safe!

• Imagine that your favourite book has had letters removed in a context based manner that is unpredictable.
• Then say 20% to 50% of these letters are placed into a bag.
• A thief steels this bag; there is no way for this person to re-assemble your book based upon this bag of stollen letters.

There are 4 key aspects to CORA included in this release of iPicPass.
1. A unique client Key that is produced when you register for the free version or purchase a mobile license.
2. A unique data Key that is created when you initiate a backup of your data.
3. Two or more data files are used to hold the context ordered replacement fragments.
4. You may choose to keep your files locally on your own, or store them centrally on different servers.

Bottom Line
• Your data is safe!
• It cannot be reassembled with just one file!
• If just one key or file is missing, your data will be safe! This multi-dimensional puzzle requires all of the pieces, in order to see any of the pieces!
• Unlike encryption which is based on large prime numbers and a single file, it doesn’t matter how powerful a computer or how much time the thief has; if they don’t have all the pieces and the context, they don’t have your data.

Context Ordered Replacement Algorithm (CORA) is ideally suited to the Global Online community.

By its very nature, CORA protects against a thief/hacker acquiring your data even if they successfully comprimise your online security.

CORA maps your data to different files which are best kept on different storage media, such as on different servers on different networks.

CORA is capable of optimizing corporate security by shielding key elements of the context mappings on a device or network that in a strickly inaccessible (offline).

CORA

The following samples illustrate the types of output obtained with CORA as of this introductory version.

This is a sample client Key: Ÿ老Ӷ㨁仃肐䝜䠬䇶盚慼ⶦʝ擊ഇ㕒҅慤緉㢄㚞湇䧈寉┨ఢⱀ

Data Keys are uniquely generated every time CORA is used. The following are samples of data Keys:
Tue Jul 26 22:12:14 EDT 2011|4767,26,0,2,|3|2|8|16|2929,2198
Tue Jul 26 22:12:36 EDT 2011|4767,26,0,3,|3|3|8|16|2196,1466,1465
Wed Jul 27 05:40:29 EDT 2011|1253,26,0,2,|3|2|31|16|787,592
Sun Jul 31 09:24:00 EDT 2011|4767,26,0,3,|3|3|8|16|2196,1466,1465
Sun Jul 31 09:25:05 EDT 2011|1253,26,0,3,|3|3|31|16|590,395,394

The following are examples of data Files that are generated and presented to the user to store locally.

This is an example of one data File being saved at the client and the second data file being saved at the server. Notice that the data Key is also saved at the client. The second data file has been saved remotely at one of two servers that are located on different networks.

This is an example of two data Files being saved at the client.