You must actively encrypt sensitive data. This is the only way you can reliably manage the risk involved.
Every iOS application's data is stored within a container. In theory only your application and the operating system can access the contents of this container.
You can opt for the operating system to handle the encryption for your app:
On Mojave, the categories with no padlock requirement are Contacts, Calendars, (no app has requested access to Reminders yet), Photos, Camera, Microphone, Automation and Advertising.
Those requiring Admin password are Location, Accessibility and Full Disk Access.
Analytics does not require unlocking to change Share iCloud Analytics but does for Share Mac ...
There is no need for external utilities — you can do it using the ootb Apple command line utilities:
# prevent idle sleep while plugged in
# COMMANDS BELOW MUST BE RUN AS ROOT
# (prefix the command with `sudo` or get a root session
# by typing `sudo -i` followed by your password)
# disable sleep (while plugged in or on battery)
This log line makes me wonder if the battery drain is location-related:
locationd(TrackingAvoidance) <Notice>: <private>
Have you granted background location permissions for any apps? If so, are they contributing to the battery drain? Check the Settings > Battery screen.
Also, what iOS version are you running?
I just ran into this problem as well, I found that it was only happening on my MacBook with the Touch ID fingerprint scanner.
If this is true for you as well then you can turn the password prompt off by going to System Preferences > Touch ID and unchecking the box next to Password Autofill.
The log snippets you have included contain no evidence of hacking.
The observations you have are some that would most likely come with normal use of the phone.
All in all, there's nothing specific that indicates any form of hacking. I would say that it is very (!) unlikely that your phone has been hacked.
To my experience, it is a question of Secure Tokens, if it doesn't accept the admin even though it has the shipped (old) macOS installed from the recovery partition.
Even though you have created an admin account, you need it to have a Secure Token and update the preboot, for the recovery partition to accept it.
I did the following (when logged in as the ...
The usual reason for using a .pkg is that the app requires support files in specific file locations.
An installer package will only allow the option of user-domain installation if the developer has expressly set and catered for that option.
With the latest security features in Catalina (and Mojave to a lesser extent), I would suggest that the difference ...
Basically certificates are used so that you can say "I got this information from an otherwise untrusted source, but because it has this associated certificate, I'm going to put some trust in it". This is possible because "someone" has done some sort of vetting of these sources.
In practice, a lot of times this means for example a company wanting to open a ...
Deny any app that needs a background helper and elevated access would be the safe way to sandbox and protect your data. If you grant full disk access and your admin password, all of your data is exploitable, it’s just a matter of how smart and intent that program is to harvest and exfiltrate the data. (Since you didn’t name a specific app, we can’t weigh in ...
This is not an exact answer to what you are looking for, but it is ONE way that you can keep your system safe.
Basically it is an outbound firewall that I have been using for years (I hold no interest in the company, just a happy customer) and it is called Little Snitch.
Basically, once installed, it monitors ALL network traffic and throws up a warning ...
This is actually a widespread issue that was reported by others on macrumors' forums yesterday. Likely we'll see this happen to more and more iPhone users.
This Twitter Thread explains that there is a security flaw in Apple's password reset process which gives explicit confirmation once a correct phone number is inputted for a given Apple ID....