Security

Useful access. Clear boundaries.

Cedros provides controls for the people, assistants, and extensions working with your website. Manage access, inspect protection activity, and keep sensitive capabilities scoped to the job.

Explore plans /pricing See the platform /about

Protection across the website’s working parts

Control team access

Use roles and permissions to determine which site areas a person can use. Review access when responsibilities change and avoid giving every account the same operational reach.

Scope assistant tools

Configure what the assistant can read or change by area. External MCP clients use authorized keys and tool permissions, with release and confirmation requirements for the relevant actions.

Inspect request protection

Review the site-protection dashboard, lockouts, and IP rules. Use the evidence to respond to abuse while understanding the effect a rule has on legitimate visitors.

Review extension capabilities

Extensions operate within the supported runtime and capability contract. Inspect their requirements, provider access, and custom behavior as part of installation and maintenance.

Keep private information deliberate

Decide which data belongs in public content, private business context, and restricted tools. Configure providers, analytics, and retention for the information your site handles.

Treat security as maintained behavior

Platform controls are part of the foundation. Your account access, custom code, connected services, and recovery setup still need ongoing review appropriate to the business.

Useful to know

Does using Cedros certify my business for a regulation?

No. Technical controls do not establish industry-specific or legal compliance on their own.

Can I inspect or change protection rules?

Authorized users can use the protection dashboard and supported rule-management tools. Review the impact before changing access.

Is every custom code block a security sandbox?

No. Different extension and authored-code surfaces have different trust models. Follow the documented runtime and author permissions for the surface you use.

Give the business tools a considered set of controls.

Build with permissions and operational visibility from the start.

Talk about your website /contact