Obviously, Apple is getting more people [to trust them and to buy into their products. The end user is also going to be impacted positively because Apple is not collecting as much data with seamless integration through biometrics. The two-factor authentication and protections limit users from all of this exposure.
Apple is also reigning in their developers. They are forcing builders to use this technology. If you are a developer of an app with Apple, Apple is going to force you—in a nice way—to use Apple’s sign on. This will occur in the upcoming OS 13.
Do you expect we’ll see big changes in the way data is ultimately mined?
Yes, especially among the third-party folks. They may be forced to rely on Apple for authentication. But the third party still wants user info, so they will go a different route in capturing this data. We will see [vendors] making changes on their end to combat against the added security by finding new ways to ask additional questions of users, likely in the apps themselves.
What do solution providers need to know right now about how to navigate Apple’s new security successfully?
From a security perspective, this is a good thing. Solution providers should know that it will crack down on fraud [and breaches]. And, in general for business, you’re going to improve security in your company. If you’re using a “bring your own device” model and [an employee may be using their own phone, for example] you can better control the security of that phone.
Could you give an example of how this works?
Companies of various sizes and technical complexities may use a combination of administrative, physical and technical safeguards to protect their work computing environments. A written policy, like having users sign terms and conditions, coupled with appropriate training on safeguarding protected information, is a great start. However, when workforce members are allowed or encouraged to bring in their own mobile devices (because the organization may not have the means or simply don’t want to purchase additional devices), then a more layered technical safeguards approach may be more viable.
More Info: a+ network+ security+ jobs
Apple is also reigning in their developers. They are forcing builders to use this technology. If you are a developer of an app with Apple, Apple is going to force you—in a nice way—to use Apple’s sign on. This will occur in the upcoming OS 13.
Do you expect we’ll see big changes in the way data is ultimately mined?
Yes, especially among the third-party folks. They may be forced to rely on Apple for authentication. But the third party still wants user info, so they will go a different route in capturing this data. We will see [vendors] making changes on their end to combat against the added security by finding new ways to ask additional questions of users, likely in the apps themselves.
What do solution providers need to know right now about how to navigate Apple’s new security successfully?
From a security perspective, this is a good thing. Solution providers should know that it will crack down on fraud [and breaches]. And, in general for business, you’re going to improve security in your company. If you’re using a “bring your own device” model and [an employee may be using their own phone, for example] you can better control the security of that phone.
Could you give an example of how this works?
Companies of various sizes and technical complexities may use a combination of administrative, physical and technical safeguards to protect their work computing environments. A written policy, like having users sign terms and conditions, coupled with appropriate training on safeguarding protected information, is a great start. However, when workforce members are allowed or encouraged to bring in their own mobile devices (because the organization may not have the means or simply don’t want to purchase additional devices), then a more layered technical safeguards approach may be more viable.
More Info: a+ network+ security+ jobs
No comments:
Post a Comment