CoreData & Data Protection

S

2

7

So I am working on a app which stores user information with CoreData framework locally. The information can be sensitive, so I am thinking how to protect the information stored to the data base. In Xcode dashboard, under the capabilities tab, I found this Data Protection switch:

Anyone knows how this works? If I turn on the switch will Xcode encode my CoreData files automatically? Or how to implement this protection on my CoreData files? Appreciate your time and patient. Thank you!

Selfhypnosis answered 21/12, 2016 at 0:5 Comment(3)

Have you tried looking in Apple's documentation at all? Which part(s) do you need help with? – Murrell 21/12, 2016 at 3:8

@Tom Harrington – Selfhypnosis 21/12, 2016 at 4:7

@Tom Harrington Yes I went through Apple's documentation about Data Protection, but it is super brief and did not mention any useful methods or how to implement. I am now confused about how to implement iOS's data protection onto my CoreData database~ – Selfhypnosis 21/12, 2016 at 4:8

K

3

You found the right spot, you have to turn on the Data Protection switch in your target's capabilities pane to signal that you want to use data protection. According to Apple's documentation, this should suffice:

The default level of protection is complete protection, in which files are encrypted and inaccessible when the device is locked. You can programmatically set the level of protection for files created by your app [...]

It states you can set the level of protection programmatically. If you want to do that (I still do that, to be save ;), you should use the appropriate option when creating the persistentStoreCoordinator:

NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
                         @YES, NSMigratePersistentStoresAutomaticallyOption,
                         @YES, NSInferMappingModelAutomaticallyOption,
                         NSFileProtectionComplete, NSPersistentStoreFileProtectionKey, // <-- HERE
                         nil];
...

__persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]];
if (![__persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:options error:&error]) {
...
}

NSFileProtectionComplete means

The file is stored in an encrypted format on disk and cannot be read from or written to while the device is locked or booting.

You could also use NSFileProtectionCompleteUnlessOpen, see the Xcode Quick Help for differences.

Kp answered 21/12, 2016 at 9:48 Comment(3)

Thank you for your response. So if i understand this right, as long as I turn on the Data Protection switch in my target's capabilities pane, all the files contained in this app are encrypted and inaccessible. – Selfhypnosis 21/12, 2016 at 10:9

But I still have the option to change the protection level programmatically. Sounds like turn on the switch is good enough for me:D – Selfhypnosis 21/12, 2016 at 10:10

Yep. Maybe this is why the documentation is so brief ;) – Kp 21/12, 2016 at 10:35

A

5

As per Apple documentation, the Data protection is enabled automatically when the user sets an active passcode for the device. The system encrypts and decrypts your content behind the scenes. These processes are automatic and hardware accelerated. But still we can set the file protection level options programmatically by using none, complete, completeUnlessOpen and completeUntilFirstUserAuthentication

let options = [NSMigratePersistentStoresAutomaticallyOption:true,
                           NSInferMappingModelAutomaticallyOption:true,
                           NSPersistentStoreFileProtectionKey: FileProtectionType.complete] as [String : Any]
            try persistantStoreCoordinator.addPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: storeURL, options: options)

Refer this link to know more information on different types of options.

Apply answered 18/1, 2019 at 11:51 Comment(0)

K

3