# Security Scan last scan date

**URL:** <https://help.nextcloud.com/t/security-scan-last-scan-date/138253>\
**Category:** ℹ️ Support\
**Tags:** github\_issue\_exists, featurerequest\
**Created:** [April 28, 2022, 2:21pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253 "2022-04-28T14:21:11Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![hedgehog](https://help.nextcloud.com/user_avatar/help.nextcloud.com/hedgehog/32/26633_2.png) [@hedgehog](https://help.nextcloud.com/u/hedgehog)\
**Post date:** [April 28, 2022, 2:21pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/1 "2022-04-28T14:21:11Z")

</div>

Hi, I did a security scan and received a **Rating of A** for NC 21.0.1 - Major version still supported  
I did this for about 10 month or so and I always received a Grade A. So I thought, fine - no need to update. Until I read today when the last scan took place 😱

I suggest to emphasis more when the last scan to place, maybe even a warning symbol or so. People like me whould help that quite a bit.  
Thanks.

![grafik](https://help.nextcloud.com/uploads/default/original/3X/6/f/6f0d25fe94a061a1371425950493eb4bd3dc13a3.png)

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [April 28, 2022, 2:30pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/2 "2022-04-28T14:30:17Z")

</div>

Have you click “trigger re-scan” and reload the website?

Also you can only use `https://cloud.server.tld/status.php` to find out your Nextcloud version. I think if the installation is actual and the certificate is fine you do not need the scanning website.

Check certificate: [SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/)

Make sure that your certificate is updated regularly.  
Update also your operating system (security patches).

---

<div class="post-metadata">

**Author:** ![fernosan](https://help.nextcloud.com/user_avatar/help.nextcloud.com/fernosan/32/39224_2.png) [@fernosan](https://help.nextcloud.com/u/fernosan)\
**Post date:** [April 28, 2022, 4:24pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/3 "2022-04-28T16:24:22Z")

</div>

I think you missed the point. Of course, one should do this and that.

Hedgehog is making a case for an improvement in the design of that particular page.

Speaking of that, maybe there is no point in showing a rating made 6 months ago, so it should be grey or anything that signalizes in 0.1s that something is wrong instead of a big A+ scanned in 2019. Additionally, instead of only “scanned in YY-MM-DD”, a “scanned X months ago” would be nice too. And yes, the button for trigger re-scan should be flashier

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [April 28, 2022, 6:31pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/4 "2022-04-28T18:31:46Z")

</div>

> [@devnull](#):
>
> Check certificate: [SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/)

They check everytime again.

Does it make sense at all to show results that are older than 1 month? New minor release come nearly every month…

---

<div class="post-metadata">

**Author:** ![devnull](https://help.nextcloud.com/user_avatar/help.nextcloud.com/devnull/32/27793_2.png) [@devnull](https://help.nextcloud.com/u/devnull)\
**Post date:** [April 29, 2022, 5:51am UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/5 "2022-04-29T05:51:33Z")

</div>

> [@tflidd](#):
>
> Does it make sense at all to show results that are older than 1 month? New minor release come nearly every month…

The **SSL Server Test** tests the SSL certificate. The application Nextcloud is not tested. I think if someone is admin of a Nextcloud and has no idea at all about updates and security [https://scan.nextcloud.com](https://scan.nextcloud.com) is needed to find out that the used Nextcloud instance is supported.

[https://www.ssllabs.com/ssltest](https://www.ssllabs.com/ssltest) (checks only SSL)  
[https://scan.nextcloud.com](https://scan.nextcloud.com) (checks also Nextcloud version)  
[Maintenance and Release Schedule · nextcloud/server Wiki · GitHub](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule)

@tflidd  
Can you post a link with all supported Nextcloud versions and subversions?

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [April 29, 2022, 6:18am UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/6 "2022-04-29T06:18:42Z")

</div>

> [@devnull](#):
>
> Maintenance and Release Schedule · nextcloud/server Wiki · GitHub

That’s all the supported versions.

> [@devnull](#):
>
> The application Nextcloud is not tested

They just test the version, should all be much easier than checking the whole SSL setup.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [April 29, 2022, 10:05pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/7 "2022-04-29T22:05:29Z")

</div>

> [@tflidd](#):
>
> They just test the version, should all be much easier than checking the whole SSL setup.

they check little bit more like cookies etc but this definitely less sophisticated than SSL Labs check.

> [@devnull](#):
>
> Can you post a link with all supported Nextcloud versions and subversions?

it would be great this link appears next to the test result (perfectly scan result reacts to outdated versions and e.g. enforce re-scan of the instance)

> [@tflidd](#):
>
> Does it make sense at all to show results that are older than 1 month? New minor release come nearly every month…

1 or 2 months **may** be OK  
…but 3+ months is definitely _bad habit_… in my eyes if somebody visit a security scan page

- if the scan is older 72d (?)  
– re-trigger new scan and shown some intermediate page e.g. “waiting for results…”
- if the scan is newer 72d (?)  
– found vulnerable or outdated version → show some warning (without details)  
– highlight “re-scan” button so admins could easily verify upgrade’s

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [April 30, 2022, 1:26pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/8 "2022-04-30T13:26:55Z")

</div>

I created a bug report on github:

> <https://github.com/nextcloud/nextcloud.com/issues/1639>
>
> When users run a security scan of their setup (often after upgrades), they tend …to find rather old results from the last time their host was scanned. The small greyed out testing date can be easily missed and people start to doubt about their setups.
> 
> There was \[a discussion on the forum\](https://help.nextcloud.com/t/security-scan-last-scan-date/138253?u=tflidd), if you can't just remove old scan results and redo new scans? There isn't any sense in showing such old result (up to a year) or is there?

Please continue with your thoughts and suggestions there.

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 13, 2024, 2:10pm UTC](https://help.nextcloud.com/t/security-scan-last-scan-date/138253/9 "2024-12-13T14:10:51Z")

</div>


