Re:ADP intentionally broke its Zenefits integration
by Someone1234 on Monday June 08, 2015 @11:10AM
(#9679571)
It is pretty typical to split sensitive personal information (e.g. SSN, pay, health records, etc) from administrative activities (e.g. leave requests). In the event that the administrative side gets compromised, it will limit how "bad" that compromise might be, additionally they may be required to store sensitive information differently (e.g. better physical security, server-drive encryption, etc).
[ Parent
| on HN ]
Re:ADP intentionally broke its Zenefits integration
by voidlogic on Monday June 08, 2015 @11:16AM
(#9679607)
In a well designed system this kind of segmentation and isolation can be done in a way that is transparent to the user experience.
TL;DR Have your front end talk to multiple backends-
Re:ADP intentionally broke its Zenefits integration
by zimbatm on Monday June 08, 2015 @12:24PM
(#9680093)
The front end is where it usually gets compromised
Re:ADP intentionally broke its Zenefits integration
by Dylan16807 on Monday June 08, 2015 @03:51PM
(#9681848)
Then both passwords get captured on the front end.
There's no benefit to multiple accounts unless the more important one is used much more rarely.
Re:ADP intentionally broke its Zenefits integration
by goodweather on Monday June 08, 2015 @03:41PM
(#9681758)
but they share the same username and password on the different portal?
Re:ADP intentionally broke its Zenefits integration
by c22 on Monday June 08, 2015 @01:48PM
(#9680793)
Is this using "TLDR" as a synonym for "hint"?
Re:ADP intentionally broke its Zenefits integration
by oldmanjay on Monday June 08, 2015 @08:34PM
(#9683407)
I'd guess it's just turning into "thing to put at the end of a post" much like "meme" became "picture with unrelated words on top"