Q: BRESINKx86Monitoring ??

That's Marcel Bresink's Hardware Monitor (or Temp Monitor.) You must have migrated it from another Mac. I think it just means that Marcel Bresink, all of whose programs are well regarded and trusted, has not, can not, or is unwilling on principle, to participate in Apple's code signing nonsense, either for Gatekeeper or for entry in to the App Store. I'm not running ML, but the default Gatekeeper option in Sys Prefs>Security must be set to the highest. You can adjust that setting, so the program will run. Maybe there's even a whitelist so you can allow poor Marcel Bresink to be an exception.

http://support.apple.com/kb/HT5290

http://apple.stackexchange.com/questions/58087/eclipse-4-2-on-mountain-lion-gate keeper-rejects-as-unidentified-developer

Message was edited by: WZZZ

This issue has nothing to do with codesigning.

Mac OS X v10.6 or later: "Insecure Startup Items folder" message appears after logging in

That's too bad. If it was Hardware Monitor, that's an excellent program and you would have paid for it. But I doubt you would have trashed that item so quickly if you had paid for a HW Monitor license; I think you would have remembered that.

Interesting; when I try to drag the item to the trash ("BRESINKx86Monitoring") it tells me "The operation can't be completed because one or more required items can't be found. (Error code -43)"

Ben Furuta wrote:

What does this mean?

As the article indicates, permissions aren't correct. One thing the article doesn't describe is what happens if the problem persists after repairing permissions. For this specific startupitem, the permissions should be owner = system w/R&W and group = wheel w/'R only. Running this Terminal command on the BRESINKx86Monitoring folder inside /Library/StartupItems/ should fix the permissions, allowing its use:

sudo chown -R root:wheel /Library/StartupItems/BRESINKx86Monitoring

For me, deleting the iStat Pro widget (and using a "full removal" uninstaller) did the trick. Hadn't used the widget in ages anyway. Next restart, issue was gone.