Manage Data Security Policies
Purpose
Provide a controlled, cross-pillar method to export, validate, and
approval-gate the import of the Manage Data Security Policies FSM setup
task. Delegate transport and live import execution to the declared shared and
core dependencies. Capture the user's policy design and prepare supported FSM changes.
Export and move the FSM setup task Manage Data Security Policies only through
the declared dependency workflows. Its catalog identity is
ASXS_MANAGE_DATA_SECURITY_POLICIES; require a current catalog or live-task
lookup to confirm that export/import remains supported before execution.
Scope and boundaries
- Support task-level FSM CSV export and subsequent import of either the exact
exported archive, a verified-template candidate or a user-supplied modified copy.
- Accept policy creation, updates, deletion and redesign, including supported
policy grants and conditions. Preserve user-specified scope and use only this
task's verified contract. Route role-definition changes to Manage Job Roles
or Manage Duties rather than substituting their archives here.
- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.
shared.setup-export.task-level-export owns export; core.data-loader owns
import preflight, upload, initiation, and monitoring.
- A modified archive is a fresh source: calculate a new SHA-256 and repeat
validation, preview, and immediate-approval gates. An approval for the
original export does not approve a modified archive.
Required preflight
- Resolve the project workspace, requested operation, source and target
environments, and exact policy scope. For migration, source and target must
differ; for a same-environment restore, require explicit confirmation.
- Confirm task name and code with
shared.setup-export.task-level-export and
verify CSVExportImportSupportedFlag is Y. On an ambiguous, unavailable,
or unsupported task, record a catalog-mismatch diagnostic and stop.
- Confirm Functional Setup Manager export access in source and Data Loader
import privileges in target. Never request or expose credentials or tokens.
- Persist redacted source/target, task-code, scope, and execution-plan details
before side effects.
Export
- Route export to
shared.setup-export.task-level-export with task name
Manage Data Security Policies, task code
ASXS_MANAGE_DATA_SECURITY_POLICIES, source environment, and project ID.
- Let that skill complete discovery, support validation, process creation,
polling, download, and project export persistence. Never substitute a
template export for a data export.
- Preserve the returned ZIP unchanged and register its path, SHA-256, process
ID, task identity, source environment, and timestamp. Preserve timeout or
failure diagnostics; do not automatically start another export.
Create, update, delete and redesign
Accept these operation requests for this task's own setup objects, including
user-specified individual changes. Prepare supported changes using the target's
FSM template and execute them through core.data-loader; do not reject a
request merely because the user does not already have an input archive.
Read FSM input preparation when preparing a change or helping a user
understand the input. Obtain and safely extract the template, explain its files
and required columns, map supplied business values, and prepare a separate
candidate. Automatically authorize only the necessary template/spec export;
retain Data Loader's validation and actual import approval workflow.
For deletion, verify the explicit supported action for the exact object or
relationship. An omitted CSV row, blank value or unrelated REMOVE action is
not whole-object deletion. If the task has no supported deletion contract,
record that specific operation gap; do not impose a blanket prohibition on all
individual changes or invent a browser/API execution route.
For update or redesign, establish existing keys, preserve unrelated values and
show the intended changes. Intentional changes in the selected target are not
same-environment restores. Apply restore confirmation only to an actual restore.
Template-first import preparation
- Unless the user explicitly overrides this sequence, export the task first
and provide that export as the import template before asking for import
content. Explain that the template establishes the supported archive and
file structure; it is not approval to import.
- When the user provides an input file, compare it with the export template
for file names, headers, column order, encoding, required values, and
task-specific references. Help correct structural defects in a separate
candidate file; preserve the supplied original and do not silently alter
business values.
- Give the user a concise change summary and identify any unresolved values
or references. Use the corrected file only after it conforms to the export
structure and has been assembled into a new candidate archive using the
supported archive shape. That candidate is a new artifact and must pass the
validation and approval gates below.
- The user may override the export-first sequence, template choice, or
proposed file corrections at any time. Honor that direction, while retaining
the required task-identity, validation, and immediate import-approval gates.
Validate and import
- Require a non-empty ZIP and bind its SHA-256 to the task code, source, and
target. Route archive validation to
shared.validation.setup-data-validator.
Fail closed on archive-shape, task-identity, scope, catalog, environment, or
privilege mismatch.
- The ZIP must remain unchanged after validation. Do not unpack, repack, merge,
or transform it. A user-modified copy begins a new validation cycle.
- Route only the immutable validated archive to
core.data-loader as an FSM,
task-routed import, with target environment, task context, SHA-256, and
validation evidence.
- Let Data Loader complete source/API validation and create an immutable
approval preview. Do not replace that route with direct FSM, UCM, REST, CSV,
or browser operations.
- Present the exact target, task code, archive name and SHA-256, validation
result, and expected policy impact. Stop before the first POST. Proceed only
after a separate, immediate approval for that unchanged preview.
- Data Loader owns upload, initiation, monitoring, and diagnostics. Do not
retry uploads, imports, overwrite/replacement operations, or failed jobs
without fresh approval.
Failure handling
Classify failures as input validation, catalog mismatch, authorization,
transport/environment, Fusion API, process timeout, process failed, artifact
persistence, or approval blocker. Redact credentials, tokens, customer data,
and sensitive policy details. Persist a redacted blocker and next action, then
stop on ambiguity or unsafe paths.
Golden scenarios
| Scenario |
Expected result |
| Export policy setup |
Confirm identity and route only to task-level export. |
| Import the unmodified export |
Require ZIP hash, shared/core evidence, and separate immediate approval before Data Loader handoff. |
| Import a modified exported file |
Treat it as a new archive and repeat validation and approval gates. |
| Request direct FSM/UCM/REST/browser import |
Stop; catalog flags do not authorize a replacement route. |
1---2skill_id: "common.security-console.manage-data-security-policies"3name: manage-data-security-policies4description: "Prepare individual data-security-policy creation, updates, deletion and redesign requests using verified FSM templates, and route supported changes through validated Data Loader imports."5layer: "pillar"6pillar: "Common"7task_code: "ASXS_MANAGE_DATA_SECURITY_POLICIES"8task_name: "Manage Data Security Policies"9parent_skill_id: "common.security-console"10available_flag: "Y"11export_import_supported_flag: "Y"12csv_export_import_supported_flag: "Y"13dataloader_import_mode: "FSM"14businessObject: ""15source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"16type: "orchestration"17execution_mode: "hybrid"18owner_team: "FSCR Security team"19version: "0.2.0"20inputs:21 - "project_id"22 - "source_environment"23 - "target_environment"24 - "requested_operation"25 - "data_security_policy_scope"26 - "setup_archive"27 - "user_input_file"28 - "execution_approval"29outputs:30 - "manage-data-security-policies-export"31 - "import-template-export"32 - "input-file-conformance-result"33 - "corrected-input-file"34 - "archive-validation-result"35 - "import-approval-preview"36 - "data-load-execution-result"37 - "diagnostics"38 - "skill-run-record"39 - "token-usage-record"40depends_on:41 - "shared.setup-export.task-level-export"42 - "shared.validation.setup-data-validator"43 - "core.data-loader"44 - "core.project-mgmt.artifact-registry-manager"45 - "core.project-mgmt.project-state-manager"46uses_core:47 - "core.data-loader"48 - "core.project-mgmt.artifact-registry-manager"49 - "core.project-mgmt.project-state-manager"50persists_project_state: true51state_updates:52 - "scope"53 - "exports"54 - "validation_results"55 - "token_usage_records"56token_usage_tracking:57 enabled: true58 granularity: "per_skill_run"59 artifact_type: "token_usage_record"60 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"61 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"62 required_fields:63 - "activity_start_time"64 - "skill_id"65 - "task"66 - "trigger"67 - "artifacts_written"68 - "files_read"69 - "estimated_input_tokens"70 - "estimated_output_tokens"71 - "estimated_total_tokens"72 - "estimation_method"73 - "notes"74workspace_outputs:75 - artifact_type: "configuration_export"76 default_location: "project/{project_id}/exports/common/security-console/manage-data-security-policies/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "validation_result"79 default_location: "project/{project_id}/artifacts/pillars/common/security-console/manage-data-security-policies/current/"80 versioning_policy: "major-new-version-minor-confirm-update"81 - artifact_type: "skill_run"82 default_location: "project/{project_id}/state/runs/"83 versioning_policy: "append-only"84 - artifact_type: "token_usage_record"85 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"86 versioning_policy: "append-only"87oracle_supplied_guidance_files:88 - purpose: "FSM archive and task identity validation"89 location: "ora-resource/ora_input_validation.md"90 - purpose: "Import dependency and same-environment restore checks"91 location: "ora-resource/ora_dependency_readiness.md"92 - purpose: "Immutable preview and Data Loader route enforcement"93 location: "ora-resource/ora_design_enforcement.md"94 - purpose: "Approval, retry, and diagnostic controls"95 location: "ora-resource/ora_error_handling.md"96oracle_supplied_guidance_status: "Repository-authored task validation guidance; current Oracle documentation and the active Fusion contract remain authoritative."97applicability:98 industries: ["All"]99 countries: ["All"]100 fusion_releases: ["Current Oracle Fusion Cloud release"]101side_effects:102 - "May route an approved task-level export to the shared export skill."103 - "May route an approved immutable FSM archive to core.data-loader for upload and import."104required_privileges:105 - "Verified Functional Setup Manager privileges to export the Manage Data Security Policies setup task."106 - "Verified target-environment privileges to upload and initiate the approved FSM archive through Data Loader."107metadata:108 source: https://skillmd.com/skills/oracle/manage-data-security-policies109---110111# Manage Data Security Policies112113## Purpose114115Provide a controlled, cross-pillar method to export, validate, and116approval-gate the import of the **Manage Data Security Policies** FSM setup117task. Delegate transport and live import execution to the declared shared and118core dependencies. Capture the user's policy design and prepare supported FSM changes.119120Export and move the FSM setup task **Manage Data Security Policies** only through121the declared dependency workflows. Its catalog identity is122`ASXS_MANAGE_DATA_SECURITY_POLICIES`; require a current catalog or live-task123lookup to confirm that export/import remains supported before execution.124125## Scope and boundaries126127- Support task-level FSM CSV export and subsequent import of either the exact128 exported archive, a verified-template candidate or a user-supplied modified copy.129- Accept policy creation, updates, deletion and redesign, including supported130 policy grants and conditions. Preserve user-specified scope and use only this131 task's verified contract. Route role-definition changes to Manage Job Roles132 or Manage Duties rather than substituting their archives here.133- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.134 `shared.setup-export.task-level-export` owns export; `core.data-loader` owns135 import preflight, upload, initiation, and monitoring.136- A modified archive is a fresh source: calculate a new SHA-256 and repeat137 validation, preview, and immediate-approval gates. An approval for the138 original export does not approve a modified archive.139140## Required preflight1411421. Resolve the project workspace, requested operation, source and target143 environments, and exact policy scope. For migration, source and target must144 differ; for a same-environment restore, require explicit confirmation.1452. Confirm task name and code with `shared.setup-export.task-level-export` and146 verify `CSVExportImportSupportedFlag` is `Y`. On an ambiguous, unavailable,147 or unsupported task, record a catalog-mismatch diagnostic and stop.1483. Confirm Functional Setup Manager export access in source and Data Loader149 import privileges in target. Never request or expose credentials or tokens.1504. Persist redacted source/target, task-code, scope, and execution-plan details151 before side effects.152153## Export1541551. Route export to `shared.setup-export.task-level-export` with task name156 `Manage Data Security Policies`, task code157 `ASXS_MANAGE_DATA_SECURITY_POLICIES`, source environment, and project ID.1582. Let that skill complete discovery, support validation, process creation,159 polling, download, and project export persistence. Never substitute a160 template export for a data export.1613. Preserve the returned ZIP unchanged and register its path, SHA-256, process162 ID, task identity, source environment, and timestamp. Preserve timeout or163 failure diagnostics; do not automatically start another export.164165## Create, update, delete and redesign166167Accept these operation requests for this task's own setup objects, including168user-specified individual changes. Prepare supported changes using the target's169FSM template and execute them through `core.data-loader`; do not reject a170request merely because the user does not already have an input archive.171172Read [FSM input preparation](../references/fsm-input-preparation.md) when preparing a change or helping a user173understand the input. Obtain and safely extract the template, explain its files174and required columns, map supplied business values, and prepare a separate175candidate. Automatically authorize only the necessary template/spec export;176retain Data Loader's validation and actual import approval workflow.177178For deletion, verify the explicit supported action for the exact object or179relationship. An omitted CSV row, blank value or unrelated REMOVE action is180not whole-object deletion. If the task has no supported deletion contract,181record that specific operation gap; do not impose a blanket prohibition on all182individual changes or invent a browser/API execution route.183184For update or redesign, establish existing keys, preserve unrelated values and185show the intended changes. Intentional changes in the selected target are not186same-environment restores. Apply restore confirmation only to an actual restore.187188## Template-first import preparation1891901. Unless the user explicitly overrides this sequence, export the task first191 and provide that export as the import template before asking for import192 content. Explain that the template establishes the supported archive and193 file structure; it is not approval to import.1942. When the user provides an input file, compare it with the export template195 for file names, headers, column order, encoding, required values, and196 task-specific references. Help correct structural defects in a separate197 candidate file; preserve the supplied original and do not silently alter198 business values.1993. Give the user a concise change summary and identify any unresolved values200 or references. Use the corrected file only after it conforms to the export201 structure and has been assembled into a new candidate archive using the202 supported archive shape. That candidate is a new artifact and must pass the203 validation and approval gates below.2044. The user may override the export-first sequence, template choice, or205 proposed file corrections at any time. Honor that direction, while retaining206 the required task-identity, validation, and immediate import-approval gates.207208## Validate and import2092101. Require a non-empty ZIP and bind its SHA-256 to the task code, source, and211 target. Route archive validation to `shared.validation.setup-data-validator`.212 Fail closed on archive-shape, task-identity, scope, catalog, environment, or213 privilege mismatch.2142. The ZIP must remain unchanged after validation. Do not unpack, repack, merge,215 or transform it. A user-modified copy begins a new validation cycle.2163. Route only the immutable validated archive to `core.data-loader` as an FSM,217 task-routed import, with target environment, task context, SHA-256, and218 validation evidence.2194. Let Data Loader complete source/API validation and create an immutable220 approval preview. Do not replace that route with direct FSM, UCM, REST, CSV,221 or browser operations.2225. Present the exact target, task code, archive name and SHA-256, validation223 result, and expected policy impact. Stop before the first POST. Proceed only224 after a separate, immediate approval for that unchanged preview.2256. Data Loader owns upload, initiation, monitoring, and diagnostics. Do not226 retry uploads, imports, overwrite/replacement operations, or failed jobs227 without fresh approval.228229## Failure handling230231Classify failures as input validation, catalog mismatch, authorization,232transport/environment, Fusion API, process timeout, process failed, artifact233persistence, or approval blocker. Redact credentials, tokens, customer data,234and sensitive policy details. Persist a redacted blocker and next action, then235stop on ambiguity or unsafe paths.236237## Golden scenarios238239| Scenario | Expected result |240| --- | --- |241| Export policy setup | Confirm identity and route only to task-level export. |242| Import the unmodified export | Require ZIP hash, shared/core evidence, and separate immediate approval before Data Loader handoff. |243| Import a modified exported file | Treat it as a new archive and repeat validation and approval gates. |244| Request direct FSM/UCM/REST/browser import | Stop; catalog flags do not authorize a replacement route. |