With ever increasing demands for specific security and authentication functionality the issue that many organizations are facing is the ability to find a solution that provides an exact fit with their requirements.
Due to this issue many corporations, especially at the enterprise level, are footing the bill to develop these solutions in-house. Although this can provide the exact fit that you are looking for, a homegrown solution is not something that PistolStar recommends. By implementing a homegrown solution it is easy to run into the following issues:
- Higher upfront costs in development and testing time/resources
- More lead-time required – deployment schedule must be pushed out
- Run into all the pitfalls and bugs yourself – impacts user adoption and satisfaction
- Workforce/expertise attrition – what if your developers leave?
- Ongoing maintenance demands and costs
With such complications being present homegrown solutions really open up the floodgates to security holes and unknown issues. By stepping out of your area of expertise and running across the bugs yourself, you have the potential to expose and open up a much larger and more dangerous “can of worms”.
Your end-users are also a concern when choosing to buy or build. By making your employees the “test bunnies” you are in danger of greatly reducing usability, productivity and employee adoption rates. Also your end-users are not always the best measure of success. When implementing a homegrown solution, it is when something is wrong that you are most likely to hear a large uproar from you users, but this gives you no direct insight into the functionality or parts of the solution which they really enjoy.
Overall if you are weighing your options between homegrown or buying we strongly recommend to stay away from homegrown. To replace the homegrown option, it is important to find a third-party solution that provides the flexibility of a custom solution but at an affordable price. By leveraging APIs, such as the PortalGuard API, you can utilize already existing functionality while reducing the complications of starting from scratch.
So whether you decide to use a fully homegrown solution, leverage an API or purchase a solution it is important to consider your users and organization’s requirements. Possibly a combination of all three methods could be the best way to go.
We encourage questions on homegrown solutions so please feel free to email us at email@example.com.