CAPTOR (IOS) 4.1.0 RELEASE NOTES

The December 2022 release of CAPTOR (iOS) includes one big new feature and a lot of improvements to backup processing. Here are the highlights:

• AI/ML Object Recognition Model. We get a lot of great user feedback on the CAPTOR Search feature, which already encompasses text found in scanned documents and photos, as well as speech detected in audio recordings. CAPTOR Search now includes objects recognized in photos. For example, searching for the word “chair” would produce any photo that includes a chair in it. This is a Beta release, and we will be updating the model periodically so that more items can be recognized. This implementation of the model is very light so that it does not hinder performance or compromise data protections. For data security reasons, the feature runs on the device without relying on cloud services, and is thus enabled by default. To disable this feature, add the app configuration key “disableimagerecognition” with value “True”.

• Backup Processing. CAPTOR supports four primary data transfer protocols (SMB, WebDAV, SFTP, and Microsoft OneDrive) for copying files to a file repository. Previously the app relied on a third party library to process files for backup. This new version introduces a native iOS function for backup processing which should be more reliable and secure. Bug fixes include deleted items backing up as “unknown files”, files missing from backup, and incoherent error messages in the backup process.

• Microsoft OneDrive. We made a lot of changes to how CAPTOR authenticates and connects with Microsoft OneDrive. The authentication library was updated to MSAL 1.2.5, we authored a custom implementation of Microsoft Graph, and now support custom authentication URLs for a variety of OneDrive for Business implementations. BlackBerry Dynamics users may be required to have the Microsoft Authenticator app installed for OneDrive authentication to succeed.

Please enjoy the update and share feedback by emailing support@inkscreen.com or completing the form on our Support page.

CAPTOR (iOS) 4.0.7 Release Notes

This week marks the release of CAPTOR (iOS) v 4.0.7 to coincide with the iOS 16 launch. Here are some highlights.

• iOS 16 Support. This version has been tested on iOS 16 beta builds up to the moment it was officially released on Monday.

• Improved Annotation Tools. New sizing slider for arrows, text labels, and drawing tools allows more granularity and range in the size of annotation elements.

• Improved Handling of Imported PDFs. Fixed an issue where some PDF layers were stripped out during the import process. CAPTOR now handles a wider array of PDF formats that are opened in CAPTOR.

• New Backup Status Indicators. You can now see the progress and status of files as they are being backed up. The added visibility will let users know if the connection to the backup server was lost or if there were errors in the backup process.

• Improved Startup Experience for InTune Users. Support for ADFS token authentication was added, as well as a better overall activation experience. The app still requires to be quit and restarted once the MAM account has been authenticated with secure InTune services (a feature of the InTune SDK).

• Updated EMM Partner SDKs. Each of our three integrated EMM partners released SDKs for iOS 16 compatibility and our 4.0.7 releases include the following SDK versions:

  • BlackBerry Dynamics SDK v11.0.0.116

  • MobileIron/Ivanti SDK 4.9.0

  • Microsoft InTune SDK 16.1.1

• Pasteboard Alerts/Permission. iOS 16 displays a new alert when an app attempts to access the pasteboard which gives the user the option to disallow the action. Some EMM platforms rely on access to the pasteboard to relay app configuration and policy changes to apps such as CAPTOR, and a user denying permission could lead to security and usability issues. Please contact your EMM provider if you experience a related issue as they likely have work-around solutions available.

Vanessa Bryant Verdict Shines Light on Privacy and Compliance

The verdict against Los Angeles County (for the sharing by first responders of photos of the tragic accident which took the lives of Kobe and Gianna Bryant and companions) raises important data security, privacy and compliance issues.

Josh Bohls, Founder and President of Inkscreen weighed in on the privacy and compliance implications of the situation.

“This is a major but under-examined data security, HIPAA compliance and privacy issue. Law enforcement and first responders to a crime scene should understand that the photos, videos, and evidence they capture and collect are extremely sensitive on multiple levels. In a sensational case such as the tragic loss of Kobe and Gianna Bryant and their companions, the stakes are even higher. We can hope that the judgement to award mother and widow Vanessa Bryant and other families who experienced this tragic loss will ultimately spur some change both in policy and in the technical way that digital evidence is captured, managed, and protected.

The fact is that we’re now 15 years into the smart mobile and social networking era, and the data leakage prevention (DLP) technology and applications to ensure content can be securely captured and managed, and that prevents unauthorized sharing of photos, documents and other sensitive data on responders’ personal devices has existed for at least 10 years. Every Federal, state and local first responder agency should mandate the use of such technology. It’s a safe guess that 99.99% of responders would never dream of violating a victim’s or family’s privacy at their most tragic moments, but how many of that .001% does that leave to do such social harm?

Mrs. Bryant and all who lost loved ones in this accident have suffered immeasurable loss. Whether intended or not, Mrs. Bryan has emerged as a voice for the otherwise voiceless parents and loved ones of victims whose anguish is compounded every time their loved one’s image is shared or re-shared. And once those images are ‘in the wild’ re-sharing by non-responders is all but inevitable. Incredibly sad – but so easily preventable.”

This post appeared first on EnterpriseSecurityTech.com