PPPMonitord.app

If it's not apparent, this is just a guess. But hopefully it gives you some leads.

First, here's what you can figure out just from the program name. If you run the command /bin/ls /usr/libexec | sort -f | egrep '.*d$' (this print all files in /usr/libexec ending in d), you'll find ftpd, hidd, networkd, systemstatsd, and a lot of programs ending in d. The "d" stands for "daemon", which basically means a helper process that always runs in the background. The sec very likely stands for "security". So secd is the "security daemon". Which makes sense because you said it looks like it works with keychain stuff.

What's the point of daemons? Some daemons stay running to either do some ongoing task. hidd ("human interface device daemon"), for example, is the process responsible for handling mouse/keyboard/trackpad input. Some other daemons do some common tasks that many other programs need. Apps can simply tell the daemon to do something instead of having code to do it themselves. So secd probably does something like this, but related to the keychain.

But what exactly? It looks like it doesn't actually handle normal use of the keychain, since I was still able to use the keychain after I disabled the secd LaunchAgent.

Inspecting the LaunchAgent gives us a clue:

It looks like secd is responsible for syncing the keychain with iCloud?

So what should you do? Try one or more of these:

1. If you don't need iCloud keychain syncing, turn it off in iCloud preferences.
2. Use launchctl to disable secd if it doesn't seem to adversely affect anything.
3. If you need iCloud keychain syncing, see if you have a ton of keychain items, and remove the ones you don't need.
4. Perhaps rebuild your keychain (make a new keychain, move items you need into it, and move it over the older one), in case there are unnecessary artifacts left over in the old keychain.

Both of these plist files appear to be part of the iOS operating system, that have been left in OS X by accident due to the shared nature of their development.

The reason you are seeing errors in EtreCheck for these files is that the plist files are telling the launchd process to run executables that don't actually exist on Macs, but only on iOS devices. And even then perhaps only on devices that are used for development.

I think you are safe to remove both files (although I would keep a copy of them somewhere), firstly because they are failing to launch anyway, and secondly because only seem to relate to components of the iOS operating system.