Why IT Provisioning and IT Configuration Roles Must Be Separate
In NetSuite, separating access provisioning from system configuration isn’t just about following a...
The principle of IT vs. Business Segmentation ensures that technical users and business users remain clearly divided in their roles and responsibilities. In modern ERP environments, separating IT and business access is not just a good practice but a security imperative.
IT segmentation restricts technical users — developers, system administrators, and security administrators, and other similar users — to tasks like maintaining system configurations, user provisioning, integrations, and other system-level functions. These users should never touch day-to-day transactional processes. On the other hand, business segmentation ensures that business users — AP clerks, controllers, HR specialists, and others — only perform transactions or operational tasks aligned with their job responsibilities. Simply put, IT keeps the system running and business users run the business.
Blurring these boundaries creates significant risk. If one person can maintain key systems configurations and process financial transactions, they hold the proverbial keys to the kingdom. This concentration of power opens the door to fraud, data manipulation, and even cover-ups. From a compliance standpoint, frameworks such as SOX, GDPR, and NIST explicitly require separation of duties. Beyond compliance, segmentation reduces the risk of accidental misconfigurations, which can, at times, be just as damaging as malicious activity.
Imagine a single Administrator role has with the ability to both configure the system — such as changing Accounting Preferences, enabling features, or modifying workflows — and process financial transactions. This dangerous combination of access would allow one individual to alter critical system settings necessary for controls over financial transactions, manipulate financial data, and even conceal the evidence, all without independent oversight. Far from being theoretical, this type of access overlap has been a well-documented root cause of fraud and control failures in many organizations.
The foundation of effective segmentation is disciplined role design. Access controls must ensure that configuration capabilities reserved for IT such as General Preferences, Role Records, The Enable Features page, access to SuiteFlow, and other key configuration pages are never included in business user roles. Likewise, transactional permissions that belong to business users such as entering invoices, processing payments, posting journals, or approving HR actions should not appear in IT roles. Additional safeguards include requiring dual approval for high-risk configuration changes and monitoring all privileged activity to detect inappropriate use.
Many organizations rely on a single “standard administrator” role that effectively holds the keys to the kingdom. By design, this role often includes the ability to provision users and assign roles, which in itself provides a pathway to unlimited access. Even if direct transactional rights are not granted, an administrator with provisioning authority can simply assign themselves or others broad access without oversight. Because this level of power is sometimes unavoidable for system operation, mitigating controls are essential! Organizations should enforce independent reviews of role assignments and user provisioning activities, require workflows for any high-risk transactions or configuration pages, and monitor administrative activities via NetSuite’s System Notes audit logging. These safeguards do not eliminate the inherent risk of powerful administrator roles but provide the necessary oversight to ensure that access cannot be abused without detection.
By maintaining this clear boundary, organizations achieve multiple benefits. Accountability becomes sharper, since each role has a clearly defined purpose. Audit processes become faster and more straightforward, because auditors can quickly see how responsibilities are separated. And most importantly, segregation lowers the risk of fraud, misstatements, and costly operational issues— ensuring that no single person can both “turn the keys and drive the car.” Segmentation enforces this principle at scale, protecting both the system and the business it supports.
In NetSuite, separating access provisioning from system configuration isn’t just about following a...
Scott Gottlieb’s FDA has implemented many policies in recent years that look to fast-track certain kinds of regenerative medicine procedures so that said procedures can...