How to create your own JSON security descriptor file
IBM or the other 3rd parties could ship their products' JSON security descriptor files, then you authorized administrator can check their product's security configuration with z/OSMF SCA as shown above, another common case of z/OSMF SCA usage is that you can create your own JSON security descriptor file for your own solution’s security requirements, that's, the JSON security descriptor file is not a product's security requirements description, but a set of resources for your own solution’s security requirements, for example, you may have a couple of user IDs who need to activate the extended MCS console and retrieve messages from OPERLOG, in order to do that your IDs need READ access to CONSOLE and SYSPLEX.OPERLOG resources (profiles), therefor, you can create the following JSON file
{
"ServiceId": "123A123MYID",
"ServiceName": "My Service",
"MetaValidationItemVersion": 1.0,
"Vendor": "My Company",
"SecurityValidationItems": [
{
"ItemID": "123A123MYID0000001",
"ItemType": "PROGRAMMABLE",
"ItemCategory": "Special Authority",
"ResourceProfile": "CONSOLE",
"ResourceClass": "TSOAUTH",
"WhoNeedsAccess": "<user or your group name>",
"LevelOfAccessRequired": "READ",
"ItemDescription": "Allow the user to activate the extended MCS console."
},
{
"ItemID": "123A123MYID0000002",
"ItemType": "PROGRAMMABLE",
"ItemCategory": "Special Authority",
"ResourceProfile": "SYSPLEX.OPERLOG",
"ResourceClass": "LOGSTRM",
"WhoNeedsAccess": "<user or your group name>",
"LevelOfAccessRequired": "READ",
"ItemDescription": "Allow the user to retrieve messages from OPERLOG."
}
]
}
Then you can upload it into the security sub-directory of z/OSMF configuration directory, by default, it is /global/zosmf/configuration/security, (or you can create the JSON in this directory directly), I named this JSON file as myservice.json. At this time when you click "Import" in the "Imported Products", Security Configuration Assistant will find it automatically, then click "load", you will find that it is almost same as you check z/OSMF service.
Suppose you want to know if your ID debug1 has the authority to activate the extended MCS console and retrieve messages from OPERLOG, you can check it by filling the "Validate for ID" box.
Regarding of how to create JSON security descriptor file, you can refer to a few samples here:
https://github.com/IBM/IBM-Z-zOS/tree/main/zOSMF/Zosmf-SCA
For details, please refer to <IBM z/OS Management Facility Configuration Guide> (https://www.ibm.com/docs/en/zos/2.4.0?topic=zmfcg-creating-security-descriptor-files-security-configuration-assistant-task)
Other z/OSMF resources links
You may find the following links are useful when using z/OSMF Security Configuration Assistant
https://mediacenter.ibm.com/media/Use+z+OSMF+to+validate+security+of+DFSMS/1_17jzrqtg/101043781
https://www.ibm.com/docs/en/zos/2.4.0?topic=facility-zos-management-configuration-guide
You can try z/OSMF SCA on z/OSMF trial system here
https://www.ibm.com/account/reg/us-en/signup?formid=urx-34578
Or refer to this blog for more details of how to apply z/OSMF trial system
https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/andrii-vasylchenko1/2018/11/11/a-public-free-on-demand-zosmf-system