OBS Buckets Have WORM Enabled
Rule Details
Parameter |
Description |
---|---|
Rule Name |
obs-bucket-default-lock-enabled |
Identifier |
obs-bucket-default-lock-enabled |
Description |
If an OBS bucket does not have write-once-read-many (WORM) enabled, this bucket is noncompliant. |
Tag |
obs |
Trigger Type |
Configuration change |
Filter Type |
obs.buckets |
Configure Rule Parameters |
None |
Applicable Scenario
In compliance mode, a WORM-protected object version cannot be overwritten or deleted by anyone, including the root user. For details, see Configuring WORM to Protect Objects from Being Overwritten or Deleted.
Solution
You can enable WORM for noncompliant OBS buckets based on Configuring WORM to Protect Objects from Being Overwritten or Deleted.
Rule Logic
- If an OBS bucket has WORM enabled, this bucket is compliant.
- If an OBS bucket does not have WORM enabled, this bucket is noncompliant.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot